This link has been bookmarked by 30 people . It was first bookmarked on 02 Aug 2006, by Jürgen R Plasser.
-
02 Jul 08
-
01 Jul 08
-
06 Nov 07
-
12 Sep 07
-
21 Aug 07
-
20 Feb 07
-
It’s certainly possible to do
-
you really need to know your PHP to do it
-
One of the biggest weaknesses of PHP (up to and including PHP 5.1) is that its built-in string functions handle multi-byte character encodings like UTF-8 and UTF-16 incorrectly. PHP was written with the assumption that one byte equals one character, which simply isn’t the case in such encodings. An optional module or library can be used to provide alternative string functions that do support multi-byte characters, but many of the PHP scripts in circulation use the built-in functions, and simply can’t handle Unicode characters as a result.
-
-
25 Oct 06
-
08 Sep 06
-
28 Aug 06
Adrian BengtsonEn genomgång av vad teckenkodning är och teckentabeller mm.
character encoding teckenkodning code utf-8 iso-latin teckentabeller Webbutveckling
-
Last month, I attended a meeting of the Melbourne chapter of the Web Standards Group, where Richard Ishida, the Internationalization Activity Lead of the W3C gave a remarkably clear presentation of one of the most ignored issues in web development: character encodings. Have you ever noticed certain characters on your site not displaying the way they should? Perhaps the curly quotation marks look like little boxes, or the long dashes have been replaced with question marks. Problems like these usually arise from an incomplete understanding of character encodings on the part of the developer responsible for the site. I’d go so far as to guess that, in English speaking circles at least, most web developers that have never learned about character encodings, and just deal with the consequences when issues like the above crop up. As a site grows to the point where it must address an international audience (or even just an audience that likes curly quotes), however, it’s more and more difficult to ignore these issues. Even worse, in these heady times of daily hack attempts, incorrect handling of character encodings can result in severe security vulnerabilities (as Google recently discovered). So what is a character encoding, exactly? Well, let’s start with something it’s not: a character encoding is not a character set.
-
-
14 Aug 06
-
09 Aug 06
-
29 Jul 06
-
14 May 06
-
11 May 06
-
17 Apr 06
-
14 Apr 06
-
31 Mar 06
-
28 Mar 06
-
17 Mar 06
-
Greg Neustaetterboth the utf8-encode AND the utf8-decode of the same data. Usually one of the 3 was right and it was then easier to find what was happening and to track down what had happenned at data-storing time.
-
16 Mar 06
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.