String encoding in Tcl_CreateCommand commands
From: Donald Arseneau (asnd_at_triumf.ca)
Date: 06/30/04
- Next message: Bruce Hartweg: "Re: TCL under Win98: Paths?"
- Previous message: Bryan Oakley: "Re: TCL under Win98: Paths?"
- Next in thread: Kevin Kenny: "Re: String encoding in Tcl_CreateCommand commands"
- Reply: Kevin Kenny: "Re: String encoding in Tcl_CreateCommand commands"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 29 Jun 2004 20:33:36 -0700
I have an older application with an "old-style string-based"
command created with Tcl_CreateCommand. I wonder what, if
any, conversion Tcl performs on strings when it prepares the
argv argument list. It appears that the character encoding
in argv is UTF-8, regardless of the current LANG setting.
Is this the case?
Internal string-object encoding is unicode, right? It looks
like Tcl calls Tcl_UniCharToUtfDString, maybe, in preparing
the arguments. Well I thought it was unicode, but the Encoding
page says "Tcl's internal character representation, UTF-8".
Is that true?
Whichever the innermost workings, when I get a string, should
I then call Tcl_UtfToExternal to get the expected encoding?
Donald Arseneau asnd@triumf.ca
- Next message: Bruce Hartweg: "Re: TCL under Win98: Paths?"
- Previous message: Bryan Oakley: "Re: TCL under Win98: Paths?"
- Next in thread: Kevin Kenny: "Re: String encoding in Tcl_CreateCommand commands"
- Reply: Kevin Kenny: "Re: String encoding in Tcl_CreateCommand commands"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|