From: "Pawel Jackowski na Onet" <jackos1@poczta.onet.pl>
Subject: Re: RME and INI
Date: Mon, 6 Oct 2003 19:50:49 +0200 [thread overview]
Message-ID: <001301c38c32$613b8550$0500a8c0@best> (raw)
In-Reply-To: <75DA43BC-F81F-11D7-B387-0030659899AA@fiee.net>
Am Montag, 06.10.03, um 13:18 Uhr (Europe/Zurich) schrieb Pawel
>> But I still can't get an idea of copying '.rme' to '.ini' since '.rme'
>> file
>> can be read as well. Is that an easy way to save orginal config file
>> untouched?
>.rme is overwritten at each update, your manually adapted .ini stays.
So that is the answer! Thanks a lot.
>> 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 think you must change that in cont-usr.tex (copy from cont-usr.ori,
>same reason).
>This file resides in texmf/tex/context/base.
I have tested a lot of modifiction of 'cont-usr.tex' (without effects)...
About two hours ago (following Patrick's hint) I added '--alone' option
while generating format and than bad dream disappeared. The conclusion is
that (probably) bypassing fmtutil in such special cases makes format
generating more reliable. Probably the best (quite advanced) way is to
generate 'strange' formats using directly 'tex_engine --ini ...' command,
but I'm not sure if I can generate proper context format in this way. I'm
afraid it's not my ligue yet :-]
Thanks, Pawe/l
next prev parent reply other threads:[~2003-10-06 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 11:18 Pawel Jackowski na Onet
2003-10-06 11:38 ` bodyfont plr Patrick Gundlach
2003-10-06 16:00 ` Pawel Jackowski na Onet
2003-10-06 17:06 ` RME and INI Henning Hraban Ramm
2003-10-06 17:50 ` Pawel Jackowski na Onet [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-06 9:37 George N. White III
2003-10-06 7:18 Pawel Jackowski na Onet
2003-10-06 9:17 ` Patrick Gundlach
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='001301c38c32$613b8550$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).