Re: localization note annotations and x-its-translate-yes

Resending my previous answer from a cleared address

dF is AFK, sent from a mobile phone..
On 19 Sep 2013 09:29, "David Filip" <davidf@davidf.org> wrote:

> Hello Nathan, let me answer inline
>
> dF is AFK, sent from a mobile phone..
> On 19 Sep 2013 00:52, "Nathan Glenn" <garfieldnate@gmail.com> wrote:
> >
> >
> > Hi all (I think especially Yves),
> >
> > I have two questions about the current XLIFF 1.2 mapping.
> >
> > First, the value of "x-its-translate-yes" is mentioned for the attribute
> 'mtype' in a <mrk> element. This value is, however, not mentioned anywhere
> in the actual XLIFF 1.2 spec. Is this something planned for 1.3? Is it
> something that will be added via the itsxlf namespace? This is more
> curiosity than practicality.
> In 1.2 user defined values must start with x- and since the spec doesn't
> have a core value for unprotecting we had to go for this transparent user
> defined value.
> BTW, the XLIFF TC doesn't plan to work on 1.3.
> In fact the TC approved a second public review draft of XLIFF 2.0 and
> plans to have an ITS 2.0 mapping module in 2.1
> >
> > Second, localization notes are supported via the <note> element, but the
> document only mentions the use of general <note>'s. The default value for a
> <note> element's 'annotates' attribute is "general". The other possible
> values are "target" and "source", indicating that the note applies either
> to the <source> or the <target> element contents. Is this to be supported,
> as well? By which, of course, I mean, is it recommended that implementers
> support this or is it to be ignored?
> I think nothing prevents the implementers from using this. Perhaps we
> should specifically say in the mapping that extracted notes should pertain
> to source and only general or target related notes should be merged back
> >
> > Nathan
>