diff options
| author | ptmcg <ptmcg@austin.rr.com> | 2018-10-28 10:52:23 -0500 |
|---|---|---|
| committer | ptmcg <ptmcg@austin.rr.com> | 2018-10-28 10:52:23 -0500 |
| commit | 1f6c7f195b54cd5bbcfae38b4855be78563d8f46 (patch) | |
| tree | 084817a95a73126dfda07ebbc4da2921c07d4dde | |
| parent | cf3930e29796f361c2c1b5822ab80618655099e4 (diff) | |
| download | pyparsing-git-pp_unicode.tar.gz | |
Update CHANGES blurb on unicode sets, prep for 2.3.0 releasepp_unicode
| -rw-r--r-- | CHANGES | 20 |
1 files changed, 13 insertions, 7 deletions
@@ -2,19 +2,25 @@ Change Log
==========
-Version 2.3.0 - TBD
--------------------
+Version 2.3.0 - October, 2018
+-----------------------------
- NEW SUPPORT FOR UNICODE CHARACTER RANGES
This release introduces the pyparsing_unicode namespace class, defining
a series of language character sets to simplify the definition of alphas,
- nums, printables, etc. in the following language sets:
+ nums, alphanums, and printables in the following language sets:
+ . Arabic
. Chinese
- . Japanese (including Kanji, Katakana, and Hirigana subsets)
- . Korean
- . Greek
. Cyrillic
- . Arabic
+ . Devanagari
+ . Greek
. Hebrew
+ . Japanese (including Kanji, Katakana, and Hirigana subsets)
+ . Korean
+ . Latin1 (includes 7 and 8-bit Latin characters)
+ . Thai
+ . CJK (combination of Chinese, Japanese, and Korean sets)
+ There is also an `all` attribute on each that contains all characters
+ in the set.
For example, your code can define words using:
|