Home > Backend Development > PHP Tutorial > Detailed explanation of strings, encoding, and UTF-8 codes in PHP

Detailed explanation of strings, encoding, and UTF-8 codes in PHP

黄舟
Release: 2023-03-06 11:58:01
Original
2577 people have browsed it

I have read a lot of articles on coding recently, so I divided it into two blog posts to talk about "PHP, strings, encoding, UTF-8" related knowledge. This blog post is the first half, divided into four major parts, namely " "Definition and use of strings", "String conversion", "The nature of PHP strings", "Multibyte strings". The first half is relatively basic, and the next article "Best Practices of PHP and UTF-8" may have more information.

Definition and use of string

There are four ways to set strings in PHP:

Single quoted string

Single-quoted strings are similar to raw strings in Python, which means that single-quoted strings do not have variable parsing functions and special character escaping functions. For example, $str='hello\nworld', the \n does not have a newline function.

 Double quoted string

Double-quoted strings have variable parsing functions and special character escaping functions that single-quoted strings do not have.

Personally, I am very interested in the special escape of hexadecimal and octal strings. Special addition:

\[0-7]{1,3} #八进制表达方式
\x[0-9A-Fa-f]{1,2} #十六进制表达方式
Copy after login

heredoc

This expression is similar to a long string in Python and can define a string containing multiple lines. Its grammatical definition is very strict, so you need to pay attention when using it.

$str=<<<EOD
hello\n
world
EOD;
Copy after login

 Nowdoc

Nowdoc is similar to a single-quoted string and does not parse variables. It is more suitable for defining a large section of text without escaping special characters.

Variable analysis

The most powerful part of PHP strings is variable parsing, which can parse variables according to context at runtime (this is an interpreted language), which can produce many wonderful uses.

Simple variable parsing means that the string can contain "variables", "arrays", and "object attributes". Complex syntax rules are to use {} symbols to operate (to form an expression).

Let’s look at the power of variable parsing through an example

class beers {
    const softdrink = &#39;softdrink&#39;;
    public static $ale = &#39;ale&#39;;
    public $data = array(1,3,"k"=>4);
}

$softdrink = "softdrink";
$ale = "ale";
$arr = array("arr1","arr2","arr3"=>"arr4","arr4"=>array(1,2));
$arr4 = "arr4";
$obj = new beers;
echo "line1:{$arr[1]}\n";
echo "line2:{$arr[&#39;arr4&#39;][0]}\n"; 
echo "line3:{$obj->data[1]}\n";
echo "line4:{${$arr[&#39;arr3&#39;]}}\n";
echo "line5:{${$arr[&#39;arr3&#39;]}[1]}\n";
echo "line6:{${beers::softdrink}}\n";
echo "line7:{${beers::$ale}}\n";
Copy after login

String conversion

Another reason why the PHP language is simpler than Python is the implicit conversion of types, which will simplify many operations, which is explained here through string conversion.

String type coercion

$var = 10 ;
$dvar = (string)$var ;
echo $dvar . "_" . gettype($dvar);
Copy after login

The strval() function is to get the string value of the variable:

$var = 10.2 ;
$dvar = strval($var) ;
echo gettype($var) . "_" . $dvar . "_" . gettype($dvar);
Copy after login

The settype() function sets the type of the variable:

$str = "10hello";
settype($str, "integer");
echo $str ;
Copy after login

During the process of forced type conversion, certain rules will be followed when converting other types of values ​​​​to strings. For example, a Boolean value of TRUE is converted into a string of "1". It’s best to understand the relevant rules.

Automatic type conversion

The above two conversions are display conversions, and what is more important to pay attention to is automatic type conversion. In an expression that requires a string, it will be automatically converted to a type. For details, see the example:

$bool = true;
$str = 10 + "hello"
echo $bool . "_" . $str ;
Copy after login

The essence of PHP string

Quoting the explanation from the PHP documentation:

String in PHP is implemented as an array of bytes plus an integer specifying the buffer length. There is no information on how to convert bytes into characters, it is up to the programmer to decide. There are no restrictions on what values ​​a string consists of, including bytes with a value of 0 that can appear anywhere in the string.

