@096d2c53 @21f06d90 Using a switch as you did is great to benefit automatic localization export (especially with String Catalog), and detecting that let’s say a new flavor introduced later doesn’t get forgotten for localization.

For automatic export, the compiler needs the string to be declared as a raw string somewhere (or inferred).

I’d use the fact that LocalizedStringResource & String.LocalizationValue are ExpressibleByStringLiteral.

https://files.mastodon.social/media_attachments/files/111/173/756/513/003/073/original/7275c8341d29cbe1.png 

 @096d2c53 @21f06d90 LocalizedStringResource can either be initialized with a raw [static] string, .init(aRawString), or .init(aLocalizationValue).
Would the latter one work? 

 @21f06d90 @096d2c53 Exactly but it should work if you can make `name` a String.LocalizationValue