[Savannah-help-public] Re: [gnu.org #337164] Fw: [sr #105901] Content negotiation disabled?

[Sylvain Beucler]

On Tue, Jun 19, 2007 at 02:16:13PM -0400, Justin Baugh via RT wrote:
> > [beuc - Sun Jun 17 04:34:17 2007]:
> > 
> > Hello www.nongnu.org admins,
> > 
> > Can you check the Content Negotiation settings at www.nongnu.org?
> > This user says they were recently modified.
> 
> Hi,
> 
> I have fixed the error (negotiation or multiviews were not turned off
> on gnu.org - apache2 simply expects different file extensions for 
> Japanese-encoded documents). I added the default of .ja for ISO-2022-JP
> and the problem seems to be resolved (for this one case). I also added
> a number of other defaults that no longer seem to exist in apache2.
> 
> I highly recommend people start using Unicode.

Hi,

Here's an anser from Daiki Ueno. Please keep him in Cc:

On Wed, Jun 20, 2007 at 09:35:19AM +0000, Daiki Ueno wrote:
>
> Follow-up Comment #2, sr #105901 (project administration):
>
> Thanks, I confirmed the problem is fixed.
>
> However, there seems to be a confusion between "Language" and "Charset", if
> apache2.conf now contains the following line.
>
> AddCharset iso-2022-jp .ja
>
> This assumes index.html.ja always being written in ISO-2022-JP, while there
> are 4 major encodings used to encode Japanese texts, i.e. ISO-2022-JP,
> EUC-JP, Shift_JIS and UTF-8.
>
> I only need the following lines (from the default configuration of apache2 in
> Debian unstable).
>
> AddLanguage ja .ja
> AddCharset ISO-2022-JP .iso2022-jp .jis
>
> With these lines, I can supply ISO-2022-JP encoded pages with a combined
> extension like "index.html.ja.iso2022-jp", even if there is
> "AddDefaultCharset UTF-8".
>
> Regards,

-- 
Sylvain