Version: 4.0.214
Website: https://www.globallinkstrings.com
Changelog: https://www.globallinkstrings.com/changelog/android
The Applanga plugin only is compatible with projects using the Android Gradle Plugin 7+.
If you still depend on Android Gradle Plugin 4+ please use Applanga version 3+.
We rewrote big parts of the plugin to align with the newest AGP APIs. Which makes the build a lot faster and more stable.
We changed the package name of the plugin, you also can add it now via the plugins{} block in your build.gradle.
The Applanga SDK will automatically initialize as soon as the first activity starts. This overcomes a lot of issues we had in the past regarding wrong initialization especially connected to deep link scenarios. You still can manually initialize Applanga, this is only needed if you want to use Applanga before an activity has started. For example, if you want to do an Applanga.update() on startup before an activity has started.
Applanga.wrap() is not needed anymore, it's done automatically by the plugin.
We deprecated Applanga.getString methods as we cover all usual getString() calls without further configurations and we have seen a lot of confusion about the existence of Applanga.getString calls.
We removed all Applanga.getQuantityString calls as all native getQuantityString calls are covered by Applanga.
Applanga.setDraftModelEnabled has a typo and was renamed to Applanga.setDraftModeEnabled.
Applanga does not require jitpack.io as a repository in your build.gradle files anymore. If you still use jitpack.io for any reason, we recommend to move mavenCentral() above jitpack.io as it's more reliable and order matters.
The Applanga SDK comes with an Applanga Gradle Plugin. Both work closely together so make sure they have the exact version number. The responsibility of the plugin is to proxy all your getString or setText calls to the Applanga SDK so that you receive the latest over-the-air updates.
Add the Applanga maven repository and the Applanga dependency to your app/build.gradle file.
// $projectDir/app/build.gradle
repositories {
maven { url 'https://maven.applanga.com/'}
}
dependencies {
implementation 'com.applanga.android:Applanga:4.0.214'
}
As shortly described above, the plugin is responsible for proxy all relevant getString calls through the Applanga SDK.
It also collects data from your resource files, which is needed for accurate translations of specific views.
This metadata data is stored in applanga_meta.xml in your assets/ folder. It's recommended to ignore these files and not commit them to your repository.
// .gitignore
...
*applanga_meta.xml
There are two different ways how to apply this plugin.
// $projectDir/app/build.gradle
plugins {
...
id 'com.applanga.gradle' version '4.0.214'
}
Insert our Applanga maven repository to the pluginManagement.repositories section.
// $projectDir/settings.gradle
pluginManagement {
repositories {
...
google()
mavenCentral()
maven { url 'https://maven.applanga.com/'}
}
}
Apply the plugin and add the Applanga maven repository to the buildscript.repositories.
// $projectDir/app/build.gradle
apply plugin: 'com.applanga.gradle'
...
buildscript {
repositories {
google()
mavenCentral()
maven { url 'https://maven.applanga.com/' }
}
dependencies {
classpath 'com.applanga.gradle:plugin:4.0.214'
}
}
IMPORTANT: Applanga SDK and Applanga Plugin should always have the same version number!
In order to keep all SDK functionality fully available when using Proguard, please make sure that the following lines are part of your Proguard configuration.
```
-keep class **.R$* {
<fields>;
}
-keepattributes JavascriptInterface
-keepclassmembers class * {
@android.webkit.JavascriptInterface <methods>;
}
```
The easiest way to initialize Applanga in your Application is by extending your Application class from ApplangaApplication.
import com.applanga.android.ApplangaApplication;
public class MyApplication extends ApplangaApplication {
...
}
If you do not have an Application class you can simply add the following to the <application .../> section of your AndroidManifest.xml
<application
android:name="com.applanga.android.ApplangaApplication"
...
>
...
</application>
NOTE: If you cannot extend ApplangaApplication, you have to call Applanga.init(), followed by Applanga.update() in your Application class manually (see Update Content).
You can also choose to manually init the Applanga SDK like so:
//called from an activity
Applanga.update(new ApplangaCallback() {
@Override
public void onLocalizeFinished(boolean b) {
//continue loading your app
}
});
The advantage of this method is that you could stop the app from loading any texts until the Applanga SDK has pulled the latest strings from the dashboard.
In this example app, you can see that we have a loading screen activity that inits and updates Applanga, and then loads the first Activity in the app once the update is complete.
Missing Strings Once Applanga is integrated and configured, it synchronizes your local strings with the Applanga dashboard every time you start your app in Debug Mode or Draft Mode if new missing strings are found.
All strings located in your project's values folder (e.g. strings.xml) will be uploaded. Applanga only skips the upload if they meet the following conditions (according to Non-translatable Strings):
Strings annotated with translatable="false" will be ignored, e.g.:
<string name="STRING_ID_IGNORED" translatable="false">This string will not be uploaded</string>
Strings inside an XML file named donottranslate.xml or a file with the following prefix: donottranslate- will not be uploaded.
Callbacks
To get notified on Localization Updates (e.g. to show a LoadingScreen at beginning of your App) override the onLocalizeFinished method in your Application class ( assuming you extend ApplangaApplication ).
public class MyApplication extends ApplangaApplication {
...
@Override
public void onLocalizeFinished(boolean success) {
//do something on finished localization
}
...
}
String Localization
There is not always the need to rewrite your code everywhere you want to get translated Strings. The following shows the usage with and without explicit Applanga calls:
3.1 Simple String
If the string exists locally in your project:
// get translated string for the current device locale
((Activity|Resources|Fragment)this).getString(R.string.STRING_KEY);
For dynamic keys retrieved from the backend or other sources outside of your resource files,
you can call Applanga.getTranslation but you need to make sure the key exists on Applanga or else the method will return null.
The dynamic keys will not be created automatically on the Applanga Dashboard.
Applanga.getTranslation("STRING_KEY");
3.2 Arguments
// get translated string with formatted arguments
// using the default string format %s %d etc
// @see http://developer.android.com/reference/java/util/Formatter.html
((Activity|Resources|Fragment)this).getString(R.string.STRING_KEY, "arg1", "arg2", "arg3");
The dynamic key equivalent:
Applanga.getTranslation("STRING_KEY", "arg1", "arg2", "arg3");
3.3 Named Arguments DEPRECATED!
We deprecated named Arguments and it will be removed on the next major release. If you want to align your placeholder logic on Android and iOS please have a look at the Convert Placeholders section.
// DEPRECATED!
// if you pass a string map you can get translated string
// with named arguments. %{someArg} %{anotherArg} etc.
Map<String, String> args = new Map<String, String>();
args.put("someArg","awesome");
args.put("anotherArg","crazy");
Applanga.getString("STRING_KEY", args);
Example:
STRING_ID = "This value of the argument called someArg is %{someArg} and the value of anotherArg is %{anotherArg}. You can reuse arguments multiple times in your text which is %{someArg}, %{anotherArg} and %{someArg}."
gets converted to:
"This value of the argument called someArg is awesome and the value of anotherArg is crazy. You can reuse arguments multiple times in your text which is awesome_, crazy_, _ awesome._"
3.4 Pluralisation
// get a string in the given quantity
((Resources)res).getQuantityString(R.plurals.STRING_KEY, quantity);
On the Dashboard, you create a pluralized ID by appending the Pluralisation rule to your ID in the following format: [zero], [one],[two],[few],[many], [other]. Plural strings also get automatically uploaded if you start the app in draft mode or with the debugger connected.
So the zero pluralized ID for "STRING_KEY" is "STRING_KEY[zero]"
You also can get quantity strings dynamically:
Applanga.getQuantityTranslation("STRING_KEY", quantity);
Dynamic quantity translations have the limitations as described for getTranslation: If the passed string key does not exist on the dashboard, it returns null.
It doesn't automatically create the string key on the dashboard if it doesn't exist yet.
3.5 String-Arrays
//returns a string-array
((Resources)res).getStringArray(R.array.STRING_KEY);
String-Arrays will automatically be uploaded as other strings from your string XML. The ID-format is the following: STRING_KEY[0], STRING_KEY[1], STRING_KEY[2], STRING_KEY[..].
You also can get string arrays dynamically:
Applanga.getTranslationArray("STRING_KEY");
Dynamic translation arrays have the limitations as described for getTranslation: If the passed string key does not exist on the dashboard, it returns null.
It doesn't automatically create the string key on the dashboard if it doesn't exist yet.
3.6 Styled Strings
We do not support html tags in xml files yet. To make the upload of styled strings from your strings.xml work you have to escape the html tags.
<string name="styled_string">Hello, <b>I am bold</b>.</string>
If you don't escape your styled strings in your strings.xml, then the html tags a stripped out with the missing string upload.
However if you translate your strings on the Applanga dashboard, you don't have to escape the html tags.
To get the styled String as a SpannableString use Html.fromHtml() as explained in the official Android documentation.
textView.setText(Html.fromHtml(getString(R.string.styled_string), Html.FROM_HTML_MODE_LEGACY));
Preference Localization
With Applanga's plugin Preference Localization is mostly automated as of Applanga version 3.0 but it is important that every PreferenceItem, even a PreferenceCategory, has to have a key - if you want to enable Applanga's localization.
After a preferences has been localized there will be a log output stating: "localize Preferences!".
As an example a working preference XML would look like this:
<?xml version="1.0" encoding="utf-8"?>
<PreferenceScreen xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools">
<PreferenceCategory
android:key="example_category_key"
android:title="@string/example_category_key_title">
<Preference
android:key="example_pref_key"
android:title="@string/example_pref_title"/>
</PreferenceCategory>
</PreferenceScreen>
We added linter warnings for all preference items without a key.
To disable those warnings you can add tools:ignore="ApplangaPreferenceKeyMissing" to your item or to the parent to disable the linting for all child items as well. E.g.:
<?xml version="1.0" encoding="utf-8"?>
<PreferenceScreen xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
tools:ignore="ApplangaPreferenceKeyMissing">
<PreferenceCategory
android:title="@string/example_category_key_title">
<Preference
android:title="@string/example_pref_title"/>
</PreferenceCategory>
</PreferenceScreen>
Menu Localization
Menu localization does not require any additional code to work. Important is that every menu item must have an id.
The logic here is similar to the Preference Localization in the section above.
We also added lint checks, you can disable them with tools:ignore="ApplangaMenuIdMissing".
Here is a small example with one item without an id and one with an id with disabled linting:
<?xml version="1.0" encoding="utf-8"?>
<menu xmlns:tools="http://schemas.android.com/tools"
xmlns:android="http://schemas.android.com/apk/res/android">
<item android:title="@string/main_menu_no_id_title"
tools:ignore="ApplangaMenuIdMissing" />
<item android:id="@+id/main_menu_change_language"
android:title="@string/main_menu_change_language"/>
</menu>
Update Content
To trigger an update call:
Applanga.update(new ApplangaCallback() {
@Override
public void onLocalizeFinished(boolean success) {
//called if update is complete
}
});
This will request the baselanguage and the long and short versions of the device's current language. If you are using groups, be aware that this will only update the main group.
To trigger an update for a specific set of groups and languages call:
List<String> groups = new ArrayList<>();
groups.add("GroupA");
groups.add("GroupB");
List<String> languages = new ArrayList<>();
languages.add("en");
languages.add("de");
languages.add("fr");
Applanga.update(groups, languages, new ApplangaCallback() {
@Override
public void onLocalizeFinished(boolean success) {
//called if update is complete
}
});
Change Language
Android 13 introduced the per-app language preference.
If you implement your own language picker within your app, make sure to call Applanga.update(groups, languages, callback) with the new language, otherwise the language will change, but there are no OTA updates until the next update call.
Also, make sure your settings file is up-to-date.
That's how you can switch languages while the app is running and it will show the most recent strings from your settings file even though the Applanga.update wasn't working due to network connection or simply didn't happen.
The AppCompat library also works together with the Applanga SDK. For switching languages you can do the following: AppCompatDelegate.setApplicationLocales(appLocale);
Important to note if you have used the legacy method Applanga.setLanguage() or Applanga.setLanguageAndUpdate(). It stores the changed language to your device.
To delete its settings you need to call Applanga.setLanguage(null) once.
You should consider using the per-app language preferences as described above.
You can change your app language at runtime using the following call:
// this changes the language but your initial update call may have not covered this language
// so it's good practice to do an Applanga.update() afterwards or use the `setLanguageAndUpdate` method
boolean success = Applanga.setLanguage(language);
// - or -
// this sets the language and directly does an update for the language before returning here
Applanga.setLanguageAndUpdate(language, applangaCallback);
language must be the iso string of a language that has been added to the dashboard. The return value will be true if the language could be set, or if it already was the current language, otherwise, it will be false. After a successful call, you should recreate the current activity, for the changes to take effect. The set language will be saved, to reset to the device language call:
Applanga.setLanguage(null);
For the app to reset to the device language it needs to be restarted.
The language parameter is expected in the format [language]-[region] or language**_region** with the region being optional. Examples: "fr_CA", "en-us", "de".
If you have problems switching to a specific language you can update your settings file or specifically request that language within an update content call (see 8. Update Content). You can also specify the language as a default language to have it requested on each update call (see Optional settings).
WebViews
Applanga can also translate content in your WebViews. You have to enable JavaScript and pass your WebView to Applanga's attachWebView(WebView webView):
WebView myWebView = (WebView) findViewById(R.id.webview);
myWebView.getSettings().setJavaScriptEnabled(true);
myWebView.loadUrl("html_file_path");
Applanga.attachWebView(myWebView);
You also need to set the following in your Manifest:
<meta-data android:name="ApplangaTranslateWebViews" android:value="true" />
To initialize Applanga for your web content you need to initialize Applanga from JavaScript:
<script type="text/javascript">
window.initApplanga = function() {
if(typeof window.ApplangaNative !== 'undefined'){ window.ApplangaNative.loadScript();
} else { setTimeout(window.initApplanga, 180); }
}; window.initApplanga();
</script>
8.1 Strings
The inner text and HTML of tags that have a applanga-text="STRING_ID"``` attribute will be replaced with the translated value of STRING_ID
<div applanga-text="STRING_ID">
***This will be replaced with the value of STRING_ID***
</div>
Alternatively, you can call Applanga.getString('STRING_ID') directly.
8.2 Arguments
You can pass arguments with the applanga-args attribute.
By default, the arguments are parsed as a comma-separated list which then will replace fields as %{arrayIndex}.
<div applanga-text="STRING_ID" applanga-args="arg1,arg2,etc">
***This will be replaced with the value of STRING_ID***
***and formatted with arguments***
</div>
Direct call : Applanga.getString('STRING_ID', 'arg1,arg2,etc')
To define a different separator instead of , e.g. if your arguments contain commas use applanga-args-separator.
<div applanga-text="STRING_ID"
applanga-args="arg1;arg2;etc"
applanga-args-separator=";">
***This will be replaced with the value of STRING_ID***
***and formatted with arguments***
</div>
Direct call : Applanga.getString('STRING_ID', 'arg1,arg2,etc', ';')
One Dimensional JSON Objects can also be used as Named Arguments if you add applanga-args-separator="json"
<div applanga-text="STRING_ID"
applanga-args="{'arg1':'value1', 'arg2':'value2', 'arg3':'etc'}"
applanga-args-separator="json">
***This will be replaced with the value of STRING_ID***
***and formatted with json arguments***
</div>
Direct call : Applanga.getString('STRING_ID', "{'arg1':'value1', 'arg2':'value2', 'arg3':'etc'}", 'json')
8.3 Pluralisation
To pluralize an HTML tag you can pass the applanga-plural-rule attribute with the values zero, one, two, few, many, and other.
<div applanga-text="STRING_ID"
applanga-plural-rule="one">
***This will be replaced with the pluralized value of STRING_ID***
</div>
Direct call : Applanga.getPluralString('STRING_ID', 'one') or with arguments : applanga.getPluralString('STRING_ID', 'one', 'arg1;arg2;etc', ';')
You can also pluralize by quantity via applanga-plural-quantity
<div applanga-text="STRING_ID"
applanga-plural-quantity=42>
***This will be replaced with the pluralized value of STRING_ID***
</div>
Direct call : Applanga.getQuantityString('STRING_ID', 42) or with arguments : applanga.getQuantityString('STRING_ID', 42, 'arg1;arg2;etc', ';')
8.4 Update Content
To trigger a content update from a WebView use javascript:
Applanga.updateGroups("GroupA, GroupB", "de, en, fr", function(success){
//called if update is complete
});
Draft Mode
To enable support for Draft Mode in your application, override the dispatchTouchEvent method in your targeted activity and forward the event to Applanga.dispatchTouchEvent. To enable Draft Mode, hold down four fingers for four seconds in this activity. A dialog appears asking you to enter a key code, which is the first four characters of your app secret and can also be found in your app's main view on the dashboard. When the right key is entered, the application will switch to Draft mode and quit, restart it manually. The Draft mode can be disabled in the same way as it was enabled. Please be aware that not all Android devices support multitouch with four fingers.
@Override
public boolean dispatchTouchEvent(MotionEvent ev) {
Applanga.dispatchTouchEvent(ev, this);
return super.dispatchTouchEvent(ev);
}
The draft mode overlay also requres the alert permission to work, please add it to your manifest like so:
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>
Automatic Screenshot Upload
The Applanga SDK offers the functionality to upload screenshots of your app, while collecting meta-data such as the current language, resolution and the Applanga translated strings that are visible, including their positions. Each screenshot will be assigned to a tag. A tag may have multiple screenshots with differing core meta-data: language, app version, device, platform, OS, and resolution.
You can read more here: Manage Tags and here: Uploading screenshots.
NOTE: To capture screenshots the app needs permission to _“_Draw over other apps”* so on the first try to make a screenshot the app might redirect you to the permissions screen to enable it.
10.1 Make screenshots manually
To manually make a screenshot you first have to set your app into draft mode.
With your app in draft mode, all you have to do is to make a two-finger swipe downwards. This will show the screenshot menu and load a list of tags.
The two-finger swipe will work in activities that pass on their mouse events via dispatchTouchEvent as shown previously.
You can now choose a tag and press capture screenshot to capture and upload a screenshot including all meta-data for the currently visible screen and assign it to the selected tag. Tags have to be created in the dashboard before they are available in the screenshot menu.
10.2 Display screenshot menu programmatically
You also have the option to display the screenshot menu programmatically, this also requires the app to be in draft mode:
Applanga.setScreenShotMenuVisible(true);
10.3 Make screenshots programmatically
To create a screenshot programmatically you call the following function:
String tag = "Mainmenu";
List<String> applangaIDs = new ArrayList<>();
applangaIDs("StringID1");
applangaIDs("StringID2");
Applanga.captureScreenshot(tag, applangaIDs);
The Applanga SDK tries to find all IDs on the screen but you can also pass additional IDs in the applangaIDs parameter.
10.4 Make screenshots during UITests
To capture screenshots from UITests like espresso, you just have to call the above function shown in Make screenshots programmatically while executing a test with Googles UITest frameworks. This function will also work in draft mode or debug mode.
The Applanga SDK automatically finds the tags of all texts on screen, but if for some reason a text is not tagged or the SDK cannot find the correct tag. There are different reasons for it, the most common reason is strings set during runtime. The best method to get all current strings on the screen correctly tagged is with the show id mode.
The show id mode shows all string ids instead of the translations. With this mode enabled the SDK can collect all string IDs on the screen. It's more reliable than OCR and it works even with localizations set at runtime.
Usage:
Applanga.setShowIdModeEnabled(true);
Note: If setIdModeEnabled is set after showing a specific screen, you have to recreate the activity or set the flag before initializing your screen.
10.6 OCR screenshots
The Applanga SDK automatically finds the tags of all texts on screen, but if for some reason a text is not tagged or the SDK cannot find the correct tag, you may take a screenshot programmatically using the enableOcr param like so.
Applanga.captureScreenshot(tag, applangaIDs, true);
Please note: in most cases enabling OCR is not necessary and will slow down the processing of screenshots for the dashboard, so please only use it if needed. Feel free to reach out to Applanga support for more info.
Multi-project setup
The multi-project setup is the same as described in Installation.
You only have to add the SDK and the Applanga plugin to your module if the module contains translatable resources (string.xml or layout files), if it inflates layouts from other modules or if you simply want to use the Applanga SDK for any reason. Otherwise, modules without the Applanga SDK and plugin remain untranslated.
Custom ViewPump Initialization
If you are already using ViewPump in your app for example if you use Calligraphy it is advised to initialize ViewPump before Applanga.init(...) because that way all interceptors will stay active. If you need to initialize it at a later stage please make sure to cache and re-add the existing interceptors as shown in the sample below.
//cache existing (Applanga) interceptors
List<Interceptor> interceptors = ViewPump.get().interceptors();
//create a new ViewPump.Builder
ViewPump.Builder builder = ViewPump.builder().addInterceptor(
new CalligraphyInterceptor(
new CalligraphyConfig.Builder()
.setDefaultFontPath("fonts/Roboto-ThinItalic.ttf")
.setFontAttrId(R.attr.fontPath)
.build()));
//re-add cached (Applanga) interceptors
for(int i = 0; i < interceptors.size(); i++) {
builder.addInterceptor(interceptors.get(i));
}
//re-initialize ViewPump
ViewPump.init(builder.build());
Unit Testing and Robolectric
When running Unit tests, Applanga only returns local resources.
The Applanga Plugin replaces all getString() calls with the Applanga SDK.
Depending on your tests, make sure that Applanga is initialized with a (mocked) Context, to be able to access your local resources.
In most cases Applanga can initialize itself, so it's may not necessary to do so.
The following log output should appear: Unit tests are running! Applanga returns local strings only. and if you use Robolectric you should see Robolectric in use..
If you don't see the logs or encounter any other issues please contact us.
Get available languages
It is possible to get the currently added languages on the dashboard:
// java
List<String> languages = Applanga.getAvailableLanguages();
// kotlin
val languages = Applanga.getAvailableLanguages()
The result will contain the iso string of each language that has been added on the dashboard.
These values are synced during the Applanaga.update() response. So to retrieve any changes to the available languages on the dashboard, an update() should be performed manually before using this list.
Specify default groups or languages
You can specify a set of default groups and languages in the manifest, which will be updated on every Applanga.update() call. These groups and languages will be added to any that are specified in the call itself, they will always be requested. The Parameter value must be a string, with a list of groups or languages separated by commata.
Specify default groups
<application>
...
<meta-data android:name="ApplangaUpdateGroups" android:value="tutorial,chapter1,chapter2"/>
...
</application>
Specify default languages
<application>
...
<meta-data android:name="ApplangaUpdateLanguages" android:value="en,de-at,fr"/>
...
</application>
Automatic Applanga Settings File Update
In case your app's user has no internet connection, new translation updates can't be fetched, so the Applanga SDK falls back to the last locally cached version. If the app was started for the first time, there are no strings locally cached yet so Applanga SDK falls back to the Applanga Settings File which contains all strings from the moment it was generated, downloaded, and integrated into your app before release.
To minimize the manual effort of updating the Applanga Settings File, we created a task that triggers the Applanga Settings File generation if changes were made and replace the old one with the new one in your app.
Be aware that the task will not fail if there is no internet connection, to be able to develop offline. In this case, a warning is printed. To activate the Automatic Settings File Update put the following line into your build.gradle:
// for all builds:
applanga.settingsFileAutoUpdate = true
// only for release builds:
applanga.settingsFileAutoUpdateRelease = true
To make sure that the script is running and to see when it does or doesn't update, check the detailed build report in Android Studio after triggering a build. There you will find logs for each update step.
If the file is updated successfully you should see the log "Settings File UPDATED". If it is already up to date you will see the log "Settings File UP-TO-DATE".
Disable automatic string updates when extending the ApplangaApplication Class
If you are initializing the SDK by extending or including the provided ApplangaApplication class, but you wish to manually control when the SDK communicates with our servers and updates to the latest strings, then you can include the following setting in your application manifest.
<application>
...
<meta-data android:name="ApplangaInitialUpdate" android:value="false"/>
...
</application>
This setting will stop the automatic updates and allow you to call Applanga.update() at any time that suits you
Disable Draft Mode
If you wish to create a build that cannot enable draft mode at any time, you can include the following setting in your manifest.
<application>
...
<meta-data android:name="ApplangaDraftModeEnabled" android:value="false"/>
...
</application>
You can also use the following method at runtime
Applanga.setDraftModelEnabled(bool);
This will override the setting in the manifest, but it will not override draft mode being disabled in the Applanga dashboard.
Convert Placeholder
To convert placeholders between iOS and Android styles you need to enable the following in your Manifest:
<application>
...
<meta-data android:name="ApplangaConvertPlaceholders" android:value="true"/>
...
</application>
Common placeholder
These placeholders will not be converted as they are supported on iOS and Android.
%e and %E%c and %C Unicode Characters%f floating point number%g and %G computerized scientific notation%a and %A Floating point numbers%o (for %O see Android to iOS conversion)%x and %X hexadecimal presentation using lowercase letters (%x) or uppercase letters (%X)%d will remain %d%1$s are converted to %1$@ and vice-versaiOS placeholder
%@ will be converted to %s%s%g and %p are converted to %d%i, %u, %U are converted to %d%f and %F will be converted to %f%s is not supported and remains %s which will be an Android String%p iOS Pointer will be converted to Android integer %d%O Octal integer is converted to %o%D is converted to %dLanguage Mapping
You can map a locale to another locale. For example, if you don't have es-CL added to your dashboard it usually has a fallback to es. But if you want to treat es-CL as es-MX then you could add it to the map. Watch out for the log: ApplangaLanguageMap: es-CL is mapped to es-MX
Example:
<application>
...
<meta-data
android:name="ApplangaLanguageMap"
android:value="zh-Hant-HK=zh-HK,es-CL=es-MX" />
...
</application>
The locale is mapped in all places in the sdk, except when used in combination with custom language fallback. In this case the custom fallback performed as set in the referenced xml, no additional mapping occurres for the entries in that xml. If you have a locale that maps to another locale that has a custom fallback, this would also work, and the custom fallback will be performed after the mapping.
Enable system language fallback
By default applanga uses a custom device locale order, this meta-data value makes the SDK iterate over the languages by using the priority set by the system. This order is used when translating strings and performing a fallback when the string wasn't found for a specified language. Then the SDK would try to translate using the next language in the list. The available possibilites are:
applanga: The default SDK order
system: Use the device system order
<application>
...
<meta-data
android:name="ApplangaLanguageFallback"
android:value="system" />
...
</application>
Enable custom language fallback
This meta-data value is a resource reference to an xml which allows to set a custom fallback per language. When the SDK would need to translate a key with a specified language, it uses the order as provided. This overrides any other system or default fallbacks only for those languages. Other languages work according to the fallback specified using the ApplangaLanguageFallback value (or default if it's not set). The fallback is only overriden for the top level language, so it's not possible to "nest" the custom fallbacks.
Example
<application>
...
<meta-data
android:name="ApplangaCustomLanguageFallback"
android:resource="@xml/custom_fallback" />
...
</application>
the xml should be structured like this:
<?xml version="1.0" encoding="utf-8"?>
<custom_fallback>
<language name="es-MX">
<item>es-MX</item>
<item>es-US</item>
<item>es</item>
</language>
<language name="de-DE">
<item>de-AT</item>
<item>en</item>
</language>
</custom_fallback>
Automatic upload of a tag with current app strings
In case you would like to upload a tag with all the local strings in your app, add the following key in the Manifest
<application>
...
<meta-data
android:name="ApplangaTagLocalStringsPrefix"
android:value="some_tag" />
...
</application>
This manifest value would be used as the tag prefix combined with the app version (for example some_tag1.0), then when you are running with the app with the debugger connected, an automatic tag upload would be performed after Applanga.update(), which is also done on app start. The tag would be created on the dashboard if it doesn't exist yet.
The ApplangaSDK supports stringResource() and stringArrayResource().
Jetpack Compose screenshots are less accurate when doing screenshots manually with the draft menu. To have accurate string positions you have to pass them to the SDK while doing tests. A compose test rule is needed as shown in the example below. The example does two screenshots: One with showIdMode enabled - to link all strings correctly to the current tag - and then it does a 'normal' screenshot where all translations are visible.
@get:Rule
val composeTestRule = createAndroidComposeRule(JetpackComposeActivity::class.java)
private fun stringPositionsToString(
positions: Map<String, Rect>,
isInShowIdMode: Boolean
): String {
var json = "{\"ALStringPositions\":[";
positions.forEach {
json += "{"
if (isInShowIdMode) {
json += "\"key\": \"${it.key}\","
}
json += "\"value\": \"${it.key}\","
json += "\"x\": \"${it.value.left}\"," +
"\"y\": \"${it.value.top}\"," +
"\"width\": \"${it.value.width}\"," +
"\"height\": \"${it.value.height}\"},"
}
json = json.substring(0, json.length - 1) + "]}"
return json
}
private fun getStringPositions(
nodes: Iterable<SemanticsNode>,
positions: Map<String, Rect> = mapOf()
): Map<String, Rect> {
var mutablePositions = positions.toMutableMap();
nodes.forEach { node ->
val pos = Rect(node.positionInWindow, node.size.toSize())
node.config.forEach { configValue ->
val key = configValue.key.name
if (key === "Text") {
val values = configValue.value
if (values is Collection<*>) {
values.forEach { value ->
if (value is AnnotatedString) {
mutablePositions[value.text] = pos;
}
}
}
}
}
mutablePositions =
getStringPositions(node.children, positions = mutablePositions).toMutableMap()
}
return mutablePositions;
}
@Test
fun testUploadStringsWithShowIdMode() {
Applanga.setShowIdModeEnabled(true)
composeTestRule.activity.runOnUiThread {
composeTestRule.activity.recreate()
};
val pos = getStringPositions(composeTestRule.onAllNodes(isEnabled()).fetchSemanticsNodes())
val jsonString = stringPositionsToString(pos, true)
Applanga.captureScreenshot("jetpack_compose_activity", null, jsonString, null);
Applanga.setShowIdModeEnabled(false)
}
@Test
fun testUploadStrings() {
val pos = getStringPositions(composeTestRule.onAllNodes(isEnabled()).fetchSemanticsNodes())
val jsonString = stringPositionsToString(pos, false)
Applanga.captureScreenshot("jetpack_compose_activity", null, jsonString, null);
}
If your project is a branching project use at least SDK version 4.0.184 and update your settings file.
The settings file defines the default branch for your current app.
This branch is used on app start and for update calls.
To be sure branching is working look for the log line: Branching is enabled.
To learn more about branching please have a look here.
When enabling the Draft Mode you can switch your branch at runtime - an app restart is required. You also can use our draft overlay to switch your current branch. Every screenshot you take is linked to the current branch.
Already published apps that still use settings files without branching and older SDKs will still work and they will use the "main" branch.