W3C home > Mailing lists > Public > www-international@w3.org > January to March 2014

Re: Comment on Declaring Character Encodings

From: Richard Ishida <ishida@w3.org>
Date: Fri, 28 Feb 2014 17:30:11 +0000
Message-ID: <5310C7A3.7010400@w3.org>
To: Karl Groves <kgroves@paciellogroup.com>, www-international@w3.org
Thanks for the comments, Karl.

You'll notice that I have removed that section from the document under 
review.  I will keep a note of your comment, and consider whether other 
articles need to be changed later.


On 28/02/2014 15:38, Karl Groves wrote:
> This comment relates to:
> http://www.w3.org/International/questions/qa-html-encoding-declarations-new
> There are several considerations when it comes to setting character
> encodings in a PHP application that are likely to render your example of
> using header() ineffective. By default, PHP < 5.6.0 and MySQL are both
> set to ISO-8859-1.  Setting the charset using header() would only
> address one piece of the puzzle. Instances where PHP's encoding differs
> from the database's encoding are likely to create issues as well.
> It probably would be out of scope for your document to discuss all of
> the necessary details with regard to PHP, so perhaps a brief note and a
> link to PHP's documentation would be useful:
> http://php.net/manual/en/refs.international.php and
> http://www.php.net/manual/en/book.mbstring.php should do.
> Chances are similar documentation exists for other server-side languages.
> Finally, I think the parenthetical mention about actually saving the
> file(s) and content as utf-8 needs more prominence: "(Remember that this
> means you also need to /save/ your content as UTF-8.)"
> This is very important, as a file saved as something else (like
> Microsoft's god-awful Windows-1252) may cause problems.
> Thanks
> --
> Karl Groves
> Senior Technical Lead Accessibility Software Consultant & Director of
> Training
> The Paciello Group
> @karlgroves
> Phone: +1 443-875-7343
> The Paciello Group.
Received on Friday, 28 February 2014 17:30:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:04 UTC