I kept getting error message saying "The default localizable file not found.Please create your default localizable file."

I have set up the project have different targets and each has its own plist.so i don't have the default info.plist. is that an issue?

xcode 6.1

rename info.plist as Filo-Info.plist, added Localizable.strings file but i get that error.

please add the possibility to select manually the file... so you have nobody with this error

First let me thank you for this cool plugin. I'm followed all the instructions you included but I can't figure out why the plugin won't recognize Localizable.strings as the default Localizable strings file for Xcode 5.1.1/iOS 7.1. I do have 2 other Pods that utilize a strings file and am wondering if that could be the cause. The demo app works fine. I would appreciate any help so I can use this potentially useful plug in.

Hey,

I am really keen to use this but can't seem to get it to work on xcode 6.3.2 working with swift.

The menu item isn't showing on the menu bar.

And when I type the keyboard shortcut nothing happens either.

Please let me know if you would like some more information.

Thanks for what looks like a great tool.

Villy

Hi there, I gave a shot to your plugin, installing it with Alcatraz, and it worked in the first place. But after restarting XCode, the shorcut doesn't appear in the refactor menu. I tried reinstalling it using Alcatraz (Remove then Install), and the shortcut appear but doesn't do anything. I don't face any other problems with other plugins installed using Alcatraz.

Hi @viniciusmo , https://github.com/chintan1891/extract-localizable-string-plugin-xcode I have forked source code of this plugin and tried to enhance its features to make it more usable. My forked source code contains below features:

• Removed "Choose Localizable File" menu. Plugin will now find all Localizable.strings files and add key-value pair into it.
• Plugin will validate if user is not adding a duplicate key.
• Plugin will alert user if he/she tries to add any value which is already exists.
• Plugin now provides option to add comment for any Localizable string.
• Current plugin stores Localizable file path into NSUserDefaults, due to which if i switch my project, this plugin will add key value pair to Localizable.strings file of old project. Fixed this bug.
• Added Cancel button in "Extract Lcoalizable String" popup.

Please look into my forked source code, and provide your suggestion. I can create a pull request if you want to add these features.

• Fixed comments in Swift code (previously created comments like ““my comment““)
• Improved comment formatting in Localizable.strings file
• Changed shortcut from ⌥⇧E to ⌥⇧L

If the key already exists, the user can now choose whether he wants to use the same key again or cancel. Using the same key again results in skipping the existing-value-check.

I want to change comment from nil. But when I click to option + shift + d , comment just be nil. Is there an other shortcut for making comment different string.

Removed "Choose Localizable File" menu. Plugin will now find all Localizable.strings files and add key-value pair into it. Plugin will validate if user is not adding a duplicate key. Plugin will alert user if he/she tries to add any value which is already exists. Plugin now provides option to add comment for any Localizable string. Current plugin stores Localizable file path into NSUserDefaults, due to which if i switch my project, this plugin will add key value pair to Localizable.strings file of old project. Fixed this bug. Added Cancel button in "Extract Lcoalizable String" popup.

Hi Vinícius:

Thanks for share this wonderful plugin, it has been saved tons of development hours!

Unfortunately, the plugin does not work at all in latest XCode version: XCode 7.3 (7D175), fix it please!

The command "Extract Localization String" is not displayed in the Edit -> Refactor menu, and the shortcut is not working either...

I tried reinstalling the plugin, using two ways: Alcatraz and Building the source project, neither of them made the plugin to work as always...

Thanks again for this Must-Have plugin! I hope it gets fixed soon...

Rigoberto Saenz Imbacuan https://www.linkedin.com/in/rsaenzi

When extracting a strings that contains a %@ format specifier, the @ symbol is not extracted properly

@"Hello %@, thanks for looking at this"

is extracted into the localized strings file as

"Hello %, thanks for looking at this"

The "@" symbol is stripped out