##  [Use Case - Internationalization and Localization on Your Portal: Multi-Language Support](/use-case/multi-language-support) 

 ## Benefits



 

 

 

  ![](/sites/default/files/inline-images/card01%402x_0.png)



 

 

![](/sites/default/files/inline-images/card02%402x%20%281%29_0.png)



 

 

![](/sites/default/files/inline-images/card03%402x_0.png)



 

 

 

 

  ## The 

## Advantages of Multi-Language Support



 

 

From a **company**’s perspective, offering multiple language options expands reach, promotes inclusivity, and ensures non-English speakers feel welcome. It also opens doors to new markets as it supports international growth.

For **administrators and content editors**, this feature empowers them to craft a truly user-centric experience. By enabling users to choose their preferred language, editors facilitate better comprehension and engagement with the content.

As a **user**, the freedom to switch between languages allows for a deeper understanding of the content, especially for those who may be more comfortable reading in their native language. This flexibility ensures a seamless and enjoyable experience for everyone.



 

 

 

 

  ## From Missed Meaning to Missed Markets: Why Localization Matters



 

 

For a non-native speaker, understanding every content on a developer portal might be challenging and time-consuming.

Issues like the **misinterpretation of technical documentation increase the risk of implementation errors**, leading to inefficiencies. Without properly localized documentation, developers are more likely to **rely on customer support** for clarifications or **ultimately choose another vendor**. This can decrease adoption rates and limit the reach of APIs, SDKs, or other developer resources.

From a strategic business perspective, the absence of localization **hinders global expansion** and **reduces competitiveness**.



 

 

 

 

  ## Requirements and Limitations of Multi-Language Support

  
Managing multilingual content demands thorough editorial oversight, even with automated translations. At least one editor **should be fluent in the target language(s) and have technical expertise** in the developer portal’s subject matter to **ensure linguistic and technical accuracy**.

We recommend an active subscription to a translation service for automated content translations upon creation or updating of the original English content. Each option has its advantages and drawbacks, but some carry more risks than others:

- **Conventional machine translation tools** (excluding GenAI solutions) are not recommended for technical documentation, as they may produce inaccurate or misleading results.
- **Professional translation services** involving human translators can deliver high-quality results, but they are often expensive, and the translators may lack the technical expertise required for API documentation.
- **AI-powered machine translation** is generally effective, but it still requires human review, particularly for core documentation where accuracy is critical.



 

 

 

  Do you need help or want to know more about how Multi-Language Support can enhance developer experience and accessibility, and provide market growth? Reach out to us and let’s discuss your case.

[Contact us »](https://pronovix.com/contact "Pronovix's contact page")