Apache OpenOffice (AOO) Bugzilla – Issue 84818
[VI] [2.4] GUI and Help translation
Last modified: 2013-08-07 15:01:53 UTC
Sorry I couldn't get this in sooner. Please identify this file as the official Vietnamese submission for OpenOffice.org 2.4, and please download it again before integrating the last fixes in the CWS. Hopefully, we will be able to update it again before that date, but meanwhile, this is our current translation. (Note: we always use the same URL, so you can grab our current translation from here anyway. If we change this URL, we will notify you.) Clytie Siddall Vietnamese Free-Software Translation Team
Sorry, I originally assigned this to ihi, because that was what we have done before. I can't change the assignee, it seems, so I have CC'd this issue to you. Please tell me if there is anything else I need to do. Clytie
reassigning to vg and setting target. Vladimir, please import. Thx
Created attachment 50527 [details] gsicheck errors
fixed in the CWS localisation27
AFAIK, I can't run gsicheck on Mac OSX, but I do run the PO checks from the Translate Toolkit. Thankyou for running gsicheck for me. How do I interpret the results? I can't see any statements about what kind of error is detected. Not that the GSI format makes much sense at the best of times, but I'd like to know what needs fixing. ;)
In first two strings opening 'variable' tag is missing. third - in cling ahelp tag \> is missing. fourth - cannot see closing ahelp-tag next 6 strings - you use unkown <meta> tag 11th - 2 closing ahelp-tags 12th - closing ahelp-tag is missing 13th - opening variable-tag is missing 14th - closing ahelp-tag is missing last - you added link that doesn't exist in original, please format link another way (use e.g. only quotes) And please compare source strings too, although all these errors were obvious there can be something more, eg. bogus hid or visibility option, at least last one often changes.
I dont know what I was going to write before phone rang, but please read: ... third - after ahelp tag \> is missing... :)
Thanks for the details. In first two strings opening 'variable' tag is missing. I don't know why the closing tag is there: there is no <variable> tag in the source text. :S third - in cling ahelp tag \> is missing. Fixed. fourth - cannot see closing ahelp-tag Fixed. next 6 strings - you use unkown <meta> tag I was translating "meta" but wanted to quote it as well. I tried escaping the angle brackets, but perhaps it's better not to use them at all. I've replaced them with guillemets. 11th - 2 closing ahelp-tags Fixed. 12th - closing ahelp-tag is missing Fixed. 13th - opening variable-tag is missing The final variable tag is spurious, probably copied from a similar string. (removed) 14th - closing ahelp-tag is missing Fixed. last - you added link that doesn't exist in original, please format link another way (use e.g. only quotes) I tried to copy the style for links in the Help, but evidently I got it wrong. I've just quoted it instead, then. And please compare source strings too, although all these errors were obvious there can be something more, eg. bogus hid or visibility option, at least last one often changes. I do check them: I'm surprised these occurred. Thanks for the information. I'll have just uploaded the fixed file. Please integrate it if there is still time.
Created attachment 50535 [details] gsicheck errors - please get gsicheck to run, otherwize you'll always get errors
Clytie: please remove item-tags around Shift, these dont exist any more in original.
I've been searching through the GSI file (which will take a while, item by item), and the first string I found where I'd applied formatting to Shift which didn't exist in the original string was: 67 0 en-US \<ahelp hid=\".uno:Pie\"\>.... To draw a circle pie, hold down Shift while you drag.\</ahelp\> 2002-02-02 02:02:02 helpcontent2 source\text\shared\02\01140000.xhp 0 help par_id3156383 67 0 vi \<ahelp hid=\".uno:Pie\"\>V... Để vẽ bánh tròn, ấn giữ phím \<item type=\"keycode\"\>Shift\</item\> trong khi kéo.\</ahelp\> 2002-02-02 02:02:02 The Help strings have very inconsistent formatting, so I have tried, for example, to put <emph> tags around menu commands which are still unformatted in the original string, and <keycode> tags around keyboard key names. I've done this so the formatting will appear consistent in the translation, even if it doesn't in the Englis text. Should I not do that?
Clytie, gsicheck checks that the count of similar tags were equal in both lines. So when you add tags, it results an error.
An by the way: looks like Pavel and Shaun explained you about using gsicheck in Mac environment? http://permalink.gmane.org/gmane.comp.openoffice.devel.porting.mac/3603
Did we solve that one? That's good news. I didn't remember, sorry. I have a disease that is eating my mind as well as my body, so until my team can find someone with enough time to donate, I'm it. (I hate admitting to being this ill, but it's not fair on people for me to pretend I can do things, when I can't anymore. I can't even add up single-digit numbers anymore, and I lecture in mathematics, or I would, if I were not ill.) I can translate strings, one at a time, and try to follow up bugs and mailing list messages, but anything more than that is very difficult or impossible for me. A gsicheck I can't just download and run isn't viable, which is probably why I didn;t get any further with that. Bummer. If they have got it into the build now, it might be possible for me. I'll try to work it out. Do I need to do any more to the file I submitted, or are we OK for now? I'm getting muddled, sorry. Clytie
@clytie: please do not revive this issue, fix erroneous strings in next update...
gsicheck is now available as download for MAC intel on http://ooo.services.openoffice.org/gsicheck/
Yay! I saw the announcement on dev@l10n and downloaded it. Now I have gsicheck! :) I went through our GSI file very carefully and fixed every error it picked. I have now uploaded our fully- checked and (according to gsicheck) perfect file. ;) It's a great relief to have that working. pofilter is good, but I think it does miss a few things specific to the GSI file.