genstrings doesn't include String(localized:)

Question

Created Jun ’23

Replies 2

Boosts 0

Participants 3

I've noticed that genstrings does not include String(localized:) in the .strings exports. I created a feedback but was wondering if anyone had any work arounds. I know there is Export Localizations, but that creates a .xliff which itself has other issues like changing \n and & to html encoded characters. This then also seems to mess up directory structure if you import them back as it puts them into the root folder and not into my localization folders. This would be fine if I wanted to do everything manually but I'm looking to automate this during the CI phase.

Boost

Answer 1

MobileTen OP

Jun ’23

Not sure why you will automate something like this during a CI phase outside of any development and developer quality checks for any layout issues before release.

0

Answer 2

Systems Engineer OP

Apple

Jun ’23

Hi, I’d encourage you to take a look at Discover String Catalogs: https://developer.apple.com/wwdc23/10155

About the directory structure, you can move the file on import the first time, but this should be improved with String Catalogs.

The Export and Import Localizations options in Xcode have a command-line equivalent to use in CI.

2