3.2.1

Fixes:

• Better error message when no Localizable.strings file found (#11)
• Escape double quotes and backslashes in translated strings (#19)

Improvements:

• Add & configure SwiftLint linter and fix all warnings & errors (#28)

3.2.0

New:

• Add support for Objective-C++ '.mm' files for subcommand code (#22)

3.1.0

New:

• Ignores NSLocalizedStrings which have ignore constant (e.g. #bc-ignore!) in comment (#16)

3.0.0

New:

• Sub Commands for updating interfaces / translate instead of options (like -t)
• New sub command to update Localizable.strings files from code

Changes:

• Streamlined names of options (force >> override, -s >> -p)
• Refactored quite some code

Removed:

• Input (-i), Exclude (-e) and Output (-o) options

Please have a look at the migration guide for a flawless upgrade from version 2.x.

2.0.0

New:

• Reworked option -a (auto) to take a path argument and renamed to -s (search)
• Automatic search for files now also possible when using -t (translate) via -s
• Translating adds missing keys by default, therefore -c option was dropped

Fixed:

• Improved build times when configured with Git root folder path

1.5.0

Adds support for adding missing keys to target translations Strings files via the -c command line option.

Note that the undocumented previous behavior of keeping keys in translation targets that didn't exist in translation source Strings files was dropped. From now on only keys that also exist in the source Strings file are kept in the target files to clean up target files. For most projects this change shouldn't have any effect.

1.4.2

Add support for Xcode 7.3 and Swift 2.2.

1.4.0

• Add support for automatically detecting all Storyboards/XIBs

Thanks to this change the suggested build script is now much shorter and will automatically adapt to new Interface Builder file additions. No need to keep the build script updated anymore (for incremental change updates)!

1.3.0

• Add comment Base value update support (only if structure not changed from defaults)
• Update actual translation value if same as Base (assuming comment value is previous Base value)

See #4 for further details on the rationale for the changes made here.

1.2.0

• Add option to use Base localization values when adding new keys