From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: texexec ignores switches
Date: Mon, 09 Jul 2001 00:33:05 +0200 [thread overview]
Message-ID: <3.0.6.32.20010709003305.0133a260@server-1> (raw)
In-Reply-To: <20010708100313.55E5552551@bart.math.muni.cz>
At 12:03 PM 7/8/01 +0200, David Antos wrote:
>>
>>so you want an english context but with czech defaults?
>
>I'd prefer Czech ConTeXt with English interface only :-)
>
>>
>> texexec --make --alone --language=en,cz --bodyfont=csr en
>>
>>will do that for you: czech as main language, with czech fonts.
>
>Oops, I've tried it before but the fonts get broken (characters with
>accents are not displayed in dvi). Maybe I misunderstand the ideas of
>multilanguage interface and texexec switches, I think --interface says,
>what language the ConTeXt commands are and the language of the messages,
>--language says what hyphenating patterns to use (it's the same as
>\mainlanguage[xx], isn't it).
right, and for czech, things have been extended recently [this what petr
and i were doing when we were sitting next to you: checking the two most
widely used encodings] so, currently context can work with the two
encodings used in czech patterne at the same time].
>The format determines the set of hyphenation patterns (they are
>hardcoded in it), sets the default language, default font and may
>install additional languages. The generated words (Chapter, Contents and
>so on) should be also set to the default language of the format.
right, but defauktlanguage is called \mainlanguage in context
>How does interface depend on format? I think I should use `format of the
>language of the document' being able to switch to any interface
>installed in the format. (In fact, I'm sure that most Czech users use
>English interfaces, why shouldn't they use texexec --format=cont-cz
>--interface=en? Or without setting the interface if someone likes Czech
>commands?)
beware
texexec cz
is enough, the format switch is for plain and mptopdf and alike
>Where am I wrong? How the things really are? BTW, if I change
>cont-usr.tex and regenerate formats, does it change all the formats? Is
>cont-usr.tex loaded by the \loaduserspecifications command in
>cont-{en,cz,...}?
cont usr is always loaded, unless you use
--language / --bodyfont
so,
texexec --language={cz,sk,en,de,sp} --bodyfont=csr en
should give you an english interface with czech as main language and the
czech tuned cmr fonts.
>Sorry for bothering too much and thanks for answer
no problem, the texexec manual should be better -)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
prev parent reply other threads:[~2001-07-08 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-07 7:59 David Antos
2001-07-07 13:37 ` Giuseppe Bilotta
2001-07-07 13:53 ` Hans Hagen
2001-07-08 10:03 ` David Antos
2001-07-08 22:33 ` Hans Hagen [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=3.0.6.32.20010709003305.0133a260@server-1 \
--to=pragma@wxs.nl \
--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).