[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-docs
Subject:    Re: Translating Korean Documentation
From:       William A Rowe Jr <wrowe () rowe-clan ! net>
Date:       2019-02-26 17:36:36
Message-ID: CACsi253wgJ0HJb2kBshCXivXOcctEz-MSyeF8c99CkP5Lhvwmw () mail ! gmail ! com
[Download RAW message or body]

On Mon, Feb 25, 2019 at 2:23 PM André Malo <nd@perlig.de> wrote:

> William A Rowe Jr wrote:
> > On Mon, Feb 25, 2019 at 11:11 AM André Malo <nd@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.

[Attachment #3 (text/html)]

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



[prev in list] [next in list] [prev in thread] [next in thread]