Ability to change Locale

[diamid6]

Could you please advise me, how can I change Locale.current here:

`private static func tr(_ table: String, _ key: String, _ args: CVarArg..., fallback value: String) -> String {

let format = BundleToken.bundle.localizedString(forKey: key, value: value, table: table)

return String(format: format, locale: Locale.current, arguments: args)
}`

[BastianKusserow]

I was just about to ask the same question. If an app has its own sense of how to localize their strings, I wonder if its correct that the String init from above gets the current locale as parameter. Apple is also not very specific about what happens with that locale (considering my format string has some string placeholders, I assume nothing will happen, but not sure about other types than strings?!).

[diamid6]

Locale affects the rule for plurals in Localized.stringdict. You may check it with two locales which has different cases for one, two, many, other. If I change locale in runtime without changing in Settings App, Locale.current is still will be the same. This can lead to incorrect string format as the result because for definition the correct plural case will being use Locale.current but not Locale(identifier: <new_locale_identifier>).

[BastianKusserow]

Ah yeah, that makes total sense! Our app has its own sense of localization and I assume that will likely break if the OS locale is different from the one of the app, which makes that lookup function a little useless for us now. I know we can always create our own template, but that would be much nicer thb..

[djbe]

The built-in templates support custom lookupFunctions, so you can do whatever crazy locale stuff you'd like. I would NOT recommend it at all (see @diamid6 comment about inconsistencies), but I know how projects & client requirements work 🤷

Read the template docs here: https://github.com/SwiftGen/SwiftGen/blob/stable/Documentation/templates/strings/structured-swift5.md

[BastianKusserow]

While that's true, in the end, even when using the lookup function, the last line of the tr function is always return String(format: format, locale: Locale.current, arguments: args). There the result returned from the lookup function is passed to the String(format:locale:) initializer and the locale that's passed there cannot be changed. This can lead to unexpected behavior in some cases.

[djbe]

Ah right, well in that case you should use custom templates (see docs).