PHP does not specify the encoding of the string. How the string is encoded depends on the programmer. Strings are encoded according to the encoding of the PHP file. For example, if your file encoding is GBK, then the content of your code will be GBK.

To supplement the concept of binary safety, a byte with a value of 0 (NULL) can be at any position in the string, and some of PHP's non-binary functions are called C functions at the bottom, which will ignore the characters after NULL.

As long as PHP's file encoding is compatible with ASCII, string operations can be handled well. However, string operations are still Native in nature (no matter what the file encoding is), so you need to pay attention when using it:

  • Some functions assume that strings are encoded in single bytes, but do not require the bytes to be interpreted as specific characters. For example, the sbustr() function.

  • Many functions need to pass encoding parameters explicitly, otherwise the default values ​​will be obtained from the PHP.INI file, such as the htmlentities() function.

  • There are also some functions related to the local area, and these functions can only operate on single byte.

Under normal circumstances, although PHP does not support Unicode characters internally, it does support UTF-8 encoding. In most cases, there will be no problems. However, the following situations may not be handled:

  • How to convert non-UTF-8 encoded strings

  • A UTF-8 encoded web page, but when users submit the form, they may use GBK encoding (which does not comply with meta tag)

  • For a UTF-8 encoded PHP file, using strlen("China") returns 6 instead of the actual number of characters (2)

​So how to solve this problem? PHP provides the mbstring extension!

Multibyte string

The mbstring extension is not turned on by default. You need --enable-mbstring when installing.

Let’s first look at the configuration of the mbstring directive in PHP.INI. It took a long time to gradually understand it.

  • I understand the mbstring.language parameter as UTF-8

  • mbstring.internal_encoding This encoding has nothing to do with PHP file encoding. It is just that in most mbstring functions, you need to specify the encoding of the string to be processed. If you do not specify it explicitly, the value of this parameter will be obtained by default. The value of this parameter is in higher versions of PHP. Used the default_charset parameter instead.

  • mbstring.http_input This parameter specifies the default encoding for HTTP input (excluding GET parameters). Generally consistent with the encoding of the HTML page, the value of this parameter is replaced by the default_charset parameter.

  • mbstring.http_output This parameter misled me. What is HTTP output? Isn’t PHP output just a page? How can there be such a concept?

  • mbstring.encoding_translation, let’s focus on this parameter. It is turned off by default. If it is turned on, PHP will automatically convert the encoding of the POST variable and the name of the uploaded file to the value specified by mbstring.internal_encoding. However, I have not tested it. You can upload a Chinese named file. It is recommended to close it and let programmers deal with related issues.

Let’s take a look at some functions extended by mbstring later:

  • mb_http_input(): Detect the HTTP input character encoding and find it necessary to process the file name of the file upload.

  • mb_convert_encoding(): A commonly used function, pay attention to the third parameter.

  • mb_detect_order(): Set/get the detection order of character encoding.

  • mb_list_encodings(): Returns the encoding list supported by the system.

Important note: PHP files must support certain encodings and must be ASCII compatible.

But do not use BIG-5 as the PHP file encoding, especially when strings appear in the form of identifiers or literals. If the actual PHP file encoding is BIG-5, then try to convert the input and output content to UTF-8.

Zend Multibyte

Finally, let’s talk about the concept of Zend Multibyte. I don’t understand it very deeply. First of all, don’t confuse it with the mbstring extension. Zend Multibyte mode is turned off by default and can be turned on via the zend.multibyte command. Then specify the encoding of the PHP parser through the declare() function.

What is the significance of this instruction? As mentioned above, the encoding of PHP files needs to be ASCII-compatible, so what to do with non-compatible ASCII encodings like BIG-5? You can operate it through this command. When the PHP parser reads the mbstring.script_encoding encoding and uses this encoding to parse PHP files.

The above is a detailed explanation of strings, encodings, and UTF-8 codes in PHP. For more related content, please pay attention to the PHP Chinese website (m.sbmmt.com)!


Related labels:
source:php.cn
Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template