[OS X TeX] input versus include in Texshop

[Curtis Clifton]

Marten,

On Jan 5, 2005, at 6:15 PM, Maarten Sneep wrote:

> I'd say this is the minimal sample that should work regardless, but 
> the master.pdfsync file seems way too short to me. I'm not getting any 
> further, other than that the pdfsync package seems to miss a lot of 
> paragraphs (but it does get some within the \inputted file).
>
> I don't see anything that would mess with pdfsync in polking or pex, 
> nothing at least that goes beyond this bare sample.
>
> Is anyone aware of recent changes to LaTeXs internals (\@@par in 
> particular) that may have thown off pdfsync? Other changes in the last 
> year? I'm running TL2005 (This is pdfeTeXk, Version 
> 3.141592-1.20b-rc5-2.2 (Web2C 7.5.3) (format=pdflatex 2005.1.4)).

I posted a similar problem to the list and received no response, other 
than Will suggesting that I ask on the comp.text.tex list.  Before I 
did that, I debugged the problem with pdfsync myself and submitted a 
patch to Jerome.  That was several weeks ago and I haven't received a 
reply, though the holidays certainly may have been a factor.  Here is 
my description of the patch:

> The pdfsync package does not insert synchronization markers at 
> paragraphs for a very simple document.
>
> The bug appears to have been introduced by in version 0.6 of 
> pdfsync.sty with the change:
> %%%%  2004-01-31:
> %%%%  \@@par is patched instead of \par
> %%%%  The pdfsync anchor is now after the \@@par
>
> I made a small change to pdfsync.sty and now I'm getting the 
> synchronization marks at the start of all paragraphs as expected.  The 
> change is to replace the following line:
>         
> \global\let\PDFSYNC at par\@@par\gdef\@@par{\PDFSYNC at par\@PDFSYNC}\fi%
>
> with the lines:
>         \global\let\PDFSYNC at everypar\everypar%
>         \newtoks\everypar%
>         \everypar\expandafter{\the\PDFSYNC at everypar}%
>         \PDFSYNC at everypar{\the\everypar\@PDFSYNC}\fi%
>
> The basic code is from a comp.text.tex post by David Kastrup.  
> Essentially it works at the TeX level instead of the LaTeX level so 
> that pdfsync does not rely on LaTeX's use of \@@par for inserting 
> synchronization marks.

I think the issue is that for more complex documents \@@par comes into 
play in LaTeX and thus the current pdfsync works fine.  However, for 
simple documents \@@par isn't used.  The patch instead redefines TeX's 
\everypar.

I've been using the patched pdfsync since mid-December without any 
difficulty on a wide variety of documents, from one page letters to a 
100+ page, math-heavy thesis.  I'm no TeX-pert, so their certainly 
could be problems with my solutions, but my research and experience 
haven't revealed any.

Best,

Curt

----------------------------------
Curtis Clifton, PhD Candidate
Dept. of Computer Science, Iowa State University
http://www.cs.iastate.edu/~cclifton

--------------------- Info ---------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
           & FAQ: http://latex.yauh.de/faq/
TeX FAQ: http://www.tex.ac.uk/faq
List Post: <mailto:MacOSX-TeX at email.esm.psu.edu>