[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Devel] New request `trin' and asciify

From: Werner LEMBERG
Subject: [Devel] New request `trin' and asciify
Date: Fri, 15 Mar 2002 22:45:49 +0100 (CET)

As already mentioned on this list, I have removed almost all `charXXX'
entities from the font definition files (and I will continue).

Right now I discovered another dependency between input and output
encoding.  For example, in latin1.tmac you can find (after macro

  .tr \[char229]\[oa]

which maps input code 0xE5 to `a with ring above', disabling the
asciify mechanism.  With the charXXX entries in the font files, this
translation wasn't necessary, and .asciify could map char229 back to
`a with ring above'.

I've added some lines of code to fix this.  `trin' is the same as `tr'
except that .asciify will use the original input code.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]