Re: Improving i18n support (Was: Re: Christmas
- From: "Donal K. Fellows" <donal.k.fellows@xxxxxxxxxxxxxxxx>
- Date: Fri, 29 Dec 2006 20:35:56 GMT
Larry W. Virden wrote:
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.
Alas, you're SOL there because we're not about to go out and define a
neatly readable escape sequence for all 65000 or so UNICODE characters
that are not in ASCII. Far far too much work...
Donal.
.
- 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: Tcl_DumpActiveMemory and tk
- Next by Date: Re: How to rotate a complex object on the canvas
- Previous by thread: Re: Improving i18n support (Was: Re: Christmas
- Next by thread: Re: Improving i18n support (Was: Re: Christmas
- Index(es):
Relevant Pages
|