Issue 11503 - Japanese layout rule (not at end of line) does not work
Summary: Japanese layout rule (not at end of line) does not work
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 643C
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: h.ilter
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-02-15 03:58 UTC by Unknown
Modified: 2003-09-08 16:56 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Screenshot describing the issue (28.95 KB, image/png)
2003-02-15 03:59 UTC, Unknown
no flags Details
sxw file used for the screenshot (5.59 KB, application/octet-stream)
2003-02-15 04:00 UTC, Unknown
no flags Details
expected result (27.67 KB, image/png)
2003-02-15 10:41 UTC, bluedwarf
no flags Details
a helpful image for I-beam problem as I reported above (112.12 KB, image/png)
2003-02-17 09:28 UTC, bluedwarf
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-02-15 03:58:35 UTC
Dear developers,

I appreciate OpenOffice.org, the valuable office suite.

Thanks to your efforts on issue #4587, the layout of Japanese general 
characters was fixed by the 643C version. A lot of Japanese users definitely
appreciate this improvement. However, we still suffer from a serious layout
problem regarding a special layout rule --- seemingly this was out of issue
#4587 scope.

Certain characters are not allowed to appear at the end of line. Though the
option dialog of OpenOffice.org appears to support this rule (Tools->Options
->Language Settings->Asian Layout->Not at end of line), the software
unexpectedly puts the specified character at the end of line.
This rule needs to be correctly implemented for the word processor to be
useful, in my opinion. The rule is highly respected in the Japanese typeset
culture.

I will attach a screenshot and the sxw file for your reference. If you need
further information, please let me know.

One of the members at ja.openoffice.org, Nakamoto-san, contacted the
developer team (Frank and Karl) and obtained some source-code information
regarding this issue. He has been attacking this matter courageously, but the
learning curve seems too steep for us to fix it quickly. Considering the 
priority of this issue and the time left before the 1.1 beta release, I submit
this issue here by agreement with Nakamoto-san.

I, and surely most Japanese users, wish this issue be handled as a defect and
would appreciate a timely fix.

Sincerely
Comment 1 Unknown 2003-02-15 03:59:41 UTC
Created attachment 4746 [details]
Screenshot describing the issue
Comment 2 Unknown 2003-02-15 04:00:44 UTC
Created attachment 4747 [details]
sxw file used for the screenshot
Comment 3 bluedwarf 2003-02-15 10:40:25 UTC
Hi,

Thank you for your report, whm.
Yes, this is the serious problem for Japanese.
All of Japanese native-lang project(cf. http://ja.openoffice.org)
members wish this problem fixed  in 1.1 Beta.

In addtion, the ideal result is not just what whm attatched. We expect
that each word space in previous line must be expand to the left of
the page.
It's hard to explain this situation so I will attach an image edited
by the GIMP which shows the expected result.

Strangely enough, "not at start of line" is working. This means
there's some fault in source code which deal with loading forbidden
characters, I guess.
Developers, first of all, please confirm the forbidden characters are
recognized. (I don't know how.)

Best Regards,
Comment 4 bluedwarf 2003-02-15 10:41:49 UTC
Created attachment 4752 [details]
expected result
Comment 5 Unknown 2003-02-15 13:21:06 UTC
Hi, Nakamoto-san,

Thanks for your comment.

I just noticed the latest developer release 644m1
appears to address this issue.
My request seems, I hope, already obsolete.

Regarding the right margin alighment, I believe the
appearance should reflect whether the paragraph setting
(Format-> Paragraph->Alighment->Options) is "Left/Top"
(this is the case when my screen shot was taken) or
"Justified" (this is the case where your expectation
would result.)
The appearance also should reflect the "hanging punctuation" setting,
which is found at Format->
Paragraph->Asian Typography.

To my knowledge, 644m1 works fine with respect
to these options.
Could you double-check its behavior?

Best Regards,
Comment 6 bluedwarf 2003-02-17 09:26:41 UTC
This issue seemes to be fixed  in 644_m1(SRX644).
(cf. 1.7 of
http://www.openoffice.org/source/browse/l10n/i18npool/source/breakiterator/breakiterator_cjk.cxx)

Thank you very much, Karl and whm.

But we have another problem, when I enter a forbidden start of line
character at a start of line (of course, the forbidden character was
put in the end of previous line), the I-beam pointer was located just
behind the previous character, not behind the forbidden start of line
character. This performance is strange.

Reproduce:You enter characters to the limit of the right in a page,
next enter punctuation mark which is forbidden to be a start of line.
The punctuation mark was forbidden to locate in the star of line so
that it was put in the end of previous line. After the forbidden
character was put in the end of line, the I-beam pointer is located in
front of the punctuation mark, never come behind it. In this
situation, or the I-beam pointer was in front of it, please push "Back
Space" key. Although the I-beam didn't point to the punctuation mark,
it will be deleted.
But we can avoid this problem by entering following characters behind
the punctuation mark.

This problem was confirmed by OO643C and 644_m1 developer release. I
will attach a helpful image of this issue.
It might be caused by the fault of information about pointer after
word wrapping process.

Karl, Frank and others, do you have any idea?
Comment 7 bluedwarf 2003-02-17 09:28:37 UTC
Created attachment 4761 [details]
a helpful image for I-beam problem as I reported above
Comment 8 Unknown 2003-02-18 04:17:03 UTC
From the perspective of issue management,
I instituted a separete item #11573 for the different
issue Nakamoto-san found and reported here.
Comment 9 prgmgr 2003-06-26 17:30:24 UTC
Has 1.1 Beta 2 address the first problem in this issue?

One problem per issue please.
Comment 10 Unknown 2003-06-26 17:43:39 UTC
Hi, P M,
Thanks for your follow-up.
644m1 and later versions don't involve the first issue.
I label this issue as 'fixed' now.

The second issue is to be handled as issue #11573.
Comment 11 prgmgr 2003-06-28 13:18:35 UTC
.