gmane.comp.tex.eplain

Re: Page xref - increment?

Michael Talbot-Wilson — 2013-04-16T08:21:44


Thanks for not answering, everyone.  I gradually felt my way towards
this very advanced way of doing it.

"This \vadjust{\focount=\folio\advance\focount by 1
\definexref{gick}{\the\focount}{p.\thinspace}
\def\epsfsize#1#2{0.7#1}
\setbox\imbox=\hbox{\epsffile{.../page1.ps}}
\penalty0\box\imbox
}} may or may not please you."

i.e. do it outside the value, even (whew!) outside the \definexref.

Page xref - increment?

Michael Talbot-Wilson — 2013-04-15T08:02:15

Thanks to Karl for trying to help, but it hasn't penetrated.  I need
to increment the page xref.

What I'm doing is scanning full A4 pages:

$ scanimage -d 'epson2:libusb:001:005' --mode=gray --depth=8 \
--format=pnm --resolution=360 --brightness=-1 --sharpness=2 \
-x209 -y295 > page$1.pgm

$ pnmmargin -black 2 page$1.pgm >tmp.pgm

$ pnmtops --equalpixels -noturn tmp.pgm >page$1.ps

(Yes, I know the resolution is too high.)

Then I'm inserting those full-page images (slightly reduced) with
visible paper texture into the final document:


\def\epsfsize#1#2{0.7#1}
\setbox\imbox=\hbox{\epsffile{.../page1.ps}}
\box\imbox

I want to do that without interrupting the text, so if there is a page
break in the middle of a paragraph I'm doing a \vadjust{} on the last
line of the page.  So the page break is unchanged, but now there is a
full page image between the two pages.

But if I do

"This \vadjust{\xrdef{gick}
\def\epsfsize#1#2{0.7#1}
\setbox\imbox=\hbox{\epsffile{.../page1.ps}}
\penalty0\box\imbox
}} may or may n

Re: How to \definexref?

Karl Berry — 2013-04-12T23:30:44

Hi Michael,

(You are the same Michael Talbot-Wilson who just posted to eplain,
right?!)

    A's letter (page 57)

If all you want is to define a reference that refers to the current
page, that's what \xrdef and \xref are for.
http://tug.org/eplain/doc/eplain.html#Page-references

I suspect you already know that and want to do something else, but I
can't tell from your description what the goal is ...

Best,
Karl

P.S. I sent this to mtw-YADDcH6fAm66c6uEtOJ/EA< at >public.gmane.org yesterday, but that bounced:
    <mtw-YADDcH6fAm66c6uEtOJ/EA< at >public.gmane.org>: cannot update mailbox /var/spool/mail/mtw for user mtw.
    error writing message: File too large

Re: How to \definexref?

Karl Berry — 2013-04-11T22:41:25

Hi Michael,

    A's letter (page 57)

If all you want is to define a reference that refers to the current
page, that's what \xrdef and \xref are for.
http://tug.org/eplain/doc/eplain.html#Page-references

I suspect you already know that and want to do something else, but I
can't tell from your description what the goal is ...

Best,
Karl

How to \definexref?

Michael Talbot-Wilson — 2013-04-11T03:13:37

Thanks, but now another problem:

\newcount\focount
\def\gotfo{\focount=\folio \advance\focount by 1 \the\focount}
...
A's letter (\ref{a-letter})
...
\definexref{a-letter}{\gotfo}{page}

doesn't work.  The .aux file contains

\< at >definelabel{a-letter}{\focount =56\advance \focount by 1 57}{page}

I'd like to see:

A's letter (page 57)

but don't.  Not even the class.

Also tried \number\focount.

Any ideas, anyone?

Re: \vadjust gyrating, not migrating

Daniel H. Luecking — 2013-04-01T17:09:16


It's a TeX thing. Anything in \vadjust is places directly below 
the line it occurs in. 


If you want something to float to a new position, use 
    \topinsert ... \endinsert 
or 
    \pageinsert ... \endinsert
(these are plain TeX macros, documented in the TeXbook).

Regards,
Dan

\vadjust gyrating, not migrating

Michael Talbot-Wilson — 2013-03-31T08:26:43

Dear all,

Dunno whether this is an eplain thing or a tex thing, but hope you can
tell me what I'm doing wrong.  Using texlive 2012.

A new paragraph starts at the end of the page (A4, but...).  So, there
is the end of the first paragraph, a parskip, then the first line of
the next para and a page break.

I want to insert of page scan, slighty reduced, between the two pages
so that they look just the same, the first page looks just the same,
with the floating first line of the next para at the end of it, but
with an image (produced by pnmtops) alone on the second page.

In the test file below, the page break occurs after the first line of
the new para IF the "%" comment marks are left in place.

If they are removed the page break happens where the para break is.
Then, the first line of the next para is at the top of the second page
and the image occupies the remainer of the page.

Shouldn't \vadjust simply cause its body to migrate out of the line,
without moving the line?  Without changing the place where t

eplain 3.5 released

Karl Berry — 2013-02-15T00:57:59

FYI, I've uploaded eplain-3.5 to CTAN and installed it in TeX Live.
Aside from bug fixes to \columnfill and others, the changes are small:

