You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by André Malo <nd...@perlig.de> on 2004/02/07 18:31:21 UTC
Shift_Jis for generated japanese output?
* nd@apache.org wrote:
> nd 2004/02/07 09:28:26
>
> Modified: docs/manual configuring.html.ja.jis
> content-negotiation.html.ja.jis mpm.html.ja.jis
> new_features_2_0.html.ja.jis
> server-wide.html.ja.jis upgrading.html.ja.jis
> docs/manual/howto htaccess.html.ja.jis
> public_html.html.ja.jis
> docs/manual/mod core.html.ja.jis mod_actions.html.ja.jis
> mod_alias.html.ja.jis mod_authz_host.html.ja.jis
> mod_cgi.html.ja.jis mod_cgid.html.ja.jis
> mod_deflate.html.ja.jis mod_expires.html.ja.jis
> mod_headers.html.ja.jis mod_info.html.ja.jis
> mod_log_config.html.ja.jis
> mod_negotiation.html.ja.jis
> mod_setenvif.html.ja.jis mod_so.html.ja.jis
> mod_speling.html.ja.jis mod_unique_id.html.ja.jis
> mpm_common.html.ja.jis prefork.html.ja.jis
> quickreference.html.ja.jis
> docs/manual/ssl ssl_intro.html.ja.jis
> Log:
> *sigh* xalan did some recoding :-(
Is there any reason, why we don't use shift_jis for output? That would seem to
me more stable.
nd
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: Shift_Jis for generated japanese output?
Posted by Yoshiki Hayashi <yo...@xemacs.org>.
André Malo <nd...@perlig.de> writes:
>> Not really. Iso-2022-jp is the most auto-detection friendly
>> encoding because of infamous escape sequence but shift_jis
>> would be OK, too. I'm +-0 on conversion at the moment
>> because it hasn't caused me much trouble so far.
>
> Well, then we should stick with it.
>
> I find it just annoying that the recoding is not stable (i.e. the xalan
> serializer output differs from version to version and depending on other
> things like moon phases or so :).
From my experience, it was Java version that mattered.
After I upgraded to JDK 1.4, I don't have problem with
encoding. The reason this happens is that iso-2022-jp is a
stateful encoding. After an escape sequence, following
bytes are interpreted in certain state. After one escape
sequence, bytes are interpreted as ASCII character and after
another, those are are interpreted as some Japanese
characters. Because of this, you can have bogus escape
sequences like switching to another state and then
immediately going back to previous state. There were lots
of these sequences when I was using JDK 1.2. I'm hoping
this won't happen anymore since all files are re-encoded
with newer JDK. If this happens again, I would give +1 for
changing the generated files to shift_jis.
> (though... actually I don't know if shift_jis would make the things better)
Yes, shift_jis would make it easier because it's a plain
8bit character encoding scheme. There is only one way to
encode a character.
--
Yoshiki Hayashi
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: Shift_Jis for generated japanese output?
Posted by André Malo <nd...@perlig.de>.
* Yoshiki Hayashi <yo...@xemacs.org> wrote:
> Sorry for disappearing from the list for a while.
No need to excuse ;-)
> Not really. Iso-2022-jp is the most auto-detection friendly
> encoding because of infamous escape sequence but shift_jis
> would be OK, too. I'm +-0 on conversion at the moment
> because it hasn't caused me much trouble so far.
Well, then we should stick with it.
I find it just annoying that the recoding is not stable (i.e. the xalan
serializer output differs from version to version and depending on other
things like moon phases or so :).
(though... actually I don't know if shift_jis would make the things better)
nd
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: Shift_Jis for generated japanese output?
Posted by Yoshiki Hayashi <yo...@xemacs.org>.
Sorry for disappearing from the list for a while.
André Malo <nd...@perlig.de> writes:
>> Log:
>> *sigh* xalan did some recoding :-(
>
> Is there any reason, why we don't use shift_jis for output? That would seem to
> me more stable.
Not really. Iso-2022-jp is the most auto-detection friendly
encoding because of infamous escape sequence but shift_jis
would be OK, too. I'm +-0 on conversion at the moment
because it hasn't caused me much trouble so far.
--
Yoshiki Hayashi
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Portuguese BR translation
Posted by Eduardo Tompson Pereira <ed...@itelefonica.com.br>.
Hi everyone!
Is there anyone working on a portuguese translation for Apache? Or is anyone
interested in doing it already? If there is, could someone indicate me where
to start helping? Where do I get the right docs to translate, etc.
Thanks!
Eduardo Pereira
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org