Created attachment 157786 [details]
locale data for Ligurian
Locale data file for Ligurian [lij-IT], as per wiki instructions.
Apart from the [$₤-410] currency designator, which I have to adapt anyway for the new LCID number 6A6 and the Euro currency symbol to [$€-6A6], the index FollowPageWord keywords look a bit odd:
<LC_INDEX ref="en_US" />
<IndexKey phonetic="false" default="true" unoid="alphanumeric">A-Z</IndexKey>
where f. and ff. are used as
# f.: page # and following page
# ff.: page # and following pages
The it_IT locale data has
<FollowPageWord> e seg.</FollowPageWord>
<FollowPageWord> e segg.</FollowPageWord>
Created attachment 157809 [details]
locale data for Ligurian v2
My bad – I was taking inspiration from Catalan and Portuguese, which also seem to (incorrectly) do that. Thanks for checking!
We can just do what it_IT does for LC_INDEX then, as it works for Ligurian too.
Seeing that the language uses accented characters, how are they to be sorted in a Writer's index page? The current definition of IndexKey A-Z would sort them after Z in their Unicode order, if that is supposed to be different the order has to be defined, for documentation of the IndexKey element see
Just write here what to put there, no need to attach a new file, I already have a modified version on disk.
Btw, the year code is YY|YYYY, not AA|AAAA (which is only in Italian for legacy reasons).
Regarding bug 130563 I also took the liberty to make 4-digit year formats the default to match the then upcoming change.
One other thing:
Apparently we don't have your license statement on file, could you
please send us a blanket statement that you contribute all your past and
future patches under the MPLv2 and LGPLv3+ licenses? Best on the dev
mailing list email@example.com so we can link to it from
Something like this does nicely:
All of my past & future contributions to LibreOffice may be
licensed under the MPLv2/LGPLv3+ dual license.
Best use Subject: <your full name> license statement
Sorry for the inconvenience and thank you for cooperating :-)
Jean, please, can you submit the license mail to the mailing list as mentioned?
Without, I can't commit your contribution to the core repository.
(In reply to Eike Rathke from comment #3)
> Seeing that the language uses accented characters, how are they to be sorted
> in a Writer's index page? The current definition of IndexKey A-Z would sort
> them after Z in their Unicode order
Oh! I had based that off of it_IT and fr_FR – looks like those might be wrong too, then?
Would it be possible to just use the default ICU collation order? If not, this will do: A À Â Ä Æ B-C Ç D-E É È Ê Ë F-I Ì Î Ï J-N Ñ O Ó Ò Ô Ö P-U Ù Û Ü V-Z
> Apparently we don't have your license statement on file, could you
> please send us a blanket statement that you contribute all your past and
> future patches under the MPLv2 and LGPLv3+ licenses?
Sent to the mailing list.
Thanks for your help!
(In reply to firstname.lastname@example.org from comment #5)
> Oh! I had based that off of it_IT and fr_FR – looks like those might be
> wrong too, then?
Italian does not use accented characters, or does it?
For French, probably the collation order is sufficient in indexes.
> Would it be possible to just use the default ICU collation order?
If the collation order for the locale suits the index needs then yes. In some languages the index order differs from the collation order, and index may have additional requirements, see the comments in locale.dtd I mentioned, hence we made this an explicit element.
I like to point that out in new locale data submissions if only A-Z is used because many are not aware of possible differences.
> If not,
> this will do: A À Â Ä Æ B-C Ç D-E É È Ê Ë F-I Ì Î Ï J-N Ñ O Ó Ò Ô Ö P-U Ù Û
> Ü V-Z
Thanks, I'll use that.
> Sent to the mailing list.
Eike Rathke committed a patch related to this issue.
It has been pushed to "master":
Resolves: tdf#130579 Add Ligurian [lij-IT] locale data
It will be available in 7.0.0.
The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.