Manfred J. Krause wrote:
This aspect had given me some new inspiration - ;-)
a workaround I tried with success ->
'The Guerrilla Way (a long way off perfection)'.
Changing all "es_CU" (Cuba) entries to e.g. a not installed Spanish
language module as "es_DO" (Dom. Rep.).
a) There are roughly fifteen language/country combinations for which
that has to be done, due to the wars that the US is currently engaged
in. "Official" OOo releases can not include them, because doing so
constitues "giving aid and comfort to the enemy" and/or "aiding and
abetting terrorist activities".
That said, at least two derivatives/forks/whatever of OOo do include
some of those country/language combinations.
b) This workaround has to be used for all language/country combinations
that OOo does not currently support.
c) This workaround also has to be used for anybody who creates documents
using an a11y writing system, and a non-a11y writing system, in the same
language. For Braille, that means 8 language/country combinations are
used per language. For Moon that means 2 language/country combinations
are used per language. [Once the ODF toolkit is released, an office
suite designed for a11y will be created, thereby negating the "need" for
OOo to fix this issue in regards to a11y.]
xan
jonathon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
