You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apple supports providing string definitions for a number of sub-English languages including (but not limited to):
British (en-GB)
American (en-US)
Canadian (en-CA)
Australian (en-AU)
I highlight these ones in particular because they are notable, large, audiences which applications may find value in providing custom translations for.
It would be helpful if Stringz provided the option to automatically adapt translations made in one English language into one or more other English languages from those highlighted above. The most important (and well documented) option being to translate American English into British English and vice-versa.
There are a number of open-source libraries and command line tools which achieve this functionality, so we would need to reinvent the wheel.
In this example, the user would only provide one translation (such as British English) and the strings file for the other languages (such as American English) would be automatically generated and maintained by Stringz providing the alternate translations where necessary.
The text was updated successfully, but these errors were encountered:
Overview
Apple supports providing string definitions for a number of sub-English languages including (but not limited to):
I highlight these ones in particular because they are notable, large, audiences which applications may find value in providing custom translations for.
Language Differences
https://en.wikipedia.org/wiki/American_and_British_English_spelling_differences
Image Source: Wikipedia
Feature Request
It would be helpful if Stringz provided the option to automatically adapt translations made in one English language into one or more other English languages from those highlighted above. The most important (and well documented) option being to translate American English into British English and vice-versa.
There are a number of open-source libraries and command line tools which achieve this functionality, so we would need to reinvent the wheel.
In this example, the user would only provide one translation (such as British English) and the strings file for the other languages (such as American English) would be automatically generated and maintained by Stringz providing the alternate translations where necessary.
The text was updated successfully, but these errors were encountered: