Hi Jordi,
On Wednesday, 2006-10-25 14:09:27 +0200, Jordi Mallach wrote:
> My progress to produce a Valencian-Catalan locale support patch is
> mostly blocked by the lack of a Microsoft Locale ID for this.
No, unfortunately that's not the main blocking thing. As already
mentioned 3 weeks ago, Valencian-Catalan is no separate language and
doesn't have an ISO 639 code assigned, and modifiers respectively
variants or subtags aren't supported yet by OOo, nor could
a corresponding language tag be stored in the OpenDocument file format
(ODF). Currently it is nearly technically impossible to support the
construct of a dialect as a separate language.
> When and how do internal locale codes get assigned once you've mailed
> this list?
Usually it's up to me to assign LangID codes. However, in this case it
is pretty much pointless to do so, as there is no valid mapping to the
ISO and file format constructs used by OOo. This has to be solved first.
> Catalan has 1027 assigned, but I obviously can't use this one too.
No, it would be indistinguishable then and map to ca-ES.
> Also, I'm apparently going to have a hard time adding stuff for a locale
> with a modifier like ours, "[EMAIL PROTECTED]".
Not supported yet.
> I'm assuming that I'll be using things like "ca_ES-valencia" or so, but
> I suspect things are not how the'd need to be. For example, in
> i18npool/source/isolang/isolang.cxx, MsLangId::IsoLangEntry, I added
>
> // { LANGUAGE_CATALAN_VALENCIAN, "ca", "ES" }, // Modifier
> names not supported yet ([EMAIL PROTECTED])
This would introduce ambiguousness to an already existing mapping:
{ LANGUAGE_CATALAN, "ca", "ES" }, // Spain (default)
and is not "round-trip-safe", conversions back and forth between that
mapping would not produce identical identifiers, which is essential for
using it in attribution and storage.
> and for IsoLangNoneStdEntry,
> { LANGUAGE_CATALAN_VALENCIAN, "ca", "valencia" }, //
> [EMAIL PROTECTED] locale
This would not produce a valid language/country pair as currently
required by ODF. See also section "15.4.23 Language" and "15.4.24
Country" of
http://www.oasis-open.org/committees/download.php/12573/OpenDocument-v1.0-os.sxw
that refer sections "7.9.2 language" and "7.9.1 country" of the XSL
http://www.w3.org/TR/2001/REC-xsl-20011015/ specification, which in turn
refer RFC 3066 http://tools.ietf.org/html/rfc3066
A possible solution according to RFC 3066 could be an identifier
"x-valenc" as language and "ES" as country, would had to be verified
though whether that is really usable within OOo. However, that would be
a private extensions and would not be recognized by any other
application, not even as being related to Catalan, which I consider
a major drawback and therefor hesitate to use the IsoLangNoneStdEntry
mechanism. I would only use it as a very last resort.
Are you sure you want to go that road with all implications it might
have?
> I named the locale definition file "ca_ES-valencia.xml", but again I'm
> not sure that's going to be grokked by OOo.
No, it wouldn't.
> But is this going to work at all?
Not yet. Vaiants would need modifications to the file format and several
modifications to the source code, probably throughout the entire
application suite.
> Any help I can get here will be fantastic.
Sorry I can't tell you "hey, that's easy, just do this and that" ...
Eike
--
OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer.
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
Please don't send personal mail to this [EMAIL PROTECTED] account, which I use
for
mailing lists only and don't read from outside Sun, use the [EMAIL PROTECTED]
account
instead if really needed. Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
