On 22.03.2012 10:31, Harald Oehlmann wrote:
I am sorry, IMHO this overstates the case.
IMHO, there is no need to support other encodings. One would use to
prepare the string with "encoding convertfrom" but this is rarely
needed. We need a tool to output html dynamic text. As utf8 is the
default Tcl encoding (e.g.) we have everything in utf8.
By the way, I have asked on clt, if it would be possible to use
"encoding convertto" to do html entities:
http://groups.google.com/group/comp.lang.tcl/browse_thread/thread/7d6b2aace01d7043#
-Harald
I hate to leave half baked ideas around...:-( I'm rather obsessive at
this and
I have too many things left around on my desk, if I can finish one I
have
a chance to feel better.
Therefore I'm exploiting 'encoding convertto' to support more than one
encoding,
use UTF-8 and intermediate encoding and then output html entities.
Perhaps no one will use it, but it won't be only unused component of
Rivet. I've been
working on an application that gets data and templates from different
sources
which may well use different encodings, so it won't be completely
useless for me
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
