Hi, On Tuesday, 2024-04-23 19:11:58 +0200, Jakub Kościelak wrote: > > > 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 > > where ca@va seems to stem from ca-valencia or kmr@l from kmr-Latn. > > I now know where these "@" signs come from. We use this script > C:\24.2.3.1\solenv\bin\localestr: #!/bin/sh case "$1" in ca-valencia) echo > ca@valencia ;; kmr-Latn) echo kmr@latin ;; sr-Latn) echo sr@latin ;; > hu-hung) echo hu@hung ;; *) echo $1 | tr '-' '_' ;; esac in these places: > C:\24.2.3.1\scp2\macros\macro.pl > C:\24.2.3.1\solenv\gbuild\AllLangMoTarget.mk > C:\24.2.3.1\solenv\gbuild\extensions\post_PackageInfo.mk and now out of > curiosity I have 2 questions: 1. What was/is the reason that for 4 languages > we replace "-" with "@" instead of underscore? 2. Is it obsolete or is it > still needed? The ca@valencia and the like include the glibc @modifiers. This is correct. Whatever later scrambles those to ca@va_LCMES_c8cb7e943 for Windows would need to adjust that to something like ca_va_LCMES_c8cb7e943 Eike -- GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A
Attachment:
signature.asc
Description: PGP signature
