@DavidCarlisle ;-). oberdiek fails a lot too, as far as I could see only (but I didn't check every failure) because of \expanded. But I think the testsuites can't work in tl18 and tl19. So how (and when) do we switch to tl19?
@DavidCarlisle You addressed that one to me. Which I think you did not mean to. And the comment you linked to was "Mercurial has sequential numbering."
@DavidCarlisle I'm glad you asked. They autoclose bugs (using a bot) that are sufficiently old, with the status "RESOLVED ARCHIVED". But without actually fixing the bugs.
I wrote a message protesting this dreadful practice, but got a predictably barmy response from one of the devs. I'm not sure who he was speaking for, though.
Let's hope this doesn't catch on.
I used the word "deranged". He wasn't too happy about that.
@FaheemMitha sure yes some people do, some still use cvs, but all major code sites github/gitlab/bitbucket/sourceforge/... now steer people towards git and I don't see any real prospect of that changing any time soon, so i doubt many projects are using mercurial that were not set up a few years ago
I'm not clear why old bugs don't get closed. Is it because they are too hard to fix? I.e. intractable. Or do people just not care enough to take the time to fix them? Or are other things just higher priority?
I mean, Mercurial is adding new features, so there are people willing to work on the project.
Overall, this attitude strikes me as distressingly similar to that of say, Microsoft.
@FaheemMitha oh there are several like that, but they are unfixed for a reason. there are cases where the current spacing is clearly "wrong" and in some of the bug reports the pached code is probably "better" but if it's just a bit ugly and I change the spacing to be better but then 30 years worth of documents by millions of people start getting overprinting because they previously have \vspace{-something} to correct for the spacing inline, then it's not clear that fixing the bug is the right
@egreg yes I get that now after a cygwin update, I'm just wondering if I should flag it on tl list, but having updated I can't reproduce so It wouldn't be a very useful report, just that the new version has a dependency on a new version of one of the thousands of dlls that I just updated:-)
@FaheemMitha that is another possibility although simpler might be to wait for @JosephWright to write an l3table package so I don't need to do anything
@DavidCarlisle Suppose you are on page 1 of a document. On page 2 you want to print a header, if a boolean value secondhead is set. Is it possible to set such a boolean on page 1 with for example \afterpage{\setboolean{secondhead}{true}} so that it remains stll false on page 1, but gets true on page 2?
Still one bug left, but hopefully someone else can figure it out :)
Here is my idea: close the thebibliography environment at the start of every \bibitem to reopen it immediately. This way, LaTeX will print the bibliography head through \bibliographyhead between every bib item.
Then it should b...
The headline for bibliography with (Continued) should be repeated at the beginning of the page when starting a new bib entry (it can happen, that the last entry has to get finished first)
@Kurt so you should set a mark at the start and end of each entry, and then the page head can compare \topmark and \firstmark and if they are not the same the top of the page has an entry (given by \topmark) that started on the previous page.
@DavidCarlisle If you mean \setboolean...that can be changed, I simply do not know and could not find in the documentation of afterpage, if setting values of variables in which form ever is possible?
@Kurt \afterpage is just like \def or \newcommand it does not inspect the supplied tokens at all, absolutely anything can be placed there, but it is re-inserted and executed when tex starts making up the next page, and it may have already typeset some or all of that page, by that time.
@Kurt but using \afterpage to control page headings is somewhat weird as the page headings are the one place where you reliably know which page you are on, so controlling them from within the page by the highly invasive \afterpage macros is somewhat brave and optimistic.
@Kurt @Kurt remember of you have a very long paragraph it's all set in a line first (and so all macros and booleans and anything else are resolved at that point) then the line is broken in to paragraphs and only then page headings and after page tokens are inserted, the page heading comes in the head and the afterpage tokens are inserted by splitting the page and re-insertkng stuff inti the vertical list but in both cases a lot and perhaps all of the following page has already been typeset
@Kurt the places where \afterpagereally executes are intersting such as if you have $$ then essentially it is executed between the dollars... the first $ has no effect` but when the second $ is seen tex exercises the page breaker so \afterpage may insert itself then, but this is before display math has started or \everydisplay has been inserted., it then has to force an internal page break so grabbing all of the page-so-far into a box then it
@Kurt restarts the main vertical list with its own tokens then the unboxed box that it grabbed from the page-so-far that actually triggered the page breaker, then anything that follows that. So the behaviour of any global settings you make in \afterpage` are well defined but not always what you might want, and typically not what you expect, unless you wrote the code:-)
@DavidCarlisle okay, I see. I thought it might be more complicated than it seems to be. Because I never heard of afterpage I just want to understand better that problem. Thanks for you explanaition!
\documentclass{article}
\setlength\textwidth{5cm}
\setlength\textheight{\dimexpr\topskip+10\baselineskip}
\usepackage{afterpage}
\sloppy
\begin{document}
\afterpage{HELLO\par\aftergroup\bfseries}
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
one two three four five six seven eight nine ten
the tokens are executed where it starts to go bold, but the typeset HELLO is re-inserted at the top of the page after half of page 2 has been typeset.
@DavidCarlisle ;-). For the pdftex failures due to the Producer entries, one should add something \AtBeginDocument{\let\@pdfproducer\relax} to regression-test, then hyperref will no longer try to add its entry (@JosephWright).
@UlrikeFischer (@JosephWright) to be honest I don't know how to handle the pdf based tests, what are you supposed to do with diffs like ! <</D[38 0 R/XYZ 109.854 704.063 null]>> just look at the pdf and if it looks OK check in the new baseline tpf file?
@DavidCarlisle I don't think that it would worth the time to do something in l3build - they probably won't change the spacing with the next luatex version again. I wonder if there is an option which removes the spaces again. But I can look at this diffs and resave the tests when we switch to tl19.
@JouleV although once you start down that path there is temptation for corruption and alteration of the facts. Not that I would every do anything like that. By coincidence i just got a palindrome too:
4
@PrabhjotSingh most likely you will find it easiest to use xelatex, I will see if i can find an example...
Here is a possible solution using the Saab font. I don't know anything about the Gurmukhi script, and the Saab font doesn't seem to recognize the Gurmukhi script tag, even though it should, so there may be problems with the font. For small sections of Punjabi text, this may be sufficient. For wh...
@PrabhjotSingh yes you need to use xelatex not pdflatex
@PrabhjotSingh with xelatex (or lualatex, but xelatex probably better here) you can use any of your normal system fonts, so if you have a font that you use in a browser or word processor you can use it in xelatex. pdftex only uses the classic tex font system so any font has to be prepared specially for tex and can have at most 256 characters, and pdftex can not do any of the complicated font shaping required by at least some languages of the region.
@PrabhjotSingh show the actual error from the log, so we can see which command was undefined. (if it is \documentclass make sure you used xelatex not xetex)
This is XeTeX, Version 3.14159265-2.6-0.99998 (TeX Live 2017/Debian) (preloaded format=xetex 2019.3.2) 2 MAR 2019 22:09 entering extended mode restricted \write18 enabled. %&-line parsing enabled. **test.tex (./test.tex ! Undefined control sequence. l.1 \documentclass {article} ? ! Undefined control sequence. l.2 \usepackage {fontspec} ? ! Undefined control sequence. l.3 \setmainfont {Nirmala UI} ? ! Undefined control sequence. l.4 \begin {document} ? Missing character: There is no ਇ in font cmr10!
@PrabhjotSingh as I guessed you are using format=xetex so plain tex not latex. use xelatex not xetex, you would get the same error if you used pdftex on a pdflatex document.
@PrabhjotSingh when you do get that going you may find that you don't have Nirmala UI font as it's probbaly a windows one.
@PrabhjotSingh yes you can not use these fonts with pdftex as we said before, what I mean is that if you take a pdflatex document and try to use pdftex you will get the \documentclass undefined error.
@PrabhjotSingh but you can replace Nirmala UI by any font that you would use with firefox or open office etc (I picked that one as that was the font firefox used on windows for the text I had translated)
@PrabhjotSingh so use xelatex and all should be fine:-)
@PrabhjotSingh google suggests you should have the lohit font in Debian so save the following as test.tex and then type the command xelatex test in the terminal in that directory and you should get a pdf file showing the text (which i hope says something, I can not read the script)
@JouleV Do you have a tikz code for making the user profiles more catchy? One could use gold badges/.initially=5 and so on to make them accessible to everyone. ;-)
@DavidCarlisle How can I define such a \topmark and \botommark for bibitem? I found package titlesec having defined a \topmark, but I do not know if I can use that. Do you have a tip for me?
@JosephWright do you know if there is something equivalent to \pdfvariable majorversion and \special{pdf:majorversion 2} in pdftex ? (to get pdf 2.0 and higher)?
@JosephWright yes replace the 1. by a variable but also the logic just above that needs to be guarded so if (fixed_pdf_minor_version >= 5) becomes if (fixed_pdf_minor_version >= 5 or fixed_pdf_major_version > 1 )
@JosephWright I'm assuming there wouldn't be time to get this asked for and tested in time for tl2019
@DavidCarlisle Yes, sure. But my point is we already have 95% of the code we need in the minor version stuff. It's pretty mechanical to extend to allow major_version as 1 or 2
@DavidCarlisle Ask KB?
@DavidCarlisle It only took a day for the pTeX bug I found to be fixed ...
@DavidCarlisle We have three weeks, and they do binary rebuilds ...
@JosephWright with latex + dvipdfmx it works via \special{pdf:majorversion 2} or \special{dvipdfmx:config V 2.0}. What about dvips? How it the version set there?
@JosephWright I suppose so, this came originally from a comment made in hyperref but there it's similar, easy to add an option to set to 2 but harder to find all the places where it's testing for minorversion<5 and removing features
@JosephWright buh blaming me ;-) Not quite sure if it is really necessary for tagging (that's hard in pdftex anyway) even if some stuff exists only in the 2.0 reference, but it would make hyperref easier, if one doesn't need different version code for pdftex.
GPL Ghostscript 9.26:
It is not possible to preserve transfer functions in PDF 2.0
transfer functions will be applied instead
Drücken Sie eine beliebige Taste . . .
@UlrikeFischer gs has a page that says: PDF 2.0 deprecates the use of transfer functions, and so when producing PDF 2.0 compatible output if the TransferFunctionInfor is set to /Preserve it will be silently replaced with /Apply. You can instead specifically set TransferFunctionInfo to /Remove when producing PDF 2.0 in order to avoid the transfer function being applied.
@DavidCarlisle All of the validation is in that one procedure, so I think adding major version support just needs us to add variables/primitives, adjust there plus I guess adjust the .ini to explicitly set v1
@UlrikeFischer probably not, they are deprecated pdf level 1 thing (I think I may have known once but not at this minute) so being a new modern pdf 2 devotee you can forget they existed.
@JosephWright btw I wrote today also to the luatex list: setting there the version to 2.0 and then using objcompresslevel=1 gives the warning objcompresslevel > 0 requires minorversion > 4.
@DavidCarlisle Quite probably. And I don't assume that there is a garanty that "2.0" really gives 2.0, but the standard is there since 2017 so some steps towards it would be good. And if the header is there, I can check with preflight.
@JosephWright yes lots of tests (eg in writepng.c) with fixedpdfminorversion <= 1 it's tempting to make the internal integer fixedpdfminorversion = 10 for pdf 2.0 then all those integer tests do the right thing
Still one bug left, but hopefully someone else can figure it out :)
Here is my idea: close the thebibliography environment at the start of every \bibitem to reopen it immediately. This way, LaTeX will print the bibliography head through \bibliographyhead between every bib item.
Then it should b...
