W3C home > Mailing lists > Public > public-i18n-its@w3.org > July to September 2007

RE: XProc

From: Yves Savourel <yves@opentag.com>
Date: Wed, 26 Sep 2007 09:21:14 -0600
To: "'Felix Sasaki'" <fsasaki@w3.org>, "'Jirka Kosek'" <jirka@kosek.cz>
Cc: <public-i18n-its@w3.org>
Message-ID: <003901c80050$e17eb3e0$a305a8c0@BREIZH>

+1.
-yves 

-----Original Message-----
From: public-i18n-its-request@w3.org [mailto:public-i18n-its-request@w3.org] On Behalf Of Felix Sasaki
Sent: Wednesday, September 26, 2007 9:13 AM
To: Jirka Kosek
Cc: public-i18n-its@w3.org
Subject: Re: XProc


+1 to your proposals, and I'd propose that you approach the WG / chair
in whatever way you like. Just keep us in the loop with the results.

Felix

Jirka Kosek wrote:
> Hi,
>
> following are XProc issues related to ITS:
>
> 1. Text of error message is stored in attribute:
>
>    <p:error code="NOVERSION"
>              description="Required version attribute missing."/>
>
>    Which means it is not possible to attach ITS info to this attribute.
> We might ask XProc WG to move NL text into element content.
>
> 2. There are not many elements that accept free text, I spotted only
> p:documentation and c:error. Specification says that extension
> attributes are allowed on any element which would mean that ITS
> attributes can be directly used in XProc instance. However XProc schema
> doesn't allow arbitrary attributes on those two elements. We also should
> check this with XProc WG.
>
> If you agree with my conclusions I can informally ask XProc chair about
> those issues or I can submit last call comment on behalf of ITS WG.
>
> 			Jirka
>
>   
Received on Wednesday, 26 September 2007 15:21:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:09 UTC