- Convert Localizable.strings to
- Set Convert Copied Files to
- Set Strings file Output Encoding to
UTF-16 ".strings" Files
Note: It is recommended that you save strings files using the UTF-16 encoding, which is the default encoding for standard strings files. It is possible to create strings files using other property-list formats, including binary property-list formats and XML formats that use the UTF-8 encoding, but doing so is not recommended. Apple String resource documentation
Apple recommended Localizable.strings encoded using UTF-16, but major Version control systems (VCS) such as Git or Mercurial doesn't like UTF-16 very much. They treat files encoded using UTF-16 as binary. So that we can't diff and merge Localizable.strings (UTF-16) like what we did to our source codes (UTF-8).
There's a solution I found by karl's post, use
gitattributes to indicate
*.strings file should convert from UTF-16 to UTF-8 on diff command. This is good and clean but not becoming my solution.
Because it's a little bit complicated, I have to set
.gitattributes file for all iOS projects, and all contributors have to set same diff's driver_name at their own
The two most important things are:
1. My favorite git command
git add -p will not work on binary file for sure.
2. GitHub doesn't handle UTF-16 either.
These two considerations are crucial for me, I need a better solution.
Use UTF-8 text encoding, convert it to UTF-16 on building process
First, convert our Localizable.strings to UTF-8 encoding, Xcode's File inspector is convenient to do it.
There is a magical flag that Xcode provided: Convert Copied Files
The description says:
Files copied with a 'Copy Files Build Phase' are unchanged by default. Setting this to TRUE causes Property Lists (.plist) and Strings files to be converted as specified by 'Property List Output Encoding' and 'Strings file Output Encoding'.. [APPLYRULESINCOPYFILES]
This description says it all, we have to find another flag Strings file Output Encoding.
Specify the encoding to be used for Strings files (by default, the output encoding will be 16-bit Unicode). The value can be either an NSStringEncoding, i.e. one of the numeric values recognized by NSString, or it can be an IANA character set name as understood by CFString. The operation will fail if the file cannot be converted to the specified encoding. [STRINGSFILEOUTPUT_ENCODING]
Set Strings file Output Encoding to
UTF-16, that's it.