in IE.
-Original Message-
From: Travis Leithead
Sent: Thursday, June 18, 2015 11:49 AM
To: 'Arthur Barstow'; Ryosuke Niwa
Cc: public-webapps
Subject: RE: [ime-api] [blink-dev] Removing IME API code from Blink
I've posted the notice on the editor's draft as suggested be
Cc: public-webapps
Subject: Re: [ime-api] [blink-dev] Removing IME API code from Blink
On 5/28/15 2:04 PM, Travis Leithead wrote:
> That sounds good to me (working the UI challenges for IME together with
> grammar/spell checking). Is this a direction the current IME spec could
> take--pos
flect this).
On the other hand, if you propose to formally stop work on the spec "as
it is" now, then it would be appropriate to have a CfC to publish a WG
Note (and if/when there is a firm commitment to do some type of followup
work, a new spec can be created).
WDYT?
-Thanks, Ar
Arthur Barstow; public-webapps
Subject: Re: [ime-api] [blink-dev] Removing IME API code from Blink
> On May 27, 2015, at 11:46 AM, Travis Leithead
> wrote:
>
> I believed the use-cases for avoiding UI clashes between site-driven
> auto-complete lists and IME auto-complete boxes
> On May 27, 2015, at 11:46 AM, Travis Leithead
> wrote:
>
> I believed the use-cases for avoiding UI clashes between site-driven
> auto-complete lists and IME auto-complete boxes is still a valid use case,
> and I think the spec is still valid to try to push to recommendation.
> However, I'
hat I can get an
idea of what its real usage is.
-Original Message-
From: Arthur Barstow [mailto:art.bars...@gmail.com]
Sent: Wednesday, May 27, 2015 5:59 AM
To: public-webapps
Subject: [ime-api] Fwd: [blink-dev] Removing IME API code from Blink
Below is a proposal to remove the "ex
Below is a proposal to remove the "experimental" IME API implementation
from Blink.
Is there sufficient interest from other implementers to keep this spec
on the TR track or should we formally stop work on it and publish a WG Note?
Travis, All, WDYT?
-Thanks, ArtB
Hi All,
A new Working Draft publication of IME API is planned for April 9 using
the following version as the basis:
<http://w3c.github.io/ime-api/TR.html>
If anyone has any major concerns about this, please reply right away.
A few notes about this spec:
* Travis is now the sole Edi
Hi,
while you are looking at HTML5, it would be really helpful if you could take a
look at the work on IME API
<http://dvcs.w3.org/hg/ime-api/raw-file/default/Overview.html> and if you have
comments or questions send them to the webapps group (copied).
(Also, I believe you could commu
Hi All,
We need someone to lead or help with the IME API testing effort:
<http://dvcs.w3.org/hg/ime-api/raw-file/tip/Overview.html>
If you can make a commitment, please let me know.
-Thanks, ArtB
On 10/27/14 9:59 AM, Web Applications Working Group Issue Tracker wrote:
ACTION-740: I
Hi,
On Thu, Dec 19, 2013 at 7:23 PM, Takayoshi Kochi (河内 隆仁)
wrote:
>
>> FYI, this is (still) being discussed at
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22018
> And your suggestion is almost same as the reason Microsoft people proposed
> this.
>
> One of the issue blocking this is a priv
On 10/9/13 2:02 AM, ext Takayoshi Kochi (河内 隆仁) wrote:
The status of IME API in the PubStatus page is correct.
I will make some modification to Editor's draft soon, taking some of
what Microsoft proposed [1],
and some clarification about event delivery.
Thanks for the update Takayoshi.
Hi Arthur,
Thanks for the coordination.
The status of IME API in the PubStatus page is correct.
I will make some modification to Editor's draft soon, taking some of what
Microsoft proposed [1],
and some clarification about event delivery.
If possible, I hope we can get live feedback on the
Hi Takayoshi and Kenji,
If any of the data for the IME spec in [PubStatus] is not accurate,
please provide corrections.
Also, if you have any new information re your plans for the spec, or the
spec's status with respect to being feature complete, implementation
status, etc. please let us kno
new WD of that
> spec was published on August 15: <
> http://www.w3.org/TR/2013/WD-ime-api-20130815/>
> >
> > If you have any comments, please send them to the public-webapps @
> w3.org list.
> >
> > -Regards, ArtB
> >
> > [Mins] <http://www.w3.or
On Aug 16, 2013, at 5:44 AM, Arthur Barstow wrote:
> You may recall WebApps and PFWG discussed WebApps' Input Method Editor API
> last April ([Mins]). As such, I wanted to let you know a new WD of that spec
> was published on August 15: <http://www.w3.org/TR/2013/WD-ime-api-2
Below, Takayoshi proposes WebApps publish a new WD of IME API and this
is a Call for Consensus to do so using the following ED as the basis for
the WD:
<https://dvcs.w3.org/hg/ime-api/raw-file/default/Overview.html>
Agreement to this proposal: a) indicates support for publishing a n
On Fri, 31 May 2013 16:36:52 +0500, Arthur Barstow
wrote:
Hi Mike, All,
During WebApps' April 25 discussion about IME API ([Mins]), Mike agreed
to a couple of actions for the ime-api spec:
[...]
Also, did the group decide to not support a webpage creating their own
IME, at leas
Hi Mike, All,
During WebApps' April 25 discussion about IME API ([Minutes]), Mike
agreed to a couple of actions for the ime-api spec:
* ACTION-690 - Ask the IME Editors to remove Canvas examples (e.g.
images) [on Michael[tm] Smith - due 2013-05-02].
* ACTION-691 - Smith to take back
Hi all,
The updated IME API spec is now published as a second working draft at:
http://www.w3.org/TR/ime-api/ (Apr 04, 2013)
Thanks to Arthur for helping this published.
We are open to any feedback and comments.
In particular, I'd like to get feedback for some things:
1. Is compos
On Thu, 21 Mar 2013 17:39:46 +0100, Arthur Barstow
wrote:
This is a Call for Consensus (CfC) to publish a new WD of Input Editor
Method (IME) API, using the following ED as the basis:
<https://dvcs.w3.org/hg/ime-api/raw-file/default/Overview.html>
Agreement to this proposal: a) ind
Microsoft supports this publication.
> -Original Message-
> From: Arthur Barstow [mailto:art.bars...@nokia.com]
> Sent: Thursday, March 21, 2013 9:40 AM
> To: public-webapps
> Subject: CfC: publish WD of Input Editor Method (IME) API; deadline March
> 28
>
> This
This is a Call for Consensus (CfC) to publish a new WD of Input Editor
Method (IME) API, using the following ED as the basis:
<https://dvcs.w3.org/hg/ime-api/raw-file/default/Overview.html>
Agreement to this proposal: a) indicates support for publishing a new
WD; and b) does not neces
On 3/19/13 5:40 AM, ext Takayoshi Kochi (河内 隆仁) wrote:
Hi all,
It's been a while since the last update for the IME API spec, but we
restarted the work on this.
I (Takayoshi Kochi) have taken over this authorship from the previous
author (Hironori Bono)
for updating the spec.
If yo
Hi all,
It's been a while since the last update for the IME API spec, but we
restarted the work on this.
I (Takayoshi Kochi) have taken over this authorship from the previous
author (Hironori Bono)
for updating the spec.
If you are interested, please take a look at the current working
Happy new year!
At our last F2F, I gave examples of use cases that would benefit from
better interactions with IMEs and asked for the WG's opinion.
In light of the feedback (see minutes), we have decided to focus our effort
on the use case around positioning (e.g. avoiding the UX overlap issue th
On Wed, Feb 29, 2012 at 2:59 AM, Kang-Hao (Kenny) Lu <
kennyl...@csail.mit.edu> wrote:
> http://dvcs.w3.org/hg/ime-api/raw-file/default/use-cases/Overview.html
>
> SUN Haitao found the description of the Traditional Chinese IME used as
> an example in this use cases document s
Kenny,
Thanks for the correction, just want to say I am sure that Changjie
radicals are NOT phonetics.
It is correct to put them in section 3.1.2
Tim
On Wed, Feb 29, 2012 at 5:59 PM, Kang-Hao (Kenny) Lu
wrote:
> http://dvcs.w3.org/hg/ime-api/raw-file/default/use-cases/Overview.html
>
http://dvcs.w3.org/hg/ime-api/raw-file/default/use-cases/Overview.html
SUN Haitao found the description of the Traditional Chinese IME used as
an example in this use cases document somewhat inaccurate.
3.1.2 Radical composer
__
# typing ‘o’ produces ‘人’ on a Traditional
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
On Wed, 08 Feb 2012 22:38:51 +0100, Robin Berjon wrote:
On Feb 8, 2012, at 13:29 , Charles McCathieNevile wrote:
thanks to Mike and the Google guys, we have
http://dvcs.w3.org/hg/ime-api/raw-file/default/use-cases/Overview.html
which explains what an IME API would do and why it would be
On Feb 8, 2012, at 13:29 , Charles McCathieNevile wrote:
> thanks to Mike and the Google guys, we have
> http://dvcs.w3.org/hg/ime-api/raw-file/default/use-cases/Overview.html which
> explains what an IME API would do and why it would be useful. I believe we
> have editors but it do
thanks, i was just checking; i'll defer to Addison and the editor of the
proposed work to handle the details
On Wed, Feb 8, 2012 at 9:02 AM, Michael[tm] Smith wrote:
> Hi Glenn,
>
> > @2012-02-08 08:33 -0700:
> > will there be liaison/participation with I18N Core WG on this work?
>
> I've alread
Hi Glenn,
> @2012-02-08 08:33 -0700:
> will there be liaison/participation with I18N Core WG on this work?
I've already given Richard Ishida and Felix Sasaki a heads-up about it. I
believe Richard is planning to propose an agenda item for it on the i18n WG
call today. But anyway certainly there s
will there be liaison/participation with I18N Core WG on this work?
On Wed, Feb 8, 2012 at 5:29 AM, Charles McCathieNevile wrote:
> Hi,
>
> thanks to Mike and the Google guys, we have http://dvcs.w3.org/hg/ime-api/
> **raw-file/default/use-cases/**Overview.html<http://dvcs.w3.org
Hi,
thanks to Mike and the Google guys, we have
http://dvcs.w3.org/hg/ime-api/raw-file/default/use-cases/Overview.html
which explains what an IME API would do and why it would be useful. I
believe we have editors but it doesn't name a test facilitator (don't
blame me, Art cho
36 matches
Mail list logo
