|
| 1 | +## Overview |
| 2 | + |
| 3 | +* If you want to view translated pages of `LoopDocs`, please click on [Translation](../translate.md). |
| 4 | + |
| 5 | +* If you want to view your app on your phone in a different language, instructions are found at [Translated App on the Phone](#translated-app-on-the-phone). |
| 6 | + |
| 7 | +* If you want to help provide translations for everyone to use on their phones, please click on [Code Translation](#code-translation). |
| 8 | + |
| 9 | +## Translated App on the Phone |
| 10 | + |
| 11 | +You can select the language you want displayed for any given app in your phone settings. |
| 12 | + |
| 13 | +If you have only one language on your phone, you will not see choices under the app settings. Click on the first link (for Apple instructions) to add language options to your phone. |
| 14 | + |
| 15 | +* [Add more than one language to your phone](https://support.apple.com/en-us/109358) |
| 16 | + |
| 17 | +Once your phone is configured to have more than one language, then the steps below should work. |
| 18 | + |
| 19 | +* Tap on phone Settings |
| 20 | +* Scroll down and tap on Apps |
| 21 | +* Choose your app, e.g., `Loop` |
| 22 | +* Scroll down to Preferred Language |
| 23 | +* Choose the language you prefer |
| 24 | + |
| 25 | +{width="600"} |
| 26 | +{align="center"} |
| 27 | + |
| 28 | +If a given phrase in the app does not have a translation string in what is called the String Catalog, then the app displays English. If you see an English phrase and you want to help yourself, and others, you can become a translator. |
| 29 | + |
| 30 | +For the *Loop* app and the submodules (Pumps, CGM and Services) associated with the *Loop* app, the [*lokalise*](https://app.lokalise.com/projects) website is used. You must be signed up with the *Loop* project to be able to see *Loop* translations at that site. |
| 31 | + |
| 32 | +## Code Translation |
| 33 | + |
| 34 | +Localization (strings translated to the selected language in the app) makes use of volunteers who input translations in a special web app. Their work is then dowloaded and imported into the code used by the *Loop* app and its submodules (repositories on *GitHub*). |
| 35 | + |
| 36 | +If you notice *Loop* app messages in English even though you selected a specific language, and you can help translate it, please volunteer. |
| 37 | + |
| 38 | +Translations for Loop are performed by volunteers at [*lokalise*](https://app.lokalise.com/projects). |
| 39 | + |
| 40 | +To volunteer, join [Loop zulipchat](https://loop.zulipchat.com/) and send a direct message to Marion Barker with your email address and the language(s) you can translate. |
| 41 | + |
| 42 | +> If you are using the *Trio* or *iAPS* app instead of the *Loop* app, you can still assist with pump, CGM and Tidepool module localization through *Loop* *lokalise*. Some repositories from *Loop* are used by [*Trio* and *iAPS*](#what-about-other-ios-apps). |
| 43 | +
|
| 44 | + |
| 45 | + |
| 46 | +### Initial Screen on *lokalise* |
| 47 | + |
| 48 | +When you log in to *lokalise*, you will see a screen similar to the screenshot below where the *Loop* icon is highlighted with a red rectangle. Tap on that icon to start translating. |
| 49 | + |
| 50 | +{width="600"} |
| 51 | +{align="center"} |
| 52 | + |
| 53 | +After tapping on the *Loop* icon, you see the general translation tasks. (Your screen may look slightly different - some items may require more permissions that are standard.) |
| 54 | + |
| 55 | + |
| 56 | +{width="600"} |
| 57 | +{align="center"} |
| 58 | + |
| 59 | + |
| 60 | +### How to Find Strings to Translate |
| 61 | + |
| 62 | +Typically you would search for strings that are not translated. |
| 63 | + |
| 64 | +### Untransalated |
| 65 | + |
| 66 | +### How to Select a Submodule |
| 67 | + |
| 68 | +Suppose you know that you want to modify translations for the OmniBLE submodule (anything to do with the DASH pump). You can choose context as a translator in *lokalise*. The example screenshot is configured for someone translating simplified Chinese for the DanaKit pump. |
| 69 | + |
| 70 | +{width="900"} |
| 71 | +{align="center"} |
| 72 | + |
| 73 | +## What About Other iOS Apps |
| 74 | + |
| 75 | +The *Trio* and the *iAPS* apps use code for CGM, pumps and services originally developed for the *Loop* app. |
| 76 | + |
| 77 | +* The shared code originally developed for the *Loop* app resides in the *GitHub* *LoopKit* organization and is under the control of the *LoopKit* owners |
| 78 | +* The *Trio* app has always used forks for these repositories so get their localizations for the CGM, pumps and services modules from *lokalise* |
| 79 | +* The *iAPS* app initially used copies of the code - not connected to the *LoopKit* repositories - configured their own crowdin site for *iAPS* localization |
| 80 | + * However, as improvements to the submodules evolved at *LoopKit*, the updates needed to be hand-edited and added to the *iAPS* copies |
| 81 | + * In late 2025, *iAPS* started the transition to using forks from *LoopKit* instead of copies |
| 82 | + * Some of the *iAPS* translations were imported into *lokalise* |
| 83 | + |
| 84 | +The bottom line is |
| 85 | + |
| 86 | +* Submodule translations are handled at [*lokalise*](https://app.lokalise.com/) |
| 87 | +* *Trio* translations are handled at [crowdin for Trio] |
| 88 | + |
| 89 | + |
| 90 | +* The *Trio* app and the *iAPS* apps each have their own translation sites |
| 91 | + * Both of those apps have a crowdin site configured |
| 92 | + * Initially *iAPS* used copies of some of the |
| 93 | + |
| 94 | +You can use the *Trio* or *iAPS* discord server to volunteer by sending a direct message to Marion if you are not a member of zulipchat. |
0 commit comments