Apache OpenOffice (AOO) Bugzilla – Issue 92866
Vietnamese HC2 100% translated but displays English
Last modified: 2013-08-07 15:02:13 UTC
http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/localisation30/ Vietnamese HC2 is marked as 100% translated in pootle[1] but when we load the help, we see so many untranslated strings[2]. Why? [1] http://pootle.sunvirtuallab.com:32300/vi/index.html [2] http://www.flickr.com/photos/8480574@N08/2762930076/
Related issue: http://www.openoffice.org/issues/show_bug.cgi?id=92834
Judging by the photo, it looks like the helpcontent2/source/text/shared files did overwrite the vi translated files, while the helpcontent2/source/text/swriter files are correct.
Hi vuhung, can you please check if the official OOo 3.0 builds for VI also have this problem?
ihi, I've just checked with 3.0.0 vi win32 on XP SP2, and yes, it still reproduces. Here is a screenshot. http://farm4.static.flickr.com/3272/3007499141_fa66a94b06_o.jpg
FYI [vuhung@aoclife helpcontent2]$ ~/usr/src/linux/gsicheck_1.9.0/gsicheck source/text/shared/localize.sdf Error: Line format, Line 1: Format of line is unknown. Ignoring! Error: Line format, Line 2: Format of line is unknown. Ignoring! Error: Line format, Line 3: Format of line is unknown. Ignoring! Error: Line format, Line 4: Format of line is unknown. Ignoring! Error: Line format, Line 5: Format of line is unknown. Ignoring! Error: Line format, Line 6: Format of line is unknown. Ignoring! Error: Line format, Line 7: Format of line is unknown. Ignoring! Error: Line format, Line 8: Format of line is unknown. Ignoring! Error: Line format, Line 9: Format of line is unknown. Ignoring! Error: Line format, Line 10: Format of line is unknown. Ignoring! Error: Line format, Line 11: Format of line is unknown. Ignoring! Error: Line format, Line 12: Format of line is unknown. Ignoring! Error: Line format, Line 13: Format of line is unknown. Ignoring! Error: Line format, Line 14: Format of line is unknown. Ignoring! Error: Line format, Line 15: Format of line is unknown. Ignoring! Error: Line format, Line 16: Format of line is unknown. Ignoring! Error: Line format, Line 17: Format of line is unknown. Ignoring! Error: Line format, Line 18: Format of line is unknown. Ignoring! Error: Line format, Line 19: Format of line is unknown. Ignoring! Error: Line format, Line 20: Format of line is unknown. Ignoring! Error: Line format, Line 21: Format of line is unknown. Ignoring! Error: Line format, Line 22: Format of line is unknown. Ignoring! Error: Line format, Line 23: Format of line is unknown. Ignoring! Error: Line format, Line 24: Format of line is unknown. Ignoring! Error: Line format, Line 25: Format of line is unknown. Ignoring! Error: Line format, Line 26: Format of line is unknown. Ignoring! Error: Line format, Line 27: Format of line is unknown. Ignoring! Error: Line format, Line 28: Format of line is unknown. Ignoring! Error: Line format, Line 29: Format of line is unknown. Ignoring! Error: Line format, Line 30: Format of line is unknown. Ignoring! Error: Line format, Line 31: Format of line is unknown. Ignoring! Error: Line format, Line 32: Format of line is unknown. Ignoring! Error: Line format, Line 33: Format of line is unknown. Ignoring! Error: Line format, Line 34: Format of line is unknown. Ignoring! Error: Line format, Line 35: Format of line is unknown. Ignoring! Error: Line format, Line 36: Format of line is unknown. Ignoring! Error: Line format, Line 37: Format of line is unknown. Ignoring! Error: Line format, Line 38: Format of line is unknown. Ignoring! Error: Line format, Line 39: Format of line is unknown. Ignoring! Error: File format, Line 100: No source language entry defined! Error: File format, Line 160: No source language entry defined! Error: File format, Line 220: No source language entry defined! Error: File format, Line 280: No source language entry defined! Error: File format, Line 342: No source language entry defined! Error: File format, Line 402: No source language entry defined! Error: File format, Line 464: No source language entry defined! Error: File format, Line 524: No source language entry defined! Error: File format, Line 586: No source language entry defined! Error: File format, Line 646: No source language entry defined! Error: File format, Line 708: No source language entry defined! Error: File format, Line 768: No source language entry defined! Error: File format, Line 829: No source language entry defined! Error: File format, Line 888: No source language entry defined! Error: File format, Line 947: No source language entry defined!
I've search the string "colors are treated as" in all the files under helpcontent2 and found it in "source/text/sbasic/shared/00000002.xhp" and "source/text/sbasic/shared/localize.sdf". However, I couldn't file this string in pootle( see below) so I think there is something wrong. Question: Is that the .po files in pootle.sunvirtuallab.com are used in OOo_3.0.0_src_l10n.tar.bz2 ? Where is the logic( the code) that generates: "source/text/sbasic/shared/localize.sdf" .po files in pootle: http://pootle.sunvirtuallab.com/vi/helpcontent2/ http://pootle.sunvirtuallab.com/vi/helpcontent2/helpcontent2-vi.zip Some text grep()'ed from helpcontent2: "source/text/sbasic/shared/00000002.xhp" line 56 of 80 --70%-- col 31 <section id="colors"> <paragraph role="heading" id="hd_id3155854" xml-lang="en-US" level="2" l10n="U" oldref="29">Colors</paragraph> <paragraph role="paragraph" id="par_id3145366" xml-lang="en-US" l10n="U" oldref="30">In $[officename] Basic, colors are treated as long integer value. The return value of color queries is also always a long integer value. When defining properties, colors can be specified using their RGB code that is converted to a long integer value using the <link href="text/sbasic/shared/03010305.xhp" name="RGB function">RGB function</link>.</paragraph> </section> ------------------------ "source/text/sbasic/shared/localize.sdf" line 474 of 301550 --0%-- col 1ink href=\"text/sbasic/shared/0301030 helpcontent2 source\text\sbasic\shared\00000002.xhp 0 help par_id3145366 30 0 vi In $[officename] Basic, colors are treated as long integer value. The return value of color queries is also always a long integer value. When defining properties, colors can be specified using their RGB code that is converted to a long integer value using the \<link href=\"text/sbasic/shared/03010305.xhp\" name=\"RGB function\"\>RGB function\</link\>. 2002-02-02 02:02:02 helpcontent2 source\text\sbasic\shared\00000002.xhp 0 help par_id3145366 30 0 zh-CN 在 $[officename] Basic 中，可将颜色作为长整数值处理。颜色查询的返回值通常也是长整数值。定义属性时，>可 使用 RGB 代码指定颜色，该代码使用 \<link href=\"text/sbasic/shared/03010305.xhp\" name=\"RGB function\"\>RGB function\</link\> 转换为长整数。 2002-02-02 02:02:02 helpcontent2 source\text\sbasic\shared\00000002.xhp 0 help par_id3145366 30 0 zh-TW 在 $[officename] Basic 中，顏色被視為長型整數值。顏色查詢的傳回值通常也是長型整數值。在定義屬性時，>可 以使用 RGB 代碼來指定顏色，該代碼透過 \<link href=\"text/sbasic/shared/03010305.xhp\" name=\"RGB 函數\"\>RGB 函>數\</link\>轉 換成長型整數值。 2002-02-02 02:02:02
Hi .... I found in the source: helpcontent2 source\text\sbasic\shared\00000002.xhp 0 help par_id3154731 6 0 vi A twip is a screen-independent unit which is used to define the uniform position and size of so the VI string is in English sadly the EIS database is down at the moment , I will check if this string was delivered in the wrong state for the last localization cws ... Can you please check if this string is also broken in pootle?
-> change component to l10n
-> set subcomponent to helpcontent
petr, can you please check those strings in the pootle database?
ihi, I've grep the string "The return value of color"( which is in locale.sdf) on all the files in pootle ( pootle.sunvirtuallab.com ) but there was no hit. My guess is that: Are the po files in pootle are correct?
I don't have access to the pootle server , Petr might help here ...
Here are the files in pootle you need. I downloaded them 10 munites ago. http://aoclife.ddo.jp/~vuhung/foss/ooo/tmp/openoffice_org-vi.zip http://aoclife.ddo.jp/~vuhung/foss/ooo/tmp/helpcontent2-vi.zip
Aijin, can you please have a look? Thanks, Petr
Hi vuhung and all, I've searched the string "The return value of color" in Pootle and could see the string existed and localized. Please refer to the attached screenshot I also checked the sdf which had been delivered from Pootle, and still could see the localized string. http://sunvirtuallab.com:32305/sdf/20080807/vi-080807.sdf In Web ling tool, the string is localized as well, therefore I think the string is correctly imported to DB.
Created attachment 57857 [details] Pootle search result
Hi Aiji Kim, Why it is 080807? Is that too old? http://sunvirtuallab.com:32305/sdf/20080807/vi-080807.sdf # Btw, 3 days ago, I've search the same string "The return value of color" and nothing was found. Now we know that the localize.sdf file in pootle and OOo 3.0.0 source are different: ( the one in pootle has the string "The return value of color" translated while OOo 3.0.0 does not). Anyone can help?
Hi vuhung, > Why it is 080807? Is that too old? It was the last delivery for 3.0 from Pootle (Aug 7th,2008). You can see the 3.0 schedule here: http://wiki.services.openoffice.org/wiki/Translation_for_3.0#Translation_Schedule > Now we know that the localize.sdf file in pootle and OOo 3.0.0 source are different Yes, I confirmed that the string is correctly localized not only in Pootle, but also in DB. Might be some error during build? ihi, Can you please take a look what did go wrong? Thanks, Aijin
hmmm ... this string haven't changed since a long time in the code: 1.8 (rt 24-Jun-05): helpcontent2 source\text\sbasic\shared\00000002.xhp 0 hcd OOOelp par_id3145366 30 0 vi In $[officename] Basic, colors are treated as long integer value. The return value of color queries is also always a long integer value. When defining properties, colors can be specified using their RGB code that is converted to a long integer value using the \<link href=\"text/sbasic/shared/03010305.xhp\" name=\"RGB function\"\>RGB function\</link\>. 2002-02-02 02:02:02 I test merged this string into the code , there seems not to be a tooling issue ... I can not say why this string don't went into the code. I can only propose that we merge vi again complete during the next l10n cws
Re:ihi, The final 3.0.0 is already out so we can't do anything with it. When is the next l10n cws? Please let me know so I can test.
we should fix this for the OOo 3.1
ihi: but why not 3.0.1?
the OOo 3.0.1 is planed only with minor changes without L10N related fixes
ping ?!
is this problem still present in the 3.1 rc ?
set target to 3.2
Thanks for the reminder. This bug is fixed in 3.1.0rc1! Thanks for your hard work.
When this issue is fixed, I set it to that state. Please check again in OOo 3.2. If the problem still occurs, please set this issue to target 3.3 and fix it. Thx