#Psiphon vpn ios how to
#Psiphon vpn ios full

While running transifex_pull.py you may see some output like this: Do some smoke tests on those languages and commit. git status will show you which languages changed. transifex_pull.py from the project root (with a valid transifex_conf.json in place).

#Psiphon vpn ios how to

(Instructions for how to update the strings in PsiphonClientCommonLibrary can be found in that project's README.) You can run pod update PsiphonClientCommonLibrary or modify the target commit hash in the Podfile and then run pod install. Updating the PsiphonClientCommonLibrary strings involves updating the pod for that library in this project. The latter has the strings specific to this app. The former has the settings and feedback strings common to all Psiphon iOS apps. Translations for this project are in two places: in PsiphonClientCommonLibrary and in this project. Provide a comment in Root.strings for every entry - this is the description/context for translators.ДЄlso, make sure you implement required methods when adding a new specifier of IASKCustomViewSpecifier type, see InAppSettingsKit README.

#Psiphon vpn ios full

Use the ALL_CAPS form described above for the key (yes, that means that the plists will be full of non-English keys), as well as the minor/major edit considerations for changing a key. Like so:ДЇor items and strings not in PsiphonClientCommonLibrary: When adding or modifying strings, you must reflect the changes in. Many of the strings in those files are translated in PsiphonClientCommonLibrary, and so they should directly reference that bundle. ist: Settings specifically broken out to help with connection problems.: The root of - and majority of - the settings.They are all based on similar files in the PsiphonClientCommonLibrary project. plist files in this project (all under Psiphon/InAppSettings.bundle).

Commit that file with your change and Transifex will automatically pick up the change (overnight).in a. Do not be precious about existing translations: if meaning changes, change the key - the translations will catch up.ДЄfter adding or modifying a string, build the project, that will trigger genstrings.sh, which will update en.lproj/Localizable.strings. When making a major edit that should invalidate existing translations, also change the key. So, when making a minor edit to a string that does not fundamentally change its meaning, do not change the key. This allows us to change or fix the string without changing its key, thereby allowing us to not lose existing translations just because we fix a typo in the English (for example). must be in an ALL_CAPS form, and not just the string itself. is a description and of and context for the string to help translators correctly localize it. is the actual string shown to the user (in English).

NSLocalizedStringWithDefaultValue(, nil,, , )