blocks|key|1413194|text|@表示文件具有与其相关联的扩展文件属性。您可以使用getxattr()函数查询它们。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1413195|没有确定的方法来检测文件的编码。阅读this+answer，它解释了原因。|1413196|有一个命令行工具enca，它尝试猜测编码。你可能会想去看看。|1413197|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/90838/how-can-i-detect-the-encodingcodepage-of-a-text-file|1|http://linux.die.net/man/1/enca^0|0|1|P|A|0|I|4|0|0|8|4|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|H|3|I|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|J|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]|R|$5|M|N|O|E|$P|S]]]]

The <code>@</code> means that the file has extended file attributes associated with it. You can query them using the <code>getxattr()</code> function.

There's no definite way to detect the encoding of a file. Read <a href="https://stackoverflow.com/questions/90838/how-can-i-detect-the-encodingcodepage-of-a-text-file">this</a> answer, it explains why.

There's a command line tool, <a href="http://linux.die.net/man/1/enca" rel="noreferrer">enca</a>, that attempts to guess the encoding. You might want to check it out.

blocks|key|1413559|text|在file命令上使用-I+(这是一个大写的i)选项似乎显示了文件编码。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1413560|file+-I+{filename}|code-block|syntax|javascript|1413561|entityMap^0|1|4|A|2|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

Using the <code>-I</code> (that's a capital i) option on the <code>file</code> command seems to show the file encoding.
<pre><code>file -I {filename}
</code></pre>

blocks|key|1628351|text|在Mac中，只要您正在测试的文件包含超出基本file+-I范围的字符，命令ASCII+(大写i)就会为您提供正确的字符集。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1628352|例如，如果您进入终端并使用vi创建一个文件，例如。然后，vi+test.txt插入一些字符并包含一个重音字符(尝试使用ALT-e后跟e)，然后保存该文件。|1628353|他们输入file+-I+text.txt，您应该会得到如下结果：|1628354|test.txt:+text/plain;+charset=utf-8|1628355|entityMap^0|M|7|0|S|B|0|4|G|0|0|Z|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|L|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|M|$]]

In Mac OS X the command <code>file -I</code> (capital i) will give you the proper character set so long as the file you are testing contains characters outside of the basic ASCII range.

For instance if you go into Terminal and use vi to create a file eg. <code>vi test.txt</code>
then insert some characters and include an accented character (try ALT-e followed by e) 
then save the file.

They type <code>file -I text.txt</code> and you should get a result like this: 

<code>test.txt: text/plain; charset=utf-8</code>

blocks|key|1413901|text|vim+-c+'execute+"silent+!echo+"+.+&fileencoding+%7C+q'+{filename}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1413902|在我的bash配置中别名为|unstyled|1413903|alias+vic="vim+-c+'execute+\"silent+\!echo+\"+.+&fileencoding+%7C+q'"|1413904|所以我只需要输入|1413905|vic+{filename}|1413906|在我的香草OSX+Yosemite上，它比“文件-I”产生更精确的结果：|1413907|$+file+-I+pdfs/udocument0.pdf
pdfs/udocument0.pdf:+application/pdf;+charset=binary
$+vic+pdfs/udocument0.pdf
latin1
$
$+file+-I+pdfs/t0.pdf
pdfs/t0.pdf:+application/pdf;+charset=us-ascii
$+vic+pdfs/t0.pdf
utf-8|1413908|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|T|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$B|C]]|$1|I|3|J|5|F|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$B|C]]|$1|M|3|N|5|F|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$B|C]]|$1|Q|3|-4|5|F|7|Z|8|@]|9|@]|A|$]]]|R|$]]

<pre><code>vim -c 'execute &quot;silent !echo &quot; . &amp;fileencoding | q' {filename}
</code></pre>
aliased somewhere in my bash configuration as
<pre><code>alias vic=&quot;vim -c 'execute \&quot;silent \!echo \&quot; . &amp;fileencoding | q'&quot;
</code></pre>
so I just type
<pre><code>vic {filename}
</code></pre>
On my vanilla OSX Yosemite, it yields more precise results than &quot;file -I&quot;:
<pre><code>$ file -I pdfs/udocument0.pdf
pdfs/udocument0.pdf: application/pdf; charset=binary
$ vic pdfs/udocument0.pdf
latin1
$
$ file -I pdfs/t0.pdf
pdfs/t0.pdf: application/pdf; charset=us-ascii
$ vic pdfs/t0.pdf
utf-8
</code></pre>

