Hi Jakub,
On Tuesday, 2024-04-23 14:14:30 +0200, Jakub Kościelak wrote:
> 1.
>
> ICE03 ERROR Invalid Language Id;
>
> Example:
>
> sd87.mo
> gid_file_res_sd_lang__libreoffice_program_resource_sat_lc_messages_sat sd.mo
> 55167 1606 16384 15468
>
> We use a Languge Id that is not in the documentation ;-) e.g. 1553 or 1606.
Yes. As MS doesn't support all languages, we define LCIDs in the
user-defined ranges, see include/i18nlangtag/lang.h for documentation.
Here
1553 = 0x0611 = {eo} = Esperanto LANGUAGE_USER_ESPERANTO
1606 = 0x0646 = {sat-IN} = Santali (India) LANGUAGE_USER_SANTALI_INDIA
> https://learn.microsoft.com/en-us/openspecs/office_standards/ms-oe376/6c085406-a698-4e12-9d4d-c3b0ee3dbc4a
Oh great, yet another place they simultaneously update, where so far
I assumed that finally this evolved to the canonical place:
https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/70feba9f-294e-491e-b6eb-56532684c37f
Someone might want to check for differences..
> Here they also wrote that language identifiers are outdated and locale names
> should be used:
>
> https://learn.microsoft.com/en-us/windows/win32/intl/language-identifier-constants-and-strings
>
> However, when I used en-US instead of 1033, it reported an error. Maybe
> someone knows how it should be done?
Maybe that's not even applicable to the installer. Or if, then to be
used with some different mechanism than LCIDs.
> ICE03 ERROR Invalid identifier; Table: Directory, Column: Directory, Key(s): LO_progr_resou_ca@va_LCMES_c8cb7e943
> ICE03 ERROR Invalid identifier; Table: Directory, Column: Directory, Key(s): LO_progr_resou_kmr@l_LCMES_c75f6f5fa
> [... and hundreds others ...]
These look very much derived from translation resources language tags,
where ca@va seems to stem from ca-valencia or kmr@l from kmr-Latn.
Whyever that is crippled that way..
Eike
--
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A
Attachment:
signature.asc
Description: PGP signature
