> The migration path is to convert the legacy-encoding PHP files to UTF-8.
Please take a look at the following code.
This is a part of the code that I am actually maintaining in the
latest version of php.
```php
<?php
pg_connect(/* omission */);
// The database server expects clients to perform queries in SJIS.
// Depending on the settings, it may not be necessary to specify it explicitly.
pg_set_client_encoding('SJIS');
$res = pg_query('select * from ่กจ');
```
Unfortunately, this code breaks if I simply convert it to UTF-8.
In the "Usage statistics of character encodings for websites"
published by W3Techs, it is true that encodings other than UTF-8 are
rarely used. However, this is only **within the range that can be
observed from the outside as a website** .
As the code above shows, PHP covers a much wider area. In addition to
external connections, for example, SimpleXML and DOMDocument also
handle character codes internally, so they can break down using the
same logic as in the example above.
As Yuya says, the conversion itself is difficult, and even if you can
convert it, it may not be enough, so as a php user from a culture that
uses multi-byte characters, please be aware of this.
Kentaro Takeda
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
