There are plenty of 'XLIFF Editors' that pop up on the Mac App market. A number of them are free, most are not super expensive. But all confuse 'XLIFF' with the poor subset that Xcode outputs. And that confuses the people who need XLIFF editors the most: professional translators.
- Xliff Editor 2 1 – Xcode Localization Made Easy Using Baking Soda
- Xliff Editor 2 1 – Xcode Localization Made Easy Using Canned
- Xliff Editor 2 1 – Xcode Localization Made Easy Using Bernat
- Xliff Editor 2 1 – Xcode Localization Made Easy Using Almond Extract
The XLIFF 2.0 Object Model contains classes and methods for generating and manipulating XLIFF 2.0 documents as described in the XLIFF 2.0 Standard. The library is built using the Portable Class Library enabling developers to generate XLIFF documents using various platforms. Goals for this project. The XLIFF 2.0 Object Model allows a developer. 1 hour ago Lessons in crisis management and the economic cycle from the story of Joseph, peace be upon him; 2 hours ago Sisi retreat and the victories of the demonstrators. Photolemur 2 2 0 – automated photo enhancement enhancer. Learn about the gifts of September 20 for Egyptians; 2 hours ago Merkel visited the Russian opposition figure Navalny in the hospital; 2 hours ago. No more messing around with the XML format, or worrying about file corruption. Xliff Editor includes full search support, handy keyboard shortcuts, and even basic read support for SDLXliff files!XLIFF files are based on the stan. Xliff Editor 2.0.7 – Xcode localization made easy. February 7, 2018. Xcode 6 introduced the ability to export/import all your localisation data, taking away the need for sending various file formats to your localisers for translating. The XLIFF format makes translating a cinch, as it removes all the layout and formatting, and just provides a simple text-to-text translation mechanism for your translators.
Complete anatomy 2018 3 2 – anatomy learning platform development. Xcode 6 introduced a new localization workflow which uses the open.XLIFF format. Xcode extracts the strings from NSLocalizedString, strings in storyboards / XIB files and creates a single XLIFF file for each localization. I'm looking for good localization tools that translators can use to open and edit the files exported by Xcode. File list export 1 7 6 download free.
XLIFF is an industry standard used in all the localization/translation world. Xcode developers who need the ability to edit their output have all the rights to create quick tools that will help them with that task. But please, don't call that XLIFF editors. What you do is Xcode l10n files editors, basically just XML simple parsers outputing the resulting data in a 2 column table with a native GUI. That's pretty much it. And that's very fine. But it's not XLIFF.If any of those developers had actually worked with a professional translator to see what are the features required to work with XLIFF (and all the other related standards: TMX, SRX, TBX, ITS, etc.) they would never call their tool an XLIFF editor, just like TextEdit is able to edit XML but nobody would think of calling it an XML Editor..
Mac developers are very picky when it comes to what looks good. Good for them. But would they rather develop in Xcode or in TextEdit? Professional translators on the Mac who need to work with XLIFF currently have the following not so good looking but rock solid choices (all Java based, by the way):
Xliff Editor 2 1 – Xcode Localization Made Easy Using Baking Soda
FOSS, very active, used by professionals all over the world:OmegaT + Okapi Framework filter plugin (GLP/LGPL)
FOSS, active, not as used as OmegaT *because* limited to XLIFF and ITS:
Ocelot, by the Okapi Framework
Update: Ocelot is 'limited' compared to the other solutions that offer either dozens of filters or round trip conversion tools for other formats to XLIFF. Limitation is not about XLIFF and ITS support.
FOSS, not active anymore, used to be used by professionals all over the world:
Heartsome's Translation Studio (GPL)
Swordfish
XLIFF is a serious standard, and translators need rock solid standard support to work. If your editor does not have inline tag/segmentation/legacy translation support, call it anything but XLIFF Editor, please.
Also, this is not a rant. This is a reminder: there is a market for robust native pro-level translation tools on Mac. With Microsoft Office for Mac feature for feature equivalent to the Windows version, translators and localizers have little need to stay on Windows machines. Except that the biggest pro-apps are Windows only. And that's a shame.
Xliff Editor 2 1 – Xcode Localization Made Easy Using Canned
Using XLIFF as your point of entry into the l10n world is a good and relatively easy way to access a large market (pro conversion engines to and from XLIFF already exist: see the Okapi Framework). But the point where you can compete with the incumbent and actually make money is way higher than what you think.There are plenty of 'XLIFF Editors' that pop up on the Mac App market. A number of them are free, most are not super expensive. But all confuse 'XLIFF' with the poor subset that Xcode outputs. And that confuses the people who need XLIFF editors the most: professional translators.XLIFF is an industry standard used in all the localization/translation world. Xcode developers who need the ability to edit their output have all the rights to create quick tools that will help them with that task. But please, don't call that XLIFF editors. What you do is Xcode l10n files editors, basically just XML simple parsers outputing the resulting data in a 2 column table with a native GUI. That's pretty much it. And that's very fine. But it's not XLIFF.
If any of those developers had actually worked with a professional translator to see what are the features required to work with XLIFF (and all the other related standards: TMX, SRX, TBX, ITS, etc.) they would never call their tool an XLIFF editor, just like TextEdit is able to edit XML but nobody would think of calling it an XML Editor..
Xliff Editor 2 1 – Xcode Localization Made Easy Using Bernat
Mac developers are very picky when it comes to what looks good. Good for them. But would they rather develop in Xcode or in TextEdit? Professional translators on the Mac who need to work with XLIFF currently have the following not so good looking but rock solid choices (all Java based, by the way):FOSS, very active, used by professionals all over the world:
Xliff Editor 2 1 – Xcode Localization Made Easy Using Almond Extract
OmegaT + Okapi Framework filter plugin (GLP/LGPL)
FOSS, active, not as used as OmegaT *because* limited to XLIFF and ITS:
Ocelot, by the Okapi Framework
Update: Ocelot is 'limited' compared to the other solutions that offer either dozens of filters or round trip conversion tools for other formats to XLIFF. Limitation is not about XLIFF and ITS support.
FOSS, not active anymore, used to be used by professionals all over the world:
Heartsome's Translation Studio (GPL)
Proprietary, by Maxprograms, one of the main actors behind Heartsome's code:
Swordfish
XLIFF is a serious standard, and translators need rock solid standard support to work. If your editor does not have inline tag/segmentation/legacy translation support, call it anything but XLIFF Editor, please.
Also, this is not a rant. This is a reminder: there is a market for robust native pro-level translation tools on Mac. With Microsoft Office for Mac feature for feature equivalent to the Windows version, translators and localizers have little need to stay on Windows machines. Except that the biggest pro-apps are Windows only. And that's a shame.
Using XLIFF as your point of entry into the l10n world is a good and relatively easy way to access a large market (pro conversion engines to and from XLIFF already exist: see the Okapi Framework). But the point where you can compete with the incumbent and actually make money is way higher than what you think.
