Issue 87832 - Languages / locales need locale data to be fully supported.
Summary: Languages / locales need locale data to be fully supported.
Alias: None
Product: Internationalization
Classification: Code
Component: localedata (show other issues)
Version: OOo 2.4.0
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: needhelp
Depends on:
Reported: 2008-04-03 18:32 UTC by andreschnabel
Modified: 2017-05-20 11:13 UTC (History)
2 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description andreschnabel 2008-04-03 18:32:31 UTC
Lower German has been introduced in 2.4.0 as language (see issue 80432).

The language can be selected in character / number format lists, but not for
language settings in the tools - options dialog (default document laguage,
spellchecking options, hyphenation ...)
Comment 1 andreschnabel 2008-08-04 18:18:25 UTC
not only lower german is affected, but several languages that have been recently

I found that e.g. Bambara, Bodo, Burmese, ... Maori, Moore ...
are missing in DEV300_m27

reassign to l10n
Comment 2 andreschnabel 2008-08-04 18:19:01 UTC
changed subcomponent
Comment 3 ooo 2008-08-05 11:42:49 UTC
Adding a language to the language list box makes it available for
character attribution and spell-checking. Availability of spell checker,
hyphenation and thesaurus of course depends on the installed
dictionaries. To be able to fully support it as a locale, including
number formats and calendar data, and having it selectable as default
document language we would need a locale data file.

You can easily generate a locale data file with the generator available

For technical details and semantics of elements please see the
generator's documentation and the comments in the locale data DTD file
and as a sample locale data file for example the en_US locale

However, an issue saying "several languages ..." that would need locale data to
be created by localization teams isn't really suited to track things. I take
this as a place holder issue so people may stumble upon when doing a query.

When available, for each new locale data a separate issue should be submitted
and the locale data attached there.
Comment 4 Marcus 2017-05-20 11:13:06 UTC
Reset assigne to the default "".