I wonder if it was possible to add a feature to export source lists to, e.g., SDLXLIFF, not only translation lists. Or even better a general project export feature that exports ALL relevant project data into a XML or CSV based format. This would be really advantageous for a Git workflow as such text based files could be merged by Git.
Source list can be exported into translation bundles to let developers comment on source strings. SDLXLIFF export for source list is not available and doesn’t make sense as SDLXLIFF is by definition a bi-lingual file format and source lists are mono-lingual.
The Passolo LPU is a data repository with settings and many database like relations. Exporting into XML, JSON or other text formats would increase the data size by factor 10 or more. It is not a source code like text that could be merged or diffed with Git tools and should treated it like a database.
OK, I understand. I will have a deeper look at the translation bundle export. Regarding the project data export, I thought of something like the MIF format of Adobe FrameMaker. It's a pure (but admittedly fairly complex) text format that can be used, e.g., for version independent data exchange or automation (without COM). Such a format can be really helpfull in various situations.
OK, I understand. I will have a deeper look at the translation bundle export. Regarding the project data export, I thought of something like the MIF format of Adobe FrameMaker. It's a pure (but admittedly fairly complex) text format that can be used, e.g., for version independent data exchange or automation (without COM). Such a format can be really helpfull in various situations.
Another example is MadCap Flare. ALL project and content data is stored in various XML and text files. You can do all kind of automations without the need of COM (whereby use of COM is also possible with Flare).
Translate
