Dear Werner, On Mon, 14 Mar 2005, you wrote:
> > > I want a library of artificial > > > characters which combines base characters and accents to composite > > > characters, [...] > > > > Such substuitution, if done properly, has to be font-dependent and > > resorted to only if the font lacks precomposed characters. > > Right. This is what the `.fchar' request does, contrary to `.char' > which always overwrites the font's definition. > > > AFM files can have a section describing the > > construction of composites. Can groff use that information? > > No. It shouldn't be too difficult to write a script which transforms > such information into proper .fschar commands. if you write such a script you will be able to create a set of .fschar substitutions for base PS fonts from pseudo-afm files of ogokify project. The files contain composition information in the form CC Acircumflex 2 ; PCC A 0 0 ; PCC circumflex 0 130 ; The files can be found as *-c.afm in oginkify subdir of a2ps program. http://www.infres.enst.fr/~demaille/a2ps/ Some more compositions (patches to the above): http://idea.hosting.lv/a/ogonkify/ If you are looking for rules to make substitution in any font (.fchar) - you may look at http://www.pps.jussieu.fr/~jch/software/cedilla/ and ftp://math.feld.cvut.cz/pub/olsak/a2ac Sincerely, Michail _______________________________________________ Groff mailing list Groff@gnu.org http://lists.gnu.org/mailman/listinfo/groff
