* What's (in) a module?
@ 2005-02-15 16:20 Thomas A.Schmitz
2005-02-15 16:32 ` Hans Hagen
0 siblings, 1 reply; 8+ messages in thread
From: Thomas A.Schmitz @ 2005-02-15 16:20 UTC (permalink / raw)
Two maybe related questions:
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.
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?
Thanks to all, best
Thomas
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: What's (in) a module?
2005-02-15 16:20 What's (in) a module? Thomas A.Schmitz
@ 2005-02-15 16:32 ` Hans Hagen
2005-02-15 17:25 ` Thomas A.Schmitz
0 siblings, 1 reply; 8+ messages in thread
From: Hans Hagen @ 2005-02-15 16:32 UTC (permalink / raw)
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
-----------------------------------------------------------------
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: What's (in) a module?
2005-02-15 16:32 ` Hans Hagen
@ 2005-02-15 17:25 ` Thomas A.Schmitz
2005-02-15 17:32 ` Hans Hagen
0 siblings, 1 reply; 8+ messages in thread
From: Thomas A.Schmitz @ 2005-02-15 17:25 UTC (permalink / raw)
On Feb 15, 2005, at 5:32 PM, Hans Hagen wrote:
> 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?
It's a file in my $HOMETEXMF which doesn't have lsR files. I ran
mktexlsr nevertheless, but to no avail. I really fail to understand...
>
>> 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]
>
Yes, I'm talking about font encodings. For the utf greek stuff, I
defined a file enco-agr to provide the named glyphs, which I call by
adding \useencoding[agr]. But I just realized that this will only add
these named files, not overload the other names in the default
encoding, so I guess that's a non-problem after all.
I guess Adam was in touch with you. unicode vectors and modules for
adding support for utf extended Greek are approaching completion. Maybe
we can think where to put the stuff (five fonts at least). Maybe a
CTAN/Context directory would be a good thing.
Thanks
Thomas
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: What's (in) a module?
2005-02-15 17:25 ` Thomas A.Schmitz
@ 2005-02-15 17:32 ` Hans Hagen
2005-02-15 18:25 ` Thomas A.Schmitz
0 siblings, 1 reply; 8+ messages in thread
From: Hans Hagen @ 2005-02-15 17:32 UTC (permalink / raw)
Thomas A.Schmitz wrote:
> It's a file in my $HOMETEXMF which doesn't have lsR files. I ran
> mktexlsr nevertheless, but to no avail. I really fail to understand...
weird; can you run with: \tracefilestrue
> I guess Adam was in touch with you. unicode vectors and modules for
> adding support for utf extended Greek are approaching completion. Maybe
> we can think where to put the stuff (five fonts at least). Maybe a
> CTAN/Context directory would be a good thing.
indeed
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
-----------------------------------------------------------------
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: What's (in) a module?
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
0 siblings, 2 replies; 8+ messages in thread
From: Thomas A.Schmitz @ 2005-02-15 18:25 UTC (permalink / raw)
On Feb 15, 2005, at 6:32 PM, Hans Hagen wrote:
> Thomas A.Schmitz wrote:
>
>> It's a file in my $HOMETEXMF which doesn't have lsR files. I ran
>> mktexlsr nevertheless, but to no avail. I really fail to
>> understand...
>
> weird; can you run with: \tracefilestrue
>
Ha! That did it! tracefiles showed that ConTeXt was expecting a file
name with six or less characters after t-; my module was called
t-utfgreek, so ConTeXt was looking for t-utfgre and couldn't find it.
Renaming to t-utfgre.tex solved the problem. Is this restriction
hard-coded into the core or could it be changed somewhere?
So what about that CTAN directory? Would be a good idea, right?
Best
Thomas
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2005-03-16 12:37 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-02-15 16:20 What's (in) a module? Thomas A.Schmitz
2005-02-15 16:32 ` Hans Hagen
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
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).