I had written a blog post about how troublesome it is to handle UTF-16 .strings files in my source tree. I've decided to store my strings files as UTF-8 to eliminate confusion with endian issues, and also so that these files can actually be diff'd in GitHub rather than appearing as binary blobs.
The final remaining step has been to somehow override genstrings' propensity to output in UTF-16. That means that I'd have to follow up with a conversion to UTF-8 so that my generated strings files (which I store in my source tree) don't get changed into UTF-16.
I've added UTF-8 output as an option to the demo "genstrings2" here, to make that step easier. Maybe others will find it useful as well. Yes, this extends the abilities of genstrings. Hopefully that is OK.
Add "-utf8" generation option to make it easier to store your source …
…tree .strings files in UTF-8, which is much easier to manage. (Modern Xcode will copy your .strings files into UTF-16 into the binary anyhow, so no need to store them as UTF-16.)