@PabloGonzálezL I must have seen the mail originally and just looked at the description now but havent looked at the diff yet (had no tex time this week)
$ latex small2e
This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020) (preloaded format=latex)
restricted \write18 enabled.
entering extended mode
(/usr/local/texlive/2021/texmf-dist/tex/latex/base/small2e.tex
@JosephWright yes (just mailed tl list to check) not being done would not be surprising but I'd expect it to fail not install old binaries in that case,
@Ulrike, I have just started into pdfmanagement-testphase. Now I am looking for the documentation of the pdftex primitive interface. Where should I go?
@Ulrike My first question. In texdoc l3pdfmanagement you say that entries in Page/Resources/Properties are housekept automatically in connection with BDC marks. While this holds true for dvips (thanks to the BDC pdfmark), this is not the case for pdftex/luatex were the only interface for inserting BDC marks in the page stream is \pdfliteral, as far as I know. Or do I miss some dedicated primitive that automatically populates the Properties dict?
@UlrikeFischer So does mine. I add BDC-associated OCG dictionary refs manually to the Properties dict. And I remove them manually from it on the next page, where they are not used anymore (I don't want to see OCGs in the Layers tab in AcroRead if they don't exist on the current page.) For this a have defined \pbs_zap_properties: in pdfbase.sty.
@AlexG with labels, if you run this you can see the info in the aux, and at shipout I then use the right one. But lualatex add the marks with luacode, and there they are added simply in the stream. So I think I should open an issue ...
@JosephWright You could add an engine to TeXShop that sets PATH and then launches the compiler. I'd really like very much an interface to engines in TeXShop similar to TeXworks'.
@UlrikeFischer Reminds me I have to track down why opacity is added more than once
@egreg Well yes, manually I'm fine in TeXworks, I'd just like everything integrated (I only have TL'20 and now TL'21 native on the Mac; on the Windows VM I've got TL'09 onwards and use TeXworks to switch versions)
@UlrikeFischer Your BDCs are not associated with a dictionary object and thus no Properties dict at all. But OCGs are indirect objects and referenced at various places (Catalog) and thus need to be mapped to a /name in /Properties for use with a BDC mark in the page content stream.
@AlexG sorry? I see /Span /l3pdf1 BDC in the stream, and << /Properties <</l3pdf1 5 0 R>> in the resources, and 5 0 o is a dictionary. What do you miss here?
@PabloGonzálezL @Rmano @DavidCarlisle ctan confirmed that they somehow broke the pdf during installation, they updated it, now I need to wait if texlive picks it up ...
@Ulrike I would love to use your \pdf_bdc:nn instead of \pbs_pdfbdc:nn. But I would need to be able to pass object refs as 2nd argument, not just a dictionary. OCG dictionary objects need to be created separately as they are referenced elsewhere, in the Catalog for instance.
@AlexG there is a \pdf_bdcobject:nn {tag} {object name} command which takes an object name defined with \pdf_object_new. (currently documentated in l3pdftools)
@AlexG Well object names must really be an object created with \pdf_object_new. It relies on l3pdf and l3backend to get the right format for the reference, I mean I don't want code which works only for pdflatex and not with xetex or dvips. But couldn't you create an intermediary object for the reference number?
Anyone knows what lualatex does differently with a pdf compared to pdflatex? I usually always use pdflatex. Just wanted to try lualatex on this project (much faster, yay), but at each compilation (via latexmk) my Evince crashes. It never crashes with pdflatex. Any idea what gives?
But he wrote "As I mentioned in passing a day or two ago, this year for the first time tlnet will continue to be updated during this pretest period. That is, regular package updates sent to CTAN will normally end up in both tlnet and tlpretest."
@daleif lots of things are different. But without an example it is not possible to guess what could be wrong.
@UlrikeFischer Karl told me he can disable updates to TL2020 if needed. So a package can be frozen for TL2020 and still be updated in the TL2021 branch.
@JosephWright but regarding the xetex.def: as the new code is guarded by the xdvipdfmx version it should be imho quite safe. I'm using it since it is there and had no problems.
@JosephWright yes. Then perhaps what Paulo suggested: update only for tl21, Karl wrote that this can be done by adding a note in the upload: "If a package update should only be in the pretest, and you haven't already told me, please say so in the CTAN upload notes".
@AlexG right, I think that came up once. The question is if one needs it. For a one shot you don't need it: you could reserve the object with \pdf_object:new, then split up the number from the reference and write it with the primitive:
\ExplSyntaxOn
\pdf_object_new:nn {myname}{dict}
\edef\myref{\pdf_object_ref:n{myname}}
\show\myref %5 0 R
%some split up command to get the 5
\ExplSyntaxOff
\immediate\pdfobj useobjnum 5 { blub }
The Island of TeX proudly presents the newest and greatest version of arara, the first release in the 6 series, coming to CTAN today! Check our changelog: islandoftex.gitlab.io/arara/changelog
@daleif Hmm... I checked with a small example, so maybe it does not scale. Continuos visualization is a PITA anyway --- when compiling the circuitikz manual the result is that most of the time you have grey refreshing pages. In my experience okular manages better (a pity its antialiasing is simply horrible).
@Rmano So far I'm fine with Evince. It would be nice if one could send it a refresh signal like one could with Xpdf, then latexmk can reload it when compilation is done.
So, pdflatex complains that "Font shape OT1/cmr/m/scit' undefined (Font) using OT1/cmr/m/sc' instead on input line [...]", when I'm perfectly okay with that substitution. I thought I could shut it up by using "\DeclareFontShape{OT1}{cmr}{m}{scit}{<-> ???}{}" but I apparently do not understand how tex names fonts and have no idea what to put as "???". "cmrmsc10" doesn't work.
Any suggestions about how best to ensure obligatory components of \frontmatter are included? I'm thinking about simply adding a flag inside each one and then checking them when \mainmatter is issued. Are there more elegant ways?
Apparently I managed to sidestep the issue by figuring out how to convince it to not be in italics mode after all... I was pretty certain that I already tried that. Excuse the spam.
@AlanMunn hmm ok so your version or somthing like \def\keywordsnotused{\packageerror...} and have \let\keywordsnotused\relax in the keywords environment definition (so no need for actual \if... tests)
@AlanMunn and @DavidCarlisle -- That sounds like the right approach for an interactive session, but I gather that I may be the only person on the planet who still works interactively.
@barbarabeeton These days most students work with Overleaf, which means not only not interactive, but nonstop mode, so they get output despite dozens of errors...
@barbarabeeton But as @DavidCarlisle says, this is about package/class definitions.
@PauloCereda Yeah, that's the problem. I don't want something that make the person look like an idiot, but I'd like to distinguish true bugs from things that weren't.
@samcarter_waiting_for_summer I would have said "certainly! but you should know that includes my girlfriend and her husband, my husband and his three girlfriends and their husbands, plus any random paramours we might have at hand at the moment." :p
@samcarter_waiting_for_summer I remember I once took a quick look at Lyx in the past (before I was this involved in coding in TeX), and found it strange, even back then. But there are certainly quite active users of it...
