Translation FAQS

Overview

• If you want to view translated pages of LoopDocs, please click on Translation.

• If you want to view your app on your phone in a different language, instructions are found at Translated App on the Phone.

• If you want to help provide translations for everyone to use on their phone with their app (Loop, Trio, or iAPS), please click on Code Translation.

Translated App on the Phone

You can select the language you want displayed for any given app in your phone settings.

If you have only one language on your phone, you will not see choices under the app settings. Click on the link below (for Apple instructions) to add language options to your phone.

• Add more than one language to your phone

Once your phone is configured to have more than one language, then the steps below should work.

• Tap on phone Settings
• Scroll down and tap on Apps
• Choose your app, e.g., Loop
• Scroll down to Preferred Language
• Choose the language you prefer

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.

For the Loop app and the submodules (Pumps, CGM and Services) associated with the Loop app, the lokalise website is used. You must be signed up with the Loop project to be able to see Loop translations at that site.

Want to Translate?

To volunteer to translate, join Loop zulipchat and send a direct message to Marion Barker with your email address and the language(s) you can translate.

If you want translate one of the new CGM / Pump repositories: DanaKit, EversenseKit and MedtrumKit, indicate that as well. Those new repositories are handled using a crowdin project for each repository.

Code Translation

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).

If you notice Loop app messages in English even though you selected a specific language, and you can help translate it, please volunteer.

Loop lokalise project

Translations for most of the repositories used by Loop are performed by volunteers at lokalise.

Some newer CGM and Pump modules, currently found in feature branches, get their translations from crowdin instead of lokalise.

• There was an early attempt to use both lokalise and crowdin but merging input from two sources was deemed impractical
• The DanaKit, MedtrumKit and EversenseKit translations are each handled by separate crowdin projects

crowdin projects

Some new pump and CGM modules are provided by developers associated with the Trio (OpenAPS) community. They have an established base of translators who are familiar with using crowdin. Translations for each of these new repositories is handled directly at the repository level. Loop translators who want to help with these repositories can just add that information to the request when they volunteer to translate.

• DanaKit crowdin
• MedtrumKit crowdin
• EversenseKit - not configured yet, coming soon

Volunteer to Translate

To volunteer, join Loop zulipchat and send a direct message to Marion Barker with your email address and the language(s) you can translate. Indicate whether you need access to the new repositories (crowdin) in addition to the Loop repositories. You will get an invitation to join the Loop lokalise project. You do not need to start a new lokalise project. Do not start a free lokalise trial or sign up for anything special; just join the project you are invited to.

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.

Alternative contacts for addtion to crowdin:

• Bastiaan Verhaar in zulipchat
  • Bastiaan is known as INeedSugar in Trio discord and iAPS discord
• lubor in iAPS discord

Lokalise Information

Initial Screen on lokalise

When you log in to lokalise, you will see a screen similar to the screenshot below. Tap on the Loop icon, highlighted in the graphic with a red rectangle, to start translating.

After tapping on the Loop icon, you see the general translation tasks. (Your screen may look different.)

On the left are keys with the English language showing. On the right is the translation for that key in the language you selected. Each key has one or more words. The statistics list the total number of keys and the total number of words.

How to Find Strings to Translate

You can search for:

• strings that are not translated, which show up as Empty
• strings in a particular submodule (for example - the Pump or CGM that you use)
• strings where the English version was copied to the translated field
• strings where you disagree with the translation
  • some strings may have been automatically translated
  • some translations may have a typographical error

Not Translated

Strings that have not been translated can be selected by tapping on Filter and choosing Untranslated. An example graphic is shown before choosing untranslated keys. First tap on Filter than tap on Untranslated.

Enter a Translation

After tapping on an item that is empty or you want to modify, type your translation into the box on the right, where you see the words "enter translation here" in the graphic below.

Notice the filename where that key is stored is indicated when you examine the details of a key. In the graphic above, the file Loop/Loop/Localizable.xcstrings is indicated.

The area under the key has a comment. This is something added in the code to explain the use of the key.

If a key does not have a translation in a given language, then when running the app, the English version is automatically provided. Do not tap on Insert source.

The only reason to use Insert source would be if that key should always be identical to the English version and you want to avoid having that key show up when looking for untranslated keys.

Select a Submodule

Suppose you know that you want to modify translations for a particular submodule (CGM, Pump or Service module). You can choose context in lokalise; or if it is one of the newer submodules, go directly to the crowdin project for that submodule. See Submodule Table for Multiple Apps for a detailed listing.

• Tap on Filter
• Tap on Context
• Choose the submodule file
  • some submodules have multiple string catalogs (*.xcstrings)
  • some items are old enough to have a few of the older string format (*.strings)
• You can ignore any file that includes "Info.plist"
  • those strings do not need to be translated and the keys should be configured to be hidden from translators

The screenshot below is configured for someone translating simplified Chinese for the DanaKit pump.

NOTE The DanaKit keys are no longer visible in lokalise. They are being handled using crowdin.

Matches Source