* make \providecommand and \newcommand \long, like LaTeX.
* restored the catcode of < at > at \endpackages.
* ifpdf.sty: update to latest version.

I also attempted to update the web pages at http://tug.org/eplain,
although undoubtedly missed some problems there.

Hope it works out ...

karl

column breaks in eplain

Karl Berry — 2013-02-08T19:05:02

Hi James - back in last October (message below for context) you reported
a problem with \columnfill in Eplain.  Indeed, it was completely broken,
failing to take into account one of the new internal fudge parameters,
namely \< at >col< at >extraheight (introduced to fix other bugs), causing the
wrong column breaks that you noted.

Although essentially all of the double-column stuff has been rewritten
since I looked at it last, I tried to fix it anyway.  Your example
works, anyway.  Clearly this will only impact documents that use
\columnfill.  I'm sure plenty of double-column bugs remain and always
will ...

The patch below adds one line (\advance\temp< at >dimen by -\< at >col< at >extraheight)
and changes some comments.  I plan to make a new release with this and
other fixes within a few days.  Any testing is welcome.

Thanks,
Karl

--- eplain.tex(revision 19)
+++ eplain.tex(working copy)
< at >< at > -3255,11 +3255,12 < at >< at >
 \newdimen\temp< at >dimen
 \def\columnfill{%
   \par
-  \dimen< at >=\pagetotal   % The height of the text set so far. 
-  \tem

Re: removing diagram and bibtex code

Luis Rivera — 2012-12-20T00:31:14

Now, that explains a lot!


ok. I guess I shall follow John's advice and not trying to isolate
features and take eplain as it is; or otherwise mix up my own macro
concoction separately.


Right. Thanks for the answers.

Best,

Luis Rivera
O< www.asciiribbon.org campaign

Re: removing diagram and bibtex code

Karl Berry — 2012-12-19T22:37:24

    Perhaps what strikes me is the dependence of  the plain macro file on
    code for BibTeX

Like I said, I put the common definitions into btxmac precisely so
*btxmac* could be independently read.  It was never a goal to have
Eplain without bibtex support.

    One of the reasons why I'm asking is that I found that the eplain used
    to typeset TeX for the Impatient is tiny in comparison with the actual

Of course.  I and a host of others kept developing eplain after the book
was done.  Up to the present day, as you have seen.

    I thought it would be nice to be able to use eplain
    macros without the bibtex et al (miniltx, names.sty, etc.) code,

Those big things aren't loaded unless you ask for them with
\beginpackages (presumably because you want to use them).
    
    perhaps by calling \input xeplain (excised eplain). 

Whatever any such name may be, it shouldn't be xeplain.  That's the name
I used (more less at random) for the commented source file, as Dan
mentioned.

    could we try to get on

Re: removing diagram and bibtex code

Luis Rivera — 2012-12-19T18:32:55

Perhaps what strikes me is the dependence of  the plain macro file on
code for BibTeX, which is an different program, now that some
replacements for BibTeX in pure TeX (Librarian, by Isambert, for
instance) are in development.


One of the reasons why I'm asking is that I found that the eplain used
to typeset TeX for the Impatient is tiny in comparison with the actual
version of eplain. I thought it would be nice to be able to use eplain
macros without the bibtex et al (miniltx, names.sty, etc.) code,
perhaps by calling \input xeplain (excised eplain). The manual says
that we can use the modules separately *except* xeplain.tex; maybe
that's actually my question: could we try to get only the eplain
macros in xeplain.tex, standalone, without the BibTeX et al support
code?

Luis Rivera
O< http://www.asciiribbon.org/ campaign

Re: removing diagram and bibtex code

Karl Berry — 2012-12-18T23:00:08

Dan's reply is on the mark.  Just a couple more historical notes:

The BibTeX stuff also becomes a standalone file, btxmac.tex, since
that's what Oren wanted.  That is why it includes various "generic"
definitions that are then also used in the rest of Eplain.  Sure, it
could be possible to split it up further, but I saw no reason to do so.

The commutative diagrams are indeed rather a different animal, but They
don't hurt anything that I can see.  They are there simply because Steve
Smith wrote them and offered them to Eplain (decades ago), and I was
enthusiastic about user contributions.

Best,
Karl

Re: removing diagram and bibtex code

Daniel Henry Luecking — 2012-12-18T22:22:33

On Tuesday, December 18, 2012 8:23 AM, John Culleton <John-nywY5H0wo4uTkO8mciVlQg< at >public.gmane.org>
wrote:

The bibtex stuff is there because it follows eplain's philosophy: 
it provides a feature many find useful without committing to a 
specific visual format. I does seem like some parts of it could 
have been left in a separate file.

As for commutative diagrams, I think that could easily have 
been left out.

Unfortunately, these things can't be easily changed in the 
distribution with breaking old files written under the present set 
of assumptions.


Actually, these particular features seem to be removable. The 
file eplain.tex used to create the format is assembled from 
several separate files which include xeplain.tex (with most 
comments removed) plus btxmac.tex,  arrow.tex and a few 
others. One could, conceivably, assemble a smaller eplain
by leaving some of this out.

The commutative diagram stuff comes from arrow.tex and the 
bibtex stuff from btxmac.tex. Unfortunately, there are parts of 
eplai

Re: removing diagram and bibtex code

john Culleton — 2012-12-18T14:23:48

On Mon, 17 Dec 2012 16:47:11 -0600
Luis Rivera <jlrn77-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:



Eplain is what it is. It is not designed to be disassembled. My
attempts to extract this or that feature have not been
successful.

removing diagram and bibtex code

Luis Rivera — 2012-12-17T22:47:11

Hello!

I'm new to the list (and to eplain, for that matter), so perhaps my
question challenges several pervading assumptions. My observation is
partly a feature request and partly a question.

I'm sure the code is there for some reason (perhaps even simply
historical reasons), but I wonder whether is it feasible to _remove_
the support for commutative diagrams and/or BibTeX bibliographies,
among other things, to preserve only the middle-level formatting
capabilities (cross references, columns, footnotes) in a slimmer, more
compact eplain. If not, why these macros got in the core code of
eplain in the first place?

