On Sat, Sep 15, 2012 at 6:00 PM, Michal Suchanek <hramr...@gmail.com> wrote: > On 15 September 2012 04:20, Csaba Kos <csaba....@gmail.com> wrote: > >> I think now would be a good time to discuss the possibility of a more generic >> text conversion framework, i.e. not only UTF16 to UTF8 but also SHIFT-JIS >> to UTF8, and so on. Also CR+NL to NL conversion could be handled by such >> framework as well. One possibility is to support calling of an external >> command >> which could be specified in some "...-glob" setting. >> > > This is not such a good idea. Converting well-formed UTF-16 into UTF-8 > is lossless and fully reversible [...] > SJIS conversion and CR/LF conversion do not behave that way.
Such conversions would have to be requested by the user explicitly (by setting some property), and if some conversion problem occurs (for example the file has mixed line endings), we can simply error out or warn the user. I agree that more generic conversions can be troublesome to implement safely and neatly, but at least the EOL conversion is a must have feature IMHO. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
