Grammatica - Bugs: bug #7874, Unicode character references
You are not allowed to post comments on this tracker with your current authentication level.
bug #7874: Unicode character references
Submitter: | None | ||
Submitted: | Tue 24 Feb 2004 04:01:53 PM UTC | ||
Severity: | 5 - Major | Item Group: | Documentation |
Status: | None | Assigned to: | cederberg |
Open/Closed: | Open |
Thu 26 Feb 2004 11:07:16 AM UTC, comment #2: |
Per Cederberg <cederberg>![]() ![]() |
Tue 24 Feb 2004 04:12:27 PM UTC, comment #1: BTW, I submitted it (dcazzulino, that is). |
Daniel Cazzulino <dcazzulino> |
Tue 24 Feb 2004 04:01:53 PM UTC, original submission:
One consequence of not using SDK built-in regular expression support is that unicode support is not available. For example, the XML grammar defines Char as follows:
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2004-02-26 | cederberg | Item Group | Software | ![]() |
Documentation |
Assigned to | None | ![]() |
cederberg |
This seems to be a documentation bug, more than anything. The Grammatica RE:s support unicode character references in the following way:
\uFFFF (where FFFF is the Unicode hexadecimal code)
So the example above would be expressed in the following way (untested):
Char = <<\x09|\x0A|\x0D|[\u0020-\uD7FF]|[\uE000-\uFFFD]>>
Note the use of \x for two-character hexadecimal encoding and \u for four-character encoding. Also note that the character sequence [#x10000-#x10FFFF] has been omitted, see bug #7916 for more information.