[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: use getSortKey in Unicode::Collate
From: |
Gavin Smith |
Subject: |
Re: use getSortKey in Unicode::Collate |
Date: |
Mon, 13 Feb 2023 18:36:22 +0000 |
On Mon, Feb 13, 2023 at 06:01:46PM +0100, Patrice Dumas wrote:
> On Mon, Feb 13, 2023 at 08:47:26AM +0000, Gavin Smith wrote:
> > > Other than that I do not have much other idea than disabling it, for
> > > instance if documentlanguage is en. The result with Unicode::Collate is
> > > better for accented letters, but not so useful in english. There could
> > > even be a customization variable to use Unicode::Collate even in
> > > english.
> >
> > Another possibility is to use getSortKey:
>
> This is done in
> https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=434dcffe6a531f2d25200b2059ddfd784ab58c6f
>
> The default is for now set to using preset keys. For now it can be
> changed in tp/Texinfo/Structuring.pm by setting $default_preset_keys to 0.
>
> I have compared the Texxinfo tests, and not pre-setting seems to be a
> bit faster. However, for the Texinfo manual pre-setting the keys leads
> to a net gain, with a doubling of the time without pre-setting.
Great work! I found it was nearly as fast as before in the testing
I did too. It should be okay to use Unicode::Collate unconditionally,
then.
- Re: texi2any is too slow because of Unicode::Collate, (continued)
- Re: texi2any is too slow because of Unicode::Collate, pertusus, 2023/02/12
- Re: texi2any is too slow because of Unicode::Collate, Gavin Smith, 2023/02/12
- texi2any 7.0 performance regression (non-XS), Gavin Smith, 2023/02/12
- Re: texi2any 7.0 performance regression (non-XS), pertusus, 2023/02/12
- Re: texi2any 7.0 performance regression (non-XS), Gavin Smith, 2023/02/12
- Re: texi2any 7.0 performance regression (non-XS), pertusus, 2023/02/12
- Re: texi2any is too slow because of Unicode::Collate, Eli Zaretskii, 2023/02/12
use getSortKey in Unicode::Collate, Gavin Smith, 2023/02/13