From: Jean-Pierre Le Narzul <JP.LeNarzul@enst-bretagne.fr>
Subject: Use of natural table
Date: Fri, 9 Feb 2001 12:18:23 +0100 (MET) [thread overview]
Message-ID: <200102091118.MAA19000@licancabur> (raw)
Hello,
Is there something special to do (configuration ...) to have support
for natural tables ?
I got the following error when inserting \bTABLE ... \eTABLE code :
>>
>> ! Undefined control sequence.
>> <argument> ...io }{\noexpand \number \pdflastxpos
>> }{\noexpand \number \pdfla...
>>
>> \writeutilitycommand ...writeutility {c \string #1
>> }
>> \doTPDsetposition ...and \number \pdflastypos }#3}
>> }\pdfsavepos \doTPDsetposi...
>>
>> \doonespecial ...{\@@tbl :\currenttbl :c:\colTBL }
>> \relax
>> \next1 #1,->\doonespecial {#1}
>> \doprocesscommaitem
>> \doprocesscommalist ...item \gobbleoneargument #1,
>> ]\relax \global \advance \...
>> ...
>> l.20 \eTABLE
I'm using the beta version cont-tmf.zip.
Thanks in advance
Jean-Pierre Le Narzul
next reply other threads:[~2001-02-09 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-09 11:18 Jean-Pierre Le Narzul [this message]
2001-02-09 11:41 ` Hans Hagen
2001-02-09 15:02 ` Jean-Pierre Le Narzul
2001-02-09 16:55 ` Hans Hagen
2001-02-09 17:34 ` Jean-Pierre Le Narzul
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=200102091118.MAA19000@licancabur \
--to=jp.lenarzul@enst-bretagne.fr \
/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).