9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9port troff no Greek letters
Date: Wed, 22 Sep 2010 20:38:34 +0200	[thread overview]
Message-ID: <AANLkTinS7s53YTdPz4i+JckfkQ2-zvq6iF9HbCouzfhO@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikRhbNQ+tK5dF8rEWisR=Uh3hhi61wkHstn5xUc@mail.gmail.com>

>> I can't see any Greek letters.
>> Is there sth. simple to do?
>
> Try using
>
> .FP luxisans
>
> at the top of your file.

I tried this as soon as sb here mentioned your earlier post where you
had proposed the same: http://9fans.net/archive/2010/09/206
However, not better with it.
Btw., I observe the same problem as Eric Q, who found that
echo α '\(*a' | 9 troff -ms | page
doesn't draw the first alpha but does draw the second...

>> PS.: Does anyone of you know if it is possible to teach linux to read
>> unicode letters as plan9 does? I mean e.g. alt+*+a means alpha, etc.
>
> Yes.  https://help.ubuntu.com/community/ComposeKey has some
> information on the X11 Compose sequence mechanism.  I have
> been meaning to prepare something in p9p to generate a config
> that makes the X11 compose do exactly what p9p does (except
> maybe the alt-X for spelling out Unicode by hex).  If you make
> one, please post it.  mklatinkbd is probably a good start.
>
> Russ

Thanks for the pointer!

Ruda



  reply	other threads:[~2010-09-22 18:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20 11:46 Rudolf Sykora
2010-09-20 12:00 ` EBo
2010-09-22 17:56 ` Russ Cox
2010-09-22 18:38   ` Rudolf Sykora [this message]
2010-09-23  1:20   ` erik quanstrom
2010-09-24  5:02 ` Tony Lainson
2010-09-20 12:25 erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTinS7s53YTdPz4i+JckfkQ2-zvq6iF9HbCouzfhO@mail.gmail.com \
    --to=rudolf.sykora@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).