JLearner is a Java-based Japanese character and vocabulary learning tool. It is mainly in German, and comes with vocabulary packages for the ikkyuu level 1 (highest "Japanese as a foreign language test"). It was written for university students who have be firm with all 2000 jouyou Kanji.
Re: What I could use!
> I don't believe you will get anywhere by
> waiting for a "group of developers" to
> do it... If you want to see your ideas
> carried out, just get going! If it
Well, I said "we", didn't I?...I'm not waiting
for anybody else. I want to start, yes, but
if I do it alone then the result will probably
be a poorly designed, inflexible and therefore
unsupported piece of code. So I would like
to see more enthusiam to design this central
thing rather than discussing between UCS-4 or
UTF-8. What I have learned: People hang on
their codepages!!!!!!!!! So let's forget this encoding
discussion, I have some basic ideas to think about:
1. If the parser buffers would be system-wide static, then it
would hurt the multi-user ability. because of that,
input buffers must be available for each user (and
probably for each open input channel, quite offen
I have an X session with multible terminals and I
would get crazy when there is already input content
when switching from one to another. On the other
hand, we could also clear the buffers when switching).
2. There must be several layers to control input:
a - keyboard code - physically raised code
b - key mapping ("virtual" keys can be emulated)
c - globally unique encoding (whatever UTF-8/UCS-4)
d - input buffer
e - pre-parsed (displayable) content, where following context may require changes
f - output (displayable) context, which should be taken over
by the terminal or GUI
That is my first idea, maybe it's quite bullshit.
Please let me know if you have other ideas.
Re: It's not that bad, actually
> b) Please tell me a realistical example
> where replacing a single character is of
> any use, without conflicting with i18n
strtolower, strtoupper, and of course
parsing stuff...but I got your point.
Yes, it's rather seldom. And you're right,
substrings cause problems anyway.
> I don't think rewriting all apps to use
> a different char size would lead to less
> bugs. And anyway, I think some of the
In case the compiler would return a different
char size, there would be even no need to rewrite