Prev: Loop through same dir from 3 different scripts
Next: Oracle 11g, patch 124861-18 and SUN Studio pkg
From: Larry W. Virden on 3 Dec 2009 14:12
A developer working on a man page needed an "accented o" in the page.
So he coded

For example, if \fBo\fR and \fB\N'244'\fR are the members of an
equivalence class, then


However, the \N'244' didn't work out so very well when nroff -man is
used on the file.

For example,
if o
andESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC
7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC {and so on for a
LONG while} are the members of an equivalence class, then


I see other places that use \N'34' to get quote marks inserted. Anyone
have an idea why the accented o isn't appearing for the 244?

From: wschaub on 3 Dec 2009 14:57
On 2009-12-03, Larry W. Virden <lvirden(a)gmail.com> wrote:
> A developer working on a man page needed an "accented o" in the page.
> So he coded
>
> For example, if \fBo\fR and \fB\N'244'\fR are the members of an
> equivalence class, then
>
>
> However, the \N'244' didn't work out so very well when nroff -man is
> used on the file.
>
> For example,
> if o
> andESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC
> 7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC {and so on for a
> LONG while} are the members of an equivalence class, then
>
>
> I see other places that use \N'34' to get quote marks inserted. Anyone
> have an idea why the accented o isn't appearing for the 244?
>

It looks to me that the reason \N'244' does not work is because that character
is not included in any of the included fonts shipped with solaris troff.

So character position 244 does not exist so nothing is displayed.
(at least that is what happens when I try your example on my Solaris 10 box)

I'm not really sure how you would solve this problem except by possibly putting
the actual high-bit ascii in there for the accented o character right after the
bold escape.

Something like:
if \fBo\fR and \fB\�\fR are the members of an
equivalence class, then

might work. although it doesn't seem to be honoring the bold it does display
the accented o.

If this was for anything else but a man page I would just say use groff instead
because Solaris troff is ancient.

From: Andrew Gabriel on 3 Dec 2009 18:17
In article <f6bf84cc-d087-4ac0-9c98-744d61322c5d(a)u7g2000yqm.googlegroups.com>,
"Larry W. Virden" <lvirden(a)gmail.com> writes:
> A developer working on a man page needed an "accented o" in the page.
> So he coded
>
> For example, if \fBo\fR and \fB\N'244'\fR are the members of an
> equivalence class, then

troff isn't 8-bit capable, so I doubt that would work.

Usual way to generate accents in troff is to use over-printing,
so

r\o"o^"le syst\o"\`e"m t\o"\'e"l\o"\'e"phonique
makes
r�le syst�m t�l�phonique
but only on an output device that supports overprinting (i.e.
not your VDU screen - I've faked it here).

>
> However, the \N'244' didn't work out so very well when nroff -man is
> used on the file.
>
> For example,
> if o
> andESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC
> 7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC7ESC {and so on for a
> LONG while} are the members of an equivalence class, then
>
> I see other places that use \N'34' to get quote marks inserted. Anyone
> have an idea why the accented o isn't appearing for the 244?

You might want to try groff instead.
troff's support for non-USASCII characters is pretty non-existant.

--
Andrew Gabriel
[email address is not usable -- followup in the newsgroup]
 | 
Pages: 1
Prev: Loop through same dir from 3 different scripts
Next: Oracle 11g, patch 124861-18 and SUN Studio pkg