sholden at holdenweb.com
Fri Mar 23 05:37:09 CET 2001
That's impressively well-though-out. Although really I meant Unicode
literals in Python sources, which might be a horse of a different color.
"Emile van Sebille" <emile at fenx.com> wrote in message
news:99ej5k$t8im$1 at ID-11957.news.dfncis.de...
> What's unicode look like in hex? How would I test it?
> Oh wait, from the Help page:
> How to Work with Unicode Files
> TextPad automatically detects 16-bit Unicode and UTF-8 encoded characters,
> when opening files. Unicode characters may be in "little endian" (Intel)
> "big endian" (RISC) order, and the order is preserved when a file is
> Internally, these files are converted to single or double byte characters
> (DBCS), using the locale corresponding to the font script selected for the
> document class. For example, if the screen font for the Text document
> is MS Mincho, with the script set to Japanese, Unicode characters in *.TXT
> files will be converted to the corresponding DBCS characters in code page
> Emile van Sebille
> emile at fenx.com
> "Steve Holden" <sholden at holdenweb.com> wrote in message
> news:sqzu6.12865$_46.475246 at e420r-atl2.usenetserver.com...
> > "Emile van Sebille" <emile at fenx.com> wrote in message
> > news:99cv2t$f20g$1 at ID-11957.news.dfncis.de...
> > >
> > > For windows, I like textpad http://www.textpad.com/ beause it uses
> > > workspaces, has a hex display mode, runs code in a separate process,
> > > supports other languages (programming and spoken), and generally
> > > well.
> > >
> > > Emile van Sebille
> > > emile at fenx.com
> > >
> > Does it show Unicode string constants correctly in hex?
> > regards
> > Steve
More information about the Python-list