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][follow-up] FW: Degrees of constraint


> but my understanding is that text within <mrk> tags is NOT translated (*).
> With most inline tags (e.g., <html:b>), the text should be translated.

The definition in the specification reads: "The <mrk> element delimits a
section of text that has special meaning, such as a terminological unit, a
proper name, an item that should not be modified, etc. It can be used for
various processing tasks. For example, to indicate to a Machine Translation
tool proper names that should not be translated; for terminology
verification, to mark suspect expressions after a grammar checking. ..."

My understanding is that "...an item that should not be modified, etc." is
just one possible example of use. But the content of <mrk> is part of the
text and can be transltable. It "delimits a section of text that has special
meaning." For example:

<source><mrk mtype="protected">Gandalf Inc.</mrk> has join the <mrk
mtype="short-form">W3C</mrk> (<mrk mtype="expanded-form">World Wide Web
Consortium</mrk>).</source>

But maybe I'm the only one reading it like this... :)


> Would treating tags from another namespace as an <xlf:g> tag allow the
> text to be translated?

Yes, <g> is a better example.

Cheers,
-yves




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