search

freme-project / e-Internationalization

Apache License 2.0
0 stars 0 forks source link

XLIFF roundtripping output question #24

Open fsasaki opened 9 years ago

fsasaki commented 9 years ago

Hi created with the input file originalXliff1.2 and the two attached requests the attached output files. They contain some placeholder and are not valid XLIFF. Is this an issue of the request or a bug? Note: the curl request says @originalXliff1.2.xlf for the file, the attached file is originalXliff1.2.txt since github does not allow to upload files with xlf extension. originalXliff1.2.txt request2.txt request1.txt out2.txt out1.txt

borriellom commented 9 years ago

Hi Felix, unfortunately the roundtripping functionality is only available for HTML files. Using other formats can produce unexpected results.

fsasaki commented 9 years ago

Hi Marta - in the example that you created a few weeks ago roundtripping was possible for for XLIFF 1.2 and 2.0. Why is that not possible via e-internationalisation?

2015-10-28 17:52 GMT+09:00 borriellom notifications@github.com:

Hi Felix, unfortunately the roundtripping functionality is only available for HTML files. Using other formats can produce unexpected results.

— Reply to this email directly or view it on GitHub https://github.com/freme-project/e-Internationalization/issues/24#issuecomment-151769065 .

borriellom commented 9 years ago

Hi Felix, it wasn't roundtripping. Those files have been managed with Ocelot. They were opened, enriched and then saved in Ocelot. The XLIFF file is not converted to NIF, but single Ocelot segments are submitted to FREME as plain text. Actually we were dealing with the issue of how saving enrichment annotations in XLIFF files. Please, let me know if you need further information.

fsasaki commented 9 years ago

Thanks, Marta, that is very helpful. I would like to have roundtripping for XLIFF and general XML in FREME too - I think this is an important value proposition for FREME in general. I understand that this is not in scope for your work on e-internationalisation, and that is fine. So this is just a heads up that we will come back to this later. Let's keep this issue open so that we won't forget. Also a heads up that there may be then two ways for having roundtripping of XLIFF 1.2 and 2.0: via Ocelot and via FREME generically. The output then is hopefully the same, but that is fine.