| 63 |
|
|
| 64 |
When there is a new release of Unicode, the files in Unicode.tables must be |
When there is a new release of Unicode, the files in Unicode.tables must be |
| 65 |
refreshed from the web site. If the new version of Unicode adds new character |
refreshed from the web site. If the new version of Unicode adds new character |
| 66 |
scripts, both the MultiStage2.py and the GenerateUtt.py scripts must be edited |
scripts, the source file ucp.h and both the MultiStage2.py and the |
| 67 |
to add the new names. Then the MultiStage2.py script can then be run to |
GenerateUtt.py scripts must be edited to add the new names. Then the |
| 68 |
generate a new version of pcre_ucd.c and the GenerateUtt.py can be run to |
MultiStage2.py script can then be run to generate a new version of pcre_ucd.c |
| 69 |
generate the tricky tables in pcre_tables.c. |
and the GenerateUtt.py can be run to generate the tricky tables for inclusion |
| 70 |
|
in pcre_tables.c. |
| 71 |
|
|
| 72 |
The ucptest program can then be compiled and used to check that the new tables |
The ucptest program can then be compiled and used to check that the new tables |
| 73 |
in pcre_ucd.c work properly, using the data files in ucptestdata to check a |
in pcre_ucd.c work properly, using the data files in ucptestdata to check a |