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: Proposed changes to translate attribute (and related) in response to csprd01 comment 009 (translate clarification), related to 038 (resegmentation PRs)

Yves, Fredrik all,

I believe that the translate attribute (flag) should be allowed on all structural levels above segment.

Currently it is only allowed on <unit>, <segment>, and <markers>.
I believe that not having it on <group> and <file> as well is an omission.

Yves also commented that we do not specify scope, which is another bad omission.

So I propose that the translate values are fully recursively inherited by all structural elements and markers.
The default remains yes.
The default applies for all the levels above the highest explicitly set (all if none set). All lower levels inherit their default from the closest level above.

IMHO the above is clear and not contentious, one point to discuss is whether we want to allow the segment element to carry the attribute.
Since the attribute is specified in core, the PRs could be set for re-segmentation, I am just not sure if it is worth the hassle.

We could simply disallow the attribute on segment and say that translate values set on unit have to be overriden with markers if need be. This would resonate with the general approach to re-segmenting, i.e. make the segment as simple as possible to make the re-segmentation PR as simple as possible.

Please let me know your thoughts on this within next week

Thanks for your attention

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

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