Am 22.03.2012 10:19, schrieb Massimo Manghi: > Thank you Jeff for the suggestion > > the PHP implementation looks more elaborate and complete, supporting more > than a single encoding and several ways to perform the translation. > > I think this justifies the adoption of rather general terms for > their commands. We may choose a lower profile adding the basic initial > implementation and keeping the door open for other encodings > (adding ISO-8859-1 should be trivial). The command could be > > ::rivet::encode <string> ?-encoding <encoding-name>? > ::rivet::decode <string> ?-encoding <encoding-name>? > > we have to make clear in the docs that current implementation supports > only UTF-8. There is still something that keeps me from adopting this > name wholeheartedly.
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 --------------------------------------------------------------------- To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
