You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by Yoshiki Hayashi <yo...@xemacs.org> on 2002/05/06 09:46:48 UTC

Re: cvs commit: httpd-2.0/docs/manual/style ja.xml

yoshiki@apache.org writes:

> yoshiki     02/05/06 00:18:44
> 
>   Added:       docs/manual/mod mod_suexec.ja.xml
>                docs/manual/style ja.xml
>   Log:
>   First cut of Japanese translation of module docs.
>   These files don't play nicely with current transformation scripts yet.

OK, I added Japanese translation of mod_suexec.xml but as in
the log, it can't be transformed to HTML in current setup.
I've started reading XSLT spec and will try to learn Ant but
I'm nowhere near competent at those stuff at the moment so
any help would be appreciated.  Here are the list of things
need to be done:

1. We need the ability to change the encoding attribute of
   xsl:output in manual.xsl.

2. Some hard-coded English text in manual.xsl should be
   moved to en.xml, ja.xml etc.

3. How can I designate XSLT processor to use ja.xml?  My
   guess from looking at the settings.xsl file was to add
   language="ja" to modulesynopsis but it didn't work.

-- 
Yoshiki Hayashi

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


Re: cvs commit: httpd-2.0/docs/manual/style ja.xml

Posted by Yoshiki Hayashi <yo...@xemacs.org>.
Patrik Grip-Jansson <pa...@gnulix.org> writes:

> On 6 May 2002, Yoshiki Hayashi wrote:
> 
> > OK, I added Japanese translation of mod_suexec.xml but as in
> > the log, it can't be transformed to HTML in current setup.
> 
> It seems to be working when using "xsltproc", but not with xalan.

I haven't tried your new manual.xsl yet, but older one
worked with Xalan-J.  Of course, I need to change
<xsl:output method="html" encoding="iso-8859-1" indent="no"/>
to
<xsl:output method="html" encoding="iso-2022-jp" indent="no"/>
so that specified encoding can correctly encode characters.
Perhaps it depends on the Java runtime?  I used Blackdown
Java 1.3.1.

I presume this setting can be conditionalized like $language
stuff in settings.xml.  Could you add logic to choose
encoding by checking modulesynopsis/language?

> > 2. Some hard-coded English text in manual.xsl should be
> >    moved to en.xml, ja.xml etc.
> 
> I'm cleaning up manual.xsl right now, while doing this I'm fixing all
> hard-coded strings. I'll probably commit this with in a couple of hours.

I noticed you have already done that.  Thanks.

> > 3. How can I designate XSLT processor to use ja.xml?  My
> >    guess from looking at the settings.xsl file was to add
> >    language="ja" to modulesynopsis but it didn't work.
> 
> There were some problems using ant and translations. Since I didn't have 
> the time to look into it properly I hard-coded the language to "en". As 
> soon as I've finished the clean up, I'll give it another go...

I'll wait for your next commit on this one.  Thanks in advance.

-- 
Yoshiki Hayashi

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


Re: cvs commit: httpd-2.0/docs/manual/style ja.xml

Posted by Patrik Grip-Jansson <pa...@gnulix.org>.
On 6 May 2002, Yoshiki Hayashi wrote:

> OK, I added Japanese translation of mod_suexec.xml but as in
> the log, it can't be transformed to HTML in current setup.

It seems to be working when using "xsltproc", but not with xalan.

> I've started reading XSLT spec and will try to learn Ant but
> I'm nowhere near competent at those stuff at the moment so
> any help would be appreciated.  Here are the list of things
> need to be done:
> 
> 1. We need the ability to change the encoding attribute of
>    xsl:output in manual.xsl.
> 
> 2. Some hard-coded English text in manual.xsl should be
>    moved to en.xml, ja.xml etc.

I'm cleaning up manual.xsl right now, while doing this I'm fixing all
hard-coded strings. I'll probably commit this with in a couple of hours.
 
> 3. How can I designate XSLT processor to use ja.xml?  My
>    guess from looking at the settings.xsl file was to add
>    language="ja" to modulesynopsis but it didn't work.

There were some problems using ant and translations. Since I didn't have 
the time to look into it properly I hard-coded the language to "en". As 
soon as I've finished the clean up, I'll give it another go...

-- 
.---------------------.
| Patrik Grip-Jansson |
| Ringen 4B           |    .--------------------.
| 78444 Borlänge   .--'----' http://gnulix.com/ `---------.
| Sweden           |  All views and opinions are my own,  |
`------------------| PH:+46(0)24382823 PW:+46(0)707354360 |
                   `--------------------------------------'


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