Re: [XeTeX] Using tikz with plain XeTeX
Dear Joseph That's excellent - many thanks for saving me from several hours of picking through an extremely long preamble. I doubt if I would have got to the offending line in ulem.sty any time soon, if at all. Best wishes John -Original Message- From: Joseph Wright Sent: Saturday, May 13, 2017 12:59 PM To: xetex@tug.org Subject: Re: [XeTeX] Using tikz with plain XeTeX On 13/05/2017 12:49, Philip Taylor wrote: John Was wrote: Even if PS-Tricks and Tikz do clash, it doesn't seem to be PS-Tricks specifically that's causing this issue (I've tried commenting it out) - suspicion currently falls on Edmac, which I use for cropmarks and sometimes for other purposes (e.g. automatic line numbering of texts when required). I don't really mind doing without tikz (at least for now), but it would be good to know the cause of the weird behaviour! Then I think you will have to strip down your fault-provoking code to something manageable, John; "necessary and sufficient" is the key -- you have provided the necessary, now it is surely incumbent on you to strip it down to the necessary if others are to be able to help you in finite time. Philip Taylor A minimal example is \input ulem.sty \input tikz \tikzpicture \path[draw=red] (0,0) -- (1,1) -- (2,1) circle (10pt); \endtikzpicture \bye with the first piece of text pointing to ifpdf: the issue is not limited to TikZ. (It doesn't help though that TikZ's emulation of a minimal LaTeX set up isn't 'self-contained': the load order cannot be reversed here.) This allows us to isolate the issue: ulem.sty does \expandafter\ifx\csname ProvidesPackage\endcsname \relax which leaves \ProvidesPackage as \relax in plain (there is no grouping). That's an issue for any code that tests 'quickly' for \ProvidesPackage, for example in ifpdf.sty \ifx\ProvidesPackage\undefined The most obvious solution is to get rid of the problematic definition: \input ulem.sty \let\ProvidesPackage\undefined \input tikz \tikzpicture \path[draw=red] (0,0) -- (1,1) -- (2,1) circle (10pt); \endtikzpicture \bye Joseph -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Using tikz with plain XeTeX
On 13/05/2017 12:49, Philip Taylor wrote: > > > John Was wrote: >> Even if PS-Tricks and Tikz do clash, it doesn't seem to be PS-Tricks >> specifically that's causing this issue (I've tried commenting it out) - >> suspicion currently falls on Edmac, which I use for cropmarks and sometimes >> for other purposes (e.g. automatic line numbering of texts when required). I >> don't really mind doing without tikz (at least for now), but it would be >> good to know the cause of the weird behaviour! > Then I think you will have to strip down your fault-provoking code to > something manageable, John; "necessary and sufficient" is the key -- you have > provided the necessary, now it is surely incumbent on you to strip it down to > the necessary if others are to be able to help you in finite time. > > Philip Taylor A minimal example is \input ulem.sty \input tikz \tikzpicture \path[draw=red] (0,0) -- (1,1) -- (2,1) circle (10pt); \endtikzpicture \bye with the first piece of text pointing to ifpdf: the issue is not limited to TikZ. (It doesn't help though that TikZ's emulation of a minimal LaTeX set up isn't 'self-contained': the load order cannot be reversed here.) This allows us to isolate the issue: ulem.sty does \expandafter\ifx\csname ProvidesPackage\endcsname \relax which leaves \ProvidesPackage as \relax in plain (there is no grouping). That's an issue for any code that tests 'quickly' for \ProvidesPackage, for example in ifpdf.sty \ifx\ProvidesPackage\undefined The most obvious solution is to get rid of the problematic definition: \input ulem.sty \let\ProvidesPackage\undefined \input tikz \tikzpicture \path[draw=red] (0,0) -- (1,1) -- (2,1) circle (10pt); \endtikzpicture \bye Joseph -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Using tikz with plain XeTeX
Hello Well, I did what was requested (the full code - an awful lot of which is just \def this, \def that, etc., accumulated over the past few decades from pre-XeTeX days). I'll try to find time for this - but I've never encountered a package that would do such a thing, and kill off my running headlines (as well as adjusting the offset positions) while it was at it! John -Original Message- From: Philip Taylor Sent: Saturday, May 13, 2017 12:49 PM To: XeTeX (Unicode-based TeX) discussion. Subject: Re: [XeTeX] Using tikz with plain XeTeX John Was wrote: Even if PS-Tricks and Tikz do clash, it doesn't seem to be PS-Tricks specifically that's causing this issue (I've tried commenting it out) - suspicion currently falls on Edmac, which I use for cropmarks and sometimes for other purposes (e.g. automatic line numbering of texts when required). I don't really mind doing without tikz (at least for now), but it would be good to know the cause of the weird behaviour! Then I think you will have to strip down your fault-provoking code to something manageable, John; "necessary and sufficient" is the key -- you have provided the necessary, now it is surely incumbent on you to strip it down to the necessary if others are to be able to help you in finite time. Philip Taylor -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Using tikz with plain XeTeX
John Was wrote: > Even if PS-Tricks and Tikz do clash, it doesn't seem to be PS-Tricks > specifically that's causing this issue (I've tried commenting it out) - > suspicion currently falls on Edmac, which I use for cropmarks and sometimes > for other purposes (e.g. automatic line numbering of texts when required). I > don't really mind doing without tikz (at least for now), but it would be good > to know the cause of the weird behaviour! Then I think you will have to strip down your fault-provoking code to something manageable, John; "necessary and sufficient" is the key -- you have provided the necessary, now it is surely incumbent on you to strip it down to the necessary if others are to be able to help you in finite time. Philip Taylor -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Using tikz with plain XeTeX
Hello Even if PS-Tricks and Tikz do clash, it doesn't seem to be PS-Tricks specifically that's causing this issue (I've tried commenting it out) - suspicion currently falls on Edmac, which I use for cropmarks and sometimes for other purposes (e.g. automatic line numbering of texts when required). I don't really mind doing without tikz (at least for now), but it would be good to know the cause of the weird behaviour! John -Original Message- From: Philip Taylor Sent: Saturday, May 13, 2017 12:29 PM To: Wilfred van Rooijen ; XeTeX (Unicode-based TeX) discussion. Subject: Re: [XeTeX] Using tikz with plain XeTeX Wilfred van Rooijen wrote: As far as I know, tikz and pstricks should not be used simultaneous in a document. That may well be the case (I am not personally aware of this, but then I have never wanted to use pstricks) but if so, should not tikz and pstricks test for each other's presence and report a clash if detected ? Philip Taylor -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Using tikz with plain XeTeX
A simple one-page file is fine: \input tikz \tikzpicture \path[draw=red] (0,0) -- (1,1) -- (2,1) circle (10pt); \endtikzpicture \bye The problem is evidently with something in the preamble to the articles (it's a periodical that comes out twice a year). Rather a gigantic run of code but since it's been requested, here goes: \hsize=24pc%288pt \vsize=40pc%480pt \input soul.sty \sodef\spaced{}{.1em}{0.333em plus 0.333em}{0.333em plus 0.333em} \sodef\spacedfixed{}{.1em}{0.333em}{0.333em} \sodef\capitalsspacedfixed{}{.1em}{0.5em}{0.5em} %%ULEM package alternative to SOUL (copes with Unicode, e.g. Greek) %%REPLACES JW's \uline and \ulinespace DEFINITIONS [commented out below] %%SEE MHRA ANIPA FOR TWEAKS IF NEEDED \def\makeatletter{\catcode`@ = 11} \def\makeatother{\catcode`@ = 12} \input ulem.sty %\ULdepth=0.225em %VC WANTS DEEPER (OS2017A): \ULdepth=0.325em \def\ULthickness{.25pt} \input pstricks \input pst-node \input pst-tree \input edmac \newif\ifquote \newdimen\noteadjustamount \noteadjustamount=0pt \newdimen\notekernamount \notekernamount=0pt%KERN ON 2nd OF SHORT CENTRED NOTES \newdimen\versindent \versindent=0pt \newdimen\tempwidth \tempwidth = 0pt \newdimen\scratchwidth \scratchwidth = 0pt \newdimen\firstarthitchup \firstarthitchup=0pt \newtoks\zerotext%Puts zero in front of single-digit \mins in headnote time \newcount\hours \hours=\time \newcount\mins \mins=\time \divide\hours by 60 \newcount\timereckon \timereckon=\hours \multiply \timereckon by 60 \advance\mins by -\timereckon \ifnum\mins<10\zerotext={0}\fi \newtoks\monthtext \newcount\monthnumber \let\monthnumber=\month \ifnum\monthnumber=1\monthtext={January}\fi \ifnum\monthnumber=2\monthtext={February}\fi \ifnum\monthnumber=3\monthtext={March}\fi \ifnum\monthnumber=4\monthtext={April}\fi \ifnum\monthnumber=5\monthtext={May}\fi \ifnum\monthnumber=6\monthtext={June}\fi \ifnum\monthnumber=7\monthtext={July}\fi \ifnum\monthnumber=8\monthtext={August}\fi \ifnum\monthnumber=9\monthtext={September}\fi \ifnum\monthnumber=10\monthtext={October}\fi \ifnum\monthnumber=11\monthtext={November}\fi \ifnum\monthnumber=12\monthtext={December}\fi \widowpenalty=1 \dimen\footins=.95\vsize % maximum footnotes per page \font\uimrfive = "ImprintMTPro-Regular:+onum:mapping=tex-text:letterspace=-0.2" at 5pt \font\uimifive = "FFImprintItalic:+onum:mapping=tex-text:letterspace=-0.2" at 5pt \font\uimprfive = "ImprintMTPro-Regular:+lnum:+smcp:mapping=tex-text:letterspace=-0.2" at 5pt \font\uimpifive = "ImprintMTPro-Regular:+lnum:+smcp:slant=0.3:mapping=tex-text:letterspace=-0.2" at 5pt \font\uimbfive = "ImprintMTPro-Bold:+onum:mapping=tex-text:letterspace=-0.2" at 5pt \font\uimbifive = "ImprintMTPro-BoldItalic:+onum:mapping=tex-text:letterspace=-0.2" at 5pt \font\uimpbfive = "ImprintMTPro-Regular:+lnum:+smcp:embolden=4:mapping=tex-text:letterspace=-0.2" at 5pt \font\uimpbifive = "ImprintMTPro-Regular:+lnum:+smcp:embolden=4:slant=0.3:mapping=tex-text:letterspace=-0.2" at 5pt \font\uimrseven = "ImprintMTPro-Regular:+onum:mapping=tex-text:letterspace=-0.2" at 7pt \font\uimiseven = "FFImprintItalic:+onum:mapping=tex-text:letterspace=-0.2" at 7pt \font\uimprseven = "ImprintMTPro-Regular:+lnum:+smcp:mapping=tex-text:letterspace=-0.2" at 7pt \font\uimpiseven = "ImprintMTPro-Regular:+lnum:+smcp:slant=0.3:mapping=tex-text:letterspace=-0.2" at 7pt \font\uimbseven = "ImprintMTPro-Bold:+onum:mapping=tex-text:letterspace=-0.2" at 7pt \font\uimbiseven = "ImprintMTPro-BoldItalic:+onum:mapping=tex-text:letterspace=-0.2" at 7pt \font\uimpbseven = "ImprintMTPro-Regular:+lnum:+smcp:embolden=4:mapping=tex-text:letterspace=-0.2" at 7pt \font\uimpbiseven = "ImprintMTPro-Regular:+lnum:+smcp:embolden=4:slant=0.3:mapping=tex-text:letterspace=-0.2" at 7pt \font\uimreight = "ImprintMTPro-Regular:+onum:mapping=tex-text:letterspace=-0.2" at 8pt \font\uimieight = "FFImprintItalic:+onum:mapping=tex-text:letterspace=-0.2" at 8pt \font\uimpreight = "ImprintMTPro-Regular:+lnum:+smcp:mapping=tex-text:letterspace=-0.2" at 8pt \font\uimpieight = "ImprintMTPro-Regular:+lnum:+smcp:slant=0.3:mapping=tex-text:letterspace=-0.2" at 8pt \font\uimbeight = "ImprintMTPro-Bold:+onum:mapping=tex-text:letterspace=-0.2" at 8pt \font\uimbieight = "ImprintMTPro-BoldItalic:+onum:mapping=tex-text:letterspace=-0.2" at 8pt \font\uimpbeight = "ImprintMTPro-Regular:+lnum:+smcp:embolden=4:mapping=tex-text:letterspace=-0.2" at 8pt \font\uimpbieight = "ImprintMTPro-Regular:+lnum:+smcp:embolden=4:slant=0.3:mapping=tex-text:letterspace=-0.2" at 8pt \font\uimrnine = "ImprintMTPro-Regular:+onum:mapping=tex-text:letterspace=-0.2" at 9pt \font\uiminine = "FFImprintItalic:+onum:mapping=tex-text:letterspace=-0.2" at 9pt \font\uimprnine = "ImprintMTPro-Regular:+lnum:+smcp:mapping=tex-text:letterspace=-0.2" at 9pt \font\uimpinine =
Re: [XeTeX] Using tikz with plain XeTeX
As far as I know, tikz and pstricks should not be used simultaneous in a document. Wilfred On Saturday, May 13, 2017 8:08 PM, Philip Taylorwrote: John Was wrote: > I get six lines of info in the output (the sort of thing I’d expect in the > log) Can you please post the /full/ code that results in this ? Philip Taylor -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Using tikz with plain XeTeX
On 13/05/2017 11:53, John Was wrote: > Dear All > > Apologies if this is the wrong list (but I’ve always found participants here > very helpful!). > > I have been sent some tikz code for diagrams to be included in a forthcoming > article. The author uses a version of LaTeX but tikz should work OK in plain > (Xe)TeX, I think – though I haven’t tried it for a number of years. Oddly > enough, when I invoke tikz with: > > \input tikz > > the package does load, and a simple drawing works: > > \tikzpicture > \path[draw=red] (0,0) -- (1,1) -- (2,1) circle (10pt); > \endtikzpicture > > (pasted from a stackexchange discussion of a different matter). > > BUT, before the drawing I get six lines of info in the output (the sort of > thing I’d expect in the log), viz.: > > pgfrcs[2010/10/25 v2.10 (rcs-revision 1.24)] > pgf[2008/01/15 (rcs-revision 1.10)] > pgfsys[2010/06/30 v2.10 (rcs-revision 1.37)] > pgfcore[2010/04/11 v2.10 (rcs-revision 1.7)] > pgffor[2010/03/23 v2.10 (rcs-revision 1.18)] > tikz[2010/10/13 v2.10 (rcs-revision 1.76)] > > It also messes up my crop marks and running headlines in subsequent pages, > but I suspect that could be rectified by invoking other \inputs in a > different order (I include edmac and pstricks at the start). I can manage > without tikz if necessary (the worst-case scenario would be redrawing with > pstricks), but it would be good to know at least that I can use tikz in > future without these unwanted half-dozen lines coming into the output. It’s > a powerful package that I’ve always meant to learn. > > Best > > > John TikZ is certainly loadable with plain. Could you give more details of your TeX system or perhaps a log for the simple file \input tikz \tikzpicture \path[draw=red] (0,0) -- (1,1) -- (2,1) circle (10pt); \endtikzpicture \bye I get the 'expected' output with both TL'16 final and TL'17 pretesting. Joseph -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
Re: [XeTeX] Using tikz with plain XeTeX
John Was wrote: > I get six lines of info in the output (the sort of thing I’d expect in the > log) Can you please post the /full/ code that results in this ? Philip Taylor -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
[XeTeX] Using tikz with plain XeTeX
Dear All Apologies if this is the wrong list (but I’ve always found participants here very helpful!). I have been sent some tikz code for diagrams to be included in a forthcoming article. The author uses a version of LaTeX but tikz should work OK in plain (Xe)TeX, I think – though I haven’t tried it for a number of years. Oddly enough, when I invoke tikz with: \input tikz the package does load, and a simple drawing works: \tikzpicture \path[draw=red] (0,0) -- (1,1) -- (2,1) circle (10pt); \endtikzpicture (pasted from a stackexchange discussion of a different matter). BUT, before the drawing I get six lines of info in the output (the sort of thing I’d expect in the log), viz.: pgfrcs[2010/10/25 v2.10 (rcs-revision 1.24)] pgf[2008/01/15 (rcs-revision 1.10)] pgfsys[2010/06/30 v2.10 (rcs-revision 1.37)] pgfcore[2010/04/11 v2.10 (rcs-revision 1.7)] pgffor[2010/03/23 v2.10 (rcs-revision 1.18)] tikz[2010/10/13 v2.10 (rcs-revision 1.76)] It also messes up my crop marks and running headlines in subsequent pages, but I suspect that could be rectified by invoking other \inputs in a different order (I include edmac and pstricks at the start). I can manage without tikz if necessary (the worst-case scenario would be redrawing with pstricks), but it would be good to know at least that I can use tikz in future without these unwanted half-dozen lines coming into the output. It’s a powerful package that I’ve always meant to learn. Best John -- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex