ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Patrick Gundlach <pg@levana.de>
Subject: bodyfont plr
Date: Mon, 06 Oct 2003 13:38:57 +0200	[thread overview]
Message-ID: <m2wubibnou.fsf@levana.de> (raw)
In-Reply-To: <002c01c38bfb$9afa8f70$0500a8c0@best> (Pawel Jackowski na Onet's message of "Mon, 6 Oct 2003 13:18:40 +0200")

"Pawel Jackowski na Onet" <jackos1@poczta.onet.pl> writes:

[...]

> The reason I'm so persistant to solve that (probably not crucial) problem is
> that I'm still spying another problem -- generating format with proper
> default font information (as described in details in other threads). I
> thought that texexec config file(s) may be important at that point. But
> after copying 'texexec.rme' to 'texexec,ini', changing some defaults, like
>
>      set  FmtLanguage to  pl
>      set  FmtBodyFont to  plr
>
> and updating ls-R, the problem still appear, means that format generated
> with proper command
>
>     texexec --make --language=pl,en --bodyfont=plr en
>
> doesn't use the proper default font.... So I'm afraid it's not the solution.

I just did a quick test:

texexec --make --alone --bodyfont=plr en

and then run a simple tex file (\starttext \input tufte \stoptext)

gave me an error that plr12 could not be found. So I guess it now
uses plr as a default. But I am not sure.

When you are using your setup, does plr12 get included in your
document?

Patrick
-- 
You are your own rainbow!

  reply	other threads:[~2003-10-06 11:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06 11:18 RME and INI Pawel Jackowski na Onet
2003-10-06 11:38 ` Patrick Gundlach [this message]
2003-10-06 16:00   ` bodyfont plr Pawel Jackowski na Onet
2003-10-06 17:06 ` RME and INI Henning Hraban Ramm
2003-10-06 17:50   ` Pawel Jackowski na Onet

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=m2wubibnou.fsf@levana.de \
    --to=pg@levana.de \
    --cc=ntg-context@ntg.nl \
    /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).