From: Andrew Dunbar (hippietrail@yahoo.com)
Date: Wed Apr 24 2002 - 03:32:38 EDT
--- Joaquin Cuenca Abela <cuenca@pacaterie.u-psud.fr>
wrote: >
> ----- Original Message -----
> From: "Andrew Dunbar" <hippietrail@yahoo.com>
> To: <abiword-dev@abisource.com>
> Sent: Tuesday, April 23, 2002 6:15 PM
> Subject: Re: undo and combining characters
>
>
> > --- Karl Ove Hufthammer <huftis@bigfoot.com>
> wrote: >
> > "Tomas Frydrych" <tomas@frydrych.uklinux.net>
> wrote
> > > in
> > > news:3CC58433.16110.B1F416@localhost:
> > >
> > > > I think in the case of the Arabic ligature,
> these
> > > have to be
> > > > treated as two characters, i.e., pressing
> > > backspace after the
> > > > second one leaves you with the first one. This
> > > case is not a
> > > > real issue, because internally the ligature is
> > > stored as two
> > > > separate characters, ligature is just a way of
> > > displaying in
> > > > them in a way that looks better,
> > >
> > > But how does selection works? Are the glyphs
> > > 'decomposed' to allow
> > > selection (which causes a reflow), and religated
> > > when you move the
> > > selection?
> >
> > Selection should select the entire ligature.
>
> The problem here is that some ligatures look
> "mostly" as the original glyphs
> (occidental "ff" "fi" "ffi" "st", etc.)
> Selecting the entire ligature here is VERY
> surprising behaviour for the
> users.
It would show the user that she is dealing with
ligatures though. You're not always editing text that
you entered yourself.
> Other ligatures look radically different from the
> original glyphs (arabic
> have some of these). To take an occidental analogy,
> put yourself in the
> epoc before the ligature "&" (from the latin "et".
> It's more visible using
> the roman form of "&") become a character itself.
>
> Now, should abiword try to select the 't' of "&"?
> (hell, what 't'? The
> original glyph it's absolutely invisible in the
> ligated glyph!)
>
> So I think that for some ligatures individual
> selection of the characters
> that build the ligature makes sense, and for others
> no (it's only me, or all
> that unicode stuff is starting to sound *REALLY*
> hard?)
It's not Unicode's fault - it's the world's fault for
not just speaking American English d-;
But hey, Word seems to work. I have no idea what
Word does for the fi ligature and friends though.
I'd guess that if it's entered as a precomposed glyph
it will handle it as a single glyph. If it's entered
as 'f' plus 'i' it will never convert it to a
ligature.
Andrew Dunbar.
> Cheers,
>
> --
> Joaquin Cuenca Abela
> cuenca@pacaterie.u-psud.fr
>
>
=====
http://linguaphile.sourceforge.net http://www.abisource.com
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
This archive was generated by hypermail 2.1.4 : Wed Apr 24 2002 - 03:33:57 EDT