## Cómo Husar.ai y Devtranslate.app trabajan juntos para desbloquear la creación de contenidos multilingües

En el vertiginoso mundo digital de hoy en día, es más importante que nunca asegurarse de que su contenido resuena en audiencias globales. En **Husar.ai**, nos comprometemos a ayudar a las empresas y a los desarrolladores a crear, gestionar y publicar contenido multilingüe sin problemas. Pero, ¿cómo conseguimos unos flujos de trabajo de traducción escalables, precisos y basados en IA? La respuesta está en nuestra colaboración con **Devtranslate.app**.

### El poder de Devtranslate.app

En esencia, [Devtranslate.app](https://devtranslate.app) es una plataforma de traducción y localización de vanguardia adaptada a los flujos de trabajo de desarrollo modernos. Aprovecha potentes modelos de IA capaces de comprender el contexto, la sintaxis y la intención, haciendo que la traducción de texto, código y datos estructurados no sólo sea posible, sino también muy eficiente.

### Integración perfecta: Husar.ai se une a Devtranslate.app

Husar.ai integra Devtranslate directamente en su proceso de creación de contenidos. Así es como funciona:

1. **Creación de contenido:** Tú o tu equipo creáis contenido original en Husar.ai, ya sean entradas de blog, descripciones de productos, documentación o cualquier otro material basado en texto.
2. \*\*Cuando necesites llegar a audiencias en diferentes idiomas, Husar.ai pasa automáticamente tu contenido a Devtranslate.app.
3. **Traducción impulsada por IA:** Devtranslate toma el relevo, utilizando modelos de IA de última generación para generar traducciones precisas. Tanto si tu texto original es un simple inglés como si se trata de complejas estructuras JSON, el sistema entiende y se adapta a los distintos tipos de contenido.
4. **Localización automatizada:** Los algoritmos de Devtranslate conservan el formato, los fragmentos de código y la jerga específica del contexto, garantizando un resultado pulido para cada variante lingüística.
5. **Revisión y publicación:** El contenido traducido se envía sin problemas a Husar.ai, donde puede revisarlo, aprobarlo y publicarlo al instante en todas sus plataformas internacionales.

### Por qué Husar.ai eligió Devtranslate

* \*\*Devtranslate se especializa en la traducción de contenido centrado en el desarrollador, especialmente archivos JSON y documentación.
* **IA sensible al contexto:** A diferencia de las API de traducción genéricas, los modelos de Devtranslate conservan los matices técnicos, por lo que es ideal para documentos de productos, referencias de API, etc.
* **Flujos de trabajo automatizados:** La integración profunda significa que no tienes que exportar-importar archivos ni activar traducciones manualmente: Husar y Devtranslate se encargan de todo por ti.

### Desbloquee el crecimiento multilingüe

Tanto si está lanzando una aplicación en todo el mundo como si está dando soporte a clientes multilingües, la asociación entre **Husar.ai** y **Devtranslate.app** agiliza su proceso de traducción y localización. Con cero sobrecarga manual, traducciones de IA similares a las humanas y flujos de trabajo centrados en el desarrollador, sus equipos pueden centrarse en crear funciones, no en lidiar con las barreras lingüísticas.

\*\*¿Preparado para experimentar el futuro del contenido multilingüe? Deja que Husar.ai y Devtranslate.app sean tu dúo de traductores

***

**Palabras clave:** devtranslate, traducir, json, ai, husar

Cómo Husar.ai y Devtranslate.app trabajan juntos para desbloquear la creación de contenidos multilingües


## How Husar.ai and Devtranslate.app Work Together to Unlock Multilingual Content Creation

In today's fast-paced digital world, ensuring your content resonates with global audiences is more important than ever. At **Husar.ai**, we’re committed to helping businesses and developers seamlessly create, manage, and publish multilingual content. But how do we achieve such scalable, accurate, and AI-enabled translation workflows? The answer lies in our partnership with **Devtranslate.app**.

### The Power of Devtranslate.app

At its core, [Devtranslate.app](https://devtranslate.app) is a cutting-edge translation and localization platform tailored for modern development workflows. It leverages powerful AI models capable of understanding context, syntax, and intent, making the translation of text, code, and structured data not only possible but highly efficient.

### Seamless Integration: Husar.ai Meets Devtranslate.app

Husar.ai integrates Devtranslate directly into its content creation pipeline. Here’s how it works:

1. **Content Creation:** You or your team create original content on Husar.ai—be it blog posts, product descriptions, documentation, or any other text-based material.
2. **Translation Trigger:** When you need to reach audiences in different languages, Husar.ai automatically passes your content to Devtranslate.app.
3. **AI-Powered Translation:** Devtranslate takes over, using state-of-the-art AI models to generate accurate translations. Whether your original text is simple English or complex JSON structures, the system understands and adapts to various content types.
4. **Automated Localization:** Devtranslate’s algorithms retain formatting, code snippets, and context-specific jargon, ensuring a polished result for each language variant.
5. **Review & Publish:** The translated content is seamlessly delivered back to Husar.ai, where you can review, approve, and publish instantly across all your international platforms.

### Why Husar.ai Chose Devtranslate

- **Developer-Friendly:** Devtranslate specializes in translating developer-centric content, especially JSON files and documentation.
- **Context-Sensitive AI:** Unlike generic translation APIs, Devtranslate’s models retain technical nuance, making it ideal for product docs, API references, and more.
- **Automated Workflows:** Deep integration means you don’t have to export-import files or manually trigger translations—Husar and Devtranslate handle everything for you.

### Unlock Multilingual Growth

Whether you're launching globally or supporting multilingual customers, the **Husar.ai** and **Devtranslate.app** partnership streamlines your translation and localization journey. With zero manual overhead, human-like AI translations, and developer-centric workflows, your teams can focus on building features, not wrangling with language barriers.

**Ready to experience the future of multilingual content? Let Husar.ai and Devtranslate.app be your translation power duo.**

---

**Keywords:** devtranslate, translate, json, ai, husar

How Husar.ai and Devtranslate.app Work Together to Unlock Multilingual Content Creation

In today's globalized world, it's crucial for web developers to create applications that can be easily localized for users from different regions and cultures. [Vue](/usecase/vue/).js is a popular JavaScript framework which provides a powerful internationalization (i18n) plugin called [Vue](/usecase/vue/) I18n. In this comprehensive guide, we will do a step-by-step exploration of the process of internationalizing a [Vue](/usecase/vue/) app using the [Vue](/usecase/vue/) I18n plugin. Whether you're a seasoned [Vue](/usecase/vue/) developer or just getting started, this guide will get you up to speed on how to create multi-language applications with ease.

## What is [Vue](/usecase/vue/) I18n?

[Vue](/usecase/vue/) I18n is a localization library for [Vue](/usecase/vue/).js that helps developers easily handle application translations. It provides a simple and flexible API to integrate translations into [Vue](/usecase/vue/) components, which makes creating multi-language apps almost effortless. With [Vue](/usecase/vue/) I18n, you can define translation messages in different languages and easily switch between them based on the user's locale. It also supports multiple advanced features like dynamic translations or pluralization which makes it a truly comprehensive solution for [Vue](/usecase/vue/) internationalization.

## Getting Started

Before we get to [Vue](/usecase/vue/) internationalization, we first need to include the necessary scripts in our HTML file. You can include [Vue](/usecase/vue/) and [Vue](/usecase/vue/) I18n using either a script tag or a module bundler like Webpack. Here's an example of including the scripts via a script tag:

`<script src="https://unpkg.com/vue@3"></script><script src="https://unpkg.com/vue-i18n@9"></script>`

Now that the scripts are included, we can go ahead and create a [Vue](/usecase/vue/) instance and configure the [Vue](/usecase/vue/) I18n plugin. In the following example, we'll define translated messages for English and Japanese:

const messages = {
&#x9;en: {
&#x9;	message: {
&#x9;		hello: 'Hello, world!',
&#x9;	},
&#x9;},
&#x9;ja: {
&#x9;	message: {
&#x9;		hello: 'こんにちは、世界！',
&#x9;	},
&#x9;},
};

const i18n = [Vue](/usecase/vue/)I18n.createI18n({
&#x9;locale: 'ja',
&#x9;fallbackLocale: 'en',
&#x9;messages,
});

const app = [Vue](/usecase/vue/).createApp({
`	`*`// Vue app options`*
});

app.use(i18n);
app.mount('#app');

In this code snippet, we've defined the translated messages in the messages object, with the keys representing the locales (e.g., en for English and ja for Japanese). We then created an instance of [Vue](/usecase/vue/) I18n using createI18n and passed in the locale, fallback locale, and messages. Finally, we installed the i18n instance on the [Vue](/usecase/vue/) app using app.use(i18n) and mounted the app on the DOM element with the ID app. This sets up the [Vue](/usecase/vue/) app to be aware of the i18n instance and enables the translation functionality.

## Translating Text in Templates

Once the setup is done, we can start working on [Vue](/usecase/vue/) internationalization, first let's go to our templates. [Vue](/usecase/vue/) I18n injects the $t translation API into each component, letting us easily access translated messages. Here's an example of how to use the $t API in a template:

\<div id="app">
&#x20; \<p>{{ $t("message.hello") }}\</p>
\</div>

In this example, we use the $t API to translate the message with the key "message.hello". The translation is determined automatically based on the current locale set in the [Vue](/usecase/vue/) I18n instance.

## Dynamic Translations

[Vue](/usecase/vue/) internationalization also supports dynamic translations, enabling passing variables to translated messages. This is useful when you need to include dynamic content in your translations, such as usernames or numbers. Here's an example:

\<div id="app">
&#x20; \<p>{{ $t("message.greeting", { name: userName }) }}\</p>
\</div>

In this example, we have a dynamic message key "message.greeting" and pass an object with a name property to the $t API. The value of userName will be dynamically inserted into the translated message.

## Pluralization

Pluralization is a common requirement in internationalization, and [Vue](/usecase/vue/) internationalization provides built-in support for handling plural forms in translations. You can define different translations for singular and plural forms of a message and let the [Vue](/usecase/vue/) I18n plugin automatically select the appropriate translation based on the quantity. Here's an example:

const messages = {
&#x9;en: {
&#x9;	message: {
&#x9;		apple: 'one apple | {count} apples',
&#x9;	},
&#x9;},
&#x9;ja: {
&#x9;	message: {
&#x9;		apple: 'りんご一つ | りんご{count}個',
&#x9;	},
&#x9;},
};

In this example, we define translations for the key "message.apple". The English translation has two forms: "one apple" for singular and "{count} apples" for plural. The Japanese translation also has two forms: "りんご一つ" for singular and "りんご{count}個" for plural. [Vue](/usecase/vue/) I18n will automatically select the appropriate translation based on the value of count.

## Using the Composition API

In addition to the options-based API shown in the previous examples, [Vue](/usecase/vue/) I18n also has a feature called the Composition API, which provides a more flexible and powerful way to handle translations. To use the Composition API, we need to call the useI18n function in our [Vue](/usecase/vue/) setup function. Here's an example:

import { useI18n } from '[vue](/usecase/vue/)-i18n';

export default {
&#x9;setup() {
&#x9;	const { t, locale } = useI18n();

&#x9;	return {
&#x9;		t,
&#x9;		locale,
&#x9;	};
&#x9;},
};

In this example, we import the useI18n function from [vue](/usecase/vue/)-i18n and call it in the setup function of a [Vue](/usecase/vue/) component. This gives us access to the t translation function and the locale property, which can then be used in the template or other parts of the component.

## Advanced Features with [Vue](/usecase/vue/) I18n

[Vue](/usecase/vue/) I18n provides a range of advanced features to handle complex translation requirements. Some of the notable features include:

* Custom Formatting: You can define custom formatters to format translated values based on your specific requirements.
* Fallback Strategies: [Vue](/usecase/vue/) internationalization allows you to define fallback strategies for missing translations, ensuring a smooth user experience even when translations are not available.
* Number and Date Formatting: [Vue](/usecase/vue/) I18n provides built-in support for formatting numbers and dates according to the user's locale.
* Pluralization Rules: You can customize the pluralization rules for different languages, allowing you to handle complex plural forms.

## Bonus - How to easily translate your i18n files

To learn more about [Vue](/usecase/vue/) internationalization and its features, refer to the official documentation of [Vue](/usecase/vue/).js. Additionally, you can use tools like DevTranslate to automate the translation process and manage your [Vue](/usecase/vue/) files efficiently.

## Conclusion

In this comprehensive guide, we explored the process of [Vue](/usecase/vue/) internationalization using the [Vue](/usecase/vue/) I18n plugin. We learned how to set up the whole process, translate text in templates, handle dynamic translations and pluralization, and use advanced features provided by the plugin. With [Vue](/usecase/vue/) I18n, developers can easily create multi-language apps that cater to a global audience. By following the steps outlined in this guide and leveraging the power of [Vue](/usecase/vue/) internationalization, you can ensure a seamless localization experience for your [Vue](/usecase/vue/) projects.

Easy Vue internationalization - guide to the Vue I18n plugin

Constantly restarting to see the changes you've made to your json files can get tiresome really fast - fortunately theres a neat trick available with next-i18next to avoid that.

If you just want to see the code, here is what we use:

import nextI18nextConfig from '@/../next-i18next.config';
import { MyResources } from '@/types/next-i18next';
import { i18n } from 'next-i18next';
import { serverSideTranslations } from 'next-i18next/serverSideTranslations';

interface ContextModel {
&#x9;params: { locale: string };
}

const getI18nPaths = () =>
&#x9;nextI18nextConfig.i18n.locales.map((lng) => ({
&#x9;	params: {
&#x9;		locale: lng,
&#x9;	},
&#x9;}));

export const getStaticPaths = () => ({
&#x9;fallback: false,
&#x9;paths: getI18nPaths(),
});

async function getI18nProps(ctx: ContextModel, ns: Array\<keyof MyResources> = \['common']) {
&#x9;const locale = ctx?.params?.locale || 'en';
&#x9;if (process.env.NODE\_ENV === 'development') {
&#x9;	await i18n?.reloadResources();
&#x9;}
&#x9;const props = {
&#x9;	...(await serverSideTranslations(locale, ns)),
&#x9;};

&#x9;return props;
}

export function makeStaticProps(ns: Array\<keyof MyResources>) {
&#x9;return async function getStaticProps(ctx: ContextModel) {
&#x9;	return {
&#x9;		props: await getI18nProps(ctx, ns),
&#x9;	};
&#x9;};
}

The gist of it is the part with `reloadResources` here:

async function getI18nProps(ctx: ContextModel, ns: Array\<keyof MyResources> = \['common']) {
&#x20;   const locale = ctx?.params?.locale || 'en';
&#x20;   if (process.env.NODE\_ENV === 'development') {
&#x20;       await i18n?.reloadResources();
&#x20;   }
&#x20;   const props = {
&#x20;       ...(await serverSideTranslations(locale, ns)),
&#x20;   };

Simple as that, with this little addition we can say goodbye to restarting the server every time to see the translations (which gets tiresome really fast)

Additionally if you want to you can also pass an array of languages or namespaces into the brackets after reloadResources if you only want to reload content in some particular language or some specific space instead of reloading everything. If you ever had to restart the server multiple times to see the translations I bet I don't have to sell you on this.

Auto reload locales in Nextjs without restarting the server

JSON (JavaScript Object Notation) is a lightweight data-interchange format that has become the industry standard for storing and exchanging data between applications. JSON files can contain various data structures, including arrays, objects, and key-value pairs, and are commonly used for websites and applications. The main advantage is thought that their key-pair structure enables faster and easier translation, provided that the correct json translator tools are used.

## Localization Management Platforms

Localization Management Platforms (LMPs) are cloud-based platforms that offer translation, localization, and management tools for global businesses. They provide a centralized platform for managing projects, translators and their progress with some additional features like translation memory or terminology management. Some popular LMPs include:

* Phrase: a powerful localization management platform with advanced features for translation memory, glossary, and QA.
* Crowdin: a feature-rich localization platform with proofreading, translation memory features and integrations for machine translation.
* Lokalise: Lokalise is a user-friendly localization platform with an intuitive interface, collaboration tools and a number of possible integrations.

While that does sound enticing LMPs rely mainly on human translators with added functionalities for better work management so if you don't employ translators you will need to hire some. While human translators provide the best quality of translation they are costly and require quite a lot of time to do their work. Unless your project needs a ton of highest-order localization work it's highly unlikely that you'll want to do so.

## Online translators

If you don't have a team of translators you can always use an online translation service. There are several of those available online and for free:

* Google Translate: Probably the best-known free translation service in the world.
* DeepL: A machine translation service that offers high-quality translations for up to 26 languages, with somewhat limited free usage.
* Microsoft Translator: a free online translation service that supports over 70 languages and provides both text and speech translation.

While they are free they are quite costly in terms of time & effort as you'll have to copy and paste the JSON content into the online translation service, and then copy the resulting translations into the files the same way, for each and every key pair in every single json file. This makes it a decent solution for small translations but wholly unfit for anything more substantial.

## Machine translation app

Alternatively, you can use DevTranslate - a dedicated json translator tool. It not only uses DeepL's algorithm to provide high-quality translations but also knows how to keep the syntax intact. All you have to do is upload the file you want to translate, pick the target languages, and click play. You will momentarily receive your translated files, which then only need to be put in the correct folders for your app or website and you're good to go. As DevTranslate provides simultaneous translation into up to 26 languages and handles multiple file formats you can be sure you'll have your localization process finished in no time regardless of what format or language you choose. Between the extremes of either relying on costly and time-consuming human translations and painstakingly copy-pasting content into an online translator, using a professional machine translation app is simply the most cost-effective solution. Whichever json translator tools you decide on it's always important to take the alternatives into consideration - if your translation needs change what you relied on so far can either become complete overkill or wholly ineffective.

Top JSON Translator Tools for 2023

XML, or Extensible Markup Language, is a popular format for storing and transmitting data across various platforms. That makes it especially well suited for translations in case your website or app needs to be available in multiple languages. This is where XML file translation applications and software come in handy. So without further ado, let's take a look at 9 different XML file translators available for us in 2023.

## Translating XML files

XML files can contain a wide range of data types, including text, numbers, and even multimedia content. This means that translators must understand the file's structure and content to do accurate translations. Another challenge is ensuring that the translated content is properly formatted and encoded. XML files often use complex encoding schemes to represent non-Latin characters or other special characters, and it is essential that a translator knows these schemes to ensure that the translated content can be properly displayed. Preserving the syntax is essential as formatting issues or errors in the encoded data can result in the file becoming unreadable or unusable. As a result XML file translations require specialized tools which can ensure that everything works and that the end result doesn't crash the whole application.

## Top XML translator tools for 2023

### DevTranslate

Yep it's us at #1! Just kidding - this isn't a ranking, it's simply a list of what you can use to translate XML files and the first spot isn't rated any higher than the ninth. DevTranslate is a brand new online xml translator that also works for json, arb and strings files and requires only your browser to do the job. Handles translations in every language supported by DeepL which it uses under the hood.

* Pros:
  * at just 4.99$/month the price isnt steep and there's also the free plan for smaller translations
  * handles 4 different file formats and simultaneous translation into up to 26 languages
  * simply register via your browser and you're good to go - no installation is required
* Cons:
  * doesn't have a history of translations (yet!)

### Redokun

Redokun is an online translation management system that supports the translation of XML files. It provides a simple and intuitive interface for import & export and its Translation Memory feature ensures consistency and accuracy across all translations.

* Pros:
  * User-friendly interface that is easy to navigate, making it a great choice for beginners
  * Integration with machine translation technology, enabling faster translation of larger XML files
  * Comprehensive translation memory feature that allows users to reuse previously translated content, reducing translation time and cost
* Cons:
  * Expensive at €120 per month for the starter plan and 300€ for the basic plan
  * Limited customization options compared to other XML file translation software

### XML Content Translator by Nikse.dk

Nikse.dk provides a small freeware XML translator program that allows users to view and edit XML files. It uses Google translate for its translation and provides validation which ensures that the XML structure is correct and error-free.

* Pros:
  * Free to use!
  * Really simple and easy to use
  * Validation feature that ensures the XML structure is correct
* Cons:
  * Relies on google translate which provides lower quality translations than DeepL
  * Limited support and resources for technical issues or bugs
  * No advanced features

### Across

Across is a comprehensive translation management platform that supports XML file translation. Its XML filter enables seamless import and export of XML files for translation, and its Translation Memory feature ensures consistency. Additionally, Across provides real-time collaboration features that enable multiple translators to work on the same project simultaneously.

* Pros:
  * Comprehensive translation memory feature that allows users to reuse previously translated content, reducing translation time and cost
  * Real-time collaboration features that enable multiple translators to work on the same project simultaneously
  * Possible connection to a variety of machine translation systems like DeepL, KantanMT, Moses, SYSTRAN and Google Translate
* Cons:
  * Has a basic free plan, but connecting machine translations requires premium
  * Machine translation results require further validation by the user
  * If all you need is a few simple translations it might be overkill in terms of complexity and features

### SDL Trados Studio

SDL Trados Studio is a powerful translation platform that supports translation of various file formats, including XML. Its XML editor allows users to view and edit the XML structure and translate the content into multiple languages.

* Pros:
  * Robust translation platform with numerous features
  * Customizable workflow that can be tailored to fit specific project requirements
  * Integration with machine translation
* Cons:
  * Expensive at 755€ for even the Freelance plan
  * Steep learning curve for beginners
  * Fit for use as a comprehensive long time service - overkill for regular projects

### MemoQ

MemoQ is another platform with an XML translator that offers a user-friendly interface and robust features. With its XML filter, users can import XML files for translation, and its Translation Memory feature ensures consistency and accuracy across all translations.

* Pros:
  * Robust translation memory feature that ensures consistency and accuracy across all translations
  * Simple & basic interface that is easy to navigate
  * Offers integration with machine translation technology
* Cons:
  * Pricey at €185 per month for small teams and €620 for freelancers
  * The quality of the machine translation feature may often require human review

### MateCat

MateCat is a web-based XML translator tool. Its simple and intuitive in-browser interface enables users to upload XML files for translation.

* Pros:
  * Free
  * Easy to use and does not require installation
  * Uses Google translate and Microsoft translator and provides alternative suggestions
* Cons:
  * Requires overview in the form of manual clicking through every translation string making it time-consuming (at least initially)

### Wordfast

Wordfast is a powerful platform that can also function as an XML translator tool. Its XML editor allows users to view and edit the XML structure and translate the content into multiple languages.

* Pros:
  * Customizable workflow that can be tailored to fit specific requirements
  * Can be integrated with machine translation technology in the pro version
* Cons:
  * Expensive as the pro version costs $480
  * Complex setup is entirely left up to the user
  * Machine translation integration has to be individually handled by the user and manually verified

### XML Notepad

XML Notepad is a simple freeware program that allows users to view and edit XML files. It isn't exactly a standalone XML translator, but it can be set up to work as one.

* Pros:
  * Free
  * Simple and easy-to-use interface
* Cons:
  * Isn't exactly an XML translator but more of an XML file manager that can also be used for translations
  * Requires another tool to actually do the translations

In short, how you set up your translation process is entirely up to your personal preference and there's a wide array of tools you can use to make it faster and easier for yourself. You can choose a simple XML file manager and do the translations yourself, or you can carefully configure a complex platform to work exactly like you need it to, or you can use a simple browser tool that requires only a few clicks to provide you with ready AI-generated translation in a matter of seconds. Which tool you use as an XML translator is entirely up to you.

9 XML Translator Tools for 2023 with Pros and Cons

Reaching more markets usually requires adapting your app to the users there. While it’s true that today mobile users usually know English, studies show most still prefer to use their local language for their devices and applications. The obvious solution that comes to mind might be translation, but that’s not enough!

## Translation

Odds are you’ve used google translate on more than one occasion, while it’s definitely a popular tool it’s often not enough for business uses and most opt for either professional translation tools or simply the services of a translator. For applications however neither is the optimal way of doing things.

## Localization

Localization or as it’s called in the business l10n is a process of not only translating everything to the local language but also adopting everything to the local customs. What exactly does that mean? To put it simply, localization is translation and then some: tailoring everything to the specific customs, tastes and preferences of a given culture and language. This is especially true for software where it extends to UX/UI as well. The purpose is to make the user feel right at home as if they were using a local app from that region.

## Why is localization necessary?

To look at a simple use case for localization we can compare even countries using the same language like English. The US uses a 12-hour clock and the imperial system instead of metric (pounds, ounces, feet, miles, fahrenheit instead of celsius etc.) additionally you have different spelling (localisation for British English, localization for US, armour and armor and many others) and completely different words (lift/elevator and such) and idioms. Often the same word can have a completely different meaning depending on the region.

For a few examples football in the US means NFL and soccer in most other countries, the first floor is the ground floor in the US and the first floor above ground level in the UK and most importantly pants are trousers in the US and underwear in the UK. The same is obviously even more true for different languages where the text length might be completely different, the font size might look bad with the particular alphabet or the UI can become less readable. Basically every localization requires a number of solutions and tweaks to keep everything smooth for every language.

In short the benefits of localization are numerous and by catering to local needs you can:

* reach new markets effectively by providing the same user experience as local apps
* communicate with users who would otherwise wither face a language barrier of be forced to use a language contrary to their preferences
* avoid misconceptions and faux pas related to specific customs and particularities of different languages and cultures
* optimize your product to fit locally used search terms and keywords

What are the differences between translation and localization?

Localization is the easiest way to reach a larger audience for your application. Users not only prefer apps in their language but also appreciate a personal and localized touch relevant to their country and culture. Regardless of how you want to translate your app, using specialized tools or simply hiring a freelance translator, it’s prudent to prepare yourself for that.

## Meet JSON

JSON or JavaScript Object Notation is one of the most popular data exchange formats used today. It is a syntax for storing and exchanging information between systems over the internet, most commonly between a server and a web application, using attribute-value pairs. Well that was more of a wikipedia-like definition, let's break it down to make things simpler:

* unlike other formats it's easy to understand for both machines and humans
* it’s completely independent of platforms and can be used for websites, apps, games etc.
* although it originated from JavaScript it is language independent and many modern languages are set up specifically to generate and parse JSON-format data

## JSON for l10n and i18n

Seeing as it’s universal in terms of both platform and language it’s easy to understand why JSON has become the standard for localization (l10n) and internationalization (i18n). Regardless of how you want to translate your app, and even if you don’t, it’s good to keep content in JSON files just in case you change your mind in the future, and to keep a clear file structure. When you do decide on localizing your app you will have the full range of solutions at your disposal and the whole process will be a lot simpler and less time consuming:

* online translators like Google Translate API will quickly translate JSON files and create new files containing the translations in the chosen language
* a professional translator or translation company will also have a much easier job dealing with JSON files (they also use professional tools to speed up the process)
* using a professional localization tool will not only instantly translate all the app content into every chosen supported language, but will also automatically handle continuous translation as your application changes and grows

## Picking the optimal solution

While using free online translators might look like the easy pick here, their quality is often a mixed bag, which can mean additional work in the shape of checking and fixing errors. Additionally you’ll need to repeat that process every time you make some change or update or if you decide on translating into additional languages, which can be a hassle. Similarly hiring freelancers or a professional translation company while usually guaranteeing high quality translations, will also require repeating the process with every new bit of translation required. While that might not be a problem for business websites which don't change much over time, it can be a big issue for applications receiving regular updates. In that case the best solution is using professional localization tools which will completely automate that entire process and save you all the trouble. Yes the algorithms are still not as good as a professional human translator with expert knowledge of all the nuances of a particular language but the advantages in cost and time saved can often easily outweigh that.

Translation and JSON files

When looking for ways to expand the audience base of your app one thing that should come to mind is localization. After all, while most mobile users are at least familiar with English, many prefer using their local language for their apps which significantly broadens the number of potential users you can reach by localizing your app into various other languages. If your app is in a different language, then the benefits of translating into English, in terms of potential audience, should be even more obvious.

## Tier 1 countries or diversification?

The usual approach when localizing is going for the so called ‘tier 1 countries' which usually includes US, Canada, France, Germany, UK and Japan. While tier 1 countries are definitely the most profitable, they are also the most competitive and can be a tough market to crack. As such, additionally targeting less popular, but also less competitive markets can actually be a more effective approach. After all, casting a wider net and trying to rake in audiences from more countries can yield better results and without complex market research it’s hard to even tell where you might find potential users for your app. You might find that by translating your app into less popular languages you find a niche that your competitors have overlooked and gain a lot more users than you expected.Who to rely on?If you’ve decided on localization, the next question is how to do it. Mobile app companies often rely on either community translators, freelancers or localization companies. Each have advantages and disadvantages:

* volunteer/community translators: While the obvious advantage is the cost (or lack thereof) the drawbacks are also significant, often both in terms of time and quality.
* freelance translators: Relying on native speakers or translators working as freelancers is a lot more reliable, you can usually be sure the work will be done in a timely and professional manner. Though you will still likely have to micromanage translators for each added language and for every future update.
* localization company: The best solution if you’re looking for a consistent professional translation service that will save you all the hassle and micromanagement. You can be sure of the quality and constant support, but it will also most likely be expensive.
* volunteer/community translators: While the obvious advantage is the cost (or lack thereof) the drawbacks are also significant, often both in terms of time and quality.
* freelance translators: Relying on native speakers or translators working as freelancers is a lot more reliable, you can usually be sure the work will be done in a timely and professional manner. Though you will still likely have to micromanage translators for each added language and for every future update.
* localization company: The best solution if you’re looking for a consistent professional translation service that will save you all the hassle and micromanagement. You can be sure of the quality and constant support, but it will also most likely be expensive.

## What about localization tools?

Various localization tools are becoming more and more popular, despite preconceived notions about their quality mainly due to how unreliable they used to be in the past. You can be sure the days of google translate spitting out unintelligible gibberish are long gone though, and modern algorithms have gotten a lot better at the job. If you’re having doubts you should know a simple fact: all those professional translators use them too. Even if you rely on freelancers or a professional translation company they will also utilize popular translation tools for one simple reason: it significantly speeds up their work. While those tools are not 100% perfect yet, the key advantages are clear:

* no hassle: no outsourcing or micromanaging freelancers
* ad hoc usage: use only when actually needed, save yourself the trouble of repeatedly looking for freelancers with each new release or constantly paying a localization company for continuous translation services
* consistency: build a glossary to ensure all translations are consistent with your app and brand
* automate: take advantage of automatic translations as you update your app with new features
* efficiency: translate into many different languages instantly without the need for weeks of translations by a host of freelancers
* no hassle: no outsourcing or micromanaging freelancers
* ad hoc usage: use only when actually needed, save yourself the trouble of repeatedly looking for freelancers with each new release or constantly paying a localization company for continuous translation services
* consistency: build a glossary to ensure all translations are consistent with your app and brand
* automate: take advantage of automatic translations as you update your app with new features
* efficiency: translate into many different languages instantly without the need for weeks of translations by a host of freelancers

Reaching a global audience through localization

ローカリゼーションについて知っておくべきこと

DevTranslateブログでアプリのローカライゼーション、i18nベストプラクティス、JSON/XML翻訳のヒントなど、開発者向けの有益な情報をご覧ください。React、Vue、Flutter、iOSアプリの多言語対応ガイドと最新トレンドを紹介。

ブログ｜jsonファイル翻訳DevTranslate

利用規約

プライバシーポリシー

お問い合わせ

角度ローカリゼーション

リアクトロケーション

Vue.jsの場所

アンドロイドロケーション

ロケーション iOS

リアクト・ネイティブの位置情報

フラッターロケーション

アプリケーション

JSONファイルトランスレータ

XML ファイル翻訳

ARBファイルトランスレータ

文字列ファイルトランスレータ

フォーマット

ヘルプセンター

ブログ

リソース

DevTranslateは、26の言語をサポートするjson、xml、arb、文字列ファイルのトランスレータです。

時間を無駄にしないでください！ブラウザで簡単に翻訳できます。

ブログ DevTranslate: ファイル翻訳者

アプリケーションを翻訳する