You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by Eunju Kang <to...@gmail.com> on 2019/02/25 12:05:14 UTC

Translating Korean Documentation

Hello. I am Eunju, working on open source technical support from South
Korea.
I'm interested in translating Korean documentation and want to try.

I have several questions before starting.

1. I saw the status on this site.
   http://home.apache.org/~takashi/translation-status/test.html#2.4
   Can I translate any documents that have not been translated or out-dated?
2. Encoding of all xml.ko documents is EUC-KR. Is it ok I change this to
UTF-8 according to your guidelines?

it's all.
thank you :)

Re: Translating Korean Documentation

Posted by André Malo <nd...@perlig.de>.
On Dienstag, 26. Februar 2019 11:30:53 CET Lucien Gentis wrote:
> Hi,
> 
> First, let's wait for some korean file to commit.
> 
> Summary for switching fr language to UTF-8 :
> 
> 1. Replace all occurrences of "ISO-8859-1" by "UTF-8" in following files :
> manual/style/manual.fr.xsl
> manual/style/xsl/util/designations.xml (only for fr line)
> manual/style/lang/fr.xml

> 
> 2. Replace all occurrences of "html.fr" by "html.fr.utf8" in following
> files :
> 
> manual/style/xsl/util/designations.xml
> manual/style/lang-targets.xml
> manual/style/lang/fr.xml

Actually, just change lang/fr.xml (both for encoding and extension) and then 
run `build bootstrap`. That should cover all this.

Originally it was made for adding new languages, but of course, changes go 
the same way.

> 
> 3. Rename all *.html.fr files to *.html.fr.utf8 through "svn mv ..."
> command then rebuild (am I right, André ?)

check.

> 
> 4. Change svnmailer:content-charset property of manual/ through this
> command :
> 
> svn pe svnmailer:UTF-8 manual

svn pe svnmailer:content-charset manual

On Folders it allows for elaborate globs for all the expected files.

On files it allows only setting it for that file:

svn ps svnmailer:content-charset UTF-8 lang/fr.xml

and then commit.

