Apache OpenOffice (AOO) Bugzilla – Issue 13624
Incorrect proportional char spacing, with Kana compressed
Last modified: 2013-08-07 14:59:30 UTC
With Asian languages support, select the option: Tools->Options->Language Settings->Asian Layout->Character spacing Select "Compress punctuation and Japanese Kana" On Writer, in a line wordwrapped at the right edge, spacing between a punctuation and a Kana becomes incorrect, which results in overlapping characters. I observe this issue with 644m7 on Japanese Windows2000 SP3 (5.00.2195) with the following six Japanese proportional fonts. I also observe this issue on Japanese WindowsXP SP1. 1."MS PMincho " Font Data: MSMincho & MS PMincho (TrueType) File Size: 8923KB Version 2.31 (C)1997 Copytight Ricoh Company.LTD. 2."MS PGothic " Font Data: MSGothic & MS PGothic & MS UI Gothic (TrueType) File Size: 8079KB Version 2.30 (C)1997 Copytight Ricoh Company.LTD. 3."HGPGothic M" Font Data: HGGothic M & HGPGothic M & HGSGothic M (TrueType) File Size: 2804KB Version 2.02 (C)1997 Copytight Ricoh Company.LTD. 4."HGP Soei Kaku Gothic UB" Font Data: HGP Soei Kaku Gothic UB & HGP Soei Kaku Gothic UB & HGP Soei Kaku Gothic UB (TrueType) File Size: 1913KB Version 2.01 (C)1997 Copytight Ricoh Company.LTD. 5."HGP Soei Kaku Pop" Font Data: HGP Soei Kaku Pop & HGP Soei Kaku Pop & HGP Soei Kaku Pop (TrueType) File Size: 2105KB Version 2.02 (C)1997 Copytight Ricoh Company.LTD. 6."HG P Gyosho" Font Data: HG Gyosho & HGP Gyosho & HGS Gyosho (TrueType) File Size: 4481KB Version 2.03 (C)1997 Copytight Ricoh Company.LTD. Reportedly this issue is also observed with 1.1Beta on Japanese Windows98SE (4.10.222A), with the following additional two Japanese proportional fonts. ex1."HG P Textbook" Font Data: HG Textbook & HGP Textbook & HGS Textbook (TrueType) File Size: 4649KB Version 2.30 (C)1997 Copytight Ricoh Company.LTD. ex2."Andale Sans UI" Font Data: Andale Sans UI (TrueType) File Size: 18020KB Version 1.01 Digitized data copytight(C)1993-2001 Agfa Monotype Corporation I attach an archive which includes: AsianProportionalSpacing.sxw: SXW KanaCompression.png: Screenshot with Kana compression enabled
Created attachment 5766 [details] Archive of SXW and screenshot
DL->SBA: Would you please takeover?
This issue is reproduced also with 644m11 (released on Apr 24.)
Renew version field
HDU->FME: looks like the problem we recently discussed. Don't apply kana compression for proportional fonts.
FME->WHM: I disabled kana compression for proportional fonts for the fix of #108498#. This should be effective from SRX644m12 on. Is this what you mean?
Hallo, Frank, Kana-compression can be useful for proportional fonts. Must we really give up Kana-compression for proportional fonts? For this particular issue, the screenshot indicates (to me) that each letter immediately following a punctuation is placed at a wrong position. Take a look at new screenshots (SXW will be also attached). In CompressKana.png: 1) As the line is compressed (I inserted spaces after the left-most digit), each letter immediately following a punctuation moves to the right excessively. 2) From the 7th line to the 8th line, four characters were wordwrapped at a time. Expected behavior would be characters should move to the next line one-by-one. 3) I placed 'a' immediately after a punctuation at the end of each line. The spacing between the punctuation and 'a' is too wide. CompressPunctuationOnly.png shows good spacing. So, my impression is, there seems to be some algorithmic flaw about the punctuation-character-spacing and word-wrap optimization when Kana-compression is enabled.
Created attachment 5988 [details] new SXW and screenshots
Will OO.o1.1 do Kana-compression for non-proportional fonts, while proportional fonts are properly spaced, when 'Compress punctuation and Japanese Kana' is selected? Then, I think that will be a practical resolution for OO.o1.1. By the time OO.o2.0 feature fix, other Japanese users may express their expectations on Kana-compression for proportional fonts, I hope. Thanks,
FME->FT: Kana compression for proportional fonts? Please decide.
Hi Frank, AFAICS this issue is not a missing feature but rather a problem in the current implementation. I therefore consider this a bug thats mentioned workaround is acceptable for OO 1.1 but should be fixed in 2.0. Please let me know on any bigger problems to solve this issue.
.
SBA: According to the OpenOffice.org roadmap (see http://tools.openoffice.org/releases) this issue was retargeted to "OOo Later".
I can not reproduce on Vista+OpenOffice.org 3.2RC3.