Run all the strings through localization

The strings "DeepL" and "Apple Translate" are now also saved in
localizable.strings and addressed through keys. They were taken
directly previously, which was inconsistent.
This commit is contained in:
Paul Schuetz 2024-05-09 14:14:13 +02:00
parent a8201e2455
commit 86c5099662
No known key found for this signature in database
GPG Key ID: 4FDE1FB89050039E
2 changed files with 24 additions and 2 deletions

View File

@ -26160,6 +26160,28 @@
}
}
},
"enum.translation-type.apple" : {
"extractionState" : "manual",
"localizations" : {
"en" : {
"stringUnit" : {
"state" : "translated",
"value" : "Apple Translate"
}
}
}
},
"enum.translation-type.deepl" : {
"extractionState" : "manual",
"localizations" : {
"en" : {
"stringUnit" : {
"state" : "translated",
"value" : "DeepL"
}
}
}
},
"enum.translation-type.use-server-if-possible" : {
"extractionState" : "manual",
"localizations" : {

View File

@ -10,9 +10,9 @@ public enum TranslationType: String, CaseIterable {
case .useServerIfPossible:
"enum.translation-type.use-server-if-possible"
case .useDeepl:
"DeepL"
"enum.translation-type.deepl"
case .useApple:
"Apple Translate"
"enum.translation-type.apple"
}
}
}