Hi Clytie,
Ah. I see. A difference file of a different type. ;)
Sorry, I think you call it .gsi file. So please use the same format you
have used for deliverying the translation files.
Clytie, all I can say is: deliver the fixes as soon as possible, attach
them to an issue and write in the issue that this are quality critical bugs.
As for the mnemonics, for the CCJK languages we run a script which
automatically takes the English letter used in the English version.
Because of this automatic script we never spend time in setting
mnemonics manually in the above *Asian* languages ... should such a
script be run on VI as well?
Rafaella
Clytie Siddall wrote:
To: OOo dev l10n
Cc: Pootle (where our translation is based)
Thanks for your reply, Rafaella :)
On 13/11/2006, at 8:50 PM, Rafaella Braconi wrote:
*Now I've fixed quite a few minor errors of this kind in our
translation file, where do I go from here?*
Please deliver an sdf file containing fixes only, that is to say
- source (English) string
- target (translated language) corrected string
please remove all other strings from the sdf file for which you do
NOT need to provide correction.
Ah. I see. A difference file of a different type. ;)
*Do I upload the fixed file over the old one, and notify that in the
original issue? *
Please submit a new issue. In case the fixes cannot be integrate in
the currect release, the target will be moved to next one and it
will be easier to track. Genrally such fixes should be delivered
before the UI freeze of the next release. For delails on the next
release roadmap, see: http://wiki.services.openoffice.org/wiki/
OOoRelease22
OK.
*How late can we do this?*
For the 2.1 release only show stoppers/critical bugs will be fixed
and integrated into the master. For all other minor issues, the
target will be the 2.2.
Great. :(
*The Release Schedule for OOo 2.1 says: "Last_cws_integration for
fixes: November 16th 2006" but I am not sure if that is the due date
for translation fixes, or not.*
The deadline for non-critical translation fixes was November 8th.
The deadline of Last CWS integration refers to critical issues/show
stoppers: All changes that have been declared as stoppers for
release have to be integrated before this time. This will then be
the basis for the Release Candidate.
Unfortunately, I am the only person who was willing to check the
interface in any detail, and I didn't get a working build until after
Nov. 8th.
That means our first official translation will have quite a few minor
errors, mostly non-unique accelerator keys, but it doesn't look
professional, and will be a bad start for us. It's true that we have
worked against the odds for this release, with very few resources and
very little time, but I had no idea we wouldn't be able to fix
anything after submitting the file. It was bad luck that I didn't get
access to a build until after the fix date, but in combination, it's
not a good situation for us.
I suppose we can take heart from the fact that our manic work up to
this point has meant there are only very minor errors left in the
translation. But I would have liked to polish it before it was
released. I feel embarrassed about releasing something with so many
non-unique accelerators. It looks sloppy. :(
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
