Re: Improving i18n support (Was: Re: Christmas
- From: Michael Schlenker <schlenk@xxxxxxxxxxxxxxxx>
- Date: Fri, 29 Dec 2006 20:44:01 +0100
Larry W. Virden schrieb:
Kevin Kenny wrote:One option to do something like your thinking about would be to use the
Larry W. Virden wrote:
The most surprising thing to me, as a developer, is that I'm expectedThat's surely a restriction of whatever editor you're using, not of Tcl.
to use obscure binary/octal/hex codes when attempting to write unicode
strings . That seems so... archaic.
Hmm - perhaps my description was either short sighted or misguided.
Here's the point I was trying to make. ascii strings like "\u084" or
whatever is how I most frequently see people code Unicode into tcl
scripts. However, after reading your comment, I now understand that
inserting Unicode binary directly into scripts is also an option.
However, that would be the equivalent of encoding the hex ascii string
or a binary character for a newline into a Tcl script.
I'm just wishing that, like \r, \n, \t and so forth, Tcl easily had
some sort of normal, 7 bit ascii shorthand for unicode characters, so
that, for instance, someone reading the code could tell what the
strings meant. Right now, attempting to read tcl scripts with Unicode
tell me nothing about the strings if the direct binary is present (I
don't have full unicode fonts available) and even the \u084 style
notation also doesn't tell me anything either.
long names mentioned in the unicode tables, but in general they are
rather longish and embedding the true character as utf-8 or using the
hex code is a more convenient.
For the \u notation i find the unicode charts (as pdf) especially useful
if i don't have a usable font:
http://www.unicode.org/charts/PDF/
Michael
.
- References:
- Christmas
- From: Ian Bell
- Re: Christmas
- From: jkj
- Re: Christmas
- From: Stephan Kuhagen
- Re: Christmas
- From: Andreas Leitgeb
- Re: Christmas
- From: Donal K. Fellows
- Improving i18n support (Was: Re: Christmas
- From: Larry W. Virden
- Re: Improving i18n support (Was: Re: Christmas
- From: Donal K. Fellows
- Re: Improving i18n support (Was: Re: Christmas
- From: Larry W. Virden
- Re: Improving i18n support (Was: Re: Christmas
- From: Kevin Kenny
- Re: Improving i18n support (Was: Re: Christmas
- From: Larry W. Virden
- Christmas
- Prev by Date: Re: Is Tcl work for large programs?
- Next by Date: Re: Tcl_DumpActiveMemory and tk
- Previous by thread: Re: Improving i18n support (Was: Re: Christmas
- Next by thread: Re: Improving i18n support (Was: Re: Christmas
- Index(es):
Relevant Pages
|