9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Koray Erkan" <koray.erkan@yahoo.com>
To: "Plan 9" <9fans@cse.psu.edu>
Subject: [9fans] Sam fonts
Date: Thu, 23 Nov 2006 09:13:06 +0200	[thread overview]
Message-ID: <BOEEJODLKDEGKJEFCFEOMEOOGAAA.koray.erkan@yahoo.com> (raw)

Hi

I've posted this earlier but it didn't generate much enthusiams, probably - as Joel Salomon suggests - due to the fact
that I didn't send it via the mailing list. Here it is again, after I've finally subscribed.

--

I'm using "Sam" on a Windows XP machine. Though I find the editor gratifying for coding purposes, I'm not entirely happy
with its font management. I'd like to use another face that my eyes are more comfortable with - such as the Windows
default "Courier".

Pike notes in a comment in the sources that the "subfonts" are from a certain "X distribution from MIT." I don't know
these resources.

Also, I have a MikTEX installation on the same machine. I tried to use *its* fonts with Sam - using its command-line
font specification switch - but this didn't work.

Given the above:

- Do you have any suggestions how I can convert Windows's font files to the format recognized by Sam?
- Where can I get more of these "X distribution" fonts?
- Are TEX's fonts compatible with the said X distribution's fonts? Is a conversion needed? If so, how, with what tools?

--

Charles kindly suggested that I check the lib/font/bit directory on the Plan9 installation (CD), but my efforts came to
nil. None of the fonts I copied and tried to load worked. Sam seems to accept them (i.e. does not issue errors), but
when I type, I only get large steps of white space.

I need Sam on the Windows platform (we don't choose our platforms just out of fancy but for commercial reasons), and I
have great difficulty working with its default settings. (Hint: I process very large text files with linguistic data in
them, and Sam's currently available fonts are either too bold/large and hence make it impossible to fit enough data into
the screen, or they are too small and, since it lacks syntax coloring, I have great difficulty visually parsing out the
already involved and intricate text strings - e.g. things like localization strings in the XML-based TMX format with
umpteen fields of data describing the strings. I currently use multiple editors to utilize their varying list processing
and regex facilities like TextPad, UltraEdit, etc. Sam, with its structured regexes and everything, is a godsend.)

Your help - or hints - would be much appreciated.

Thanks in advance.


Cheers
Koray



             reply	other threads:[~2006-11-23  7:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23  7:13 Koray Erkan [this message]
2006-11-26 16:17 ` Russ Cox

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=BOEEJODLKDEGKJEFCFEOMEOOGAAA.koray.erkan@yahoo.com \
    --to=koray.erkan@yahoo.com \
    --cc=9fans@cse.psu.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).