| commit | fb7b01eeb99242f1c63e62178392173a136f8d7e | |
| author | Vitaliy Filippov <vitalif@yourcmc.ru> | |
| Mon, 30 May 2011 16:16:14 +0000 (30 19:16 +0300) | ||
| committer | Slava Zanko <slavazanko@gmail.com> | |
| Fri, 8 Jul 2011 14:28:07 +0000 (8 17:28 +0300) | ||
| tree | dc504db9a3ab9e6a60f6bff5deb5da0eea351ab3 | treesnapshot (tar.gz zip) |
| parent | 3ced63361b4280ef69cfb737ded15278a5dbf73a | commitdiff |
Despite of the fact that algorithm now ignores the absence of closing curly
brace '}' (which probably isn't 100% correct), this should be checked in tests
for replace_handle_esc_seq function, not process_escape_sequence - it is the
replace_handle_esq_seq who decides whether it is an escape sequence or not.
Also, \x{4344} is usually a code for wide character (UTF-8), and not for "CD".
So we can either ignore the higher bits, or generate wide character codes...
The second would be convenient, but would also introduce a hard-coded UTF-8 charset.
Signed-off-by: Slava Zanko <slavazanko@gmail.com>
Signed-off-by: Andrew Borodin <aborodin@vmail.ru>
brace '}' (which probably isn't 100% correct), this should be checked in tests
for replace_handle_esc_seq function, not process_escape_sequence - it is the
replace_handle_esq_seq who decides whether it is an escape sequence or not.
Also, \x{4344} is usually a code for wide character (UTF-8), and not for "CD".
So we can either ignore the higher bits, or generate wide character codes...
The second would be convenient, but would also introduce a hard-coded UTF-8 charset.
Signed-off-by: Slava Zanko <slavazanko@gmail.com>
Signed-off-by: Andrew Borodin <aborodin@vmail.ru>