> Actually there's nothing wrong with \input{filename}, it is I believe
> well documented and part of LaTeX, and it differs from \include in
> the fact that it does not try a \clearpage. I couldn't find a
> reference right now, but I believe that "\input filename" is actually
> a different command, and that is the "TeX" one that one might want to
> avoid, and that's the one that pdfsync definitely does not follow.
> But pdfsync will follow \input{filename}, as a simple example can show.
The difference between \input and \include is a little more than that.
For one, I can \include files that don't exist, and \include responds to
\includeonly type commands.
Also, consider the impact of \include on (for example) chapter-level
bibliographies. You're not going to get the extra AUX files with an \input.
They are simply two different things meant for two different purposes
(and they both work with pdfsync, and of COURSE you should include your
parameter in grouping braces).
--Ted
--
Ted Pavlic <[EMAIL PROTECTED]>
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Skim-app-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/skim-app-users