Some of the String Catalogs have had the English version inserted in the translation field. This was done inadvertently. To find these instances in the language you are translating, set up a custom filter.

First click on Filter, then Customize (see red highlights in graphic below)

The next screen allows you to choose Translation in one drop-down and then matches source in the adjacent drop-down.

You can hit Apply or Save and Apply and give it a name so you can select the Name next time.

The screenshot below is after creating and naming a custom filter called Translation Matches Source.

Find a String

If you observe a string you want to modify, you can type it in directly. The text you type in the search box can be all or part of a string, and in English or the language you are translating.

---

What About Other iOS Apps

The Trio and the iAPS apps use submodules for CGM, Pump and Service features originally developed for the Loop app. New CGM and Pump modules are coming soon or already available. These are being configured for use with all these iOS apps.

• The shared code originally developed for the Loop app resides in the GitHub LoopKit organization and is under the control of the LoopKit owners
• The Trio app has always used forks for these repositories so get their localizations for the CGM, Pump and Service modules from lokalise
• The iAPS app initially used copies of the code - not connected to the LoopKit repositories - and configured their own crowdin site for iAPS localization
  • However, as improvements to the submodules evolved at LoopKit, the updates needed to be hand-edited and added to the iAPS copies
  • In late 2025, iAPS started the transition to using forks from LoopKit instead of copies
  • Some of the iAPS translations for CGM, Pump and Service submodules were imported into lokalise at this time

The bottom line is

• Loop and older (pre 2025) submodule translations are handled at lokalise
• New submodules, DanaKit, EversenseKit, and MedtrumKit. are currently handled in crowdin projects for the individual repositories
• Trio translations are handled at crowdin for Trio
• iAPS translations are handled at crowdin for iAPS

You can use the Trio or iAPS discord server to volunteer to translate using lokalise by sending a direct message to Marion Barker if you are not a member of zulipchat.

Submodule Table for Multiple Apps

These submodules are used by the Loop, Trio and iAPS apps and are handled by lokalise.

Type	Name	Files
CGM	CGMBLEKit	CGMBLEKit/CGMBLEKit/Localizable.xcstrings CGMBLEKit/CGMBLEKitUI/Localizable.xcstrings
CGM	G7SensorKit	G7SensorKit/G7SensorKit/Localizable.xcstrings G7SensorKit/G7SensorKitUI/Localizable.xcstrings
CGM	LibreTransmitter	LibreTransmitter/LibreTransmitter/Localizable.xcstrings LibreTransmitter/LibreTransmitterUI/Localizable.xcstrings
CGM	Dexcom Share	dexcom-share-client-swift/ShareClient/Localizable.xcstrings dexcom-share-client-swift/ShareClientUI/Localizable.xcstrings
CGM	NightscoutRemoteCGM	NightscoutRemoteCGM/NightscoutRemoteCGM/Localizable.xcstrings
Pump	OmniBLE	OmniBLE/Localizable.xcstrings OmniBLE/OmniBLE/Localizable.xcstrings
Pump	RileyLinkKit	RileyLinkKit/RileyLink/Localizable.xcstrings RileyLinkKit/RileyLink/LoopKit.xcstrings RileyLinkKit/RileyLinkBLEKit/Localizable.xcstrings RileyLinkKit/RileyLinkKitUI/Localizable.xcstrings
Pump	MinimedKit	MinimedKit/MinimedKit/Resources/Localizable.xcstrings MinimedKit/MinimedKitUI/Resources/Localizable.xcstrings MinimedKit/MinimedKitUI/Resources/mul.lproj/MinimedPumpManager.xcstrings
Pump	OmniKit	OmniKit/Localizable.xcstrings OmniKit/OmniKit/Resources/Localizable.xcstrings OmniKit/OmniKitUI/Resources/Localizable.xcstrings
Misc	LoopKit	LoopKit/LoopKit/Resources/Localizable.xcstrings LoopKit/LoopKitUI/Resources/Localizable.xcstrings LoopKit/LoopKitUI/Resources/mul.lproj/InsulinKit.xcstrings LoopKit/LoopKitUI/Resources/mul.lproj/LegacyInsulinDeliveryTableViewController.xcstrings LoopKit/MockKit/Resources/Localizable.xcstrings LoopKit/MockKitUI/Resources/Localizable.xcstrings
Service	TidepoolService	TidepoolService/TidepoolServiceKit/Localizable.xcstrings TidepoolService/TidepoolServiceKitUI/Localizable.xcstrings

These submodules are used by the Loop, Trio and iAPS apps and are handled by crowdin.

Type	Name	Files
Pump	DanaKit	see DanaKit crowdin
Pump	MedtrumKit	see MedtrumKit crowdin
CGM	EversenseKit	crowdin project is not yet configured

The modules are specific to the particular app:

Type	Name	Files
Loop	Loop	use Loop lokalise
Trio	Trio	use Trio crowdin
iAPS	iAPS	use iAPS crowdsin

---

Adding Languages

We can add languages if a translator commits to take on that task.

At lokalise, the language must be added first before translators have access to that language. Send a DM to Marion Barker with your request for a new language.