blocks|key|1628403|text|您还可以使用以下命令从一种文件类型转换为另一种文件类型：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1628404|iconv+-f+original_charset+-t+new_charset+originalfile+>+newfile|code-block|syntax|javascript|1628405|例如：|1628406|iconv+-f+utf-16le+-t+utf-8+file1.txt+>+file2.txt|1628407|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You can also convert from one file type to another using the following command :

<pre><code>iconv -f original_charset -t new_charset originalfile &gt; newfile
</code></pre>

e.g. 

<pre><code>iconv -f utf-16le -t utf-8 file1.txt &gt; file2.txt
</code></pre>

blocks|key|1413570|text|只需使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1413571|file+-I+<filename>|code-block|syntax|javascript|1413572|就这样。|1413573|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Just use:

<pre><code>file -I &lt;filename&gt;
</code></pre>

That's it.

blocks|key|1628591|text|将file命令与--mime-encoding选项(例如file+--mime-encoding+some_file.txt)一起使用，而不是使用-I选项，可以在OS+X上工作，并且具有省略mime类型"text/plain“的额外好处，而您可能并不关心这一点。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1628592|entityMap^0|1|4|8|F|S|Y|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

Using <code>file</code> command with the <code>--mime-encoding</code> option (e.g. <code>file --mime-encoding some_file.txt</code>) instead of the -I option works on OS X and has the added benefit of omitting the mime type, "text/plain", which you probably don't care about.

blocks|key|1413376|text|传统的8位LaTeX在可以使用哪些UTF8字符方面有很大的限制；它高度依赖于您正在使用的字体的编码以及该字体可用的字形。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1413377|由于您没有给出具体的示例，因此很难确切知道问题出在哪里--您是否正在尝试使用您的字体没有的字形，或者您是否一开始就没有使用正确的字体编码。|1413378|下面是一个最小的示例，展示了如何在LaTeX文档中使用几个UTF8字符：|1413379|\documentclass{article}
\usepackage[T1]{fontenc}
\usepackage{lmodern}
\usepackage[utf8]{inputenc}
\begin{document}
‘Héllø—thêrè.’
\end{document}|code-block|syntax|javascript|1413380|您可能会更幸运地使用utf8x编码，但需要注意的是，与utf8相比，它不再受支持，并且有一些特殊之处。但如果它成功了，对你来说这才是最重要的。|offset|length|1413381|entityMap|0|LINK|mutability|MUTABLE|url|as+far+as+I+recall;+it's+been+a+while+since+I've+looked+at+it^0|0|0|0|0|R|4|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@$M|11|N|12|1|13]]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

Classic 8-bit LaTeX is very restricted in which UTF8 characters it can use; it's highly dependent on the encoding of the font you're using and which glyphs that font has available.

Since you don't give a specific example, it's hard to know exactly where the problem is — whether you're attempting to use a glyph that your font doesn't have or whether you're not using the correct font encoding in the first place.

Here's a minimal example showing how a few UTF8 characters can be used in a LaTeX document:

<pre><code>\documentclass{article}
\usepackage[T1]{fontenc}
\usepackage{lmodern}
\usepackage[utf8]{inputenc}
\begin{document}
‘Héllø—thêrè.’
\end{document}
</code></pre>

You may have more luck with the [utf8x] encoding, but be slightly warned that it's no longer supported and has some idiosyncrasies compared with [utf8] (as far as I recall; it's been a while since I've looked at it). But if it does the trick, that's all that matters for you.

