Richard Wordingham wrote:
>
> On Sun, 23 Mar 2014 22:46:49 +
> Marc Durdin wrote:
>
> > All the Keyman products -- on Windows, web, iOS and Android, as well
> > as KMFL, which is a port of Keyman, work on the principle of modifying
> > the text buffer directly.
>
> I had been going to remark
On Sun, 23 Mar 2014 22:46:49 +
Marc Durdin wrote:
> All the Keyman products -- on Windows, web, iOS and Android, as well
> as KMFL, which is a port of Keyman, work on the principle of
> modifying the text buffer directly.
I had been going to remark that they couldn't do that directly, but
fu
On 2014/03/20 02:28, Whistler, Ken wrote:
It is really annoying, particularly to efficient typists, when
a sequence of 4 keystrokes is *not* exactly undone by a
sequence of 4 backspace strokes. When that occurs, the
flow of text composition is suddenly interrupted by forcing
the user out of "com
from this issue with the varying
composition schemes we've seen enforced by limited input methods.
-Original Message-
From: Unicode [mailto:unicode-boun...@unicode.org] On Behalf Of Richard
Wordingham
Sent: Monday, 24 March 2014 12:07 AM
To: unicode@unicode.org
Subject: Re: Editing
On Sun, 23 Mar 2014 03:32:06 +0100
Philippe Verdy wrote:
> 2014-03-23 1:16 GMT+01:00 Richard Wordingham <
> richard.wording...@ntlworld.com>:
>> The use of 'COMPOSE' indicates that one is not simply entering a
>> sequence of characters. 'COMPOSE, C, CEDILLA, ACUTE' should mean
>> an input proce
On Sun, 23 Mar 2014 03:32:06 +0100
Philippe Verdy wrote:
> 2014-03-23 1:16 GMT+01:00 Richard Wordingham <
> richard.wording...@ntlworld.com>:
>> The use of 'COMPOSE' indicates that one is not simply entering a
>> sequence of characters. 'COMPOSE, C, CEDILLA, ACUTE' should mean
>> an input proce
2014-03-23 1:16 GMT+01:00 Richard Wordingham <
richard.wording...@ntlworld.com>:
> On Sat, 22 Mar 2014 23:37:49 +0100
> Philippe Verdy wrote:
>
> > 2014-03-22 20:50 GMT+01:00 Richard Wordingham <
> > richard.wording...@ntlworld.com>:
> >
> > > > But it won't apply to "diacritics" (combining chara
On Sat, 22 Mar 2014 23:37:49 +0100
Philippe Verdy wrote:
> 2014-03-22 20:50 GMT+01:00 Richard Wordingham <
> richard.wording...@ntlworld.com>:
>
> > > But it won't apply to "diacritics" (combining characters or joiner
> > > controls like CGJ, ZWK and ZWNJ, and possibly even some oher
> > > forma
2014-03-22 20:50 GMT+01:00 Richard Wordingham <
richard.wording...@ntlworld.com>:
> > But it won't apply to "diacritics" (combining characters or joiner
> > controls like CGJ, ZWK and ZWNJ, and possibly even some oher format
> > controls) that have combining class 0 because their encoding order i
On Sat, 22 Mar 2014 09:41:40 +0100
Philippe Verdy wrote:
> 2014-03-22 1:04 GMT+01:00 Richard Wordingham <
> richard.wording...@ntlworld.com>:
> So if you enter or , you get
> in the editor's backing store some encoding form (which my be
> precombined or not, or with diacritics not necessarily
2014-03-22 1:04 GMT+01:00 Richard Wordingham <
richard.wording...@ntlworld.com>:
> On Thu, 20 Mar 2014 05:59:49 +0100
> Philippe Verdy wrote:
> Not all Indic diacritics have combining class 0, and Hebrew diacritics
> have non-zero combining classes.
>
Did I say something else ? You have probabl
Japanese Windows IME does similar. After committing converted text, Backspace
erases the last converted character, while CTRL+Backspace right after commits
undo the commit and put the text back to converted (i.e., undetermined or
editing) state.
/koji
On Mar 20, 2014, at 9:24 PM, Andre Schapp
WRT Hangul Syllables & OSX TextEdit
Take a Hangul Syllable such as 반
backspace erases the whole syllable
control+backspace erases one jamo at a time from the syllable
André Schappo
On 19 Mar 2014, at 16:38, Doug Ewell wrote:
> Andre Schappo wrote:
>
>> WRT Latin. I have just tested with OSX
On 3/19/2014 9:17 PM, J. Leslie Turriff wrote:
Perhaps it might be useful to be able to distinguish between an "editing
mode" and a "composition mode": editing mode would be active when a document
is first loaded into the editor, when the editor has no keystroke history to
consult, and
sequences, but not
>> by any existing content, but that steps beyond my earlier point.) These
>> constraints in how we think limit possibilities
>>
>>
>> Peter
>>
>>
>> -Original Message-
>> From: Doug Ewell [mailto:d...@ewellic.org]
>&
On 20 March 2014 15:17, J. Leslie Turriff wrote:
> Perhaps it might be useful to be able to distinguish between an
> "editing
> mode" and a "composition mode": editing mode would be active when a
> document
> is first loaded into the editor, when the editor has no keystroke history
> to
possibilities
>
>
> Peter
>
>
> -Original Message-
> From: Doug Ewell [mailto:d...@ewellic.org]
> Sent: March 19, 2014 9:39 AM
> To: Peter Constable; unicode@unicode.org
> Subject: RE: Editing Sinhala and Similar Scripts
>
> Peter Constable wrote:
>
&
Perhaps it might be useful to be able to distinguish between an
"editing
mode" and a "composition mode": editing mode would be active when a document
is first loaded into the editor, when the editor has no keystroke history to
consult, and in this mode the backspace key would merely r
by the
input sequences, but not by any existing content, but that steps beyond my
earlier point.) These constraints in how we think limit possibilities
Peter
-Original Message-
From: Doug Ewell [mailto:d...@ewellic.org]
Sent: March 19, 2014 9:39 AM
To: Peter Constable; unicode@unic
On Wed, 19 Mar 2014 14:17:00 +0100
Daniel Bünzli wrote:
> Le mercredi, 19 mars 2014 à 02:33, Doug Ewell a écrit :
> > There are two types of people:
> >
> > 1. those who fully expect Backspace to erase a single keystroke,
> > and feel it is a fatal flaw if it erases an entire combination, and
>
"Whistler, Ken" wrote:
> But what Peter was pointing out that in the *generic* case
> for editing, such as first cursor down at some random
> location in already existing text, there is no existing history
> of how that text was created. And thus there are no "keystrokes"
> to be undone by hittin
Andre Schappo wrote:
> WRT Latin. I have just tested with OSX TextEdit and the precomposed
> character é U+00E9
>
> Backspace erases é
> Control+Backspace erases ´ leaving one with e
>
> I had not realised this was possible until I experimented with
> combinations of Backspace + alt/command/ctrl/
And I think you need to distinguish between *proximate*
behavior in an editor and editing behavior in general.
Once a user enters editing mode, the expectation that we
(the software community writing text editors) have built,
in interaction with users, is that within reason, something that
you ha
Peter Constable wrote:
>> There are two types of people:
>>
>> 1. those who fully expect Backspace to erase a single keystroke
>
> It is nonsensical to talk about erasing a _keystroke_.
But that's what they expect.
--
Doug Ewell | Thornton, CO, USA
http://ewellic.org | @DougEwell
On 3/19/2014 7:57 AM, Peter Constable wrote:
It is nonsensical to talk about erasing a _keystroke_.
"undo", "revert" the effect of a keystroke. The concept is meaningful.
Eric.
___
Unicode mailing list
Unicode@unicode.org
http://unicode.org/mailman/
From: Unicode [mailto:unicode-boun...@unicode.org] On Behalf Of Doug Ewell
>>> When you backspace it destroys multiple keystrokes.
> There are two types of people:
>
> 1. those who fully expect Backspace to erase a single keystroke
It is nonsensical to talk about erasing a _keystroke_. That wou
On 19 Mar 2014, at 01:33, Doug Ewell wrote:
> Richard Wordingham wrote:
>
>>> Typing is a nightmare.
>>
>>> When you backspace it destroys multiple keystrokes.
>>
>> I suspect this is a widespread and unsolved problem.
>
> There are two types of people:
>
> 1. those who fully expect Backspa
LOL, that's why, if the input framework allows it, its easier to support
both approachable to backspace or at least an option to choose one or the
other.
; )
Andrew
On 19/03/2014 11:37 PM, "Doug Ewell" wrote:
> Richard Wordingham wrote:
>
> Typing is a nightmare.
>>>
>>
>> When you backspa
Le mercredi, 19 mars 2014 à 02:33, Doug Ewell a écrit :
> There are two types of people:
>
> 1. those who fully expect Backspace to erase a single keystroke, and
> feel it is a fatal flaw if it erases an entire combination, and
>
> 2. those who fully expect Backspace to erase an entire combin
Richard Wordingham wrote:
Typing is a nightmare.
When you backspace it destroys multiple keystrokes.
I suspect this is a widespread and unsolved problem.
There are two types of people:
1. those who fully expect Backspace to erase a single keystroke, and
feel it is a fatal flaw if it er
30 matches
Mail list logo
