New FAQ: Setting 'charset' information in .htaccess

[Richard Ishida]

The GEO task force has published another article based on an FAQ:

How do I use .htaccess directives on an Apache server to serve files with a specific encoding?

At: http://www.w3.org/International/questions/qa-htaccess-charset





You can find links to internationalization specifications, FAQs, articles, tools, tests, and soon tutorials at http://www.w3.org/International/






============
Richard Ishida
W3C

contact info: http://www.w3.org/People/Ishida/

http://www.w3.org/International/

[Jungshik Shin]

I'm sorry I wasn't able to give you my feedback before the
publication, but I guess it's not too late :-).

Post by Richard Ishida
How do I use .htaccess directives on an Apache server to serve files with a specific encoding?
At: http://www.w3.org/International/questions/qa-htaccess-charset

FAQ> Note that this FAQ is aimed at people who know that their server is
FAQ> set up to use .htaccess files, and who know that they have FAQ>
FAQ> permission to alter .htaccess files.

I think this had better be made a little bit more specific. Having the
permission to alter '.htaccess' files (that most users would have as long
as they have shell accounts on the server) is different from having
the permission to get what they put in '.htaccess' files effective
(to be acted upon by the server). Even if their server is set up to
use .htaccess files, their server can be set up to _ignore_ 'AddType',
'AddCharset', 'ForceType' directives in '.htaccess' while
honoring other directives in .htaccess. (see the apache manual
mentioned below).

FAQ> If these approaches fail, you should consult the Apache manuals (see
FAQ> attached links) or your server administrator.

The Apache manuals at the end point to the pages on 'content
negotiaton', which is not so relevant to this FAQ (although remotely
related). I guess the following four pages have to be listed, instead.

http://httpd.apache.org/docs/howto/htaccess.html
http://httpd.apache.org/docs/mod/core.html#allowoverride
http://httpd.apache.org/docs-2.0/howto/htaccess.html
http://httpd.apache.org/docs-2.0/mod/core.html#allowoverride

Jungshik

[Richard Ishida]

Hi Jungshik,

Thanks for these comments. I make some proposals for modification below.

-----Original Message-----
Sent: 07 July 2004 07:27
To: Richard Ishida
Subject: Re: New FAQ: Setting 'charset' information in .htaccess

...

Post by Richard Ishida
At: http://www.w3.org/International/questions/qa-htaccess-charset

FAQ> Note that this FAQ is aimed at people who know that
their server is
FAQ> set up to use .htaccess files, and who know that they have FAQ>
FAQ> permission to alter .htaccess files.
I think this had better be made a little bit more specific.
Having the permission to alter '.htaccess' files (that most
users would have as long as they have shell accounts on the
server) is different from having the permission to get what
they put in '.htaccess' files effective (to be acted upon by
the server). Even if their server is set up to use .htaccess
files, their server can be set up to _ignore_ 'AddType',
'AddCharset', 'ForceType' directives in '.htaccess' while
honoring other directives in .htaccess. (see the apache
manual mentioned below).

I propose the following change:

"Note that this FAQ is aimed at people who know that their server is set up
to use .htaccess files, and who know that they have permission to alter
.htaccess files."

to:

"Note that this FAQ assumes that your server is set up to use .htaccess
files, and that the directives described below work in .htaccess files on
your server."

FAQ> If these approaches fail, you should consult the Apache manuals
FAQ> (see attached links) or your server administrator.
The Apache manuals at the end point to the pages on 'content
negotiaton', which is not so relevant to this FAQ (although

Actually this was meant to point to the location where the directives
AddCharset etc are defined. Thanks for pointing it out.

http://httpd.apache.org/docs/mod/mod_mime.html
http://httpd.apache.org/docs-2.0/mod/mod_mime.html

remotely related). I guess the following four pages have to
be listed, instead.
http://httpd.apache.org/docs/howto/htaccess.html
http://httpd.apache.org/docs/mod/core.html#allowoverride
http://httpd.apache.org/docs-2.0/howto/htaccess.html
http://httpd.apache.org/docs-2.0/mod/core.html#allowoverride

Good suggestions.

So I propose to add these four and the two above in place of the links to
content negotiation.

Jungshik

[Jungshik Shin]

Richard Ishida wrote:

Hi Richard,

Thank you for your quick response.

Post by Richard Ishida

