Apache OpenOffice (AOO) Bugzilla – Issue 81728
[VI] [2.3] [Windows] Display bug in Installer screens
Last modified: 2013-08-07 15:26:05 UTC
My teammate reported this on 2007-09-01, but has only now had time to send in a screenshot. As you may be able to see from the attachment, we have three problems with the Windows install wizard (the problems appear on more than one page, but so far my teammate has only sent the screenshot for page 1): 1. The titlebar is not translated. (Should it be?) 2. "Welcome to the OpenOffice.org Install Wizard" is broken up: there are spaces between letters where there shouldn't be. It looks very messy. The string from the GSI file is: ___ instsetoo_native inc_openoffice\windows\msi_languages\Control.ulf 0 LngText OOO_CONTROL_27 0 vi {&TahomaBold10}Chào mừng bạn dùng Trợ lý Cài đặt cho [ProductName] ___ (We don't usually have problems with Tahoma.) The long space between the "ba" and the "n" shouldn't be there at all. The "n" is the third letter in that word. The long space between "Tro" and "ly" should only be a single character space. (These are two separate words.) The long space between "da" and "t" shouldn't be there at all. The "t" is the third letter in that word. This spacing error doesn't seem to affect all accented characters, or all non-Latin-1 characters. :S 3. The text below "Welcome to..." is not displayed correctly, although the characters are in the right position. Compound diacritics are missing, or are not displayed correctly. Some accents are also displayed way too high above the vowel and/or indistinctly. From the GSI file: ___ javainstaller2 src\Localization\setupstrings.ulf 0 LngText STRING_PROLOGUE2 0 en-US This Installation Wizard will install ${PRODUCT_FULLNAME} on your computer. 2002-02-02 02:02:02 javainstaller2 src\Localization\setupstrings.ulf 0 LngText STRING_PROLOGUE2 0 vi Trợ lý Cài đặt này sẽ cài đặt ${PRODUCT_FULLNAME} vào máy tính của bạn. 2002-02-02 02:02:02 javainstaller2 src\Localization\setupstrings.ulf 0 LngText STRING_PROLOGUE3 0 en-US To continue, click 'Next'. 2002-02-02 02:02:02 javainstaller2 src\Localization\setupstrings.ulf 0 LngText STRING_PROLOGUE3 0 vi Để tiếp tục, bấm nút « Kế ». ___ although I think these more recent strings have replaced the strings displayed in the screenshot which comes from OOG680m1. There are diacritic-display issues in all parts of the text in the screenshot. In detail: A. The "Welcome to OpenOffice.org..." bold text. (i) The y acute (U+00FD) in « Trợ lý » is only shown as a dot. B. The two sentences below the "Welcome..." bold text. (i) The e tilde (U+1EBD) in « sẽ »: the tilde is shown way too high above the vowel. (ii) The u hook above (U+1EE7) in « của » is also shown way too high above the vowel, and it is indistinct. (iii) The e circumflex hook above (U+1EC3) in « Để » does not show either accent correctly, but some strange squished shape. (iv) The e circumflex acute (U+1EBF) in « Tiếp tục » and « Kế » is missing the acute. (v) The a circumflex acute (U+1EA5) in « nhấn » is also missing the acute. C. The credits paragraph: (i) The a hook above (U+1EA3) in « Bản » is like the u hook in B (ii). (ii) The u hook above (U+1EE7) in « của » ditto. (iii) The o circumflex grave (U+1ED3) in « đồng » does not show the grave. (iv) The e circumflex hook above (U+1EC3) in « có thể » is as in B (iii). D. The buttons: (i) (iv) The e circumflex acute (U+1EBF) in « Kế » is missing the acute, as in B (iv). My teammate is current downloading OpenOffice.org 2.3rc3 Vietnamese, and hopes to get it downloaded, and have enough time to check this issue and send us more data, by some time tomorrow. (Note: Internet connections in Vietnam are extremely unreliable. Downloading a huge file like OpenOffice.org takes a long time, often several days. Downloading OOo builds repeatedly to test problems is a big ask of anyone in Vietnam.) Stephan Bergmann downloaded and installed OpenOffice.org 2.3rc3 Vietnamese on his Windows 2003 Server, and said he thought the install wizard looked OK. He didn't take a screenshot, so we can't be sure, since even the spacing errors might not be apparent to someone who can't read Vietnamese. I will ask if anyone else using Windows can give us further information on this problem.
Created attachment 48319 [details] Screenshot of the Windows Install Wizard
One issue per issue, PLEASE! We can't handle such issues in IZ properly! Yes, "... Install Wizard" is a dupe of other bug. If I'd handle Instllation project bugs, I'd take this bug as the bug described here and mark it as duplicate, sorry.
But how do I know if they are separate issues or not? They could all be part of the same problem. I don't understand how you decide that.
Created attachment 48321 [details] screenshot
I've attached a screenshot of OOGm5 made on my XP with standard system settings. It looks much better than your screenshot. I would suspect your font settings to be damaged.
Yes, that does look better. :) Apart from the titlebar not being translated, which Pavel says is already reported, the display is correct in the second screenshot. The odd thing is that my teammate had no problem installing our OpenOffice.org 2.1 builds. OOG680_m1 was the first build to have a display problem on his machine. He's not having any display problems using Vietnamese elsewhere on his machine.
Bad news. :( Another teammate has just installed our 2.3rc3 build on his WinXP machine. These two screenshots of "Preparing to Install OpenOffice.org": http://picasaweb.google.com/lh/viewPhoto? uname=cumeo89&aid=5110350534790164449&iid=5111936786077438754 http://picasaweb.google.com/lh/viewPhoto? uname=cumeo89&aid=5110350534790164449&iid=5111936790372406066 are a mess. The first one is the "Thankyou for downloading OpenOffice.org" page, the second is "Choose a directory". The text is a jumble of incorrect characters, and the buttons aren't translated (except one which has "Decompress" on it, I think). The user has Tahoma specifically chosen in his Windows prefs (Display Properties > Appearance (tab) > Advanced). And this is the same user who reported the Help fuzzy text (issue 81631): he has previously installed our 2.3 builds without encountering this sort of mess. The problem I originally entered in this issue, with some extra spaces and missing accents, looked unprofessional: this looks like a joke. Nobody will take us seriously if they encounter this. :(
Created attachment 48360 [details] nsis screenshot 1
Created attachment 48361 [details] nsis screenshot 2
I've attached two further screenshots. Please please compare these screenshot with your screenshots. We shohave to find out if this issue is an issue of broken fonts. I also use tahoma as system font. Untranslated buttons is a different problem (as pjanik wrote).
Thankyou for your screenshots. Yes, they show the same problem as User 2 reported. User 1 has just sent me four screenshots, from installing the latest langpack (2.3rc3) on Windows XP Home, and that brings the two problems together. Screenshots langpack_XP_1 and langpack_XP_2 show the hideous character-display mess on the two screenshots supplied by User 2, and by you. Screenshots langpack_XP_3 and langpack_XP_4 show the spacing and diacitic errors originally reported in this issue. These are screens 1-4 of the langpack install wizard. You get both problems in one wizard. Please bear in mind that both these users have previously installed our OpenOffice.org 2.1 builds without problems. They can view the OpenOffice.org 2.3 application and Help without problems. They can use Vietnamese elsewhere on their system, without problems. As to the untranslated buttons, Pavel said the untranslated titlebar was a separate issue. I didn't know the untranslated buttons were part of that issue (or a separate issue?). 2.3 is not looking good, for our language at least. :(
Created attachment 48362 [details] Screenshot of screen 1 of langpack install
Created attachment 48363 [details] Screenshot of screen 2 of langpack install
Created attachment 48364 [details] Screenshot of screen 3 of langpack install
Created attachment 48365 [details] Screenshot of screen 4 of langpack install
@ is: Can you do something in the 'installation' project? Or does this belong to l10n?
Hm, this task describes obviously two important problems, which seem to have different causes. Task 1: screenshot 1 and 2 belong to the nsis download installer based on strings in nsis.ulf. Task 2: screenshot 3 and 4 belong to the Windows Installer Installation Wizard based on strings in Control.ulf. Obviously after each letter containing a dot below the letter, a space is included behind the letter. (All strings are located in instsetoo_native, not in javainstaller2\src\Localization\setupstrings.ulf) Task 2 has the problem, that we cannot reproduce it. All pages look good on our systems. Which Windows Version do you use? Do you use Windows 98 ? Proposal to task 1: The strings commited to nsis.ulf have changed the encoding after OOo 2.1. As an example I add the string "SetupCaption" in nsis.ulf. Did you change the utf-8 encoding, when saving the strings? OOE680: instsetoo_native inc_openoffice\windows\msi_languages\Nsis.ulf 0 LngText SetupCaption 0 vi Chuẩn bá» cà i Äặt %PRODUCTNAME %PRODUCTVERSION 2002-02-02 02:02:02 OOG: instsetoo_native inc_openoffice\windows\msi_languages\Nsis.ulf 0 LngText SetupCaption 0 vi ChuâÌn biÌ£ cà i ÄÄÌ£t %PRODUCTNAME %PRODUCTVERSION 2002-02-02 02:02:02 Proposal to task 2: For the Windows Installer database I could not find changed strings. But I found a change in the encoding of the Windows Installer database. This was included in task i72905 (task of clytie). We should check, if this looks good again on your system, if the encoding is set from 1258 to 0 again. Unfortunately we cannot test this inhouse, because the wizard always looks good.
The problem has been reported by several users on Windows XP. We have not changed the UTF-8 encoding of any strings. All our work is done in UTF-8 by default, because our language requires UTF-8. For NSIS, in OpenOffice.org 2.1 a script was integrated into the code to convert our UTF-8 strings into the appropriate Windows codepage (since NSIS does not yet support Unicode). Please see bugs 73103 and 73192, to one of which you refer in your comments. When we encountered what looked like a very similar problem in OpenOffice.org 2.3 (I was not well enough to work on 2.2), I immediately enquired if that code was still active, and developers reported that it was. So I don't know what new encoding mess may have emerged. :( Interestingly, I saw a UTF-8 patch for NSIS recently: https://sourceforge.net/tracker/?func=detail&atid=373087&aid=1795257&group_id=22049 I don't know if it would be of any use, under the circumstances?
Setting the encoding from 0 to 1258, this influenced both, the Windows Installer database and the nsis download installer. In all language specific database tables of the Windows Installer database the encoding is written. With the value 0, the database table is encoded with 65001 (meaning utf-8). For the nsis installer this is relevant, because the conversion from ulf files to mlf files has changed. With encoding 0, the content of the ulf file is written directly into the mlf file. But with 1258 this is different, so that the content of nsis.mlf is different. Obviously the nsis download installer has problems with this encoding. I found the tasks i72905 and i73103 and ask myself, if the vietnamese installer has ever been working correctly, after this two bug were fixed.
is -> clytie: Did you use the script mentioned in i73192 for the last translations you made? I spoke with IHI and he told me, that he got new translations from you, which he wants to integrate this week. If I understand all this tasks correct (i72905, i73303, i73192) you have seen the nsis download installer and the windows installer without encoding problems, after all this tasks were integrated? Then there is no reason to use the nsis patch, you mentioned. I tested, if it is possible to use the strings from OpenOffice.org 2.1, but it seems, that they cannot be used anymore, because the installation wizard looks more garbled than before. So my hope is, that you did not use the script mentioned in i73192. is -> pj: Pavel, you have an idea for this encoding problems with Vietnamese. Script problems?
Ah, the script from task i73192 is no longer needed, since cws sb69 with task i73103 is integrated (happened in src680m206 for OOo 2.3). It seems, as if the fix in sb69 does not work correctly (or there are new encoding problems). After discussion with mh I shift this task to sb, who has to look for the correct encoding from cws sb69. Of course there is another very fast solution: We could add Vietnamese to the list of languages, that need to be installed with English installation wizard. Then we could win some time, to fix the encoding problems for OOo 2.4.
To answer your questions: I only used the script until the patch was integrated into the code. Using the script, then the patch, our 2.1x builds were fine on Windows. The "inc_openoffice\windows\msi_languages\Nsis.ulf" strings are displayed correctly (UTF-8) in our current GSI file, and have been all along. So I don't know what's gone wrong now. :( It would be a big step backwards for us, to have to install in English. I hope there is another way.
@IS: My dear former colleague, ;-) pj = Peter Junge pjanik = Pavel Janik Best regards Peter
is -> pjanik: This time trying the correct name :-) SB can take care on this task next Tuesday. Pavel, your script is no longer needed after integration of cws sb69. Have you already seen correct Vietnamese encoding after sb69 ? Or do you have another idea for this problem.
cc'ing ihi, because he will integrate new Vietnamese strings this week.
pj: sorry ;-) Ingo: I do not do changes to GSI file provided by Clytie. I just merge it.
@is: as discussed offline, back to you
Okay, now we analyzed all string and saw that all encodings are correct (encoding 1258). Furthermore I created an installation set based on OOE680 (OOo 2.1) and found that the nsis installer did not work in OOo 2.1, either. I suppose, there has never been a correct download installation set. I tried to fix this by inserting the correct locales into the nsis files, but this also failed. So I think, there is currently no way, to create a correct download installation set for Vietnamese. The problem with the dialogs from the Windows Installer is different. The database is fine, but there are font problems. We have different versions of the database with UTF-8 (OOE680) and encoding 1258 (OOG680). Both are fine. But with the encoding 1258 there seem to be font problems, that are shown in the bitmaps sent by clytie. In house we cannot reproduce this. Perhaps the UTF-8 version (which has other problems (Win 98?) ) has less font problems. IS -> MH: How do we want to proceed? We can add Vietnamese to the list of languages, that need an installer in English. Or we could think of avoiding the creation of the nsis download installer for Vietnamese. The Windows Installer part has much less problems.
Sorry I haven't been able to reply sooner. For 2.4, I think we had better default to the English installer. At least I can put up instructions on how to use that. I do not use Windows (OSX ;) ), so I'm sorry I can't actually test any of this myself. But my team-mates report that they _were_ able to install our 2.1 version: the installer did display correctly. I have no idea why you don't get that result now. We are going to lose a LOT of users if we don't solve this problem. The vast majority of our users are on (pirated) Windows, although we are encouraging them to move to Linux. Having our first successful release in 2.1 means new users are coming in very fast, and we can't afford to mess that up. Among other things, the Vietnamese government is about to move 20,000 machines to OpenOffice.org. They have to be able to install it. Incidentally, how can we have font problems, when the users reporting this problem are using the same fonts as elsewhere on their machine? Do we need to set a specific, non-Unicode font for the installer? ***And can we use the Unicode NSIS, which has been released?*** http://www.scratchpaper.com/
@is: a switch to UniCode NSIS might be promising.
We switched to Unicode NSIS a long time ago. is -> clytie: please verify, if this problems still occur.
reassigning
Reset assignee on issues not touched by assignee in more than 1000 days.