/
usr
/
share
/
doc
/
perl-Text-Unidecode
/
/usr/share/doc/perl-Text-Unidecode
mkdir
upload
Name
Size
Mode
Actions
ChangeLog
8135
0644
edit
dl
rm
README
5268
0644
edit
dl
rm
TODO.txt
5053
0644
edit
dl
rm
Edit:
/usr/share/doc/perl-Text-Unidecode/TODO.txt
(5053B)
# -*-coding:utf-8;-*- ·················································· # Last Modified Time-stamp: "2015-10-16 03:34:44 MDT sburke@cpan.org" #====================================================================== ~~ Text::Unidecode TODO file ~~ TODO: make the table files be built from the Unicode character database, transitioning from the values in the current table files. I used to have a whole bunch of concise files that compiled to the xXX.pm table files. But they're in a file format I haven't dealt with since 2001, so screw it all, I'm starting from zero and it will be... well, you'll see. (Presumably the Hangul and the Unihan blocks are outside the scope of that whole ruckus of named characters.) TODO GTD: Keep plugging in suggestions from Tomaž Šolc's message TODO: Figure out how to courteously declare dependencies in my Makefile.PL TODO: Bundle with a "unidecode" util that calls a routine in Unidecode.pm? Or maybe just show it as a one-liner in the POD? TODO: Also show it with an example use with iconv TODO: Plow through more bug reports, applying patches etc, especially stuff from that nice Tomaž Šolc man. TODO: ***DEFINITELY*** Make it handle stuff in Astral Plane (over U+FFFF) Take that plunge, or ascend into the plane, or whatever. DOIT. TODO: Currently, all the files are in Unix newline format (LF). Maybe CR+LF is technically more universal, and I could switch to that. But so far I've gotten no complaints that I should go do that. TODO: THEN re-run the thing that reads the Unihan database and generates all the Text/Unidecode/__.pm files. (Do the hyperspace handling first, because lots of Unihan stuff is up there.) TODO: Look to see whether I need to deal with the Arabic stuff in the U+FBxx etc blocks. I thought it was always just font-internal stuff, but I'm starting to suspect that it may be encountered in the real world TODO: Of course: - Check for new glyphs in existing tables. - Look at whole new tables (like the Philippine scripts) in normal space (x < U+FFFF) - Look at the wild wilderness in hyperspace (x > U+FFFF ====================================================================== ====================================================================== ######################################################################## Below here is TODOs from the Unicode version in 2001. Yes, that long ago. ============================== BLOCK 09 ============================== What's an isshar? (09FA = "bengali isshar") ============================== BLOCK 0b ============================== What's an isshar? (0B70 = "oriya isshar") ============================== BLOCK 0e ============================== What is 0E4C = "thai character thanthakhat" ? What is 0E4E = "thai character yamakkan" ? ============================== BLOCK 0f ============================== Various questions to do with Tibetan (0f00-0fff)... A lot of these characters end up as "". What to do with them? How to represent these Astrological signs, 0F15-0F1F ? What is a 0F38 = "Tibetan mark Che Mgo" ? Should I leave "Marks and Signs" (0F82-0F87) as ""? What to do with "Transliteration head letters" (0F88-0F8B) ? ============================== BLOCK 11 ============================== Various Hangul components need checking: What are chitueumsios, chitueumssangsios, ceongchieumsios, and ceongchieumssangsios? Is "Z" a good transliteration for pansios? I'm using "N" for yesieung and kapyeoun both. Is this right? What are chitueumcieuc, chitueumssangcieuc, ceongchieumcieuc, ceongchieumssangcieuc, chitueumchieuch, and ceongchieumchieuch? Is "kapyeounphieuph" best transliterated as "Np" or "pN"?, and so on for: kapyeounrieul, kapyeounmieum, kapyeounpieup, kapyeounssangpieup, kapyeounphieuph I'm using "Q" for yeorinhieuh, apparently an archaic glottal stop character. Is that right? ============================== BLOCK 14 ============================== How to transliterate 0x1426, AKA "canadian syllabics final double short vertical strokes"? How to transliterate 0x1429, AKA "canadian syllabics final plus"? ============================== BLOCK 16 ============================== Fact-check the Ogham and Runes. What are eabhadh, or, uilleann, ifin, eamhancholl, and peith (1695-169A)? ============================== BLOCK 18 ============================== What's 180A = "Mongolian nirugu" ? ============================== BLOCK 31 ============================== I leave the Kaeriten (3190-319F) as null-string. Is that good? ============================== BLOCK fb ============================== Arabic Presentation Forms-A (FB50-FDFF) -- do I need to do these, or are they never actually found in text files? ============================== BLOCK fe ============================== Arabic Presentation Forms-B (FE70-FEFF) -- do I need to do these, or are they never actually found in text files? ====================================================================== (end)
Save
cmd:
run