Bug 8535 – perfectly valid uncidoe chars give: "Unsupported char xxx"

Status
RESOLVED
Resolution
INVALID
Severity
normal
Priority
P2
Component
dmd
Product
D
Version
D2
Platform
All
OS
All
Creation time
2012-08-10T14:19:00Z
Last change time
2012-08-10T14:29:40Z
Assigned to
nobody
Creator
dmitry.olsh

Attachments

IDFilenameSummaryContent-TypeSize
1137new.dtables with "wrong" charstext/plain70375

Comments

Comment #0 by dmitry.olsh — 2012-08-10T14:19:07Z
When compiling unicode casefolding table (see attach it's a plain string table) dmd outputs this: Error: unsupported char 0x2d17 Error: unsupported char 0x2c11 Error: unsupported char 0x2c41 Error: unsupported char 0xa726 Error: unsupported char 0xa727 Error: unsupported char 0x2d18 Error: unsupported char 0x2c12 Error: unsupported char 0x2c42 Error: unsupported char 0x2d19 Error: unsupported char 0x2c13 Error: unsupported char 0x2c43 Error: unsupported char 0xa728 Error: unsupported char 0xa729 Error: unsupported char 0x2d1a Error: unsupported char 0x2c14 Error: unsupported char 0x2c44 Error: unsupported char 0x2d1b Error: unsupported char 0x2c15 Error: unsupported char 0x2c45 Error: unsupported char 0xa72a Error: unsupported char 0xa72b All of the above a perfectly valid characters, and in fact have mappings lower case -- upper case. So either DMD reject chars it doesn't know (wrong way - see Unicode standard) or has broken validiation. About characters see here : http://unicode.org/cldr/utility/list-unicodeset.jsp?a=%5Cu2d17%0D%0A%5Cu2c11%0D%0A%5Cu2c41%0D%0A%5Cua726%0D%0A%5Cua727%0D%0A%5Cu2d18%0D%0A%5Cu2c12%0D%0A%5Cu2c42%0D%0A%5Cu2d19%0D%0A%5Cu2c13%0D%0A%5Cu2c43%0D%0A%5Cua728%0D%0A%5Cua729%0D%0A%5Cu2d1a%0D%0A%5Cu2c14%0D%0A%5Cu2c44%0D%0A%5Cu2d1b%0D%0A%5Cu2c15%0D%0A%5Cu2c45%0D%0A%5Cua72a%0D%0A%5Cua72b&g=
Comment #1 by dmitry.olsh — 2012-08-10T14:20:05Z
Created attachment 1137 tables with "wrong" chars
Comment #2 by dmitry.olsh — 2012-08-10T14:29:40Z
Scratch that, string were not escaped... I had to catch some sleep :)