Home > Archive > Tex > July 2006 > pdflatex vs latex : pdflatex-only error using graphicx & kerkis
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
pdflatex vs latex : pdflatex-only error using graphicx & kerkis
|
|
| george.varsamopoulos@gmail.com 2006-07-16, 7:03 pm |
| (I use MiKTeX --latest updates-- on WinXP)
Using the following LaTeX document:
\documentclass[10pt]{article}
\usepackage{graphicx}
\usepackage[T1]{fontenc}
\usepackage[iso-8859-7]{inputenc}
\usepackage[english,gr ]{babel}
\usepackage{kerkis}
\begin{document}
%\noindent
\end{document}
I get an error-free latex run, but pdflatex stops with:
Tracing the problem down, I found that the error refers to Line 4 in
kerkis.sty:
[color=darkred]
>1> \ProvidesFile{kerkis.sty}
>2> [2000/02/25 v1.5 Package `kerkis.sty']
>3> \NeedsTeXFormat{LaTeX2e}
>4> \message{ }\MessageBreak
Moreover, if i comment out the \include{graphicx} line, or if I put it
*after* kerkis, the error disappears.
My questions are:
1. Why pdflatex "chokes" on \message{ } when graphicx is loaded?
2. Why latex doesn't "choke" on that?
| |
| Robin Fairbairns 2006-07-16, 7:03 pm |
| "george.varsamopoulos@gmail.com" <george.varsamopoulos@gmail.com> writes:
>(I use MiKTeX --latest updates-- on WinXP)
>Using the following LaTeX document:
>
>\documentclass[10pt]{article}
>\usepackage{graphicx}
>\usepackage[T1]{fontenc}
>\usepackage[iso-8859-7]{inputenc}
>\usepackage[english,gr]{babel}
>\usepackage{kerkis}
>\begin{document}
>%\noindent
>\end{document}
>
>I get an error-free latex run, but pdflatex stops with:
>
>
>Tracing the problem down, I found that the error refers to Line 4 in
>kerkis.sty:
>
>
>Moreover, if i comment out the \include{graphicx} line, or if I put it
>*after* kerkis, the error disappears.
>My questions are:
>1. Why pdflatex "chokes" on \message{ } when graphicx is loaded?
>2. Why latex doesn't "choke" on that?
question 1 i can't answer; question 2 doesn't seem to me to require an
answer (it's correct behaviour, after all).
incidentally, question 1 isn't quite right: the evidence is that
\MessageBreak is the command provoking the error.
trivial tests, loading just graphicx, and then executing the
"offending" commands seems not to provoke any errors.
ditto, loading babel gr.
could you please
1. try the test without the inputenc and babel calls (three tests --
without either, without both)
2. add \listfiles before the start of your minimal failing document
(one without inputenc and babel, if it still fails then) and report
the result
it's a poser, this effect, for sure.
--
Robin Fairbairns, Cambridge
| |
|
| On 16.07.2006 20:25, george.varsamopoulos@gmail.com wrote:[color=darkred]
> I get an error-free latex run, but pdflatex stops with:
>
It's pdftex.def, which is loaded by graphicx, that defines \MessageBreak
as {^^J}; usually, it's \relax, and only defined inside messages. kerkis
uses \MessageBreak outside a message, which triggers the error. Here's a
more minimal example:
\documentclass{minimal}
\input pdftex.def
%\show\MessageBreak
\MessageBreak
\begin{document}
\end{document}
I suppose this should be called a bug in kerkis.sty, since it uses
\MessageBreak in a way not warranted by the latex kernel. However, I
also don't understand why pdftex.def wants \MessageBreak to be defined
even outside messages.
Best regards,
Robert.
| |
| Heiko Oberdiek 2006-07-16, 7:03 pm |
| RS <w.m.l@gmx.net> wrote:
> It's pdftex.def, which is loaded by graphicx, that defines \MessageBreak
> as {^^J}; usually, it's \relax, and only defined inside messages. kerkis
> uses \MessageBreak outside a message, which triggers the error. Here's a
> more minimal example:
>
> \documentclass{minimal}
> \input pdftex.def
> %\show\MessageBreak
> \MessageBreak
> \begin{document}
> \end{document}
>
> I suppose this should be called a bug in kerkis.sty, since it uses
> \MessageBreak in a way not warranted by the latex kernel. However, I
> also don't understand why pdftex.def wants \MessageBreak to be defined
> even outside messages.
Compatibility for plain-TeX.
Yours sincerely
Heiko <oberdiek@uni-freiburg.de>
| |
|
| On 16.07.2006 23:58, Heiko Oberdiek wrote:
> RS <w.m.l@gmx.net> wrote:
>
> Compatibility for plain-TeX.
I see. But maybe pdftex.def should test for
\ifx\MessageBreak\@undefined, since \@ifundefined{MessageBreak} will
always be true (with \MessageBreak being \relax outside messages).
Regards,
Robert.
| |
| george.varsamopoulos@gmail.com 2006-07-17, 8:02 am |
| Now that the problem is pinpointed, do you suggest tweaking kerkis.sty?
However, with a work-around available to it (i.e. loading the .sty
files in a certain order), I'd wait for the package author to fix it.
Regards,
--George
P.S. Back to an initial question, shouldn't latex & pdflatex, in
principle, have identical behaviour on input, at least error-wise?
RS wrote:
> I see. But maybe pdftex.def should test for
> \ifx\MessageBreak\@undefined, since \@ifundefined{MessageBreak} will
> always be true (with \MessageBreak being \relax outside messages).
>
> Regards,
> Robert.
| |
| Dan Luecking 2006-07-17, 10:01 pm |
| On 17 Jul 2006 03:34:54 -0700, "george.varsamopoulos@gmail.com"
<george.varsamopoulos@gmail.com> wrote:
>Now that the problem is pinpointed, do you suggest tweaking kerkis.sty?
>
I would suggest both kerkis.sty and pdftex.def need changing.
kerkis.sty uses \MessageBreak outside messages, which makes little
sense, and will not do what it seems the author is trying to do.
Also, the relevant messages should probably be in \PackageInfo or
\ProvidesPackage commands. I note that there seems to a \ProvidesFile,
command, but no \ProvidesPackage. Thus any package doing
\@ifpackageloaded{kerkis} would get the wrong result.
pdftex.def checks \@ifundefined{MessageBreak}, which will return true
both in plainTeX and LaTeX and so has no reason to be. Perhaps
pdftex.def should define its own message breaking command and use
that. Or let \GPT@error and \GPT@warn redefine it inside local
groups.
>However, with a work-around available to it (i.e. loading the .sty
>files in a certain order), I'd wait for the package author to fix it.
>
>Regards,
>--George
>
>P.S. Back to an initial question, shouldn't latex & pdflatex, in
>principle, have identical behaviour on input, at least error-wise?
In this case inputs are not identical: the graphicx package inputs
different driver files. Certainly errors about unrecognized graphics
extensions will have to be different.
Dan
To reply by email, change LookInSig to luecking
--
Posted via a free Usenet account from http://www.teranews.com
| |
| Heiko Oberdiek 2006-07-31, 8:03 am |
| Dan Luecking <LookInSig@uark.edu> wrote:
> pdftex.def checks \@ifundefined{MessageBreak}, which will return true
> both in plainTeX and LaTeX and so has no reason to be.
I have now changed the test to \ifx\MesageBreak\@undefined
and expect that this minimal change will cure the problem.
Yours sincerely
Heiko <oberdiek@uni-freiburg.de>
| |
| Heiko Oberdiek 2006-07-31, 8:03 am |
| "george.varsamopoulos@gmail.com" <george.varsamopoulos@gmail.com>
wrote:
> Now that the problem is pinpointed, do you suggest tweaking kerkis.sty?
Yes, please notify the author that kerkis.sty should fix its bug.
[color=darkred]
> RS wrote:
Done in 0.03s.
Yours sincerely
Heiko <oberdiek@uni-freiburg.de>
|
|
|
|
|