W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2015

RE: [XSLT30] Bug 27615: any likely future action? [I18N-ACTION-403][I18N-ISSUE-394]

From: Phillips, Addison <addison@lab126.com>
Date: Tue, 24 Feb 2015 00:32:13 +0000
To: Michael Kay <mike@saxonica.com>
CC: "public-qt-comments@w3.org" <public-qt-comments@w3.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <7C0AF84C6D560544A17DDDEB68A9DFB52EC0E028@ex10-mbx-9007.ant.amazon.com>
So a resolution of "later" wouldn't really address our comments if "later" we expect to see changes to how numbers are handled in QT but those aren't really possible to preserve compatibility? Or am I misreading that? 

I18N's concern is that the current number formatting has gaps from current best practices. We'll review the Bugzilla item carefully, with the understanding that it is very "late in the day" for you. Look for a response following our weekly call (Thursday).

If there is a "next time", though, I would suggest that we coordinate quite early in the process to help ensure that we mutually arrive at the best available solution.

Addison

> -----Original Message-----
> From: Michael Kay [mailto:mike@saxonica.com]
> Sent: Monday, February 23, 2015 3:11 PM
> To: Phillips, Addison
> Cc: public-qt-comments@w3.org; public-i18n-core@w3.org
> Subject: Re: [XSLT30] Bug 27615: any likely future action? [I18N-ACTION-
> 403][I18N-ISSUE-394]
> 
> If by "actual plan" you mean "charter", then no, there are no actual plans.
> 
> It's too early to say whether that situation will change. I think there will be a
> lot of discussion about it over the next few months. The conversation has
> started, and there is certainly some sentiment that it's time to "declare
> victory". On the XSLT side there's certainly a risk that that continuing to
> develop the language, leaving an increasing number of implementations
> behind on earlier versions, is not in the best interests of interoperability.
> However, there may well be scope for adding new function libraries without
> changing any language features.
> 
> Michael Kay
> Saxonica
> mike@saxonica.com
> +44 (0) 118 946 5893
> 
> 
> 
> 
> On 23 Feb 2015, at 18:55, Phillips, Addison <addison@lab126.com> wrote:
> 
> > Hello QT,
> >
> > The I18N WG has tasked me [0] with asking about the response to our
> comment tracked as bug 27615 [1].
> >
> > Specifically, your response ends with this paragraph:
> >
> > --
> > I'm closing this on behalf of the WG with the disposition "later", meaning
> that we will come back to it if we ever start work on a future version of the
> language. XSL WG hopes that this disposition is acceptable to I18N, and if so,
> requests that you close the bug.
> > --
> >
> > We would like to know if you have actual plans to work on a future version
> of the language or revision of the spec or if, rather, we should not expect you
> to be considering additional work on numeric formatting in the foreseeable
> future.
> >
> > Thanks (for I18N),
> >
> > Addison
> >
> > [0] http://www.w3.org/International/track/actions/403

> > [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=27615

> >
> > Addison Phillips
> > Globalization Architect (Amazon Lab126) Chair (W3C I18N WG)
> >
> > Internationalization is not a feature.
> > It is an architecture.
> >

Received on Tuesday, 24 February 2015 00:32:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 24 February 2015 00:32:44 UTC