Xcode CopyStrings defaults to UTF-8 when no encoding specified on UTF-16 file

Originator:jeremy.knope
Number:rdar://13218994 Date Originated:14-Feb-2013 04:52 PM
Status:Duplicate/12647913 Resolved:
Product:Developer Tools Product Version:4.6/4H127
Classification:Other Bug Reproducible:Always
 
Summary:
If you have a UTF-16 strings file, commonly created from older versions of Xcode, Xcode will auto-detect that it's UTF-16 in the UI but will fail to treat it as such during build.  CopyStrings will produce a warning saying it detected that it's UTF-16 and not UTF-8 like it was told. 

Steps to Reproduce:
1. Add a UTF-16 strings file to a project (iconv -f UTF-8 -t UTF-16 Localizable.strings > Localizable2.strings is oen way of getting one if using Xcode 4.6)
2. Hit build

Expected Results:
No warnings

Actual Results:
Warning about strings file being UTF-16 instead of the specified UTF-8. 

Notes:
File inspector on strings file indicates "Default (UTF-16)" so there's no indication why it's doing UTF-8. Manually changing to UTF-16 will make warning go away.

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!