OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [xliff] Re: Survey/SUO feedback

Thanks, Lucía, the changes I suggested are important for user experience, but all editorial
Can you send me later on my responses? So that I can see what we are going to send to the non-members for endorsement through the comment list
Thanks and cheers

Dr. David Filip
University of Limerick, Ireland
telephone: +353-6120-2781
cellphone: +353-86-0222-158
facsimile: +353-6120-2734
mailto: david.filip@ul.ie

On Wed, Apr 2, 2014 at 12:19 PM, Lucia Morado Vazquez <Lucia.Morado@unige.ch> wrote:
Thank you Yves and David for all your comments. I will apply the suggested changes later this afternoon when I will be done with my teaching duties.

-----Message d'origine-----
De : Yves Savourel [mailto:ysavourel@enlaso.com]
Envoyé : mercredi 2 avril 2014 12:50
À : Lucia Morado Vazquez; 'Dr. David Filip'; 'Chet Ensign'
Cc : xliff@lists.oasis-open.org
Objet : RE: [xliff] Re: Survey/SUO feedback

Hi Lucia,

>>- "21. Please select from the following required XLIFF attributes the
>>ones that your tool can process:" list only some of the <xliff>
>>element (trgLang is missing)
> Following the spec, I had made a distinction between "required"
> elements and attributes  and the total set of elements and attributes.
> I can just leave the whole set if you think that it is confusing.

Oh, I see trgLang in the optional list now.
I think it doesn't really matter: as David said the OPTIONAL stated near the names doesn't mean much anyway: it's all about the constraints and PRs.

>>- " 17. Which XLIFF version does your tool support?" :
>>I assume we will remove all version but 2.0?
> Done. Should we change that question to: "level of XLIFF 2.0 support?"

"XLIFF 2.0 modules support"? or something like that.

Input for the future:

It's too late to change now, but maybe next time we do a survey for 2.x it could be better to list the constraints and PRs rather than the elements and attributes. For this time around there are too many (about 125 just for the Core) to change.

For 2.x we also may want to make sure they are display in some very visible way in the specs (colored or in a frame, etc. and possibly labeled per type of agents) having them with a heading 'Constraints' and 'Processing Requirements' helps, but they are still easy to miss.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]