From 252cae64d0bdd02f6c10c2251e0d0abd5e386ce7 Mon Sep 17 00:00:00 2001 From: Turdaliev Nursultan Date: Tue, 2 Feb 2016 14:50:45 +0100 Subject: [PATCH] Update 05-05-01-PHP-and-UTF8.md --- _posts/05-05-01-PHP-and-UTF8.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/05-05-01-PHP-and-UTF8.md b/_posts/05-05-01-PHP-and-UTF8.md index 578656b..de0d659 100644 --- a/_posts/05-05-01-PHP-and-UTF8.md +++ b/_posts/05-05-01-PHP-and-UTF8.md @@ -40,7 +40,7 @@ Additionally, many PHP functions that operate on strings have an optional parame encoding. You should always explicitly indicate UTF-8 when given the option. For example, `htmlentities()` has an option for character encoding, and you should always specify UTF-8 if dealing with such strings. Note that as of PHP 5.4.0, UTF-8 is the default encoding for `htmlentities()` and `htmlspecialchars()`. -Finally, If you are building an distributed application and cannot be certain that the `mbstring` extension will be +Finally, If you are building a distributed application and cannot be certain that the `mbstring` extension will be enabled, then consider using the [patchwork/utf8] Composer package. This will use `mbstring` if it is available, and fall back to non UTF-8 functions if not.