On Oct 11, 2008, at 5:44 PM, jonathon wrote:
On Sat, Oct 11, 2008 at 06:11, Douglas St.Clair wrote:
<snip>
For many situations ie databases, unicode recommend againsts
ligature use[4].
The problem I expect is that if you use the code for the glyph
instead of recognizing the ligature for example and displaying the
glyph for the letter pair then data entry might get screwed up with
some entries having the ligature and others having the letter pair.
That "problem" exists only when the programmer doesn't consider what
writing system the database uses.
I'd drop back a little and suggest that maybe the problem may lie in
part in the way features are suggested. I would call each application
(calc, writer, ...) a subsystem. If each subsystem encourages users to
submit their suggestions to a wish list that is unique to that
subsystem. Then an additional mechanism needs to be in place to
coordinate the impact of a suggestion on each/all of the secondary
subsystems when the primary subsystem elects to implement it. If a
project has superordinate/overarching goals then all the subsystems
examine what they implement in the light of the superordinate goals. I
think it is easier for people to consider how their subsystem should
be designed to meet a common goal than to coordinate inputs coming in
from a variety of sources at random times.
--
St. Doug, Tigger and Puppy in our memory.
Tir na nOg
Wilton, NH USA
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
