Utf-8 编码不适用于使用 php 5.5 的 utf-8 编码文档
Utf-8 encoding not working on utf-8 encoded document using php 5.5
我遇到了一种非常奇怪的编码问题，我并不真正理解也从未遇到过。我在 Ubuntu 机器上使用 PHP 5.5 只是为了获得信息。
问题
我有一个简单的文件index.php，我想在其中打印这个简单的字符串
<?php echo "übermotivierter"; ?>
在浏览器中查看时，我希望得到以下输出
�bermotivierter
这符合预期！
为了以正确的方式显示它，我已完成以下步骤
- 将我的 IDE ( Zend Studio ) 的编码更改为 UTF-8 并再次保存文件
设置适当的 html 元标记
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
设置合适的phpheader
<?php header("Content-Type: text/html; charset=utf-8"); ?>
完成此操作后，我本以为它会以正确的方式显示，但我仍然在输出中看到这个奇怪的 �！
解决方法
为了让这个东西正确显示，我必须这样做
<?php echo utf8_encode("übermotivierter"); ?>
现在它以正确的方式显示。
我的问题
我真的不明白为什么我必须使用 utf8_encode，而我的文档已经编码并保存为 utf-8。这对我来说没有任何意义。对此有什么解释吗？
不是答案，但评论太长了：
你能试试吗
<?php
$s = "übermotivierter";
echo '<p>', $s, '</p><p>';
for($i=0; $i<strlen($s); $i++) {
printf('%02x ', ord($s[$i]));
}
echo '</p>';
在你<?php echo "übermotivierter"; ?>?
的地方
它的输出是什么？
使用 Git 2.18+（2018 年第 2 季度），您可能不需要任何第三方技巧即可将 repo 内容转换为 UTF-8，因为 new "checkout-encoding" attribute 可以要求 Git 在签出到工作树时将内容转换为指定的编码（签入时则相反）。
参见 commit e92d622, commit 541d059, commit 7a17918, commit 107642f, commit c6e4865, commit 10ecb82, commit 2f0c4a3 (15 Apr 2018), commit 66b8af3 (09 Mar 2018), and commit 13ecb46, commit a8270b0 (15 Feb 2018) by Lars Schneider (larsxschneider)。
（由 Junio C Hamano -- gitster -- in commit 1ac0ce4 合并，2018 年 5 月 8 日）
convert: add 'working-tree-encoding' attribute
Git recognizes files encoded with ASCII or one of its supersets (e.g.
UTF-8 or ISO-8859-1) as text files.
All other encodings are usually interpreted as binary and consequently built-in Git text processing tools (e.g. 'git diff') as well as most Git web front ends do not visualize the content.
Add an attribute to tell Git what encoding the user has defined for a
given file. If the content is added to the index, then Git reencodes
the content to a canonical UTF-8 representation. On checkout Git will
reverse this operation.
如果有任何问题，您现在可以 the GIT_TRACE_WORKING_TREE_ENCODING environment variable 启用对使用 'working-tree-encoding' 属性重新编码的内容的跟踪。
这对于调试编码问题很有用。
documentation现在提到：
Please note that using the working-tree-encoding attribute may have a
number of pitfalls:
Alternative Git implementations (e.g. JGit or libgit2) and older Git
versions (as of March 2018) do not support the working-tree-encoding
attribute.
If you decide to use the working-tree-encoding attribute in your repository, then it is strongly recommended to ensure that all clients working with the repository support it.
For example, Microsoft Visual Studio resources files (*.rc) or
PowerShell script files (*.ps1) are sometimes encoded in UTF-16.
If you declare *.ps1 as files as UTF-16 and you add foo.ps1 with a working-tree-encoding enabled Git client, then foo.ps1 will be stored as UTF-8 internally.
A client without working-tree-encoding support will checkout foo.ps1 as UTF-8 encoded file. This will typically cause trouble for the users of this file.
If a Git client, that does not support the working-tree-encoding attribute, adds a new file bar.ps1, then bar.ps1 will be stored "as-is" internally (in this example probably as UTF-16).
A client with working-tree-encoding support will interpret the internal contents as UTF-8 and try to convert it to UTF-16 on checkout. That operation will fail and cause an error.
Reencoding content requires resources that might slow down certain Git operations (e.g 'git checkout' or 'git add').
Use the working-tree-encoding attribute only if you cannot store a file
in UTF-8 encoding and if you want Git to be able to process the content
as text.
As an example, use the following attributes if your '*.ps1' files are
UTF-16 encoded with byte order mark (BOM) and you want Git to perform
automatic line ending conversion based on your platform.
*.ps1 text working-tree-encoding=UTF-16
Use the following attributes if your '*.ps1' files are UTF-16 little
endian encoded without BOM and you want Git to use Windows line endings
in the working directory.
Please note, it is highly recommended to explicitly define the line endings with eol if the working-tree-encoding attribute is used to avoid ambiguity.
*.ps1 text working-tree-encoding=UTF-16LE eol=CRLF
我遇到了一种非常奇怪的编码问题，我并不真正理解也从未遇到过。我在 Ubuntu 机器上使用 PHP 5.5 只是为了获得信息。
问题
我有一个简单的文件index.php，我想在其中打印这个简单的字符串
<?php echo "übermotivierter"; ?>
在浏览器中查看时，我希望得到以下输出
�bermotivierter
这符合预期！
为了以正确的方式显示它，我已完成以下步骤
- 将我的 IDE ( Zend Studio ) 的编码更改为 UTF-8 并再次保存文件
设置适当的 html 元标记
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />设置合适的phpheader
<?php header("Content-Type: text/html; charset=utf-8"); ?>
完成此操作后，我本以为它会以正确的方式显示，但我仍然在输出中看到这个奇怪的 �！
解决方法
为了让这个东西正确显示，我必须这样做
<?php echo utf8_encode("übermotivierter"); ?>
现在它以正确的方式显示。
我的问题
我真的不明白为什么我必须使用 utf8_encode，而我的文档已经编码并保存为 utf-8。这对我来说没有任何意义。对此有什么解释吗？
不是答案，但评论太长了：
你能试试吗
<?php
$s = "übermotivierter";
echo '<p>', $s, '</p><p>';
for($i=0; $i<strlen($s); $i++) {
printf('%02x ', ord($s[$i]));
}
echo '</p>';
在你<?php echo "übermotivierter"; ?>?
的地方
它的输出是什么？
使用 Git 2.18+（2018 年第 2 季度），您可能不需要任何第三方技巧即可将 repo 内容转换为 UTF-8，因为 new "checkout-encoding" attribute 可以要求 Git 在签出到工作树时将内容转换为指定的编码（签入时则相反）。
参见 commit e92d622, commit 541d059, commit 7a17918, commit 107642f, commit c6e4865, commit 10ecb82, commit 2f0c4a3 (15 Apr 2018), commit 66b8af3 (09 Mar 2018), and commit 13ecb46, commit a8270b0 (15 Feb 2018) by Lars Schneider (larsxschneider)。
（由 Junio C Hamano -- gitster -- in commit 1ac0ce4 合并，2018 年 5 月 8 日）
convert: add 'working-tree-encoding' attributeGit recognizes files encoded with ASCII or one of its supersets (e.g. UTF-8 or ISO-8859-1) as text files.
All other encodings are usually interpreted as binary and consequently built-in Git text processing tools (e.g. 'git diff') as well as most Git web front ends do not visualize the content.Add an attribute to tell Git what encoding the user has defined for a given file. If the content is added to the index, then Git reencodes the content to a canonical UTF-8 representation. On checkout Git will reverse this operation.
如果有任何问题，您现在可以 the GIT_TRACE_WORKING_TREE_ENCODING environment variable 启用对使用 'working-tree-encoding' 属性重新编码的内容的跟踪。
这对于调试编码问题很有用。
documentation现在提到：
Please note that using the
working-tree-encodingattribute may have a number of pitfalls:
Alternative Git implementations (e.g. JGit or libgit2) and older Git versions (as of March 2018) do not support the
working-tree-encodingattribute.
If you decide to use theworking-tree-encodingattribute in your repository, then it is strongly recommended to ensure that all clients working with the repository support it.For example, Microsoft Visual Studio resources files (
*.rc) or PowerShell script files (*.ps1) are sometimes encoded in UTF-16.
If you declare*.ps1as files as UTF-16 and you addfoo.ps1with aworking-tree-encodingenabled Git client, thenfoo.ps1will be stored as UTF-8 internally.
A client withoutworking-tree-encodingsupport will checkoutfoo.ps1as UTF-8 encoded file. This will typically cause trouble for the users of this file.If a Git client, that does not support the
working-tree-encodingattribute, adds a new filebar.ps1, thenbar.ps1will be stored "as-is" internally (in this example probably as UTF-16).
A client withworking-tree-encodingsupport will interpret the internal contents as UTF-8 and try to convert it to UTF-16 on checkout. That operation will fail and cause an error.Reencoding content requires resources that might slow down certain Git operations (e.g '
git checkout' or 'git add').Use the
working-tree-encodingattribute only if you cannot store a file in UTF-8 encoding and if you want Git to be able to process the content as text.
As an example, use the following attributes if your '
*.ps1' files are UTF-16 encoded with byte order mark (BOM) and you want Git to perform automatic line ending conversion based on your platform.*.ps1 text working-tree-encoding=UTF-16Use the following attributes if your '
*.ps1' files are UTF-16 little endian encoded without BOM and you want Git to use Windows line endings in the working directory.
Please note, it is highly recommended to explicitly define the line endings witheolif theworking-tree-encodingattribute is used to avoid ambiguity.*.ps1 text working-tree-encoding=UTF-16LE eol=CRLF