Should not re-sort the keys when writing back .strings files

[tempelmann]

It makes it difficult to track the changes, e.g. in a version control system (git).

Also, I like to have my own ordering, where I group strings by purpose.

Another problem with the sorting is that it does not preserve comments at the end of a line. Example:

"Tr.trash_verb" = "löschen"; /* as a verb, i.e. to trash */

If this line gets reordered, the comment ends up with a different line.

Since the keys do not change while editing in this tool, I suggest to preserve the order of the keys when reading the file, and restoring them in the same order when writing back. Or by using a OrderedDictionary (though that's not a standard class in Cocoa, I'm afraid, unless Swift now has one?).

[igorkulman]

You are right the app does not correctly handle comments at the end of a translation, that is definitely a bug and should have its own separate issue (#52).

I thought about keeping the sort order in the beginning, but it seemed like too much work, especially when you realize every language file can have a different sort. So I decided to just always keep the strings sorted. I get that the first time you use the app you will get a commit with a huge unreadable diff but then it gets better :)

Anyway, I do not plan to implement this, but if you send a PR I will be happy to accept it.

[Tantalum73]

Hi @tempelmann, PR #53 should fix your issues with trailing comments 🙃