This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

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 <>
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 ='iconv -f TCVN -t UTF-8'.split(), 

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

And the additionally *did* have a copyable VN1 - UCS2 table
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: <>
2016-10-21 21:02:40ztanelinkissue21081 messages
2016-10-21 21:02:40ztanecreate