extract-localizable-string-plugin-xcode icon indicating copy to clipboard operation
extract-localizable-string-plugin-xcode copied to clipboard

no key created in any localized files, not work in xCode6.4 ?

Open maimake opened this issue 9 years ago • 16 comments

I reinstall this plugin, and restart xCode 6.4 , still not working.

Nothing is created in any localized files.

I don't know why

maimake avatar Aug 21 '15 08:08 maimake

Same story

greenmood avatar Oct 01 '15 11:10 greenmood

Xcode version?

viniciusmo avatar Oct 09 '15 19:10 viniciusmo

Same in Xcode 7.0.1 (7A1001), or does it require the Localizable.strings file to be in project root?

EdwinOtten avatar Oct 13 '15 10:10 EdwinOtten

same here Xcode 7.0 no key created and cannot select file

croccio avatar Oct 13 '15 16:10 croccio

I found the problem (in my case): I already had a Localizable.strings file (in multiple languages) in a folder called "Resources" inside my project folder. The localized strings created by the plugin were actually added to another Localizable.strings (in a folder called "[ProjectName]-assets") which is not included in my workspace.

I just created all the localized strings I needed and then copied them to the right language file to keep things simple.

EdwinOtten avatar Oct 14 '15 08:10 EdwinOtten

i've open all strings file, and key there isn't

croccio avatar Oct 14 '15 08:10 croccio

@croccio Try to refactor your string with the plugin and use a certain key (e.g. "my_key"). Then do a command+Z to undo and do the same thing again with the same key ("my_key"). The plugin should warn you that the key already exists, if this is the case then the key is saved somewhere. The question is where..

EdwinOtten avatar Oct 14 '15 09:10 EdwinOtten

no, plugin doesn't tell me that key already exists

croccio avatar Oct 14 '15 09:10 croccio

Okay, and you did create the Localizable.strings file like the README.md shows?

@viniciusmo Does the plugin give a error if it can't find the Localizable.string?

EdwinOtten avatar Oct 14 '15 09:10 EdwinOtten

yes i create it as read show

croccio avatar Oct 14 '15 09:10 croccio

I'm getting the same issue in 7.1. I create the strings file as shown. Only difference is my project doesn't have a base localisation.

Megatron1000 avatar Nov 02 '15 10:11 Megatron1000

It happens to me the same thing.

HeltonSampaio avatar Jan 19 '16 15:01 HeltonSampaio

Same here, doesn't work at all

MagnusJohansson avatar Jan 19 '16 20:01 MagnusJohansson

It would be good if in the README.md, you indicate the process to download and test the plugin from source code. I would like to help trying and submitting pull requests, but I have no idea about getting started after downloading your code.

jeryRazakarison avatar Feb 07 '16 23:02 jeryRazakarison

For a temporary fix:

  • Copy the full path of your Localizable.strings
  • Open the project ExtractorLocalizableStrings downloaded from Github
  • In [EditorLocalizable getDefaultLocalizableFilePath], add return <Full path to your Localizable.strings>; at the very top of the method.
  • In [EditorLocalizable localizableFilePaths] add return @[<Full path to your Localizable.strings>];
  • Compile the project
  • Restart XCode Now, the keys should be added to the Localizable.strings.

When I have time, I will look into why these two methods can't find the file and return nil

jeryRazakarison avatar Apr 07 '16 08:04 jeryRazakarison

Hi All,

Following steps worked for me -

  1. Remove extract-localizable-string-plugin-code using alcatraz
  2. Reinstall it.
  3. relaunch Xcode.

Thanks

Amandeep-iOS avatar Sep 07 '16 05:09 Amandeep-iOS