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
Something that Scribe-iOS will need to implement for a common localization process with Scribe-Android is to have a common JSON directory that has all of the localized strings that are needed for the app. This directory would then be controlled by Scribe-i18n in a way that changes to i18n would then trigger PRs in Scribe-iOS and Scribe-Android (and any other repos). We'll need a base en-US.json file and then a file for any other language that we're localizing Scribe into 😊
We're choosing to stick with JSON to assure that localization tools like Transifex or weblate can be used for community localizations. We have some texts like the privacy policy that need formatting and thus their own .swift files, but for individual like menu option labels these can be stored within a common file. The general idea would be to save them in a JSON and then make use of SwiftyJSON to load them in and access the key-value pairs.
Parts to this issue:
See if there's a good extension for this that is well maintained
Set up Transifex/Weblate for Scribe
Explore commits from external source i18n software to i18n repo to this repo
Switch over string references in the menu to use JSON keys for localized strings
Contribution
Happy to discuss the implementation of this and work on it or support! The focus should be on first getting all the English texts into the system, and then we can move over to Scribe-i18n to start adding in new languages that will then be triggered when the user changes their system language.
The text was updated successfully, but these errors were encountered:
Terms
Description
Something that Scribe-iOS will need to implement for a common localization process with Scribe-Android is to have a common JSON directory that has all of the localized strings that are needed for the app. This directory would then be controlled by Scribe-i18n in a way that changes to i18n would then trigger PRs in Scribe-iOS and Scribe-Android (and any other repos). We'll need a base
en-US.json
file and then a file for any other language that we're localizing Scribe into 😊We're choosing to stick with JSON to assure that localization tools like Transifex or weblate can be used for community localizations. We have some texts like the privacy policy that need formatting and thus their own
.swift
files, but for individual like menu option labels these can be stored within a common file. The general idea would be to save them in a JSON and then make use of SwiftyJSON to load them in and access the key-value pairs.Parts to this issue:
Contribution
Happy to discuss the implementation of this and work on it or support! The focus should be on first getting all the English texts into the system, and then we can move over to Scribe-i18n to start adding in new languages that will then be triggered when the user changes their system language.
The text was updated successfully, but these errors were encountered: