Issue 81631 - [VI] 2.3 Help display fuzzy, missing letters
Summary: [VI] 2.3 Help display fuzzy, missing letters
Status: CONFIRMED
Alias: None
Product: Internationalization
Classification: Code
Component: helpcontent (show other issues)
Version: current
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL: ftp://ftp.linux.cz/pub/localization/O...
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-17 06:50 UTC by clytie
Modified: 2017-05-20 11:31 UTC (History)
1 user (show)

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


Attachments
Screenshot of 2.3 Help on Windows 2003 (2.83 MB, image/bmp)
2007-09-17 10:16 UTC, clytie
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description clytie 2007-09-17 06:50:29 UTC
On Windows XP, using our OpenOffice.org 2.3 Vietnamese build (see URL above):

User 1 reported unreadable text, with fuzzy and/or missing characters, in the "Welcome to 
OpenOffice.org Help" section. User 2 also reported it in other parts of the Help, supplying this 
screenshot:

http://picasaweb.google.com/lh/viewPhoto?
uname=cumeo89&aid=5110350534790164449&iid=5110350624984477698

the first red circle indicates this bug. (The second red circle indicates bug 81602, which was due to 
the default CSS font for Help Western languages not covering the Vietnamese glyph range: fixed by 
changing the font in the CSS file.)

User 2 then tried copying that fuzzy section into an application in which he can edit Vietnamese 
correctly. Please see this screenshot:

http://picasaweb.google.com/lh/viewPhoto?
uname=cumeo89&aid=5110350534790164449&iid=5110701399258509346

The first comment line says "all of these in the Bitstream font" (which is the default Help CSS font for 
this build).
The second comment line says "this line input manually": below it is the unreadable text from the first 
screenshot, input manually (we know what it should be, from the GSI file). It is readable.
The third comment line says "this line copied from the Help": below it is the unreadable text from the 
first screenshot, copied and pasted directly from the Help.

As you can see, in screenshot 2, the text copied from the Help in screenshot 1 remains unreadable.

One of my team-mates speculates that the characters in the Help might be decomposed Unicode. I 
devoutly hope not. Decomposed Unicode causes hideous problems in input and display of languages 
with combined diacritics. (I remember one bug due to decomposed Unicode, which took me six 
months to solve, where the accent would become separated from the parent vowel, and follow the 
cursor around the page!)

Please confirm if display of the Help is decomposed or precomposed Unicode.

I hope we can solve this problem. It makes our initial Help translation look messy and unprofessional: 
most of our users currently use Windows. (We do not know, as yet, whether this problem affects all 
Windows versions, or only Windows XP.)
Comment 1 pavel 2007-09-17 06:56:37 UTC
.
Comment 2 clytie 2007-09-17 10:13:02 UTC
I'm adding a screenshot (help.bmp) from Stephan Bergmann, showing the same Help paras in 
OpenOffice.org 2.3 Vietnamese, on "Microsoft Windows Server 2003 R2, Enterprise Edition, Service Pack 
2".

Note that the phrase concerned is less fuzzy, but the two words « sơ yếu » (resumé) overlap. So this bug 
does occur in more than one version of Windows.
Comment 3 clytie 2007-09-17 10:16:07 UTC
Created attachment 48273 [details]
Screenshot of 2.3 Help on Windows 2003
Comment 4 frank.thomas.peters 2008-06-05 09:47:57 UTC
Sending to Ivo. I don't know about the charset of the localized help files, so I
don't know what to do about this.

Clythie:  next time, please don't use bmp as screenshot format, if possible use
png, gif, or jpg. Thanks.
Comment 5 clytie 2008-06-05 10:12:05 UTC
I'll mention the format issue on our l10n list, but I just checked myself, and the screenshot program on 
my Mac (Grab) creates TIFF images. Are they OK?

Although it's not complicated to convert images, it does mean opening another program, opening the 
image in it, and doing the conversion. People tend to send in bug reports when they have a few spare 
minutes. I'm not sure that period of time will always be enough to convert images.
Comment 6 ivo.hinkelmann 2008-06-09 15:50:12 UTC
herbert , do you have an idea whats wrong here?
Comment 7 Marcus 2017-05-20 11:31:13 UTC
Reset assigne to the default "issues@openoffice.apache.org".