![[TEST] Document Foundation Community](https://communitytest.documentfoundation.org/images/discourse-logo-sketch.png){kind=logo}
Hi,
Yesterday LibreOffice 3.3 RC2 was tagged in git and I extracted the
en-US strings in order to see, whether there were something new to
localize. There were quite a few, I have to update the pot file soon.
Most of them come from the scp2 module and they are rather boring, i.e.
you'll have to translate 110 times "Installs <language name> help in
%PRODUCTNAME %PRODUCTVERSION". Anyway, be prepared for additional
translation work in the coming days.
Thanks,
Andras
2010.12.19. 22:23 keltezéssel, Andras Timar írta:
Hi,
Yesterday LibreOffice 3.3 RC2 was tagged in git and I extracted the
en-US strings in order to see, whether there were something new to
localize. There were quite a few, I have to update the pot file soon.Most of them come from the scp2 module and they are rather boring, i.e.
you'll have to translate 110 times "Installs <language name> help in
%PRODUCTNAME %PRODUCTVERSION". Anyway, be prepared for additional
translation work in the coming days.Thanks,
Andras
Hi,
I updated the po/pot/sdf files in git. Rimas, can you please update
Pootle. There are 5 fuzzies and 321 new strings, mainly
langpack/helppack names and descriptions, but "Help -> LibreOffice
Credits..." is also there, finally...
Best regards,
Andras
Hi folks,
Pootle is now updated to accommodate the new strings Andras has mentioned below.
Since the numbers shown in Pootle are a bit off, here are the real ones:
Strings: 780
Words: 4864
If you had everything translated by now, you'll now have 5 new fuzzy and 321 untranslated strings (19 and 1173 words, respectively).
As usually, backups of the old files have been made, so in case you're seeing some sort of problem, feel free to raise it.
Rimas
2010.12.21 00:25, Andras Timar rašė:
Hello, Rimas and Andras,
can you list the extensions that will be bundled with 3.3?
I want to check that all are localized into Slovenian.
All the OOo extensions, part of SDF, already are localized. So are the
LanguageTool and the extra solver by Kohei. Will there be any other
extension bundled so I must localize it?
Lp, m.
Since this question went by unanswered I am putting some attention back to
it.
Lp, m.
I think that Rimas and Andras don't have more the answer than you 
May be you should ask on the developers list, they may be able to answer you.
May be we should add an Extensions part on the wiki page listing the new features or LibO?
Kind regards
Sophie
Hi Martin,
Hello, Rimas and Andras,
can you list the extensions that will be bundled with 3.3?
I want to check that all are localized into Slovenian.All the OOo extensions, part of SDF, already are localized. So are the
LanguageTool and the extra solver by Kohei. Will there be any other
extension bundled so I must localize it?Since this question went by unanswered I am putting some attention back to
it.
I think that Rimas and Andras don't have more the answer than you May be you should ask on the developers list, they may be able to answer you.
May be we should add an Extensions part on the wiki page listing the new features or LibO?
Kind regards
Sophie
Hi,
Having completed Telugu translation, I would like to share my feedback
Hi,
Yesterday LibreOffice 3.3 RC2 was tagged in git and I extracted the
en-US strings in order to see, whether there were something new to
localize. There were quite a few, I have to update the pot file soon.Most of them come from the scp2 module and they are rather boring, i.e.
you'll have to translate 110 times "Installs <language name> help in
%PRODUCTNAME %PRODUCTVERSION". Anyway, be prepared for additional
translation work in the coming days.1.This is lot of unnecessary work for the translators, as I have seen that
there is more occurences of same strings when a language has more than one
locale (based on country), even though there is no difference in the
language. For example same strings repeat for te and te-IN. I do not know
the current constraints or whether current POT file is not properly put
together, but this could have been handled by capturing translations for
substrings and putting them in the UI.
Virtaal tool was helpful in the translation work of such strings, though it
fails to show the exact match, even though it was just entered.
2. I have noticed some more strings for installing spell checker dictionary
for some languages, as more extensions are added, maintaining the
translation becomes difficult.
3. I have seen some repeats for installation commands for different
distributions as well.
4. In the HTML paras, the string to be highlighted is given as URL instead
of appropriate English word.
Hope that there will be a better system for the future releases.
Cheers
Arjuna Rao Chavala
> 1.This is lot of unnecessary work for the translators, as I have seen
that
there is more occurences of same strings when a language has more than one
locale (based on country), even though there is no difference in the
language. For example same strings repeat for te and te-IN. I do not know
the current constraints or whether current POT file is not properly put
together, but this could have been handled by capturing translations for
substrings and putting them in the UI.
Yes, unfortunately we have a lot more helppack entries than actually needed.
Probably it was a copy&paste from other part of the code. Sorry for the
repeated strings. I already proposed to review the list of languages in
libreoffice@fdo list, it can be a part of that.
2. I have noticed some more strings for installing spell checker dictionary
for some languages, as more extensions are added, maintaining the
translation becomes difficult.
Can you please give some details, I don't understand what you mean.
3. I have seen some repeats for installation commands for different
distributions as well.
Repetitions should really be handled by the translation tool. It is not
desirable (or sometimes not even possible) to re-use the same source string
in a different context.
4. In the HTML paras, the string to be highlighted is given as URL instead
of appropriate English word.
Do you refer to the readme?
Thanks,
Andras
Response embedded.
> > 1.This is lot of unnecessary work for the translators, as I have seen
> that
> there is more occurences of same strings when a language has more than
one
> locale (based on country), even though there is no difference in the
> language. For example same strings repeat for te and te-IN. I do not
know
> the current constraints or whether current POT file is not properly put
> together, but this could have been handled by capturing translations for
> substrings and putting them in the UI.
>
>
Yes, unfortunately we have a lot more helppack entries than actually
needed.
Probably it was a copy&paste from other part of the code. Sorry for the
repeated strings. I already proposed to review the list of languages in
libreoffice@fdo list, it can be a part of that.Thanks
> 2. I have noticed some more strings for installing spell checker
dictionary
> for some languages, as more extensions are added, maintaining the
> translation becomes difficult.
>Can you please give some details, I don't understand what you mean.
Example: Galician spellchecker dictionary for %PRODUCTNAME ,
Why there were no such strings for other languages? Will they appear later.
If they again repeat for languages with more locales, it will be a problem.
>
> 3. I have seen some repeats for installation commands for different
> distributions as well.
>
>
Repetitions should really be handled by the translation tool. It is not
desirable (or sometimes not even possible) to re-use the same source string
in a different context.Virtaal that I used seem to have limitations/bugs at present. Some times
translators may be using primitive tools, hence it is better for strings to
be minimal and occuring only once.
> 4. In the HTML paras, the string to be highlighted is given as URL
instead
> of appropriate English word.
>
In the below example source string, note the repetition of the url as the
string to be highlighted.
If you appreciate their efforts, and would like to ensure that
${PRODUCTNAME} continues to be available far into the future, please
consider contributing to the project - see <a href="
http://www.documentfoundation.org/contribution/">
http://www.documentfoundation.org/contribution/</a> for details. Everyone
can make a contribution of some kind.
Do you refer to the readme?
No. Not sure I understand readme in your question above.
Thanks
Arjun