On 19-Oct-2010, Axel Beckert wrote: > This is probably cause by the code at the end of the patch causes > that the order of digraphs are no more interchangeable.
That's necessary, since RFC1345 defines many mnemonics that are only
distinguished from others by the sequence of characters.
> Without this hunk, at least the ":a" digraph is working again.
Without order dependency, there's no way for the input processor to
distinguish the following pairs:
{'*', 'X', 0x00d7}, /* MULTIPLICATION SIGN */
{'X', '*', 0x03a7}, /* GREEK CAPITAL LETTER CHI */
{'.', ':', 0x2234}, /* THEREFORE */
{':', '.', 0x2235}, /* BECAUSE */
and many more.
> So I think enlarging the amount of available digraphs is in general
> a very good idea, but the patch must be modified to _not_ remove any
> previously working digraph. It may IMHO change the result of an
> entered digraph if the currently resulting glyph can be entered with
> another digraph.
Someone is going to need to decide which is more important: to allow
the full range of two-character RFC1345 mnemonics in Screen, or to
allow the lax character ordering currently in Screen. They are not
compatible.
My preference, obviously, is to have the two-character RFC1345
mnemonics as the authoritative list of digraphs, overruling the
existing lax ordering. This keeps it consistent with other systems
that use the full set of two-character RFC1345 mnemonics, such as
input modes in Emacs, IBus, and others.
--
\ “I bought a self learning record to learn Spanish. I turned it |
`\ on and went to sleep; the record got stuck. The next day I |
_o__) could only stutter in Spanish.” —Steven Wright |
Ben Finney <[email protected]>
signature.asc
Description: Digital signature
