LO33RC4 Known L10N Issues

l10n
#1

Hello,

just a short update - today RC4 came out and the online help (on Windows,
without help L10N pack installed) still opens in English, at least for the
Slovenian LO. Can other non-en language teams confirm this?

I hope that RC5 gets it right. Otherwise I suggest non-en languages are
dropped from the multi installer and separate lang packs are offered for
Windows (same as for Linux and OS X).

Thanks,
m.

#2

Hi Martin,

2011.01.20. 23:27 keltezéssel, Martin Srebotnjak írta:

just a short update - today RC4 came out and the online help (on Windows,
without help L10N pack installed) still opens in English, at least for the
Slovenian LO. Can other non-en language teams confirm this?

Do you mean this: https://bugs.freedesktop.org/show_bug.cgi?id=33258
or that the Slovenian help is still not uploaded, or both?

Thanks,
Andras

#3

Yes, Andras,

Hi Martin,

2011.01.20. 23:27 keltezéssel, Martin Srebotnjak írta:
> just a short update - today RC4 came out and the online help (on Windows,
> without help L10N pack installed) still opens in English, at least for
the
> Slovenian LO. Can other non-en language teams confirm this?

Do you mean this: https://bugs.freedesktop.org/show_bug.cgi?id=33258
or that the Slovenian help is still not uploaded, or both?

just like you reported in that bug. If I install the Slovenian helppack, the
help is in Slovenian, as expected.

But the online help is English only. And your bug reports only that links
always contain only "en" parameter, but that is only part of the problem.
Currently, it seems, other help languages are not available in wiki at all,
so even if that link would look proper, the content still isn't there.

Lp, m.

#4

Yeah, but if the link always contains the "en" parameter, then it will
never be right. Content can be changed easily on the web, but URL is
constructed by the code and it cannot be changed after release. I
don't worry about the web contents, that's work-in-progress anyway.

Best regards,
Andras

#5

Yeah,

Yeah, but if the link always contains the "en" parameter, then it will
never be right. Content can be changed easily on the web, but URL is
constructed by the code and it cannot be changed after release. I
don't worry about the web contents, that's work-in-progress anyway.

totally agree with you on this one.

Lp, m.