.strings 文件几乎应始终为 UTF-16，如 本地化字符串资源。
.strings
UTF-16
只要 TextEdit 将 .strings 文件正确解释为 UTF-16，它就应该可以正常工作。
.strings files should almost always be UTF-16, as outlined in Localizing String Resources.
TextEdit should work okay as long as it's properly interpreting the .strings files as UTF-16.
从 OS X 10.7 开始，属性列表编辑器默认不再可用。我们现在需要使用臃肿的 XCode 4 编辑 plist 文件。
但是，可以获取旧的 Snow Leopard 版本的 属性列表编辑器致力于 Lion：
Property List Editor is no longer available by default as of OS X 10.7. We are now expected to edit plist files using bloated XCode 4.
However, it's possible to get the old Snow Leopard version of the Property List Editor working on Lion:
使用 /Developer/Applications/Utilities/ 中的 Property List Editor
/Developer/Applications/Utilities/
Property List Editor
或者，如果您更喜欢文本编辑器，请获取 BBEdit 如果你还没有。每个 Mac 程序员都应该拥有一本。
Use Property List Editor in /Developer/Applications/Utilities/
Or if you prefer text editor, get BBEdit if you haven't yet. Every Mac programmer should have a copy.
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
暂无简介
文章 0 评论 0
接受
发布评论
评论（3）
.strings文件几乎应始终为UTF-16，如 本地化字符串资源。只要 TextEdit 将 .strings 文件正确解释为 UTF-16，它就应该可以正常工作。
.stringsfiles should almost always beUTF-16, as outlined in Localizing String Resources.TextEdit should work okay as long as it's properly interpreting the .strings files as UTF-16.
从 OS X 10.7 开始，属性列表编辑器默认不再可用。我们现在需要使用臃肿的 XCode 4 编辑 plist 文件。
但是，可以获取旧的 Snow Leopard 版本的 属性列表编辑器致力于 Lion：
Property List Editor is no longer available by default as of OS X 10.7. We are now expected to edit plist files using bloated XCode 4.
However, it's possible to get the old Snow Leopard version of the Property List Editor working on Lion:
使用
/Developer/Applications/Utilities/中的Property List Editor或者，如果您更喜欢文本编辑器，请获取 BBEdit 如果你还没有。每个 Mac 程序员都应该拥有一本。
Use
Property List Editorin/Developer/Applications/Utilities/Or if you prefer text editor, get BBEdit if you haven't yet. Every Mac programmer should have a copy.