blocks|key|1413450|text|@符号表示文件包含extended+attributes。xattr+file显示了它拥有的属性，xattr+-l+file也显示了属性值(有时可能很大-例如，尝试xattr+/System/Library/Fonts/HelveLTMM可以看到存在于资源分支中的旧式字体)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1413451|entityMap|0|LINK|mutability|MUTABLE|url|http://arstechnica.com/apple/reviews/2005/04/macosx-10-4.ars/7^0|T|A|1D|D|2A|11|9|J|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

The @ sign means the file has <a href="http://arstechnica.com/apple/reviews/2005/04/macosx-10-4.ars/7" rel="nofollow noreferrer">extended attributes</a>. <code>xattr file</code> shows what attributes it has, <code>xattr -l file</code> shows the attribute values too (which can be large sometimes &mdash; try e.g. <code>xattr /System/Library/Fonts/HelveLTMM</code> to see an old-style font that exists in the resource fork).

blocks|key|1628214|text|在终端中输入file+myfile.tex有时可以使用一系列算法和幻数告诉您文件的编码和类型。它相当有用，但不要依赖它提供具体或可靠的信息。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1628215|Localizable.strings文件(在本地化的Mac应用程序中找到)通常被报告为UTF-16C源文件。|1628216|entityMap^0|6|F|0|0|J|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

Typing <code>file myfile.tex</code> in a terminal can sometimes tell you the encoding and type of file using a series of algorithms and magic numbers. It's fairly useful but don't rely on it providing concrete or reliable information.

A <code>Localizable.strings</code> file (found in localised Mac OS X applications) is typically reported to be a UTF-16 C source file.

blocks|key|1628465|text|Synalyze+It!允许比较ICU+library提供的所有编码中的文本或字节。使用该特性，您通常可以立即看到哪个代码页对您的数据有意义。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1628466|entityMap|0|LINK|mutability|MUTABLE|url|http://www.synalysis.net/|1|http://icu-project.org/^0|0|C|0|G|B|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

<a href="http://www.synalysis.net" rel="nofollow">Synalyze It!</a> allows to compare text or bytes in all encodings the <a href="http://icu-project.org" rel="nofollow">ICU library</a> offers. Using that feature you usually see immediately which code page makes sense for your data.

blocks|key|1413789|text|您可以尝试将文件加载到firefox窗口中，然后转到View+-+Character+Encoding。文件的编码类型旁边应该有一个复选标记。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1413790|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You can try loading the file into a firefox window then go to View - Character Encoding. There should be a check mark next to the file's encoding type.

blocks|key|1628706|text|我实现了下面的bash脚本，它对我很有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1628707|它首先尝试从file+--mime-encoding返回的编码iconv到utf-8。|offset|length|style|CODE|1628708|如果失败，它将遍历所有编码，并显示原始文件和重新编码文件之间的差异。它跳过产生大差异输出的编码(由MAX_DIFF_LINES变量或第二个输入参数定义的“大”)，因为它们很可能是错误的编码。|1628709|如果“坏事情”是由于使用这个脚本而发生的，请不要怪我。那里面有个rm+-f，所以里面有怪物。我试图通过在带有随机后缀的文件上使用它来防止负面影响，但我没有做出任何承诺。|1628710|在Darwin+15.6.0上测试。|1628711|#!/bin/bash

