2012/11/20 Richard Hipp <[email protected]>:
> I think that there needs to be two separate versions of
> fossil_utf8_to_unicode(), or perhaps a parameter on one function, so that
> some strings can get the conversion of problematic characters to the unicode
> private-use range, while others go unaltered.
I guess you are completely right! My patch just does it the
'quick-and-dirty' way. It needs more eyes to be sure it
is done correctly. Just see it as a proof-of-concept.
Feel free to improve things on the branch! I will continue
to try it as well.
Thanks! That was a quick response!
Regards,
Jan Nijtmans
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
