On 20 March 2014 15:17, J. Leslie Turriff <jlturriff_at_centurylink.net> 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 remove text
> "glyph
> by glyph", so to speak, as happens with ASCII text; composition mode would
> be active when keystrokes have been recorded in a buffer, so that backspace
> could be used to "unstroke" the original strokes; the "unstroke" operations
> would mimic the order in which the originals were entered, even if the
> editor
> had optomized the composition.
>
>
>
Although that requires an input framework and application that utilise that
buffer in various ways during "composition mode". It is possible, and in
the past I have written a manual and run training on advanced editing for
Dinka language translators on how to utilise such features. But not many
applications support such features.
Andrew
--
Andrew Cunningham
Project Manager, Research and Development
(Social and Digital Inclusion)
Public Libraries and Community Engagement
State Library of Victoria
328 Swanston Street
Melbourne VIC 3000
Australia
Ph: +61-3-8664-7430
Mobile: 0459 806 589
Email: acunningham_at_slv.vic.gov.au
lang.support_at_gmail.com
http://www.openroad.net.au/
http://www.mylanguage.gov.au/
http://www.slv.vic.gov.au/
_______________________________________________
Unicode mailing list
Unicode_at_unicode.org
http://unicode.org/mailman/listinfo/unicode
Received on Wed Mar 19 2014 - 23:26:30 CDT
This archive was generated by hypermail 2.2.0 : Wed Mar 19 2014 - 23:26:30 CDT