Author ztane
Recipients ezio.melotti, jwilk, lemburg, matorban, progfou, serhiy.storchaka, vstinner, ztane
Date 2016-10-21.21:02:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1477083760.3.0.682076123946.issue21081@psf.upfronthosting.co.za>
In-reply-to
Content
Ah there was something that I overlooked before - the VN1 and VN2 both have combining accents too. If I read correctly, the main letter should precede the combining character, just as in Unicode; VN3 seems to lack combining characters altogether.

Thus, for simple text conversion from VN* to Unicode, VN1 should be enough, but some VN2/VN3 control/application specific codes might show up as accented capital letters.

---

The following script rips the table from iconv:

    import subprocess
    mapping = subprocess.run('iconv -f TCVN -t UTF-8'.split(), 
                             input=bytes(range(256)), 
                             stdout=subprocess.PIPE).stdout.decode()

There were several aliases but all of them seemed to produce identical output. Output matches the VN1 from the tables.

And the luatvn.net additionally *did* have a copyable VN1 - UCS2 table
History
Date User Action Args
2016-10-21 21:02:40ztanesetrecipients: + ztane, lemburg, vstinner, jwilk, ezio.melotti, progfou, serhiy.storchaka, matorban
2016-10-21 21:02:40ztanesetmessageid: <1477083760.3.0.682076123946.issue21081@psf.upfronthosting.co.za>
2016-10-21 21:02:40ztanelinkissue21081 messages
2016-10-21 21:02:40ztanecreate