From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Unable to make cont-en.fmt
Date: Thu, 25 Aug 2005 12:43:50 +0200 [thread overview]
Message-ID: <430DA0E6.4050601@elvenkind.com> (raw)
In-Reply-To: <430D913F.8070106@logosrl.it>
luigi.scarso wrote:
>
> symlink it's the magic word...
Like I said: From personal experience :)
> PS:
> What do you think about to write a dense guide to programmer on how to add
> a pdftex primitive (something like \pdfhelloworld) and how to interface
> to an external libray (like zlib) ?
It goes roughly like this:
* create pdfetex-main.web from all of the web and change files so you
have a least a sane source while coding, and make a copy for future
comparison
* find an existing command who's syntax/semantics are close to the
one you intend to implement ("extension" is fairly useless for
anything that actually does have an impact on typesetting, you
probably want 'convert' or 'last_item').
* hook a new subcode into the processing of that existing command,
* add a call to primitive()
* create a code line to print_cmd_chr()
* when it builds ok, create a change file by running diff on the
original pdfetex-main.web, and add this change file at the end
of the change file list in pdfetex.mk
I'll see if it is possible to create a document with a bit more specific
info
Taco
next prev parent reply other threads:[~2005-08-25 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 23:55 How to customize the default verbatim colors Eugene Toporov
2005-08-25 8:40 ` Unable to make cont-en.fmt luigi.scarso
2005-08-25 9:07 ` Taco Hoekwater
2005-08-25 9:37 ` luigi.scarso
2005-08-25 10:43 ` Taco Hoekwater [this message]
2005-08-25 9:42 ` Vit Zyka
2005-08-25 11:23 ` How to customize the default verbatim colors Taco Hoekwater
2005-08-26 17:17 ` Eugene Toporov
2005-08-27 9:12 ` Taco Hoekwater
2005-08-29 11:06 ` Hans Hagen Outside
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=430DA0E6.4050601@elvenkind.com \
--to=taco@elvenkind.com \
--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).