A little explanation of file types
XML files are files of input details used for management and exchanging information, XML stands for Extensible Markup Language. At first, they were used in web domains to rewrite SGML (Standard Generalized Markup Language).
Now, XML files are used in a wide range of IT fields. They can be found for example in the Microsoft Office Suite (under different derived formats), as well as in website sitemaps not forgetting the transfer of information databases.
XLIFF means XML Localization Interchange File Format, XLIFF files are based on XML but are bilingual. In projects where there are 2 or more languages, in other words multilingual, there will be several XLIFF files.
First created for translation tools, XLIFF files are used today by web developers to prepare data that need to be translated. For example, web developers who work with Symfony use this format to export content and set it up for translation.
Each XLIFF file has an indication on them which specifies the language into which it will be translated in the <file> element that is labelled ‘target language’.
JSON is used in the serialisation and transmission of structured data to a connecting channel (especially for transmitting data from a server to a website application). It is used as an alternative to XML.
JSON is a file format of textual data that is completely independent of other computer languages. It uses the syntax of type C programming languages for example C, C++,or C#.
The JSON character set by default is UTF-8, but it is also possible to use UTF-16 and UTF-32.
To learn more about JSON: Click here
PO and POT
PO and POT files are very similar files, PO means Portable Object and POT means Portable Object Template. These file types are mainly used by the POedit software, as well as computer programmes used in Linux.
POT files contain the text extracts of your application or your website. In terms of PO files, they are files that bring us back to translators, as they contain original texts as well as their completed translations.
A few explanations on how our software works.
The majority of files that we receive are very similar structure-wise thanks to the programming rules, but a lot of developers have specific notations.
Because of this, our software has the possibility of having translation filters. Therefore, it is possible, according to your data export, to choose the type of content to translate without creating problems during the import of the translation.
For example, in the previous image you can see that in the last single ‘img’ tag (image) we only have to translate the attribute ‘desc’ (image description) and not the attribute ‘src’ (link to the image in the files).
However, it is possible to have to translate it in the case where a textual image with other conditions such as the addition of another tag ‘lang’.