| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This was added in the 5.17 series so there's no code relying on its
current name. I think that the abbreviation is clearer.
|
|
|
|
|
|
| |
This now uses the U+ notation to indicate code points, which is
unambiguous not matter what the platform's character set is. (charnames
accepts the U+ notation)
|
|
|
|
|
| |
This was added in the 5.17 series, so can't be yet in the field; and
isn't needed.
|
|
|
|
|
|
|
|
|
|
| |
join_exact() prior to this commit returned a delta for 3 problematic
sequences showing that the minimum length they match is less than their
nominal length. It turns out that this is needed for all
multi-character fold sequences; our test suite just did not have the
tests in it to show that. Tests that do show this will be added in a
future commit, but code elsewhere must be fixed before they pass.
regcomp.c
|
|
|
|
|
|
|
| |
A future commit will want to use the first surrogate code point's UTF-8
value. Add this to the generated macros, and give it a name, since
there is no official one. The program has to be modified to cope with
this.
|
|
|
|
|
|
|
|
|
|
| |
A previous commit has caused macros to be generated that will match
Unicode code points of interest to the \X algorithm. This patch uses
them. This speeds up modern Korean processing by 15%.
Together with recent previous commits, the throughput of modern Korean
under \X has more than doubled, and is now comparable to other
languages (which have increased themselved by 35%)
|
|
The recently added utf8_strings.h has been expanded to include more than
just strings. I'm renaming it to avoid confusion.
|