On 06/11/2006, at 4:42 AM, Erdal Ronahi wrote:
for the Kurdish translation we have also the impression that an older translation was used that for the build found atftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/680/ SRC680_m190/Build-1/
This is exactly what happened for Vietnamese. Pavel's build used the file from the current issue (70827), but the ooo-translation.services (cws localization17) used an older file.
Then Pavel said:
Our translation has not been reflected into the builds at this address. It _has_ been integrated into Pavel's builds at:... it has been integrated once you fixed the ISO code in your GSI file,right?
I don't understand "integrated". Once we submit our issue, is there another process that occurs before translations are built?
AFAIK, if you fetched our file from the address in our issue 70827 after I replaced it on the 2nd November, you have built the corrected vi file, where the language code is "vi", but I don't know yet, because I can't install any of your current builds.
Maho on the Mac OSX list has built using an old translation, the same one as cws localization17. Confusing.
The same will happen to upstream build.
Where is upstream in OOo, and what is not upstream?
Please access the file submitted with our issue 70827, using the link freshly, because we had to replace our original file on 2nd November, since the language-code used in the first file was incorrect.You can't change the history.
No, I don't want to do that. I hate time-travel plots. ;)But we had to replace the file we originally submitted with our issue, because the language-code was wrong. So we need people to use the newer file, available from the same link in our issue, but from the 2nd November.
Otherwise we will not have a translation for OOo 2.1. That would be better than using the very old and imperfect one that has somehow been integrated into cws localization17, but it would be the end of our attempt to revitalize the viOOo translation project. Nobody is willing to put in months of effort for no result.
I don't understand why the first builds on oootranslation.services have used an old translation, but the important thing is to fix this.Because the old translation was in the source tree and the new one wasmerged for different language because you have submitted it for differentlanguage.
I submitted the translation for "vi". That is our language code. "vi" was also used in the filename.
Or is the translation classified by the language code used _inside_ the file? If so, that would make sense in terms of this error, since our well-meaning Pootle admin got that code wrong while converting our translation to .sdf format.
One day, when we have enough resources, there probably _will_ be region-specific sub-languages for Vietnamese, since we have several distinct dialects. But not yet, certainly not while we have only a very few active translators, and only one or two of them consistently active.
Then Ivo said (in part):
- vi I will fetch new ( iso code fixed ) file and merge / new build
Thankyou!! :D Aiet rejoined:
So I guess I should no longer file issue for vi and other languages mentioned?vi definitely has an encoding issue with win installer as well as GUI.
Yes, all the packages built by Pavel had the encoding issue, and all the packages built at ooo-translation.services used an old translation. Neither of the problems were architecture-specific. They related to the translation being used.
I've noticed Pavel's builds for OOE680_m2 (Build 1) are up for Linux Intel. I devoutly hope they do integrate our current translation, as I've just announced them to the lists again. I think if one more poor user spends a whole day downloading one of those huge files over dialup and a sputtery phone line, and doesn't get the current translation, I may have a community PR problem beyond fixing.
I hope for the best. :)from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN
PGP.sig
Description: This is a digitally signed message part
