> Japanese patch. Suppose a Japanese sentence
> includes English name, for example Donald Knuth. Japanese
> sentences in general don't includes white space. If a white space
> is included in a sentence, LyX recoginizes a sentence as two very
> long words and try to make it right justfied. As the results, the line is
> broken at the white spece. This makes a document difficult to read.
I should have realized this. Obviously I had misunderstood the effect
of par->SetFont(pos, current_font) Masahiko Kawakami put. We had better
compare what Yu-chung Wang is doing to his Taiwanization patch.
Now here is something for 1.1
Asger, is the proposal of Wed, 18 Mar 1998 still valid?
I still think ElementType class you proposed is the best for addressing
this problem. By letting ElementType getNextElementType() to return
"Word" if the cursor is on <CJK> or other east Asian character, and
if the next element is not a certain punctuation, we will be able to
have a working line breaking algorithm. UnicodeData will be of
use here.
> There are also some problems. When these problems are
> solved. I will put lyx files on my web page.
Agreed. I'm looking forward to it. Thanks in advance.
> But it is difficult to choose materials. At least, I'm using LyX for writing
> papers in English. So hyphenation is important, for example. I think almost
> LyX users in Japan use it for writing English documents.
... I personally keep lyx, lyx-jp and lyx-devel all in my disk and,
in fact, use lyx (unpatched) exclusively for writing English.
Probably you are right. I was careless about the choice. However,
it is necessary to sort out what to be in.
Regards,
SMiyata
