cocoanetics/dtlocalizablestringscanner

An open source substitute for Apple's genstrings which can be integrated in Apps.

dtlocalizablestringscanner's Issues

need the support for omit the comments

If we can support this, I think that would be better. (comments may not be used)

Dealing with multi-line Strings

Apparently you can have strings that span multiple lines.

genstrings2 only recognizes the last part "with the option..."

Make Macro params optional

If the second parameter of NSLocalizedString(key, comment) would be optional then this would also support people using custom MacrosLike ODLocalizedString(key). The comment would be assumed to be nil.

Homebrew

Should the command line tool be added to Homebrew?

Output is broken if you have a NSLocalizedString with an empty string.

Description:
It seems Localized.strings must never contain a row like this:

"" = "";

If it does, the localization tables will mess up, and the application will complain it does not find strings in Foundation framework.

App warning looks like this:
Localizable string "(A Document Being Saved By %@)" not found in strings table "Document" of bundle CFBundle 0x12e508f60 </System/Library/Frameworks/Foundation.framework>
(need to have -NSShowNonLocalizedStrings YES as startup argument to enable the warning)

The original genstrings tool will not include empty strings, but output a warning.
DTLocalizableStringScanner unfortunately does include the empty string, and thus, the output is broken.

Proposed fix:
Make sure empty strings are never included in the output.

This can be done by adding:
if([key compare:@""""] == NSOrderedSame) {
continue;
}

in the for-loop in [DTLocalizableStringTable stringRepresentationWithEncoding], but there are probably better ways to do it :)