Profile

Yes, we could, should there be an overlap with ENLASO. Best regards, Joachim From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Dr. David Filip Sent: Dienstag, 7. Juli 2015 18:00 To: Schnabel, Bryan S Cc: XLIFF Main List Subject: Re: [xliff] ...

Bryan, thank you very much – I will pass this on directly to the fine people who had been hosting us! 4text: Also in my name, thank you very much for your hospitality, it was a very productive meeting! Best regards, Joachim From: Schnabel, Bryan S [mailto:bryan.s.schnabel@tektronix.com] Sent: Mittwoch, ...

Hi all, I am a bit unsure if we get all this done in a hurry. Particularly the discussions about the version integration that Yves mentions below. Anyway, here a preliminary, for discussion, proposal to add the capability to point to internal matches to XLIFF 2.1 Translation Candidate ...

Hi Yves, yes, thanks! I had been thinking about using a custom , and it would work (by adding match quality in the value attribute), but it is – custom and hence is not easily understood across tools of multiple parties. I know that translation candidates are optional either, but at least if they are ...

Dear colleagues, I wonder if we have overlooked a use case in the translation candidates module. As you know, with XLIFF 2.0, it is easily possible to include reference data into the translatable file, such as matches and glossary data. The agent working on these data does not need to perform searches ...