ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Pawel Jackowski na Onet" <jackos1@poczta.onet.pl>
Subject: Re: bodyfont plr
Date: Mon, 6 Oct 2003 18:00:21 +0200	[thread overview]
Message-ID: <001501c38c22$f2ac7130$0500a8c0@best> (raw)
In-Reply-To: <m2wubibnou.fsf@levana.de>


Subject: [NTG-context] bodyfont plr
(default font)


> "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?

When I use format generated during first context installation, everything
works fine, means that context use plr by default. However this quite old
format contains only pl-hyphenation patterns.
For a couple of weeks I had been trying hard to generate format with
additional hyphenation patterns AND plr as default font. But each attempt
gave me a format which use cmr by default. Of course when I included i.e
plr10 definition in tex code or input some pl-oriented typescript,
everything was ok since I have correclty instaled and configured pl-fonts.
But default was still cmr, not plr.

I've just tried to generate format with additional option '--alone' (as in
your quick test) and that was the solution! Generated format uses the proper
default font now. Actually I didn't know that texexec uses 'fmtutil' by
default while generating formats (is there any special reason for that?...).
My problem shows that texexec (its self) is able to generate format in more
reliable way :)

Anyway Thank You Very Much For That Hint!


Regards, Pawe/l

  reply	other threads:[~2003-10-06 16:00 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 ` bodyfont plr Patrick Gundlach
2003-10-06 16:00   ` Pawel Jackowski na Onet [this message]
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='001501c38c22$f2ac7130$0500a8c0@best' \
    --to=jackos1@poczta.onet.pl \
    --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).