if+[[+$#+-lt+1+]]
then
++echo+"ERROR:+need+one+input+argument:+file+of+which+the+enconding+is+to+be+detected."
++exit+3
fi

if+[+!+-e+"$1"+]
then
++echo+"ERROR:+cannot+find+file+'$1'"
++exit+3
fi

if+[[+$#+-ge+2+]]
then
++MAX_DIFF_LINES=$2
else
++MAX_DIFF_LINES=10
fi


#try+the+easy+way
ENCOD=$(file+--mime-encoding+$1+%7C+awk+'{print+$2}')
#check+if+this+enconding+is+valid
iconv+-f+$ENCOD+-t+utf-8+$1+&>+/dev/null
if+[+$?+-eq+0+]
then
++echo+$ENCOD
++exit+0
fi

#hard+way,+need+the+user+to+visually+check+the+difference+between+the+original+and+re-encoded+files
for+i+in+$(iconv+-l+%7C+awk+'{print+$1}')
do
++SINK=$1.$i.$RANDOM
++iconv+-f+$i+-t+utf-8+$1+2>+/dev/null+>+$SINK
++if+[+$?+-eq+0+]
++then
++++DIFF=$(diff+$1+$SINK)
++++if+[+!+-z+"$DIFF"+]+&&+[+$(echo+"$DIFF"+%7C+wc+-l)+-le+$MAX_DIFF_LINES+]
++++then
++++++echo+"=====+$i+====="
++++++echo+"$DIFF"
++++++echo+"Does+that+make+sense+[N/y]"
++++++read+$ANSWER
++++++if+[+"$ANSWER"+==+"y"+]+%7C%7C+[+"$ANSWER"+==+"Y"+]
++++++then
++++++++echo+$i
++++++++exit+0
++++++fi
++++fi
++fi
++#clean+up+re-encoded+file
++rm+-f+$SINK
done

echo+"None+of+the+encondings+worked.+You're+stuck."
exit+3|code-block|syntax|javascript|1628712|entityMap^0|0|6|K|V|5|11|5|0|1D|E|0|W|5|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]|$D|Y|E|Z|F|G]|$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@$D|13|E|14|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|18|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|19|8|@]|9|@]|A|$Q|R]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|T|$]]

I implemented the bash script below, it works for me. 

It first tries to <code>iconv</code> from the encoding returned by <code>file --mime-encoding</code> to <code>utf-8</code>. 

If that fails, it goes through all encodings and shows the diff between the original and re-encoded file. It skips over encodings that produce a large diff output ("large" as defined by the <code>MAX_DIFF_LINES</code> variable or the second input argument), since those are most likely the wrong encoding.

If "bad things" happen as a result of using this script, don't blame me. There's a <code>rm -f</code> in there, so there be monsters. I tried to prevent adverse effects by using it on files with a random suffix, but I'm not making any promises. 

Tested on Darwin 15.6.0.

<pre><code>#!/bin/bash

