If Localizable.strings files have different sets of keys the output gets messed up badly about babelish

[netbe]

Hi @ekurutepe,

Could you be more explicit on what do you expect? Do you an example we can work on ?

Thanks ;)

[ekurutepe]

Sure. I’m working on it now. Expect a detailed example or pull request later today :)

E.

On 23 Oct 2013, at 11:17, François Benaiteau [email protected] wrote:

Hi @ekurutepe,

Could you be more explicit on what do you expect? Do you an example we can work on ?

Thanks ;)

—
Reply to this email directly or view it on GitHub.

[ekurutepe]

This one is caused when running strings2csv as such:

strings2csv -i en.lproj/Localizable.strings de.lproj/Localizable.strings

Since the lang_order array is filled with basename(filename), it ends up being all :Localizable.

Not good.

What do you say we just take the full file path as the key in the lang_order array? It seems to work for me.

[netbe]

Yep need to change:
https://github.com/netbe/CSV-to-iOS-Localizable.strings-converter/blob/master/lib/strings2csv/converter.rb#L18-L23

Using the file path will work if you assume you always use .lproj/Localizable.strings maybe good idea for default headers to parse this .

Other solution is to use the --headers and specify what you want as headers:
https://github.com/netbe/CSV-to-iOS-Localizable.strings-converter/blob/master/lib/strings2csv_command.rb#L12

[netbe]

@ekurutepe version 0.2.2 includes this change, thanks. Available on Rubygems