[Fedora-i18n-bugs] [Bug 734976] libreoffice-langpack-*-* not pulled in by yum install libreoffice

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=734976

Kevin Kofler <kevin at tigcc.ticalc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kevin at tigcc.ticalc.org

--- Comment #17 from Kevin Kofler <kevin at tigcc.ticalc.org> 2011-09-29 08:39:05 EDT ---
> BCP-47 style FWIW (http://www.rfc-editor.org/rfc/bcp/bcp47.txt) rather than
> anything to do with Java.

Why can't we just accept that the glibc/gettext format has become the de-facto
standard and that it doesn't make sense to invent a new, incompatible one? It's
way too late for that!

> BCP-47 offers a relatively sane way to describe e.g. Serbian written in Latin
> script, sr-Latn or Sindhi written in Devanagari script, sd-Deva.

So does glibc/gettext, that's what the @variant suffix is for. kde-l10n uses at
least sr at latin, sr at ijekavian, sr at ijekavianlatin and ca at valencia.

> I have some code to map existing glibc locales to best-fit tags
> http://people.redhat.com/caolanm/BCP47/ but its err... a work in progress.

I see you have a hunspell patch there, which renames all the hunspell
dictionaries. I have to warn you that this is an incompatible change which will
undoubtedly break many applications using hunspell. (We already have enough
problems as it stands now with some KDE applications assuming they can just
request "de" as a dictionary as opposed to de_DE, de_AT or de_CH. But if you
also rename away the de_DE etc. ones, many more applications will be broken. No
application will be looking for a de-DE dictionary.) Please do not make such
gratuitously incompatible changes.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.