if [[ $# -lt 1 ]]
then
 echo "ERROR: need one input argument: file of which the enconding is to be detected."
 exit 3
fi

if [ ! -e "$1" ]
then
 echo "ERROR: cannot find file '$1'"
 exit 3
fi

if [[ $# -ge 2 ]]
then
 MAX_DIFF_LINES=$2
else
 MAX_DIFF_LINES=10
fi


#try the easy way
ENCOD=$(file --mime-encoding $1 | awk '{print $2}')
#check if this enconding is valid
iconv -f $ENCOD -t utf-8 $1 &amp;&gt; /dev/null
if [ $? -eq 0 ]
then
 echo $ENCOD
 exit 0
fi

#hard way, need the user to visually check the difference between the original and re-encoded files
for i in $(iconv -l | awk '{print $1}')
do
 SINK=$1.$i.$RANDOM
 iconv -f $i -t utf-8 $1 2&gt; /dev/null &gt; $SINK
 if [ $? -eq 0 ]
 then
 DIFF=$(diff $1 $SINK)
 if [ ! -z "$DIFF" ] &amp;&amp; [ $(echo "$DIFF" | wc -l) -le $MAX_DIFF_LINES ]
 then
 echo "===== $i ====="
 echo "$DIFF"
 echo "Does that make sense [N/y]"
 read $ANSWER
 if [ "$ANSWER" == "y" ] || [ "$ANSWER" == "Y" ]
 then
 echo $i
 exit 0
 fi
 fi
 fi
 #clean up re-encoded file
 rm -f $SINK
done

echo "None of the encondings worked. You're stuck."
exit 3
</code></pre>

blocks|key|1413257|text|您使用的是哪种LaTeX？当我使用teTeX时，我必须手动下载unicode包并将其添加到我的.tex文件中：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1413258|%25+UTF-8+stuff
\usepackage[notipa]{ucs}
\usepackage[utf8x]{inputenc}
\usepackage[T1]{fontenc}|code-block|syntax|javascript|1413259|现在，我已经从TeXlive+2008包(here)切换到XeTeX，它甚至更简单：|1413260|%25+UTF-8+stuff
\usepackage{fontspec}
\usepackage{xunicode}|1413261|至于文件编码的检测，你可以使用file(1)+(但它相当有限)，但就像其他人所说的那样，这很困难。|style|CODE|1413262|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ctan.org/tex-archive/macros/latex/contrib/unicode/|1|http://www.tug.org/mactex/^0|V|7|0|0|0|L|4|1|0|0|F|7|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|15|8|@]|9|@$A|16|B|17|1|18]]|C|$]]|$1|K|3|L|5|F|7|19|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|1A|8|@$A|1B|B|1C|O|P]]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]|Y|$5|T|U|V|C|$W|Z]]]]

Which LaTeX are you using? When I was using teTeX, I had to manually download the <a href="http://www.ctan.org/tex-archive/macros/latex/contrib/unicode/" rel="nofollow noreferrer">unicode</a> package and add this to my .tex files:

<pre><code>% UTF-8 stuff
\usepackage[notipa]{ucs}
\usepackage[utf8x]{inputenc}
\usepackage[T1]{fontenc}
</code></pre>

Now, I've switched over to XeTeX from the TeXlive 2008 package (<a href="http://www.tug.org/mactex/" rel="nofollow noreferrer">here</a>), it is even more simple:

<pre><code>% UTF-8 stuff
\usepackage{fontspec}
\usepackage{xunicode}
</code></pre>

As for detection of a file's encoding, you could play with <code>file(1)</code> (but it is rather limited) but like someone else said, it is difficult.

blocks|key|1413310|text|一种暴力检查编码的方法可能是在十六进制编辑器或类似编辑器中检查文件。(或编写程序进行检查)查看文件中的二进制数据。UTF-8格式相当容易识别。所有ASCII字符都是值小于128+(0x80)的单字节。多字节序列遵循wiki+article中显示的模式|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1413311|如果您能找到一种更简单的方法让程序为您验证编码，这显然是一条捷径，但如果所有其他方法都失败了，这将会起到作用。|1413312|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Utf-8#Description^0|2Z|C|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

A brute-force way to check the encoding might just be to check the file in a hex editor or similar. (or write a program to check) Look at the binary data in the file. The UTF-8 format is fairly easy to recognize. All ASCII characters are single bytes with values below 128 (0x80)
Multibyte sequences follow the pattern shown in the <a href="http://en.wikipedia.org/wiki/Utf-8#Description" rel="nofollow noreferrer">wiki article</a>

If you can find a simpler way to get a program to verify the encoding for you, that's obviously a shortcut, but if all else fails, this would do the trick.

I'm trying to enter some UTF-8 characters into a LaTeX file in <a href="http://en.wikipedia.org/wiki/TextMate" rel="noreferrer">TextMate</a> (which says its default encoding is UTF-8), but LaTeX doesn't seem to understand them.

Running <code>cat my_file.tex</code> shows the characters properly in Terminal. Running <code>ls -al</code> shows something I've never seen before: an "@" by the file listing:

<pre><code>-rw-r--r--@ 1 me users 2021 Feb 11 18:05 my_file.tex
</code></pre>

(And, yes, I'm using <code>\usepackage[utf8]{inputenc}</code> in the LaTeX.)

I've found <code>iconv</code>, but that doesn't seem to be able to tell me what the encoding is -- it'll only convert once I figure it out.

How do I determine file encoding in OS X?

命令行工具

我尝试在的LaTeX文件中输入一些UTF-8字符(默认编码是UTF-8)，但是LaTeX似乎不能理解它们。运行cat my_file.tex可在终端中正确显示字符。运行ls -al会显示一些我以前从未见过的东西:文件列表的旁边有一个"@“：-rw-r--r--@  1 me      users      2021 Feb 11 18:05 my_file.tex(是的，我在LaTeX中使用了\u

问如何在OS X中确定文件编码？
EN

回答 15

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在OS X中确定文件编码？EN

回答 15

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在OS X中确定文件编码？
EN