| 70 |
can be run to generate a new version of pcre_ucd.c, and GenerateUtt.py can be |
can be run to generate a new version of pcre_ucd.c, and GenerateUtt.py can be |
| 71 |
run to generate the tricky tables for inclusion in pcre_tables.c. |
run to generate the tricky tables for inclusion in pcre_tables.c. |
| 72 |
|
|
| 73 |
|
If MultiStage2.py gives the error "ValueError: list.index(x): x not in list", |
| 74 |
|
the cause is usually a missing (or misspelt) name in the list of scripts. I |
| 75 |
|
couldn't find a straightforward list of scripts on the Unicode site, but |
| 76 |
|
there's a useful Wikipedia page that list them, and notes the Unicode version |
| 77 |
|
in which they were introduced: |
| 78 |
|
|
| 79 |
|
http://en.wikipedia.org/wiki/Unicode_scripts#Table_of_Unicode_scripts |
| 80 |
|
|
| 81 |
The ucptest program can be compiled and used to check that the new tables in |
The ucptest program can be compiled and used to check that the new tables in |
| 82 |
pcre_ucd.c work properly, using the data files in ucptestdata to check a number |
pcre_ucd.c work properly, using the data files in ucptestdata to check a number |
| 83 |
of test characters. |
of test characters. The source file ucptest.c must be updated whenever new |
| 84 |
|
Unicode script names are added. |
| 85 |
|
|
| 86 |
|
Note also that both the pcresyntax.3 and pcrepattern.3 man pages contain lists |
| 87 |
|
of Unicode script names. |
| 88 |
|
|
| 89 |
|
|
| 90 |
Preparing for a PCRE release |
Preparing for a PCRE release |