No. yLocalizer does not override existing translations in a given file. If you want to override the existing translations, you need to delete them.

Copy the source xml file, rename it to include target language code and translate it with yLocalizer.

Copy the source strings file, rename it to include target language code and translate it with yLocalizer.

Copy the source resx/resw file, rename it to include target language code and translate it with yLocalizer.

If the source and target language of the localization task is one of well-known languages, then the translations accuracy reaches as much as 99%. If the software is used in civil society applications in which any mistake in the localization does not lead to any substantial loss, then there is no urgent need to review the translations. In any case, we recommend to have one human review to give your user best experience.

It depends on what the target language is. If the target language is one of well-known languages, then the format specifier is also correctly translated in the target language as well.

It depends on what the target language is. If the target language is one of well-known languages, then the format specifier is also correctly translated in the target language as well.

Yes. The yLocalizer translates to RTL languages. But your software has to be able to show those strings correctly as well.

You can translate as many file as you want. But it takes time to translate large number of files or files with large quantity of texts in it.

Currently, yLocalizer supports 10 well-known localization file formats: 1. gettex po/pot file 2. Android xml/arb file 3. iOS strings file 4. Windows resx/resw file 5. ts file 6. xliff file 7. subtitle srt file. If your software uses other localization file format, send us request to add that file format to yLocalizer.

Yes. We offer localization and human-review services for organizations with large localization quote.