huh… if I put a minipage and a parbox with identical parameters into a colorbox (width is something like 135mm - 2\fboxsep using the calc package), the minipage is slightly wider, how come?
@JosephWright I got upgraded to 98 and now trying to open any tab makes it spin forever, in fairness the "about" version banner does advertise "nightly is experimental and may be unstable", but had to switch to chrome this morning.
@samcarter It would be nice to relabel the Windows-key to Duck-key with a nice cover... duck-b seems better that windows-b (or whatever ;-), b seems appropriate).
Dear TeX-experts, can I ask you if there is way to debug file paths for images in LaTeX? I would like to make a slide show with tifs, I found code to convert them to pngs and using the option --shell-escape with pdflatex. If the tif-file is in the same folder, it works. If it is outside and on a different level, it does not work. Also the very long file path contains white space. Thank you
For the moment the .tif has to be in the same folder as the .tex. I am able to convert it with --shell-escape to a png. I found on texstackexchange: ``` \usepackage{epstopdf} \epstopdfDeclareGraphicsRule{.tif}{png}{.png}{convert #1 \OutputFile} \AppendGraphicsExtensions{.tif} ```
But convert 6720B2_019.tif x.png gives convert: Not a TIFF or MDI file, bad magic number 28514 (0x6f62). 6720B2_019.tif' @ error/tiff.c/TIFFErrors/599.` And I updated imagemagick via homebrew today.
I mean with the convert on its own in the terminal in the last section
The terminal command convert is from /usr/local/bin/convert
My idea was to create a overview slideshow with the images that are located in different folders than the tex file, but the paths have always white space. I don't know how to do it best. Should I create alias or symbolic links to a subfolder where the .tex file ? I could in this folder perform the conversion of the tifs to png and then linke them into the .tex file.
@DavidCarlisle Yes, it seems so, but convert gives a warning in the terminal, convert: Unknown field with tag 34682 (0x877a) encountered. TIFFReadDirectory' @ warning/tiff.c/TIFFWarnings/959.` But it does the job. x.png appears.
and so does the .png from the shell - escape latex.
@Gudrun tiff is a weird format it's basically a container for all kinds of stuff so it's not that unusual to find tiff that give warnings or don't convert. Or at least it used to be not unusual I haven't seen a tiff file for decades now:-)
@Gudrun pdflatex has no part in that at all it is just literally using the command that you specify in an internal shell just as if you typed it on the commandline
That is what the microscope software provides :-) Thank you for your explanation. Do you have maybe a good advice how to deal with the paths, please? I don't want to do this in Keynotes, because it is so click intensiv.
Re pdflatex: Yes, I understand! That is very logical. I think you also commented on this tex stackexchange issue. :-)
But shell-escape has to be used to be able to execute the code?
@Gudrun yes but avoid that on any document that you need to share with anyone, never run pdflatex --shell-escape on some random document you copied from the internet, it could do anything on your machine that you can do. Delete all your files, forward all your mail to another person, ...
@Gudrun it is of course no different to other programs you might copy, if I give you a shell script for mac or linux or a bat file for windows, they can also run arbitrary commands but then it is more obvious that you are runing a command. If you use pdflatex --shell-escape then that is exactly the same (no worse, just the same)
When my .tex is in one folder, but the images would be in a different location and not below the tex file folder's location, and the paths have space, is there a way to work with \graphicspath{}, please? For example, one part of the path-to-image is in graphicspath and the rest is in \includegraphics{/rest/path /to /image} ?
@Gudrun png is one of the worst formats to use with LaTeX regarding compile times. Use PDF for vector graphics or JPG for raster graphics. Both can be included without further conversion.
I did also not know about png. I sometimes saved images to png as I thought it is better for my TeX document. I will never do this again, but opt for jpg or pdf. Thank you.
@DavidCarlisle Because they are all in different folders distributed.
and maybe it is easier to link them into one image folder location, convert them there, and then I have to deal with only one path to all images.
talking of running code copied off the internet but something like find . -name \*.tif -exec convert \{\} \{\}.png \; (untested) will convert any tif file at any folder below the current directory
@Gudrun shrug you might find a single command to convert them all is easier to type than running multiple commands just on the ones you want, so it's a bit of compute time and disk space but...
@DavidCarlisle the other way round :) However the audio quality seems more related to the speaker having an actual microphone instead of just a laptop somewhere in the room...
@DavidCarlisle Yeap, currently I am running low on diskspace as well. Sorry. But I can convert also linked files with one command. Could be a compromise.
The part that causing the white space problem is to some extend the One Drive - Uni name. :( But nevermind. I can link all the images now happily thanks to your help in a nice beamer slide show!!!!
@samcarter: True, but when I speak, I have my headphone with microphone on :-)
So I try to think of my audience.
I have to change the location. Thank you so much for your help! I wish you a good remaining day.
@Gudrun That's nice of you! For online-only talks, things usually works well. The speaker either using a microphone or were close enough to their computer to be understandable. But now that hybrid meetings are en vogue, things are much worse :(
@UlrikeFischer and @egreg your tex.stackexchange.com/a/130142/43807 works fine for me, aligning the last page to 48, except the PDF now has 54 pages because the numbering (according to Okular) goes 1, 2, 1, 2, i, ii, 1, 2, 3, 4, …
so \the\c@page does not seem to be the right page number to use…
:60136661 hmm, might be, but the setup is:
\put(0mm,-234mm){\transparent{.898}\colorbox{AlekSIStransp}{\transparent{1}% ← indented 1 space
\begin{minipage}[t][50mm][c]{135mm - 2\fboxsep}
% ↑ not indented
% content here, indented 2 spaces
% ↓ not indented
\end{minipage}
}% ← indented 1 space again
I’m not too sure if I should add % to the end of the \begin/\end as well, I think that broke something when I did it once, but I am adding it to the end of all the other lines
back to the page numbers problem, when I use \theps@count via tex.stackexchange.com/a/150832/43807 latexmk aborts in the first run with undefined references :(
as for the minipage vs parbox problem, I changed the one where the millimetres did matter to parbox (luckily I could)
@DavidCarlisle ouch ok, so, should I append % after \end{minipage} or does that fail or does that not help and I should just not indent things?
so, directly after a \clearpage (but not inside an \AddToShipoutPictureFG* or something), it contains the page number of the previous page?
the next one can be changed by user code, which I need to avoid
(end goal is to insert enough empty pages before the last one so that the last one is a multiple of 4, for booklet printing, the last one is the back cover)
@DavidCarlisle I am pleased ;-) But patterns are not necessarly loaded only at format creation, if the user is using polyglossia they perhaps use lualatex.
% clear 1‥4 pages for the back cover \clearpage% \pagestyle{empty}% \null\clearpage% force one to be empty for inner back cover % align outer back cover to multiple of 4 % from https://tex.stackexchange.com/a/130142/43807 \makeatletter% % \the\c@page is the current page number but can be reset % cf. https://tex.stackexchange.com/a/150832/43807 % \theps@count would be an absolute page number but adding % the pagesel package breaks the build with undefined refs % https://chat.stackexchange.com/transcript/message/60142085#60142085
Hey, quick question. I'm drawing a tikz diagram and simply want an arrow from one node to another. This is all fine and good, but for some reason when addressing the starting node with Pi.north west instead of just Pi the arrow becomes a double arrow <->... Does someone happen to know why and/or how I can fix it?
Ahh, nevermind! The "trick" is to use \path instead of \draw.... :^)