-----Original Message-----

Post by Richard Ishida
At: http://www.w3.org/International/questions/qa-htaccess-charset

"Note that this FAQ is aimed at people who know that their server is set up
to use .htaccess files, and who know that they have permission to alter
.htaccess files."
"Note that this FAQ assumes that your server is set up to use .htaccess
files, and that the directives described below work in .htaccess files on
your server."

With a reference to the links to the apache manual (especially about
'AllowOverride')
added here as well, I think that should do the job.

Post by Richard Ishida

FAQ> If these approaches fail, you should consult the Apache manuals
FAQ> (see attached links) or your server administrator.
The Apache manuals at the end point to the pages on 'content
negotiaton', which is not so relevant to this FAQ (although

Actually this was meant to point to the location where the directives
AddCharset etc are defined. Thanks for pointing it out.
http://httpd.apache.org/docs/mod/mod_mime.html
http://httpd.apache.org/docs-2.0/mod/mod_mime.html

remotely related). I guess the following four pages have to
be listed, instead.
http://httpd.apache.org/docs/howto/htaccess.html
http://httpd.apache.org/docs/mod/core.html#allowoverride
http://httpd.apache.org/docs-2.0/howto/htaccess.html
http://httpd.apache.org/docs-2.0/mod/core.html#allowoverride

Good suggestions.
So I propose to add these four and the two above in place of the links to
content negotiation.

Yeah, that should work.

Jungshik

[Deborah Cawkwell]

Re .htaccess, as well as the developer being able to physically change that .htaccess file and those changes being not ignored because of server setup, many organisations have guidelines about how .htaccess should be used efficiently/effectively. Ideally, you always work with server administrators to avoid redundant/duplicated load on the server.

Deborah

-----Original Message-----
From: www-international-***@w3.org on behalf of Richard Ishida
Sent: Wed 07/07/2004 12:46
To: 'Jungshik Shin'
Cc: www-***@w3.org
Subject: RE: New FAQ: Setting 'charset' information in .htaccess




Hi Jungshik,

Thanks for these comments. I make some proposals for modification below.

-----Original Message-----
Sent: 07 July 2004 07:27
To: Richard Ishida
Subject: Re: New FAQ: Setting 'charset' information in .htaccess

...

Post by Richard Ishida
At: http://www.w3.org/International/questions/qa-htaccess-charset

FAQ> Note that this FAQ is aimed at people who know that
their server is
FAQ> set up to use .htaccess files, and who know that they have FAQ>
FAQ> permission to alter .htaccess files.
I think this had better be made a little bit more specific.
Having the permission to alter '.htaccess' files (that most
users would have as long as they have shell accounts on the
server) is different from having the permission to get what
they put in '.htaccess' files effective (to be acted upon by
the server). Even if their server is set up to use .htaccess
files, their server can be set up to _ignore_ 'AddType',
'AddCharset', 'ForceType' directives in '.htaccess' while
honoring other directives in .htaccess. (see the apache
manual mentioned below).

I propose the following change:

"Note that this FAQ is aimed at people who know that their server is set up
to use .htaccess files, and who know that they have permission to alter
.htaccess files."

to:

"Note that this FAQ assumes that your server is set up to use .htaccess
files, and that the directives described below work in .htaccess files on
your server."

FAQ> If these approaches fail, you should consult the Apache manuals
FAQ> (see attached links) or your server administrator.
The Apache manuals at the end point to the pages on 'content
negotiaton', which is not so relevant to this FAQ (although

Actually this was meant to point to the location where the directives
AddCharset etc are defined. Thanks for pointing it out.

http://httpd.apache.org/docs/mod/mod_mime.html
http://httpd.apache.org/docs-2.0/mod/mod_mime.html

remotely related). I guess the following four pages have to
be listed, instead.
http://httpd.apache.org/docs/howto/htaccess.html
http://httpd.apache.org/docs/mod/core.html#allowoverride
http://httpd.apache.org/docs-2.0/howto/htaccess.html
http://httpd.apache.org/docs-2.0/mod/core.html#allowoverride

Good suggestions.

So I propose to add these four and the two above in place of the links to
content negotiation.

Jungshik

http://www.bbc.co.uk/ - World Wide Wonderland

This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless specifically
stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately. Please note that the
BBC monitors e-mails sent or received.
Further c