localization bug

l10n
#1

Hello,

is there a way to fix this bug that Hamburg was ignoring all the time:
http://qa.openoffice.org/issues/show_bug.cgi?id=66304

Also, could we please get a localized license file for localized LO (OOo
didn't want it either)? Just can't find a bug, it was probably closed as
"will never happen".

These two are the most outstanding localization issues from OOo AFAIK.

Since the first one represents just one string and the other one is a
license that is probably already localized in many languages for other
projects, could we see this in LO3.3?

LP, m.

#2

Martin Srebotnjak wrote:

Also, could we please get a localized license file for localized LO (OOo
didn't want it either)? Just can't find a bug, it was probably closed as
"will never happen".

Actually, it was not OOo; it was, and still is, the Free Software
Foundation. http://www.gnu.org/licenses/translations.html states why
they won't officially approve translated licenses. So a translated
license could be included, but still you would have to accept the
English text and the English one would have to be more prominent and the
unofficial translation clearly marked as such.

Regards,
  Andrea.

#3

2010.11.09 11:29, Andrea Pescetti rašė:

Martin Srebotnjak wrote:

Also, could we please get a localized license file for localized LO (OOo
didn't want it either)? Just can't find a bug, it was probably closed as
"will never happen".

Actually, it was not OOo; it was, and still is, the Free Software
Foundation. http://www.gnu.org/licenses/translations.html states why
they won't officially approve translated licenses. So a translated
license could be included, but still you would have to accept the
English text and the English one would have to be more prominent and the
unofficial translation clearly marked as such.

Talking about this, would it perhaps be possible to license oficial builds differently than source code? Instead of telling the user to agree to a source license, we could probably present them with a short, understandable and localized EULA.

However, if this is not possible, here's an alternate proposal: how about we prepend the license with a localized string that would contain short localized summary of the license, and explain in a few words that the license itself is in English and that only English text is legally binding.

Rimas

P.S. This is most likely more relevant to general list than l10n. Somebody care to forward?

#4

It's not an issue in your language (Slovenian), is it? I see it
translated as "Moje samobesedilo" in
extras/source/autotext/lang/sl/mytexts.bau.
If other teams want this localized, file a bug, provide the
translation for "My Autotexts" and assign it to me, I'll commit + push
it.

Andras

#5

Talking about this, would it perhaps be possible to license oficial builds
differently than source code? Instead of telling the user to agree to a
source license, we could probably present them with a short, understandable
and localized EULA.

LGPL is not an EULA. In fact I don't think we need an EULA. The users
should be informed about their rights but they can install and use
LibreOffice even if they don't accept LGPL. LGPL says nothing about
installing and using free software, everyone is free to do that. Its
terms should be followed only in case of redistribution and
modification.

However, if this is not possible, here's an alternate proposal: how about we
prepend the license with a localized string that would contain short
localized summary of the license, and explain in a few words that the
license itself is in English and that only English text is legally binding.

+1 (license.html, license.txt etc.)

Andras

#6

Hi Andras,

It's not an issue in your language (Slovenian), is it? I see it
translated as "Moje samobesedilo" in
extras/source/autotext/lang/sl/mytexts.bau.
If other teams want this localized, file a bug, provide the
translation for "My Autotexts" and assign it to me, I'll commit + push
it.

Please do so for Lithuanian: https://bugs.freedesktop.org/show_bug.cgi?id=31493

Thanks,
Modestas

#7

Yes, Andras, it is an issue. We translated the string, but it is hard-coded
in that specific dialog in English. In all language versions, AFAIK.

I should look it up in the interface and make a screenshot for you.

Lp, m.

#8

Yes, Andras, it is an issue. We translated the string, but it is hard-coded
in that specific dialog in English. In all language versions, AFAIK.

OK, then we have two issues.
1. This string is not translated in most languages. Currently only sl
and hu have localized mytext.bau, Lithuanian is pending.
2. Even if it is translated, it is not displayed. I need to find out why...

I should look it up in the interface and make a screenshot for you.

No need to do that, I checked it my Hungarian build, and I see the issue.

Thanks for your explanations.

Andras

#9

Update: here is what I've found out.
Localized mytext.bau files are not used in the build and there is a
good reason for that. The file mytext.bau goes into the user profile.
It is an empty file, users can put their custom AutoText in it. It
could have been localized for a single language install, but in a
multi language install it would have been troublesome. For example the
hard-wired string in the file would not change, if the user changed
the UI language.

Conclusion: localized mytext.bau files (currently hu and sl) can be
removed from the source, because they are useless. Don't send more
translations via bugzilla. We need to localize this string elsewhere.
I guess we can "intercept" this string in
sw/source/ui/misc/glossary.cxx and replace it to the localized
equivalent (a new "My AutoText" string should be added to
glossary.hrc/src in order we can localize it normally). I don't have
the patch but I'll work on it.

Best regards,
Andras

#10

2010.11.14. 22:13 keltezéssel, Andras Timar írta:

Conclusion: localized mytext.bau files (currently hu and sl) can be
removed from the source, because they are useless. Don't send more
translations via bugzilla. We need to localize this string elsewhere.
I guess we can "intercept" this string in
sw/source/ui/misc/glossary.cxx and replace it to the localized
equivalent (a new "My AutoText" string should be added to
glossary.hrc/src in order we can localize it normally). I don't have
the patch but I'll work on it.

The patch has been pushed to libreoffice-3-3 branch, I updated the pot
file and all po files (hu, lt, sh, sl, and sr already have translations
for "My AutoText"). Please update the files in Pootle.

Thanks,
Andras

#11

Hi all,

sorry for the delay. I've just updated the Pootle files from git. Hopefully this didn't drop any existing translations, but in case it did, please raise your hand.

This update added one string (My AutoText) to the localization files, which means all translations are now incomplete again.

Regards,
Rimas

2010.11.20 01:20, Andras Timar rašė:

#12

All ok Rimas,

Updated

#13

Done.
Thanks Rimas.

Olivier