Daniel ab1334c0cf the whole shebang | 10 years ago | |
---|---|---|
.. | ||
class | 10 years ago | |
README.md | 10 years ago | |
composer.json | 10 years ago |
Patchwork UTF-8 provides both :
It can also serve as a documentation source referencing the practical problems that arise when handling UTF-8 in PHP: Unicode concepts, related algorithms, bugs in PHP core, workarounds, etc.
Unicode handling in PHP is best performed using a combo of mbstring
, iconv
,
intl
and pcre
with the u
flag enabled. But when an application is expected
to run on many servers, you should be aware that these 4 extensions are not
always enabled.
Patchwork UTF-8 provides pure PHP implementations for 3 of those 4 extensions. Here is the set of portability-fallbacks that are currently implemented:
mbstring
: mb_convert_encoding, mb_decode_mimeheader, mb_encode_mimeheader,
mb_convert_case, mb_internal_encoding, mb_list_encodings, mb_strlen,
mb_strpos, mb_strrpos, mb_strtolower, mb_strtoupper, mb_substitute_character,
mb_substr, mb_stripos, mb_stristr, mb_strrchr, mb_strrichr, mb_strripos,
mb_strstr,iconv
: iconv, iconv_mime_decode, iconv_mime_decode_headers,
iconv_get_encoding, iconv_set_encoding, iconv_mime_encode, ob_iconv_handler,
iconv_strlen, iconv_strpos, iconv_strrpos, iconv_substr,intl
: Normalizer, grapheme_extract, grapheme_stripos, grapheme_stristr,
grapheme_strlen, grapheme_strpos, grapheme_strripos, grapheme_strrpos,
grapheme_strstr, grapheme_substr.pcre
compiled with unicode support is required.
Grapheme clusters should always be
considered when working with generic Unicode strings. The Patchwork\Utf8
class implements the quasi-complete set of native string functions that need
UTF-8 grapheme clusters awareness. Function names, arguments and behavior
carefully replicates native PHP string functions so that usage is very easy.
Some more functions are also provided to help handling UTF-8 strings:
Mirrored string functions are: strlen, substr, strpos, stripos, strrpos, strripos, strstr, stristr, strrchr, strrichr, strtolower, strtoupper, wordwrap, chr, count_chars, ltrim, ord, rtrim, trim, str_ireplace, str_pad, str_shuffle, str_split, str_word_count, strcmp, strnatcmp, strcasecmp, strnatcasecmp, strncasecmp, strncmp, strcspn, strpbrk, strrev, strspn, strtr, substr_compare, substr_count, substr_replace, ucfirst, lcfirst, ucwords, number_format, utf8_encode, utf8_decode.
Missing are printf-family functions.
The recommended way to install Patchwork UTF-8 is through
composer. Just create a composer.json
file and run
the php composer.phar install
command to install it:
{
"require": {
"patchwork/utf8": "1.1.*"
}
}
Then, early in your bootstrap sequence, you have to configure your environment:
\Patchwork\Utf8\Bootup::initAll(); // Enables the portablity layer and configures PHP for UTF-8
\Patchwork\Utf8\Bootup::filterRequestUri(); // Redirects to an UTF-8 encoded URL if it's not already the case
\Patchwork\Utf8\Bootup::filterRequestInputs(); // Sanitizes HTTP inputs to UTF-8 NFC
Run phpunit
in the tests/
directory to see the code in action.
Make sure that you are confident about using UTF-8 by reading Character Sets / Character Encoding Issues and Handling UTF-8 with PHP, or PHP et UTF-8 for french readers.
You should also get familar with the concept of Unicode Normalization and Grapheme Clusters.
Do not blindly replace all use of PHP's string functions. Most of the time you will not need to, and you will be introducing a significant performance overhead to your application.
Screen your input on the outer perimeter so that only well formed UTF-8 pass
through. When dealing with badly formed UTF-8, you should not try to fix it.
Instead, consider it as ISO-8859-1 and use utf8_encode()
to get an UTF-8
string. Don't forget also to choose one unicode normalization form and stick to
it. NFC is the most in use today.
This library is orthogonal to mbstring.func_overload
and will not work if the
php.ini setting is enabled.
Patchwork\Utf8 is free software; you can redistribute it and/or modify it under the terms of the (at your option):
Unicode handling requires tedious work to be implemented and maintained on the long run. As such, contributions such as unit tests, bug reports, comments or patches licensed under both licenses are really welcomed.
I hope many projects could adopt this code and together help solve the unicode subject for PHP.