On Thu, Sep 13, 2012 at 2:08 PM, Richard Hipp wrote: > It would be an interesting project to enhance Fossil so that it could > support UTF16 in addition to UTF8. What would be needed is an algorithm to > detect when a file was UTF16. (The BOM at the beginning of Kevin's example > ought to be a big hint.) Then automatically call a convert routine to > generate UTF8 prior to passing the content into the diff logic, or into the > wiki engine, or prior to display on the UTF8 webpage, etc. > [...]
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. I'm not a git user, but as far as I know, git has a generic text filtering framework that is capable of the above. Regards, Csaba PS I'm a new list member, so I'll take this opportunity to briefly introduce myself. I've been using fossil for a while and love the integrated wiki and simplicity. I work in a multi-platform environment (Linux, Win, Mac), so I bump into the EOL problem every day. Because of that, I have started working on some EOL handling patches for fossil, mostly to make my life easier. :) But it would be great to have character encoding conversion support as well. PS to Richard: contributor agreement should be arriving shortly! _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
