groff
[Top][All Lists]
Advanced

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

Re: [Groff] Latin-2 woes...


From: Ralph Corderoy
Subject: Re: [Groff] Latin-2 woes...
Date: Thu, 12 Oct 2000 09:33:30 +0100

Hi,

> > Nevertheless, the general solution is to write a proper input
> > encoding file to map Latin-2 to glyph names; something like
> > 
> >   .char £ \[/L]
> >   .char ³ \[/l]
> >   ...
> 
> I don't quite follow. '.char' isn't a groff macro, is it ? (4 letters ?)

Sure is.  Look at groff's troff(1) man page.

    .char c string
        Define  character c to be string.  Every time char- acter c
        needs to be printed, string  will  be  pro- cessed  in  a
        temporary environment and the result will be wrapped up into a
        single object.   Compati- bility mode will be turned off and
        the escape char- acter will be set to \ while string is  being
        pro- cessed.  Any emboldening, constant spacing or track
        kerning will be applied to this object rather  than to
        individual  characters  in string.  A character defined by this
        request can be  used  just  like  a normal character provided
        by the output device.  In particular other characters can be
        translated to it with  the  tr  request;  it  can be made the
        leader character by the lc request; repeated patterns  can be
        drawn  with  the  character using the \l and \L escape
        sequences; words  containing  the  character can  be
        hyphenated correctly, if the hcode request is used to give the
        character a  hyphenation  code.  There  is  a special
        anti-recursion feature: use of character within the character's
        definition will be handled  like  normal  characters  not
        defined with char.  A character definition can be  removed
        with the rchar request.

The two letter restriction has gone for many things in groff.


Ralph.


reply via email to

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