From: SourceForge.net <no...@so...> - 2009-08-27 08:10:17
|
Feature Requests item #2788497, was opened at 2009-05-07 18:45 Message generated for change (Comment added) made by nijtmans You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=360894&aid=2788497&group_id=10894 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: 44. UTF-8 Strings Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Don Porter (dgp) Assigned to: Jan Nijtmans (nijtmans) Summary: toupper limitations Initial Comment: kbk \u0149 should uppercase to \u02bc\u004e dgp Tcl_UniCharToUpper() cannot represent that. dgp one Tcl_UniChar in; one Tcl_UniChar out. kbk The fundamental assumption underlying Tcl_UniCharToUpper is wrong. ---------------------------------------------------------------------- >Comment By: Jan Nijtmans (nijtmans) Date: 2009-08-27 10:10 Message: How about a simpler path. utf8proc already has ruby bindings, but no Tcl binding. I am planning to write a Tcl stub-enabled extension to utf8proc, with full TEA support. This extension is simply a wrapper to all UTF-8 conversions we need. As soon as this works, we know it is integratable with Tcl. And the development can be done in the utf8proc repository. I only have to become an utf8proc submitter, but I already am talking to Jan Behrens about that. No it won't make 8.6, for sure. I wouln't even try that. ---------------------------------------------------------------------- Comment By: Donal K. Fellows (dkf) Date: 2009-08-27 09:58 Message: OK, my non-technical objections are dealt with. Now it's more to do with the actual details of how to do the integration, but that's not something that I expect to be a show-stopper. Just takes effort. This probably ought to be done on a feature-dev branch so that we can get things sorted out (including what API changes we want) before rolling into the mainline, and that also means it won't make 8.6. ---------------------------------------------------------------------- Comment By: Jan Nijtmans (nijtmans) Date: 2009-08-27 08:53 Message: utf8proc has a new home: http://www.public-software-group.org/utf8proc I think that answers the concern regarding the maintainance of this software. utf8proc is not perfect, and in its current form not even usable for Tcl (e.g. it doesn't compile with MSVC 6). But all this is fixable, and having an organisation as contact point is a big improvement compared to the earlier situation ---------------------------------------------------------------------- Comment By: Jan Nijtmans (nijtmans) Date: 2009-05-08 13:25 Message: yeah, like libtommath ;-) ---------------------------------------------------------------------- Comment By: Donal K. Fellows (dkf) Date: 2009-05-08 11:03 Message: Definitive link is http://www.flexiguided.de/publications.utf8proc.en.html My principal concern is that it doesn't look to be actively maintained. Perhaps it is perfect...? :-) ---------------------------------------------------------------------- Comment By: Jan Nijtmans (nijtmans) Date: 2009-05-08 09:36 Message: On the long run, I don't think it's wise to do all UTF-8 processing specially in Tcl, while there are better solutions outside, e.g. utf8proc: http://freshmeat.net/projects/utf8proc/ I would be in favour of including utf8proc in Tcl, and deprecate Tcl's own UTF-8 handling functions. Anyone knows of (better) alternatives to utf8proc? This is worth a TIP! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=360894&aid=2788497&group_id=10894 |