Hello Art,
Could you better define what "soon" means? More specifically, do you have a
deadline for comments? I don't see any dates in the thread below.
Thanks,
Addison Phillips
Principal SDE, I18N Architect (Amazon)
Chair (W3C I18N WG)
Internationalization is not a feature.
It is an
Dear webapps,
This note is to forward a minor comment from the I18N WG about your document
"Manifest for web applications" [1] that we missed forwarding previously.
Our comment is editorial in nature:
--
The title of the specification is "Manifest for web application". Should this
be
This appears to make visual selection appealing--although it doesn't, for
the
reasons mentioned elsewhere, lead to sensible text operations unless the
selected run happens to be all in a single direction.
and if the text runs all in a single direction, there's no difference between
what's the use case driving this, and where are the requirements
coming from?
i ask because i'm inclined to think that the circumstances in which
this would a produce useful results, given the way it carves up the
actual content, are quite, perhaps extremely, limited.
Well, the web
Message-
From: Christiansen, Kenneth R [mailto:kenneth.r.christian...@intel.com]
Sent: Friday, March 20, 2015 1:15 AM
To: Phillips, Addison; public-webapps@w3.org
Cc: public-i18n-c...@w3.org
Subject: RE: I18N comments on Manifest for Web applications
Hi there,
The spec authors use
From tracker:
==
http://www.w3.org/TR/2015/WD-appmanifest-20150212/
Having read the entire document, I can't find any mention of localizbility.
There is no way to indicate in the manifest the language of any of the language
bearing metadata (name, short_name, etc.) nor a way to indicate
From Tracker:
http://www.w3.org/International/track/issues/414
http://www.w3.org/TR/2015/WD-appmanifest-20150212/#obtaining
Section 6.1 discusses the steps in obtaining a manifest. There is no discussion
of obtaining a correctly localized reference, particularly for use in cases
where the
From Tracker:
http://www.w3.org/International/track/issues/415
http://www.w3.org/TR/2015/WD-appmanifest-20150212/#name-member
The 'name' manifest member does not provide a way to indicate the language of
the string. This may be necessary for proper presentation/rendering of the
name, since,
From Tracker:
http://www.w3.org/International/track/issues/413
http://www.w3.org/TR/2015/WD-appmanifest-20150212/#example-manifest
There is an example of a manifest, but no example of non-English or non-ASCII
data. Please consider adding some of each.
(This is an editorial comment)
From Tracker:
http://www.w3.org/TR/2015/WD-appmanifest-20150212/#sizes-member
In section 8.3 there are instructions for comparing/extracting size values that
are either the string 'any' or in the format wwwxyyy (e.g. 1024x768). This
section refers to ASCII case-insensitive comparison in an
Hello Webapps,
As previously mentioned, I am about to send you comments from the
Internationalization Working Group on your document (whose current iteration
lives at [1]). Because we use Tracker for our comments, I will be sending each
comment under separate cover. The I18N WG is always happy
From Tracker:
http://www.w3.org/International/track/issues/416
http://www.w3.org/TR/2015/WD-appmanifest-20150212/#name-member
The 'name' manifest member does not provide a means of indicating the base
direction of the name string. This is equivalent to extracting the 'dir'
attribute
Dear webapps,
The Internationalization Working Group is reviewing [2] your specification
Manifest for web application per your request [1]. We were unable to complete
our review during this week's teleconference. Our next teleconference is
scheduled for 5 March, which is your deadline for
)
Internationalization is not a feature.
It is an architecture.
-Original Message-
From: Phillips, Addison
Sent: Tuesday, June 03, 2014 12:45 PM
To: cha...@w3.org
Subject: Last Call for: Encoding
All,
Today, 3 June 2014, the Internationalization Working Group published a Last
Call Working
Dear Webapps,
Glenn Adams was kind enough to copy me on a recent note regarding the proposal
to add IME API work to your charter [1]. The I18N Core WG discussed this
proposal at our most recent teleconference [2]. Members of the WG are receptive
to reviewing and commenting on this work.
Hi Marcos and Webapps,
This is a personal last call comment [chair hat off]. I realize that it is
late, but I was on vacation
A developer recently sent me a code review implementing the latest spec and I
found some code that was utterly mystifying to me. It turns out that he
implemented
.
It is an architecture.
-Original Message-
From: Marcos Caceres [mailto:marc...@opera.com]
Sent: Thursday, March 17, 2011 6:17 AM
To: Arthur Barstow
Cc: Phillips, Addison; public-webapps@w3.org; public-i18n-c...@w3.org
Subject: Re: Minor comments on Widgets
Hi Art,
On 3/17/11 1:14 PM, Arthur
Robin Berjon asked:
I happened to be referring to the Widget spec this morning
Out of curiosity: in what context?
One such context is on-going work on JavaScript/ECMAScript
internationalization. My team at Lab126 is implementing the strawman [1] (and
then some) for the Kindle version of
.
It is an architecture.
-Original Message-
From: Phillips, Addison
Sent: Tuesday, March 15, 2011 8:41 AM
To: 'public-webapps@w3.org'
Cc: 'public-i18n-c...@w3.org'
Subject: Minor comments on Widgets
Hello Webapps WG,
(these are personal comments)
I happened to be referring
Dear Webapps WG,
This is a personal comment on the Widgets PC draft dated 5 October 2010. I
recognize that your last call period closed, however, a colleague of mine
noticed that rule 9 at [1] defines only the ASCII alphabetic ranges and does
not include the ASCII digits. This means that it
Dear Marcos,
[this is a reply on behalf of the Internationalization Core WG]
We agree that not providing a default locale for a Widget is an oversight in
the Widget's localization model. The ability to provide multiple languages in
the configuration file or in the locales directory structure
Hello Art, Marcos, and Webapps,
During our teleconference yesterday [1], I was tasked with formally replying to
this request on behalf of the Internationalization WG.
I would still like to see the 'locale' field restored to the interface. It's
important to be able to query which locale the
]
Sent: Tuesday, October 12, 2010 5:16 AM
To: marc...@opera.com; Phillips, Addison; public-i18n-c...@w3.org
Cc: public-webapps
Subject: Re: Comment on Widget Interface...
Hi Addison - our Widget Interface spec is blocked, pending
feedback
from the I18N community regarding Marcos' proposal
, September 30, 2010 6:18 AM
To: Phillips, Addison
Cc: public-webapps
Subject: Re: Comment on Widget Interface...
Hi Addison,
On 9/7/10 6:06 PM, ext Phillips, Addison wrote:
Hello Webapps WG,
(This is a personal comment and is not necessarily indicative of
the I18N WG's opinion
)
Internationalization is not a feature.
It is an architecture.
-Original Message-
From: Arthur Barstow [mailto:art.bars...@nokia.com]
Sent: Thursday, September 30, 2010 11:15 AM
To: Phillips, Addison
Cc: public-webapps; public-i18n-c...@w3.org
Subject: Re: Comment on Widget Interface
Hello Webapps WG,
(This is a personal comment and is not necessarily indicative of the I18N WG's
opinion)
In Section 5 (The Widget Interface), the interface provides for retrieving
values such as 'name', 'shortName', etc. In Widgets PC, these can be localized
in the configuration document (I
(personal response)
Having case-sensitive file/folder matching is going to lead to frustrated
authors being unable to figure out why their localizations don't work. If there
is no way to do case-less matching in the widget engine itself, I think your
solution is workable. While it would be
-- Lab126
Internationalization is not a feature.
It is an architecture.
From: mark.edward.da...@gmail.com [mailto:mark.edward.da...@gmail.com] On
Behalf Of Mark Davis ?
Sent: Wednesday, April 28, 2010 12:14 PM
To: Phillips, Addison
Cc: Robin Berjon; Jungshik Shin
(신정...@poing.nachbaur.com?utf-8
Internationalization is not a feature.
It is an architecture.
-Original Message-
From: Robin Berjon [mailto:ro...@berjon.com]
Sent: Tuesday, April 27, 2010 6:49 AM
To: =?utf-
8?q?=22jungshik_shin_=28=ec=8b=a0=ec=a0=95=ec=8b...@poing.nachbaur.
com; _?= 申政湜)
Cc: Phillips, Addison; marc...@opera.com
Hi,
I think that Internationalization support in JavaScript has been too long
overlooked and represents a barrier to development of multilingual web sites.
The Internationalization WG actually approached the ECMASCript folks about
providing for international support in the JavaScript language.
[mailto:marc...@opera.com]
Sent: Monday, March 29, 2010 4:35 AM
To: Martin J. Dürst
Cc: Felix Sasaki; Arthur Barstow; Phillips, Addison; public-i18n-
c...@w3.org; public-webapps; Richard Ishida
Subject: Re: i18n comments:
Hi Martin,
On 29/03/10 10:01 AM, Martin J. Dürst wrote:
[comments below
Hi Scott,
One reason to make 'dir' available on higher-level elements is that 'dir', like
'xml:lang', has scope. It is often useful to specify a base directionality
for an entire document or block of elements rather than having to repeat it
over-and-over on each affected element. I can agree
Thanks Addison - and yes, I think this makes a lot of sense for a
content-style spec like HTML, however as the Widgets PC is a
configuration document most of which is IRIs, integers and so on
rather than text content its less of a clear case.
No, I understand and don't disagree. However,
Hello Marcin,
Thank you for the note. This is a PERSONAL response.
I immediately spotted some red flags in your email. You state:
1. The widget configuration document may contain only US-ASCII
characters, and thus conform to PC.
This appears to me to be false. The widget configuration
(personal response)
The WebApps WG believes that removing the redundant repetitions in
a
standardized way may avoid interop issues. Having said that, in the
latest editors' draft, the rightmost occurrences are removed (as
suggested above).
Actually, I don't believe that there are
(personal response)
Fantastic. Unfortunately, implementer feedback has raised concerns
about ITS and so the WG has put ITS features at risk (and marked
as
such in the soon to be released CR spec). We will see what happens
in
CR; hopefully implementers will understand the value of
-- W3C Internationalization WG
Internationalization is not a feature.
It is an architecture.
-Original Message-
From: Marcos Caceres [mailto:marc...@opera.com]
Sent: Friday, July 10, 2009 8:49 AM
To: Phillips, Addison
Cc: ish...@w3.org; public-Webapps@w3.org; public-i18n-c...@w3.org
, Marcos Caceres
marcosscace...@gmail.com wrote:
On Thu, Jan 29, 2009 at 10:56 PM, Phillips, Addison
addi...@amazon.com wrote:
2. Section 7.4 (Widget) The various language bearing elements
such as name, description, etc. are of the zero-or-one type.
However, it is typically better to allow any
.
-Original Message-
From: Marcos Caceres [mailto:marc...@opera.com]
Sent: Friday, April 03, 2009 8:03 AM
To: Phillips, Addison
Cc: public-i18n-c...@w3.org; public-webapps@w3.org
Subject: Re: Widgets 1.0 Packaging and Configuration: I18N
comments...
Hi Addison,
On Fri, Apr 3, 2009
.
It is an architecture.
-Original Message-
From: Lachlan Hunt [mailto:lachlan.h...@lachy.id.au]
Sent: Friday, January 30, 2009 3:16 PM
To: Phillips, Addison
Cc: public-webapps@w3.org; public-i18n-c...@w3.org
Subject: Re: [selectors-api] Selectors API I18N Review...
Phillips
-- Lab126
Chair -- W3C Internationalization WG
Internationalization is not a feature.
It is an architecture.
-Original Message-
From: Lachlan Hunt [mailto:lachlan.h...@lachy.id.au]
Sent: Tuesday, January 27, 2009 9:39 AM
To: Phillips, Addison
Cc: public-webapps@w3.org; public-i18n-c
41 matches
Mail list logo
