Hi,
Kendy's patch was pushed today, I update pot file in git. Rimas, can you
please upload it to Pootle.
I do hope it was the last string change.
Many thanks,
Andras
Hi,
Kendy's patch was pushed today, I update pot file in git. Rimas, can you
please upload it to Pootle.
I do hope it was the last string change.
Many thanks,
Andras
Good news everyone!
New strings have arrived to Pootle. All locales now lack at least 127 words
Rimas
2011.01.06 23:19, Andras Timar rašė:
Andras, Rimas, thanks a lot
Kind regards
Sophie
Hi all,
Do I understand correct that one week before axpected release we get 127 new
strings to translate?
A few days ago I saw Michael Meeks write in an email that release is
expected within very shor time (next week was his words).
I see more and more that we will *not* be able to get a complete
translatione ready for release. I'm sorry but I can't release a product that
is not translated. I fear that our first 'production' release will end up
being a very low quality product that will never get in production anywhere.
If you ask me, a patch with strings comitted this close to release should be
rejected (actually be postponed). If we have changes at present that are
needed - ok fine, but then the release should be postponed.
Cheers,
Leif Lodahl
Danish Team
7 strings, 127 words. If you leave this untranslated, no problem, it's not a
regression. This change was demanded by other translators, devs only wanted
to please them.
Cheers,
Andras
Hi Leif,
Hi all,
Do I understand correct that one week before axpected release we get 127
new
strings to translate?7 strings, 127 words. If you leave this untranslated, no problem, it's not a
regression. This change was demanded by other translators, devs only wanted
to please them.
It's not final that will come next week but RC3, to be tagged on monday if possible.
Kind regards
Sophie
Hi, Leif,
Hi all,
Do I understand correct that one week before axpected release we get 127
new
strings to translate?A few days ago I saw Michael Meeks write in an email that release is
expected within very shor time (next week was his words).I see more and more that we will *not* be able to get a complete
translatione ready for release. I'm sorry but I can't release a product
that
is not translated. I fear that our first 'production' release will end up
being a very low quality product that will never get in production
anywhere.If you ask me, a patch with strings comitted this close to release should
be
rejected (actually be postponed). If we have changes at present that are
needed - ok fine, but then the release should be postponed.
LO is still in its first steps and the interpretation of RC is not the same
as with OOo (at least not for 3.3) - in RC2 several things don't work yet
(see known limitations) etc. LO RC2 is more like a beta version in the OOo
dev language.
As localization teams we must strive to offer our users a completely
localized experience. I rather see "wild" deadlines instead of non-fully
localizable GUI (the will to get smaller localization issues solved, even if
just before the release date, is a great change from the OOo development
that wouldn't even bother with these issues).
127 new strings should not pose a serious problem for a localization team,
just the deadline itself could be a problem. I hope the releases team will
give enough time for it (I already translated the new strings yesterday).
Lp, m.
2011.01.07. 11:37 keltezéssel, Sophie Gautier Ãrta:
It's not final that will come next week but RC3, to be tagged on monday
if possible.
If it's true, then translators please make sure you update your
translations in Pootle by Sunday 9:00 PM GMT, I'll take them from Pootle
and push them to git then. I'll make subsequent pushes later, if tagging
does not happen on Monday and I see updated translations.
Thanks,
Andras
Funny, isn't the discussion about LO icons just going on on the design list?
Or will LO ship with OOo icons?
Or maybe they will make an express decision and the icons will be changing
for the next version.
Lp, m.