Open Jeehut opened 1 year ago
Consider consulting Apple Glossaries for this feature.
I use https://gov.wales/bydtermcymru/search for Welsh (official government resource for translating between English and Welsh) - it is an open source CSV (https://github.com/cwd24/termcymru) if it was able to be used 👀
I know Welsh is one of those awkward languages with it's half support from Apple (as per #32)
@Sherlouk This sounds like an extra feature that would need extra logic. For example, I'd need to implement a logic to download and update the file when needed (I won't be shipping a >5 MB CSV file for all users in the app if it's only needed for those supporting Welsh) and maybe even a setting to use it or not.
Could you create an extra issue for that so I don't forget and can track the interest separately? Thank you!
I would like to add some more thoughts to this feature: Apple has a lot of own terms for their apps and features. For example the Shortcuts
app is localized and is called Kurzbefehle
in German. This name can also appear in sentences and it would be good to exclude them from the translation. I guess this is the hardest part of the feature because you send a string with a missing word to the translation API and you don't know where the word belongs then.
Example sentence:
Start the Shortcuts App and create a new Shortcut.
this looks great. Would be brilliant to incorporate Apple's glossaries...
@ConfusedVorlon It's already noted, see https://github.com/FlineDev/RemafoX/issues/55#issuecomment-1316403649. :)
Problem Statement
Machine translation is most useful for longer texts, but shorter buttons like "Done" or "Save" tend to be translated wrong in some languages as they can have multiple correct translations depending on the context, and a single word doesn't make the context very clear, leading to many wrong translations.
Suggested Solution
For common words such as "Done" or "Save" a validated translation should be provided to common languages and these translations should be used automatically instead of using machine translation for them.
Additional Considerations
Possibly, existing translations could even be checked for these common texts and an auto-correction functionality could be provided. How this should look in the UI is unclear though.
Consider also open-sourcing the "common translations" list to a public repository so the community can correct mistakes and or provide evaluated translations to more languages.
Also consider supporting things like gender forms or politeness levels for these from which one could be selected per app.