[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Groff] New request `trin' and asciify
From: |
Werner LEMBERG |
Subject: |
Re: [Groff] New request `trin' and asciify |
Date: |
Mon, 18 Mar 2002 09:25:39 +0100 (CET) |
> It turned out that this works (cutting and pasting from macro def):
>
> .char \\[oa] \\s[\\n[.sc.ps]]Å\\s[\\n[.cap.PS]]
>
> whereas this don't:
>
> .char å \\s[\\n[.sc.ps]]Å\\s[\\n[.cap.PS]]
>
>
> Bug or feature (truth or dare)?
Good question. This problem is a general one, and I think this is a
feature. Doing
.char å Å
is incorrect IMHO. There shouldn't be input characters as the first
parameter of a `char' request. It has only worked previously because
å was hardcoded to a `charXXX' glyph and no `tr' request was active.
Otherwise, I think that groff's behaviour is correct, i.e., `tr' takes
precedence over `char'.
If you do
.tr åå
.char å Å
you will get the previous result.
I will add a note to the documentation of `char'.
Werner