On Sun, Feb 04, 2024 at 03:42:22PM +, Gavin Smith wrote:
>
> COLLATION_LANGUAGE would be an argument to use
> for Unicode::Collate::Locale to get language-specific tailoring, which
> in language-independent terms means to use the UCA with tailoring, with
> variable collation elements treated
On Sun, Feb 04, 2024 at 08:38:28PM +, Gavin Smith wrote:
> >
> > strcmp is always used as a transformation on the string is done with
> > strxfrm_l for the collation in C. If USE_UNICODE_COLLATION=0 the string
> > is not transformed, which amounts to using strcmp on the original
> > string.
On Sun, Feb 04, 2024 at 08:38:45PM +0100, Patrice Dumas wrote:
> Thanks. This is very confusing to me, then, as it is not told that way
> in perllocale, especially the section:
> https://perldoc.perl.org/perllocale#Category-LC_COLLATE%3A-Collation%3A-Text-Comparisons-and-Sorting
> There is more
On Sun, Feb 04, 2024 at 08:38:45PM +0100, Patrice Dumas wrote:
> >offer much more powerful solutions to collation issues.
> >
> > - from "man perlop".)
>
> Thanks. This is very confusing to me, then, as it is not told that way
> in perllocale, especially the section:
>
I can't build from commit 5154587461e (2024-02-04). It ends with the
errors:
make[2]: Entering directory '/home/g/src/texinfo/GIT/tp/Texinfo/XS/gnulib/lib'
gperf -m 10 ./iconv_open-aix.gperf > ./iconv_open-aix.h-t && \
mv ./iconv_open-aix.h-t ./iconv_open-aix.h
/bin/bash: line 1: gperf: command
>> (Note that "cmp" is documented not to work with "use locale" for UTF-8
>> strings: [...]
>
> Thanks. This is very confusing to me, then, as it is not told that way
> in perllocale, especially the section: [...]
Perhaps Bruno Haible can help?
Werner
On Sun, Feb 04, 2024 at 03:42:22PM +, Gavin Smith wrote:
> On Sun, Feb 04, 2024 at 12:17:16PM +0100, Patrice Dumas wrote:
> > On Thu, Feb 01, 2024 at 10:16:07PM +, Gavin Smith wrote:
> > > An alternative is not to have such a variable but just to have an option
> > > to collate according
> From: Gavin Smith
> Date: Sun, 4 Feb 2024 15:58:28 +
> Cc: pertu...@free.fr, bug-texinfo@gnu.org
>
> On Fri, Feb 02, 2024 at 08:57:01AM +0200, Eli Zaretskii wrote:
> > > An alternative is not to have such a variable but just to have an option
> > > to collate according to the user's
>>You can undefine a macro FOO with ‘@unmacro FOO’. It is not an
>>error to undefine a macro that is already undefined. For
>>example:
>>
>> @unmacro foo
>>
>> However, this doesn't work.
>
> I don't know if this is a regression as the code for this error
> message existed as
On Fri, Feb 02, 2024 at 08:57:01AM +0200, Eli Zaretskii wrote:
> > An alternative is not to have such a variable but just to have an option
> > to collate according to the user's locale. Then the user would run e.g.
> > "LC_COLLATE=ll_LL.UTF-8 texi2any ..." to use collation from the ll_LL.UTF-8
>
On Sun, Feb 04, 2024 at 12:17:16PM +0100, Patrice Dumas wrote:
> On Thu, Feb 01, 2024 at 10:16:07PM +, Gavin Smith wrote:
> > An alternative is not to have such a variable but just to have an option
> > to collate according to the user's locale. Then the user would run e.g.
> >
>> An alternative is not to have such a variable but just to have an
>> option to collate according to the user's locale. Then the user
>> would run e.g. "LC_COLLATE=ll_LL.UTF-8 texi2any ..." to use
>> collation from the ll_LL.UTF-8 locale. They would have to have the
>> locale installed that
On Sun, Feb 04, 2024 at 12:17:16PM +0100, Patrice Dumas wrote:
> Here is my updated thinking on the possibilities
>
> 1) lexicographic sorting on unicode strings (corresponds to
> USE_UNICODE_COLLATION=0 currently)
> 2) unicode default sorting obtained by
On Sun, Feb 04, 2024 at 12:07:17PM +0100, Andreas Schwab wrote:
> On Feb 04 2024, Eli Zaretskii wrote:
>
> > If we want collation which uses only codepoints, disregarding any
> > collation weights defined by the Unicode TR10, we could use
> > en_US.utf-8, but then, as Gavin says, using glibc
On Sun, Feb 04, 2024 at 12:55:36PM +0200, Eli Zaretskii wrote:
> > Date: Sun, 4 Feb 2024 11:42:52 +0100
> > From: pertu...@free.fr
> > Cc: Gavin Smith , bug-texinfo@gnu.org
> >
> > On Fri, Feb 02, 2024 at 08:57:01AM +0200, Eli Zaretskii wrote:
> > > I think en_US.utf-8 is (or at least can be by
On Thu, Feb 01, 2024 at 10:16:07PM +, Gavin Smith wrote:
> An alternative is not to have such a variable but just to have an option
> to collate according to the user's locale. Then the user would run e.g.
> "LC_COLLATE=ll_LL.UTF-8 texi2any ..." to use collation from the ll_LL.UTF-8
> locale.
On Feb 04 2024, Eli Zaretskii wrote:
> If we want collation which uses only codepoints, disregarding any
> collation weights defined by the Unicode TR10, we could use
> en_US.utf-8, but then, as Gavin says, using glibc collation function
> you get more than you asked, because weights are not
> Date: Sun, 4 Feb 2024 11:42:52 +0100
> From: pertu...@free.fr
> Cc: Gavin Smith , bug-texinfo@gnu.org
>
> On Fri, Feb 02, 2024 at 08:57:01AM +0200, Eli Zaretskii wrote:
> > I think en_US.utf-8 is (or at least can be by default) a combination
> > of @documentlanguage and @documentencoding.
>
>
On Fri, Feb 02, 2024 at 08:57:01AM +0200, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Thu, 1 Feb 2024 22:16:07 +
> > Cc: Patrice Dumas , bug-texinfo@gnu.org
> >
> > On Thu, Feb 01, 2024 at 09:01:42AM +0200, Eli Zaretskii wrote:
> > > > Date: Wed, 31 Jan 2024 23:11:02 +0100
> > > >
19 matches
Mail list logo
