Merge pull request #544 from ArtemGordinsky/gh-pages

Fix a typo
This commit is contained in:
Phil Sturgeon
2015-01-26 09:44:40 -05:00

View File

@@ -38,8 +38,7 @@ Explicitly defining the encoding of your strings in every script will save you a
Additionally, many PHP functions that operate on strings have an optional parameter letting you specify the character Additionally, many PHP functions that operate on strings have an optional parameter letting you specify the character
encoding. You should always explicitly indicate UTF-8 when given the option. For example, `htmlentities()` has an 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. 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()`.
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 an 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 enabled, then consider using the [patchwork/utf8] Composer package. This will use `mbstring` if it is available, and