From: Hans Hagen <pragma@wxs.nl>
Subject: Re: What's (in) a module?
Date: Tue, 15 Feb 2005 17:32:44 +0100 [thread overview]
Message-ID: <4212242C.2090709@wxs.nl> (raw)
In-Reply-To: <ffff3d1f6431214db91f189c8e6e6450@uni-bonn.de>
Thomas A.Schmitz wrote:
> 1. What constitutes a module? I wrote a couple of definitions and put
> them in a file t-foo.tex. When I write "\input t-foo" in the preamble of
> my document, everything works fine (so the file is found by TeX). When I
> say \usemodule[t-foo] or \usemodule[foo], I get "system : no
> macros found in module foo" and, obviously, "undefined control
> sequence." So: is there any special form for a module? I'm very curious
> because I defined a set of similar macros in another module, and
> everything works fine.
did you run mktexlsr?
> 2. Is it possible to use a certain encoding file, enco-bar.tex, for
> parts of a file only? Could one define a macro (in a module???) that
> would do something like \switchtoencoding[bar] and switch back to the
> file's default encoding afterwards?
you're talking about font encodings?
\definetypeface [PalatinoA] [rm] [serif] [palatino] [default] [encoding=texnansi]
\definetypeface [PalatinoB] [rm] [serif] [palatino] [default] [encoding=ec]
works ok; typefaces live in their own namespace
if you're talking about input encoding, you can switch regimes whenever you want
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2005-02-15 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 16:20 Thomas A.Schmitz
2005-02-15 16:32 ` Hans Hagen [this message]
2005-02-15 17:25 ` Thomas A.Schmitz
2005-02-15 17:32 ` Hans Hagen
2005-02-15 18:25 ` Thomas A.Schmitz
2005-02-16 8:26 ` Hans Hagen
2005-03-16 9:48 ` Patrick Gundlach
2005-03-16 12:37 ` Thomas A.Schmitz
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=4212242C.2090709@wxs.nl \
--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).