Cheers,

Luis Rivera
O< http://www.asciiribbon.org/ campaign

Re: column breaks in eplain

Karl Berry — 2012-10-09T22:52:07

Hi James,

    Any advice for how to fix this?

I've also had problems with the column breaking.  I don't have any
obvious work-around to suggest :(.  Thanks for the small self-contained
test case, though.

I'm going to be away the rest of this week, but I'll try to look into it
after I get back.  (Unless you get there first, Oleg, which would be
very nice. :)

Thanks for the report,
Karl

P.S. I'm not surprised that adding \par (bb's suggestion) made no
difference.  The first thing \columnfill does is \par.

column breaks in eplain

James Mckernon — 2012-10-09T11:04:55

Hi all,

I'm new to TeX and experimenting with eplain's columns feature, but I
don't seem to be able to get column breaks to work as expected. An
example:

\input eplain
\hsize 188mm \vsize 188mm
\hoffset 5mm \voffset 5mm
\nopagenumbers
\doublecolumns
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do
eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad
minim veniam, quis nostrud exercitation ullamco laboris nisi ut
aliquip ex ea commodo consequat. Duis aute irure dolor in
reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla
pariatur. Excepteur sint occaecat cupidatat non proident, sunt in
culpa qui officia deserunt mollit anim id est laborum.
\columnfill
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do
eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad
minim veniam, quis nostrud exercitation ullamco laboris nisi ut
aliquip ex ea commodo consequat. Duis aute irure dolor in
reprehenderit in voluptate velit esse cillum dolore eu

Re: Bug(?) in \newcommand

Karl Berry — 2012-09-12T22:55:36

Hi Dan,

    The definition of \newcommand comes from btxmac.tex, so perhaps 
    there is a reason for bibliographies to use \edef. 

It's been 20+ years since I wrote that macro, but I can't imagine any
reason why that would be the case.

   \def\< at >startdef{\expandafter\edef\< at >commandname}%

Does your failing example work if you just replace the \edef with \def?

It appears to have been that way "since the beginning", at least as of
1995, which is the oldest file I found quickly.  

In general, the btxmac \newcommand was just supposed to be a bare-bones
good-enough-for-bib-files replacement for LaTeX \newcommand.  Since, as
you point out, LaTeX \newcommand certainly doesn't do \edef, it seems
btxmac's shouldn't either.

Thanks,
k

Bug(?) in \newcommand

Daniel Henry Luecking — 2012-09-12T18:49:29

Hello:

The definition of \newcommand in eplain eventually invokes \< at >newcommand 
(see below). This atempts to \edef the macro and leads to errors in simple cases:

\input eplain
\newcommand\y{\gobble}
\bye

Of course the error is 
    ! Argument of \gobble has an extra }
But this is certainly a valid way to define \y, as long as one 
does not try to expand its replacement text. 

The definition of \newcommand comes from btxmac.tex, so perhaps 
there is a reason for bibliographies to use \edef. I have never 
used \newcommand in \eplain directly. I only encountered the error 
when a supposedly plain.tex compatible file performed a test
 \expandafter\ifx\csname newcommand\endcsname\relax
and then tried to \newcommand something instead of \def-ing it.

The questionable eplain.tex/btxmac.tex code follows. The \edef 
occurs in the first line of \< at >newcommand, but is only invoked 
in the last one:
\def\< at >newcommand#1{%
   \def\< at >startdef{\expandafter\edef\< at >commandname}%
%
% The remainder of this long definition is irr

Re: Manual eplain.pdf

Oleg Katsitadze — 2012-03-20T15:55:51

Hi Suresh,

On 3/19/12, Suresh Govindachar <sgovindachar-/E1597aS9LQAvxtiuMwx3w< at >public.gmane.org> wrote:

Eplain manual uses Texinfo (http://www.gnu.org/software/texinfo/)
which generates PDF bookmarks.  Eplain does not include any support
for them, although it's possible to add bookmarks yourself using
pdfTeX's primitives.


Here it is:

    http://tug.org/svn/eplain/trunk/doc/

HTH,
Oleg