[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] Uniqueness of language pair
|
David, Next meeting is in two weeks; that is enough time for TC members to consider the pros and cons of multilingual/bilingual XLIFF. Don’t look for a champion outside the TC, Bryan owns this feature in the wiki. The feature has been on the wiki long enough and the wiki is public. There were multiple opportunities to send feedback to the TC regarding this issue. If you really want multilingual XLIFF, please provide the basic design for multilingual support and we will discuss it. This feature may affect the work on XLIFF 2.0 that we are doing at this moment. We can’t keep waiting for someone to join OASIS sometime in the future and became a champion for multilingual support, sending us back to square one to adjust the design. Regards, Rodolfo -- From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Dr. David Filip Thanks Rodolfo, I would first try and find a champion for this feature. If such a champion is found I would give him/her some time for thinking of possible implementations. If a champion is not found soon, the feature should be moved to 3, but next meting might be to quick, IMHO. I would expect the champion to be a large publisher or a cloud based TMS provider, if anyone at all. We might be able to bring Stephan from Wordbee to the table after all.. Rgds dF
======================= LRC | CNGL | LT-Web | CSIS University of Limerick, Ireland telephone: +353-6120-2781 mobile: +353-86-049-34-68 facsimile: +353-6120-2734 mailto: david.filip@ul.ie On Thu, Jan 5, 2012 at 21:23, Rodolfo M. Raya <rmraya@maxprograms.com> wrote: Hi David, If we opt for having multilingual XLIFF files, there is no reason for not allowing their use in translation editors. Editing a multilingual XLIFF file should be as easy as editing a bilingual file for the end user. Designing an editor that can handle multilingual files is not a trivial task but can be done. As developer of XLIFF editors, I certainly prefer XLIFF files to be bilingual. Nevertheless, I admit that language service providers may prefer multilingual XLIFF documents. The wiki has a feature request for “Ability to store Multilingual Content” (item 2.12 in the feature tracking page). It is not clear how this can be achieved and there is no proposal for implementation. Perhaps we should vote whether we want bilingual or multilingual files in next meeting and send this pending item to section 1) or 3). If it goes to section 1), we need to start working right now on how multilingualism will be implemented in XLIFF 2.0 because that affects the elements we define. It would not be the same to have multiple <file> elements, each one with its own language pair, than to have a single <file> and multiple <target> elements per segment. From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Dr. David Filip Thanks Rodolfo, for opening this. I think that it makes perfect sense to set language pair uniqueness constraint at the file level. I was talking to Wordbee in summer trying to recruit them for the TC. Anyway, Wordbee (as our customer) would represent a business need for bulk exchange of multilingual collections. I assume that a collection of different files with various source and target languages would do the trick. Nevertheless, I suspect that Stephan (Wordbee CTO and cowner) would be even more radical than that, and that he would simply want to allow systematically multilingual use of multiple targets. I quote Wordbee position to impartially illustrate an existing business need. I personally would use multilingual formats only with utmost caution, as they pose obvious business process issues, e.g. problematic merging to central data store. If we allowed some controlled sort of multilingualism (multi- in the sense of more than bi-) [if I remember correctly, Andrzej had a good study of why multilingual formats are to be discouraged in translation automation], we would need to explicitly say in processing requirements, that this format MUST NOT be used in and for translation editors. We would need to specify canonical transforms to facilitate canonical behavior of translation editors, that should be bilingual. The multilingual bulk exchange construct should be restricted to CMS<->TMS and TMS<->TMS bulk exchange. [I am aware that alt-trans target is sometimes being used multilngually, I am however not sure what are the support levels for this in tools.. IMHO this is a seprate discussion..] Rgds dF Dr. David Filip ======================= LRC | CNGL | LT-Web | CSIS University of Limerick, Ireland telephone: +353-6120-2781 mobile: +353-86-049-34-68 facsimile: +353-6120-2734 mailto: david.filip@ul.ie On Thu, Jan 5, 2012 at 11:31, Rodolfo M. Raya <rmraya@maxprograms.com> wrote: Hi, In an XLIFF 1.2 document you may have multiple <file> elements and they could have different source/target languages. In theory, that would allow someone to create an XLIFF document with many copies of the same <file> element, each having a different target language. In practice, that would be a bad idea as tools that work with XLIFF usually expect bilingual documents. It might be interesting for XLIFF 2.0 to set source and target language in the <xliff> element and let all <file> children inherit the declared language pair. Opinions? Regards, Rodolfo -- |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]