Hi,
The "Using Symbols" section of the groff manual states:
Here the exact rules how `gtroff' searches a given symbol:
* If the symbol has been defined with the `char' request, use it.
This hides a symbol with the same name in the current font.
* Check the current font.
* If t
> [...] Between checking .char definitions (which apply to all fonts)
> and checking the current font, there should be a check for a
> font-specific definition that overrides the symbol defined in that
> font.
>
> This omission makes it impossible to straightforwardly redefine
> select symbols in
On 2/12/15, Werner LEMBERG wrote:
>> Am I missing something? Is there a mechanism to override specific
>> symbols in specific fonts?
>
> You are correct, such a mechanism isn't available. It has never been
> requested.
I suppose I should go to the bug tracker to remedy that.
> As a work-around
On 2/12/15, Werner LEMBERG wrote:
> In case you want to follow Bringhurst everywhere, I guess you have to
> define a `.paren' macro anyways because `\,' and `\/' have no effect
> within a `.char' definition, IIRC.
With the mom macros, there's no need to define a macro because of
the '\,' '\/' pro
>> As a work-around, I suggest that you define a `font environment'
>> that sets up proper `.char' definitions as soon as you enter it.
>
> I don't follow. The manual seems to indicate that .char definitions
> are global, not per-environment. (Also, arbitrary environments
> don't always play wel
