# Internalization Readiness, Localization, and Unicode for Mobileforce Products

- Updated on Dec 3, 2024
- Published on Feb 6, 2024

Since all Mobileforce products use the same underlying low-code/no-code platform, it becomes crucial to ensure that the platform as well as the products (CPQ, FSM, Connected Portal) are designed and developed in a way that can be adapted to different languages, cultures, and regions without requiring changes to the source code.

The Mobileforce Platform is i18N ready. This means that the platform

- separates text and other user UI content from the source code,
- formats data and content in a way that is easily adaptable for different locales

The Mobileforce FSM Application has already been localized for Italian. Localization involves adjusting user interfaces on a cultural level going beyond what is being shown to how it's being said.

The following Mobileforce **strings, dates, currencies, and numbers** in data, tables, and code have undergone various levels of internalization readiness :**

- Mobile App: Strings
- UI Response : messages
- Application description language (ADL): strings
- Scripts, especially server-side: UI responses.
- Mobileforce APIs: and their responses
- Datatable layouts: Strings
- Database tables: strings therein that are exposed in the UI.

Mobileforce applications have various levels of localization, with FSM having a specific localization into Italian.

## Unicode in Mobileforce Products

Mobileforce Products support the use of Unicode **(3 byte UTF-8)** in various UI and screen elements. For example, to create the Trademark (TM) as a special superscript symbol, one can use the Unicode: "™" to get the "Trademark" symbol:

Code snippet

````none
™
````

So, instead of the string "AskCPQ Proposals", you could also specify

"AskCPQ ™ Proposals"

which would render as follows: