StringParser didn't work when using UTF-8 encoded title.strings file. about frameit HOT 7 CLOSED

.strings files should always be UTF-16. Have you created them in UTF-8? If so, I think frameit should detect this and show a proper error message. What do you think?

from frameit.

I created .strings files in UTF-8 because I didn't know .strings files should always be UTF-16. I appreciate if frameit tell this by error message.

from frameit.

strings files are UTF-16 by default, but UTF-8 works just fine inside iOS projects, why not handle both?

from frameit.

@voisine agreed, frameit should just handle both formats.

from frameit.

Ran into this too. This library looks like it could help with the charset detection and conversion: https://github.com/brianmario/charlock_holmes

from frameit.

Note, if you're creating your title.strings and keywords.strings files in Sublime Text, you'll need to save them as UTF-16 BE as the little endian option is not recognized by frameit either.

from frameit.

This issue was migrated to fastlane/fastlane#1747. Please post all further comments there.

fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo 🚀

from frameit.