LGTM, although I don't understand why the two Localizable.strings are both empty files?

There's... some sort of git setting necessary to override its defaults. Seems to think those plain-text files are actually binary for some reason.

There's... some sort of git setting necessary to override its defaults. Seems to think those plain-text files are actually binary for some reason.

https://stackoverflow.com/a/21020607/1836776

It thinks they are binary because they are UTF-16LE, which it doesn't recognise by default.

@jahorton - can you see if converting the .strings files to UTF-8 works?

From an SO thread there's a reference to Cocoa documentation about Xcode being able to copy and convert back to UTF-16

https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/LoadingResources/Strings/Strings.html

@jahorton you'll also need to convert the existing strings files from UTF-16 to UTF-8.

Took a bit to find it, but Xcode has this:

It doesn't show unless you've clicked within the file, for some reason. The other caveat... is that it simply doesn't work. "Convert" did literally nothing (even when applied in the UTF-8 direction). Had to use an online tool instead. Yet another case of "thanks, Apple!"

Had to use an online tool instead.

VSCode is my go-to for file encoding conversion, "Change file encoding" command

While the files still aren't viewable on this PR, using "View File" no longer talks about the file being binary, so it should be fixed for the future now.

Changes in this pull request will be available for download in Keyman version 14.0.253-beta

Changes in this pull request will be available for download in Keyman version 15.0.19-alpha