Custom Translation Layer

Product Suggestions
1

Hi Beth,

As a side question: is it possible to add additional ‘English’ selections under the language dropdown? That way a translation for a non-supported language can be manually implemented under the additional English selection? Better yet, include an option to select a translation language that can be named by the user and the player menu can remain in English?

I don’t know if my question is coherent. I can do a better job of explaining if it is not clear.

Best,
Kevin

2

@kkl -

This is a really interesting idea! I mad this a separate request, since it would be a separate bucket of work from just adding Arabic as one of the supported languages.

But I like the idea of you being able to “create your own language” and the do the translation yourself and save that for future use - am I understanding this the right way?

1 Like
3

Hi Beth,

When you say “do the translation yourself”, my understanding is that all of the in-app translations are performed ourselves (manually, not automatically). In the app/app player, the only thing that is done automatically is the app player menu buttons.

Let me describe the process I go thru when performing a translation just to make sure we are on the same page!

  1. App done. Original language is English.
  2. Now I want an Arabic version of the app.
  3. Go to app editor. Open app.
  4. In the language dropdown, select “Edit Languages”
  5. Add Arabic from the “additional languages” menu.
    Note: this is where I want Arabic to be included. It is currently not
  6. Back in the editor, select Arabic from the language dropdown.
  7. Manually open all of the static text in the app and make my translations
    Translations complete!
  8. In the app player, select Arabic.
    Note: this is where I want Arabic to be included. It is currently not
  9. Now, the app shows my manually entered Arabic translations. AND the player menu (the 5 or 6 buttons) are displayed in Arabic

The “create your own language” idea changes steps 5) and 8) above.

If the desired translation language is not supported in the app editor/player, the user would select “add new” from the additional languages menu, enter the name of their translation, and add their translations in the editor. When the created language is selected in the app player, the app translations would be present but the player menu buttons would be in English.

Right now, the Tulip community seems to be suggesting to make translations for non-supported languages under a random language. That is confusing. The app user (which there could be 100’s) must know which random language to select. Additionally, the menu buttons will be displayed in that random language.

If we can add a new language and edit the name, the menu buttons will still be in English, but at least the language will be readily identifiable in the player dropdown.

My explanation is not clear I don’t think. But let me know if it makes sense.