From: Patrick Gundlach <patrick@gundla.ch>
Subject: Re: documentation of presentation modules?
Date: Fri, 11 May 2001 20:46:15 +0200 [thread overview]
Message-ID: <01051120461501.00352@levana> (raw)
In-Reply-To: <3.0.6.32.20010511180154.016ff100@server-1>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 732 bytes --]
Hallo Hans (and others)
> >2) what use is the %D stuff in all the modules? Is there any way
> >to get the documentation out of these modules?
>
> texexec --modu --pdf somefile
Great! I had something exactly like this in mind.
> i already repaired that but cannot upload a new beta because i'm in the
> middle of merging new otr code into the core [and splitting main-*.tex
> files in the process. This means that the next release will be a major
> update: additional encoding support, a whole new font layer [which
Oh no! not more encodings :-)
> >4) how do I use the hz-like stretching/shrinking with the 'new' font
> >mechanism?
>
> not yet there, but will come
looking forward :-)
--
Viele Grüße,
Patrick Gundlach
next prev parent reply other threads:[~2001-05-11 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 13:59 Patrick Gundlach
2001-05-11 16:01 ` Hans Hagen
2001-05-11 18:46 ` Patrick Gundlach [this message]
2001-05-13 11:41 ` Hans Hagen
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=01051120461501.00352@levana \
--to=patrick@gundla.ch \
/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).