- From: Felix Sasaki <fsasaki@w3.org>
- Date: Mon, 11 Dec 2006 23:45:46 +0900
- To: Yves Savourel <yves@opentag.com>
- Cc: public-i18n-its@w3.org
Hi Yves, On Mon, 2006-12-11 at 06:09 -0700, Yves Savourel wrote: > Hi Felix, all, > > The <its:locNote_Text> is a mistake. It should be just <locNote_Text> (sometimes we have <locNote_Reference>). The its prefix is a > bug. The goal was to make the distinction between text and reference. Thanks, I now remember the discussion. > > I think the question is: should we have its markup at all in the output file? Strictly speaking things like its:locNoteType in > <output> are not ITS. > > I would propose to just get rid of any ITS markup in the output, and use the same attributes. sorry, I don't understand: what attributes do you want to use? Also, in the case of <p its:locNote="Some locale note"> versus a global localization note: would you put all contents of the localization note in <locNote_Text> element, no matter if the note comes from global or a local ITS markup? My question again would be: were to we describe this in the draft, since it is different to e.g. its:translate or its:withinText ? I'm also asking because my "generic" ITS processor does only understand what is in the draft, so it is not able to produce decide "should I produce just text (in the case of locNote) or copy ITS markup? (in the case of its:translate)" ;) Cheers, Felix > > Cheers, > -yves > > > > -----Original Message----- > From: public-i18n-its-request@w3.org [mailto:public-i18n-its-request@w3.org] On Behalf Of Felix Sasaki > Sent: Sunday, December 10, 2006 9:16 PM > To: public-i18n-its@w3.org > Subject: What does "attaching ITS information" mean? > > > I looked at > 1) http://www.w3.org/International/its/tests/test2/LocNote1-result.xml > and 2) > http://www.w3.org/International/its/tests/test2/WithinText2-result.xml > and have a question: > > in the case of 1), the result is created by generating a "dummy" > <locNote_text> element, which contains the localization note: > <node path="/msgList/body[1]/msg[3]" outputType="new-value-global"> > <output its:locNoteType="alert"> > <its:locNote_Text>The variable <code>{0}</code> has three possible values: 'printer', > 'stacker' and 'stapler options'.</its:locNote_Text> > </output> > </node> > > in the case of 2), the result is created by copying ITS markup to the <output> element, i.e. the its:withinText attribute: > <node path="/myDocument/content[1]/section[1]/p[1]/kw[1]" > outputType="new-value-global"> > <output its:withinText="yes"/> > </node> > > Why this difference? In the case of 1), there would be an <its:locNote> element available which could be used instead of > <its:locNote_Text>, see the rule from LocNote1.xml: > <its:locNoteRule locNoteType="alert" selector="//msg[@id='DisableInfo']"> > <its:locNote>The variable <code>{0}</code> has three possible > values: 'printer', > 'stacker' and 'stapler options'.</its:locNote> > </its:locNoteRule> > > What worries me about the difference of the output for 1) and 2): how does an ITS processor "know" whether it should just generate > textual content,like 2), or copy the ITS markup, like 1)? We have not specified that difference anywhere in the draft. And: what > would happen in the case of 1) if the localization Note contains markup, e.g. > <its:locNote_Text>The <term>variable</term> <code>{0}</code> has three possible values: 'printer', 'stacker' and > 'stapler options'.</its:locNote_Text> would the markup be copied to the output or thrown away? > > Cheers, > > Felix > > >
Received on Monday, 11 December 2006 14:46:05 UTC