(and now I hope, I didn't miss anything :-)
Cheers,

> 
> Le 25/02/2019 à 21:23, André Malo a écrit :
> > 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> 
> > :-)
> > 
> > The language files are special, they're configured individually:
> > 
> > $ svn pg svnmailer:content-charset manual/style/lang/*.xml
> > [...]
> > manual/style/lang/ko.xml - euc-kr
> > [...]
> > 
> > Cheers,
> > nd
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
> For additional commands, e-mail: docs-help@httpd.apache.org


-- 
package Hacker::Perl::Another::Just;print
qq~@{[reverse split/::/ =>__PACKAGE__]}~;

#  André Malo  #  http://pub.perlig.de  #



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: Translating Korean Documentation

Posted by Lucien Gentis <lu...@univ-lorraine.fr>.
Hi,

First, let's wait for some korean file to commit.

Summary for switching fr language to UTF-8 :

1. Replace all occurrences of "ISO-8859-1" by "UTF-8" in following files :
manual/style/manual.fr.xsl
manual/style/xsl/util/designations.xml (only for fr line)
manual/style/lang/fr.xml

2. Replace all occurrences of "html.fr" by "html.fr.utf8" in following 
files :

manual/style/xsl/util/designations.xml
manual/style/lang-targets.xml
manual/style/lang/fr.xml

3. Rename all *.html.fr files to *.html.fr.utf8 through "svn mv ..." 
command then rebuild (am I right, André ?)

4. Change svnmailer:content-charset property of manual/ through this 
command :

svn pe svnmailer:UTF-8 manual

(am I still right, André ?)



Le 25/02/2019 à 21:23, André Malo a écrit :
> 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
> :-)
>
> The language files are special, they're configured individually:
>
> $ svn pg svnmailer:content-charset manual/style/lang/*.xml
> [...]
> manual/style/lang/ko.xml - euc-kr
> [...]
>
> Cheers,
> nd

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: Translating Korean Documentation

Posted by William A Rowe Jr <wr...@rowe-clan.net>.
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.

Re: Translating Korean Documentation

Posted by André Malo <nd...@perlig.de>.
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 
:-)

The language files are special, they're configured individually:

$ svn pg svnmailer:content-charset manual/style/lang/*.xml
[...]
manual/style/lang/ko.xml - euc-kr
[...]

Cheers,
nd
-- 
Ook. Ook. Ook. Ook. Ook. Ook. Ook. Ook. Ook. Ook. Ook. Ook. Ook. Ook.
Ook! Ook? Ook. Ook? Ook. Ook. Ook. Ook. Ook. Ook. Ook. Ook. Ook. Ook.
Ook. Ook. Ook. Ook. Ook? Ook. Ook! Ook! Ook? Ook! Ook. Ook? Ook. Ook.
Ook. Ook. Ook. Ook. Ook! Ook. Ook! Ook! Ook! Ook!           Ook! Ook.



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: Translating Korean Documentation

Posted by William A Rowe Jr <wr...@rowe-clan.net>.
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!)

Re: Translating Korean Documentation

Posted by André Malo <nd...@perlig.de>.
Hi,

welcome as well and thanks for taking up this task.

Regarding the encoding change: Do we want to change the output files as 
well? In this case it might be wise to script it and do all those things at 
the same time:

- rename html.ko.euc-kr  to html.ko.utf-8
- change the config to actually generate those files
- change svnmailer config (somewhere in the svn properties)
- possibly change the httpd.conf, but I think, we're good there

This will give the least hassle on the commit list :-)
If we want that, I can help out and just do it.

Regarding the outdated files: After a successful local build, you'll also 
find a file ".outdated.ko" in the manual directory, which lists all outdated 
files.

Cheers,
nd


On Montag, 25. Februar 2019 17:05:32 CET Lucien Gentis wrote:
> Hello Eunju,
> 
> First of all, welcome in the translation team.
> 
> I am part of the french translation team and can help you during your
> translation works.
> 
> If you didn't already do it, you can begin reading this :
> http://httpd.apache.org/docs-project/translations.html and particularly
> "Getting started"
> 
> Concerning coding, yes you can change it to UTF-8
> 
> What you have to do yet is searching in
> http://home.apache.org/~takashi/translation-status/test.html#trunk what
> is to translate/update. You must first translate document in trunk
> (development) branch, then port it to current (2.4) branch.
> 
> When you have finished translating an XML file, it should be reread by
> another Korean speaker, then you can send the document to this list; we
> will commit it to the doc for you.
> 
> Lucien
> 
> Le 25/02/2019 à 13:05, Eunju Kang a écrit :
> > Hello. I am Eunju, working on open source technical support from South
> > Korea.
> > I'm interested in translating Korean documentation and want to try.
> > 
> > I have several questions before starting.
> > 
> > 1. I saw the status on this site.
> > http://home.apache.org/~takashi/translation-status/test.html#2.4
> >    Can I translate any documents that have not been translated or
> > out-dated?
> > 2. Encoding of all xml.ko documents is EUC-KR. Is it ok I change this
> > to UTF-8 according to your guidelines?
> > 
> > it's all.
> > thank you :)
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
> For additional commands, e-mail: docs-help@httpd.apache.org


-- 
Winnetous Erbe: <http://pub.perlig.de/books.html#apache2>



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: Translating Korean Documentation

Posted by Lucien Gentis <lu...@univ-lorraine.fr>.
Hello Eunju,

First of all, welcome in the translation team.

I am part of the french translation team and can help you during your 
translation works.

If you didn't already do it, you can begin reading this : 
http://httpd.apache.org/docs-project/translations.html and particularly 
"Getting started"

Concerning coding, yes you can change it to UTF-8

What you have to do yet is searching in 
http://home.apache.org/~takashi/translation-status/test.html#trunk what 
is to translate/update. You must first translate document in trunk 
(development) branch, then port it to current (2.4) branch.

When you have finished translating an XML file, it should be reread by 
another Korean speaker, then you can send the document to this list; we 
will commit it to the doc for you.

Lucien

Le 25/02/2019 à 13:05, Eunju Kang a écrit :
> Hello. I am Eunju, working on open source technical support from South 
> Korea.
> I'm interested in translating Korean documentation and want to try.
>
> I have several questions before starting.
>
> 1. I saw the status on this site.
> http://home.apache.org/~takashi/translation-status/test.html#2.4
>    Can I translate any documents that have not been translated or 
> out-dated?
> 2. Encoding of all xml.ko documents is EUC-KR. Is it ok I change this 
> to UTF-8 according to your guidelines?
>
> it's all.
> thank you :)
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org