skaller wrote: > Ops like trim/strip will simply miss some whitespaces, they won't > do the wrong thing provided they treat high bit set chars as non-space. >
That's only if you're using trim/strip to remove whitespace. You can also use them to trim substrings, or strip all the chars in a string. Those won't work on unicode. >> How can we deal with this? >> > > We don't, it needs user libraries, some of which are extremely > expensive because they need tables of 30,000 characters. > We could just wrap one of the apis. >> But it might be better to just write it in felix. >> > > Probably better in C++ because then it is pre-compiled. > Felix code gets compiled every time. > We really need to get precompiling felix code working :) > Also, considerable expertise is required to maintain > a library, why not let the project team working on it > do that? We're short of resources. > That's sadly true. > But i have no idea if that library is useful: our RTL already > has a UTF-8 codec I wrote. > I missed that. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
