Renames .strings files into .xib and .storyboard for projects with Base localization

[lazarev]

Renames .strings files into .xib and .storyboard for projects with Base localization

[SpencerMichaels]

This is still a problem in the latest version; it makes synx totally unusable for apps with localization.

[tylermilner]

This issue is still present in the current version. Unfortunately, I didn't know about this before an app update went live and it broke localization in my app for thousands of our Spanish and French users. While it's nice that there is a work around to get things working again, Synx shouldn't be doing this in the first place.

[MrNickBarker]

We fixed this in our project like this:

1. Select the storyboard/xib
2. Un-tick the languages in the localisation panel that have been converted from .strings to .storyboard/.xib. Make sure that the "Delete localized resources from disk" is not checked in the popup.
3. In Finder open the language project folder (de.lproj, fr.lproj or whatever) and rename the .storyboard/.xib files back to .strings
4. Back in Xcode select the storyboard/xib and add re-add the localisations. Make sure to select the option to use the existing file in the popup.

[eugenpirogoff]

@numen31337

a friendly advice: cool down, its an FOSS project. take it or leave it. no need for harsh words here. and yes I ran into the same issue.

[erwald]

I have the same issue, and am, surprisingly, having trouble repairing it manually. If I rename the files back to .strings, Xcode won't let me insert them to the correct place in the project, and, moreover, it won't let me remove any references to the deleted files.

How did you go about fixing this @lazarev? It took me some days before I noticed, so I would rather not return to a previous commit.

Edit: Bah, never mind – I figured it out.

[isair]

+1

[Mazyod]

@erwald Just a thought: Did you check the encoding of the strings file? It may have changed in the process to something other than the required encoding UTF-16 (I think it's required to be that, at least).

[erwald]

@Mazyod Do you mean in order to re-add them? I think it's UTF-8 now, but it also works now again. I don't remember exactly what I had to do, but I think it was just another half an hour of fiddling in Xcode that did it.

[Mazyod]

@erwald Oh, got it. Yeah, I thought it was a requirement, but it seems to just be a best practice, it is not actually enforced. From Apple docs:

Note: It is recommended that you save strings files using the UTF-16 encoding, which is the default encoding for standard strings files.

[radex]

Ah, same issue here. Does the fix in #77 work well?

[eugenpirogoff]

Same issue here.

[beseder42]

Any progress possible on this? Still not useable on localized Projects!

[pschneider]

@MrNickBarker 's solution worked for us, too. Thanks!

[NikKovIos]

MrNickBarker's answer works, but it's poor that the issue still presents.

[numen31337]

Same issue here, noticed it too late and already done a lot of changes in the project to just reverse a commit. This was the last time for us when we were using this utility. This is unacceptable for the apps that are in production.

[seasox]

I ran into the same issue, was able to fix it using the diff of my app's project.pbxproj. Would be great to see a fix in an upcoming release.