Cantara Multi Language FAQ
Identify all the fields in the mobile app that you want translated (Labels + Warning Messages).
Compile a list of these fields.
Manually workout the Spanish (or specific language) translation.
We then construct a Spanish (or specific language) Translation File that is installed onto the Device.
The Device MUST be set to the Spanish (or specific language) Locale.
When the user opens the mobile app, everything that has been translated now appears in Spanish (or any other language specified).
No. Dropdown content is sourced directly from JD Edwards (E1) and is not translated by the application.
Yes, it works on both. While the approach is similar, Android and iOS have separate native implementations.
The device’s language setting controls which translation is displayed. Setting the Android device to Spanish will activate the Spanish content within the app.
Language is controlled via the iOS device’s system settings. If a device is shared by English and Spanish users, the language must be manually changed in Settings—this can be inconvenient.
Recommendation: Use dedicated English and Spanish devices in shared environments. Because devices are generally low-cost, this is rarely a major issue—unless managing thousands of units.
Translation is generally handled by the customer. For Rinami to estimate effort or cost, we would need to understand the scope—specifically which app, how many labels, and how many error messages are involved.
No. Rinami only translates hardcoded (baked-in) application error messages. Any messages sourced from E1 are displayed exactly as received and are not translated.
No. E1 error messages are not translated by the app. If translations are needed, new Spanish error messages must be created and associated accordingly.
For checklists, separate Spanish UDCs were created for Spanish-speaking users.
It can be handled by Rinami, the customer, or jointly. Typically, the customer’s native Spanish-speaking users review and validate translations.
Where possible, we reuse existing translations. Otherwise, we use tools such as Google Translate, and translations are then verified by a native speaker. Ultimately, it is the client’s responsibility to confirm translation accuracy.
Technically, yes—but in practice, it's not ideal. Switching device language settings frequently is inconvenient for users.
Recommendation: Use separate devices for each language to ensure a smoother experience for both English and Spanish speakers.