On Mon, Feb 25, 2019 at 2:23 PM André Malo <n...@perlig.de> wrote: > William A Rowe Jr wrote: > > On Mon, Feb 25, 2019 at 11:11 AM André Malo <n...@perlig.de> wrote: > > > In this case it might be wise to script it and do all those things at > > > > the same time: > > > - change svnmailer config (somewhere in the svn properties) > > > - possibly change the httpd.conf, but I think, we're good there > > > > Correct, neither of the above should be needed, when the output > > file is named .utf8 and we already correctly process the individual > > language tags before processing the charset (including for svnmailer, > > I would hope!) > > The svnmailer is pretty much agnostic when it comes to extensions. Just > looked > up the config and here's the one for the main manual files: > > $ svn pg svnmailer:content-charset manual/ > # charsets to recognize by the svnmailer > > # Korean > *.xml.ko = euc-kr > *.html.ko.euc-kr = euc-kr > [...] > > If you look at the full output, there is, however, potential for > simplifcation > :-) >
That gave me a headache. Simplified, thanks for the pointers! Once we are done with euc-kr, I'm happy to take care of migrating the limited koi8-r files and we can be done with most exception handling.
