On Mar 31, 2017, at 1:42 PM, Andy Bradford <amb-fos...@bradfords.org> wrote: > > You could have continued on the way you were > doing things. No need to change anything except tell your browser that > the content is not Unicode, but is instead ``Western'' or ISO-8895-1 or > something else.
That only fixes one browser on one machine. The browser is just obeying what Fossil tells it in the Content Type header. The minimal fix, if someone wants their Fossil instance to serve ISO-8859 or similar over HTTP would be to modify the hard-coded “utf-8” declaration in src/cgi.c. Then browsers would understand how to render the content given. I don’t think that would let you have non-ASCII or non-UTF-8 characters in, say, checkin comments, though. To fix that, you’d probably have to make a whole lot in invasive changes to all the code that selects either UTF-8 or UTF-16 depending on the platform. Messy. The main thrust of my prior replies to this thread isn’t that people should throw away working and preferred tools, it’s that UTF-8 is a solved problem now, and has been solved for a long time. Someone brought up TECO. I don’t expect anyone’s TECO implementation to handle UTF-8, but that doesn’t count as “in 2017,” any more than watching Casablanca in 2017 would cause the movie to be set “in 2017.” But if you’re using a 20-year-old version of nvi, *that* problem has a solution. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
