TMW->ACIP is much improved. V and W were confused, # and * were
confused; many glyphs that should have yielded errors were not. I've added a test case that transforms every TMW glyph save the one with no TM mapping to ACIP. I hand-checked that it was correct. ACIP->TMW is fixed for # and *. I never noticed it, but each needed an extra swoosh (U+0F05). Round-tripping would be good, as would testing real-world use of TMW->ACIP.
This commit is contained in:
parent
244a9d1370
commit
1bfd3772e6
10 changed files with 1110 additions and 85 deletions
|
@ -23,6 +23,8 @@
|
|||
// glyphs from TMW. 0F6A is not listed here (DLC FIXME: should it be?),
|
||||
// but the glyph for it is the glyph for 0F62.
|
||||
//
|
||||
// The EWTS is not a unique key -- see "r", for example.
|
||||
//
|
||||
// DuffPaneTest ensures that the na-ro column truly contains na-ros,
|
||||
// by the way.
|
||||
//
|
||||
|
@ -70,7 +72,8 @@ __TILDE__X~102,5~~9,102~~~~~~~0F35
|
|||
// though, and we let it become U+0F7E when you convert TMW->Unicode.
|
||||
// That is, we treat them as interchangeable except for in TMW->TM
|
||||
// mappings, where [8,91] does not map to any TM glyph (though you
|
||||
// could argue that it should become what [8,90] becomes).
|
||||
// could argue that it should become what [8,90] becomes -- DLC
|
||||
// FIXME).
|
||||
M~~~8,91~~~~~~~0F7E
|
||||
__TILDE__M~241,1~~8,94~~~~~~~0F83
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue