sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: matty@cs.su.oz.au (James Matthew Farrow)
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: printing utf
Date: Thu, 7 Oct 1993 00:15:02 -0400	[thread overview]
Message-ID: <19931007141502.24890.frobozz@orthanc.cs.su.OZ.AU> (raw)
In-Reply-To: <9310061326.AA12492@zombie.gec-epl.co.uk>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=X-utf-2, Size: 2083 bytes --]

    Date:	Wed, 6 Oct 1993 09:26:11 -0400
    From:	steve@gec-epl.co.uk (Steve_Kilbane)
    Message-Id: <9310061326.AA12492@zombie.gec-epl.co.uk>
    To:	sam-fans@hawkwind.utcs.toronto.edu
    Subject: printing utf
    X-Sun-Charset: US-ASCII
    Content-Length: 287
    
    ok, so i've got sam and 9term running with the utf fonts - having
    produced some files with utf in them, any idea how i'd print them
    on a postscript printer..?

    [ this is probably a dumb question, but then it took me 2.5 hours
    last night just to get the X fonts installed. sigh. ]

    steve

Currently to print I am doing two things.  I have a latin1 `device'
for troff which uses ISOLatin1Encoding for PostScript fonts rather than
the Adobe StandardEndcoding.  I have a filter which reads utf files
and can produce plain ascii approximations (`;-)' for `☺' (a smiley)
for example) or troff codes when asked, so `→' (that's a right arrow)
becomes `\(->').  It's a hack, but hey, it gets Welsh poetry printed
with wcirumflex and ycircumflex!

I can make this available but it's written using bio at the moment
and I can't release that so I'd have to rewrite it.  I also want a
more general solution to the problems `unutf' tackles.  I originally
intended it for use in our department here as a MIME decoder for
utf-2 so the members of our department without 9terms could handle
utf-2 mail.

A more general solution again I've thought about but requires a
rethinking to some extent of the tools people use when printing.

To handle the printing of utf-2 strings in PostScript you'd need
something to decode the encoding at the PostScript level if you want
to include them in the strings themselves, perhaps something akin to
`(general utf string) utfshow'.

					Matty.
--
James Matthew Farrow                    | "For in that moment I beheld the ruin
matty@cs.su.OZ.AU                       | of my existence.  My world fell dark
Basser Department of Computer Science   | and my life became a shallow dream.
Sydney University - FAX: +61 2 692 3838 | `Odi et amo. Excrucior.'" - Tlindah



      reply	other threads:[~1993-10-08  6:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-10-06 13:26 Steve_Kilbane
1993-10-07  4:15 ` James Matthew Farrow [this message]

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=19931007141502.24890.frobozz@orthanc.cs.su.OZ.AU \
    --to=matty@cs.su.oz.au \
    --cc=sam-fans@hawkwind.utcs.toronto.edu \
    /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).