- From: Nathan Glenn <garfieldnate@gmail.com>
- Date: Sun, 29 Sep 2013 13:06:33 -0700
- To: Yves Savourel <ysavourel@enlaso.com>
- Cc: "public-i18n-its-ig@w3.org" <public-i18n-its-ig@w3.org>
- Message-ID: <CACs83pgDPGWVMXo6iNkOy0Ho-VwCDw3HL9X_ZFE37ZvWb5gTjw@mail.gmail.com>
Thanks. I wonder if it's worth even trying to preserve global rules in my application. If I were to create an XLIFF file for a given XML file, and also try to preserve the global rules by making them point to new nodes in the XLIFF file, is there any generic place where I could put the contents contained by nodes selected through *Pointer attributes in the rules, or would I have to use the specific locations that differ for each type of ITS (e.g. its:termInfo, itsxlf:domains or a <note> element)? Nathan On Sun, Sep 29, 2013 at 4:35 AM, Yves Savourel <ysavourel@enlaso.com> wrote: > Hi Nathan, ** **** > > ** ** > > Yes, the mapping doesn’t use global rules. The idea is that an XLIFF > processor should be able to add support for ITS by just implementing > support for the attributes defined by the mapping.**** > > ** ** > > This doesn’t prevent an ITS processor to support XLIFF by having global > rules describing the XLIFF features, just like for any other XML format.** > ** > > **** > > -ys**** > > ** ** > > ** ** > > *From:* Nathan Glenn [mailto:garfieldnate@gmail.com] > *Sent:* Sunday, September 29, 2013 12:18 AM > *To:* public-i18n-its-ig@w3.org > *Subject:* ITS rules in XLIFF**** > > ** ** > > Hi all (especially Yves),**** > > I'd like to confirm an observation on ITS in XLIFF. At least judging by > the mapping documentation, it seems that ITS in XLIFF does not allow for > global rules of any kind, and that during mapping all rule matches must be > turned into local attributes of some kind. Is this correct?**** > > Nathan**** >
Received on Sunday, 29 September 2013 20:06:59 UTC