CP65001 fails (was re: ...)

Mark Lawrence breamoreboy at yahoo.co.uk
Sat Dec 14 22:05:05 CET 2013


On 14/12/2013 20:48, wxjmfauth at gmail.com wrote:
>
>>>> print((os.linesep).join([unicodedata.name(c) for c in u]))
> ETHIOPIC SYLLABLE SEE
> LATIN SMALL LETTER E WITH ACUTE
> EURO SIGN
> CJK UNIFIED IDEOGRAPH-3456
> CYRILLIC CAPITAL LETTER GJE
> COUNTERBORE
> ASTERISK
>
> -----
>
> cp65001, font: Consolas
>
> D:\jm\jmgo>echo "ሴé€㑖Ѓ⌴*"
> "ሴé€㑖Ѓ⌴*"
>
> As I explained some chars are rendered with the .notdef glyph:
> the chars 1, 4 and 7.
>
> I build an exe with the golang. Same result.
>
> Just for curiosity:
> XeTeX -> pdf: same result.
> LucidaConsole CID TrueType,
> Consolas CID TrueType
> understand: "OpenType"
>
> jmf
>

Where is the Python related issue here?  Why do you keep posting double 
spaced crap, despite repeated requests not to do so?  Or do you blame 
this on the allegedly failed PEP 393 FSR implementation?

-- 
My fellow Pythonistas, ask not what our language can do for you, ask 
what you can do for our language.

Mark Lawrence




More information about the Python-list mailing list