Hello all!

@egreg 1) I would like to know what program or how did you do for paste this "First first LaTeX document" image into a beamer document (taken from your course: profs.scienze.univr.it/~gregorio/corso-latex.pdf, slide 88)

@egreg 2) and I would to know how you have managed to increase and place in what appears to be a geometric arrangement (looking at the sides) the next 2 images of the same document, slides 89 and 90

Thank you so much!

@PauloCereda uwekorn.com/2019/10/19/taking-duckdb-for-a-spin.html

hi, which package should we call in order to use symbols in The Comprehensive LATEX Symbol List

tug.ctan.org/info/symbols/comprehensive/symbols-a4.pdf

@UlrikeFischer ooh

@CarLaTeX yay

@EnthusiasticEngineer The packages are indicated in the document. For example, to get a hand with an index that indicates a direction, you can use the dingbat package and the \leftpointright command as indicated on page 132 or the bbding package with the \HandRight command

Weird, \includegraphics{g2sebevrazdy.jpg} that previously worked doesn't any more. The file cannot be found according to LuaLaTeX but it is there.

@wilx As always, MWE and a log file please ...

@JosephWright ooh Microsoft Web Expression

MWE is always a problem. :) But I will try.

The MWE: gist.github.com/wilx/09b2fab982b320f0a1e4456bbf9a64a8

The log: gist.github.com/wilx/09b2fab982b320f0a1e4456bbf9a64a8

@wilx github.com/ho-tex/oberdiek/issues/73

@UlrikeFischer I see.

@manooooh I made an auxiliary file, compiled it and used \includegraphics.

Using the \let\quote@name\unquote@name workaround works.

Watching the debate in the House of Lords is boring. Commons is way more amusing.

@wilx This spaces and dots business is quite a pain. << @DavidCarlisle

@AndréC thank you ^_^

@UlrikeFischer I think I have a plan but not sure how much time I have next few days

@DavidCarlisle In view of the discussion about pdffilesize etc I'm starting to wonder how many slightly different variants there are ...

@UlrikeFischer See my check-in

@JosephWright where?

@JosephWright latex3?

@UlrikeFischer Yes

@JosephWright what happens with filenames with a space directly before the extension? e.g. space .png. Will then \includegraphics{space .png} work but \includegraphics{space } not?

@UlrikeFischer At present they act differently; @DavidCarlisle points out that this is already a similar case with the input path

@JosephWright I don't mind it much - people adding spaces there get what they deserve ;-). We should simply request that there should be no spaces at the begin, the end and around dots ...

@EnthusiasticEngineer -- The Comprehensive Symbols List was written by Scott Pakin, not @DavidCarlisle. But yes, it is an amazing and useful document.

@JosephWright I can now run checks for pdfsyntax on the command line - that's really nice ;-)

@UlrikeFischer Hope it's OK for you now ... I've tightened up a bit

@JosephWright you mean the file extension/space?

@UlrikeFischer Yes

@JosephWright looks ok imho (but I didn't run tests).

@UlrikeFischer If you, @DavidCarlisle and perhaps @egreg look over the change, I'll probably release: we are sweeping up various bugs at the present, and it's good to stay on top of those

@JosephWright I may look but I'm at Mum's until Tuesday so only sporadically online

@DavidCarlisle Ah, got it

@DavidCarlisle Got things going with the build business ...

@UlrikeFischer I have \pdfmajorversion working for the basic idea of 'this PDF': need to work on the PDF-inclusion code (C ...)

@JosephWright ;-)

@UlrikeFischer See mail to TL list

@UlrikeFischer Works here on WSL, at least in a demo file:

\documentclass{article}
\pdfmajorversion=2
\pdfminorversion=0
\pdfcompresslevel=0
\begin{document}
Hello world
\end{document}

gives

%PDF-2.0
%����
3 0 obj
<<
/Length 93
>>
stream
BT
/F8 9.9626 Tf 148.712 707.125 Td [(Hello)-333(w)27(orld)]TJ 154.421 -567.87 Td [(1)]TJ

I've not looked at how it interacts with \pdfminorversion

@JosephWright looks good. I wished I could test, but I don't have the space for WSL ;-(

@UlrikeFischer I could do with a bigger HD, I have to say ...

@JosephWright I think you have a typo in the patch code: help2 ("The pdfminorversion must be 1 or 2.")@/. I think it should be pdfmajorversion there

@PhelypeOleinik Ooops, I'll fix

@JosephWright why restrict to 1 or 2?

@DavidCarlisle I just tried with luatex and it doesn't allow 3 either.

@DavidCarlisle Seems reasonable given the speed of PDF development: we will have a lot more than a year if we need to alter

@JosephWright that's the thinking that lead to the current problem, that it was Ok to hardwire major version=1, problem is not that it will change in a year more that it may change in 10 and it will be hard to track down all the places that need changing.

@DavidCarlisle I get that: feel free to critic on the TL list ;)

@JosephWright ok:-)

@DavidCarlisle More tricky is the fact that PDF major version isn't passed at all to the C

@DavidCarlisle Grinding slowly with C ... this is going to be hard

@JosephWright are you pushing back to gh? (I could sync my checkout with your branch if you wanted an extra tester)

@DavidCarlisle Er, I can do: I'll probably be rebasing and the like

@DavidCarlisle Give me ... a minute or so

@JosephWright as I say I'm probably not going to do anything for a day or two so no rush

@DavidCarlisle OK, let me get a few more things done

@DavidCarlisle I'm learning C the hard way ...

@JosephWright if I have a branch that is just tracking you as a remote and I don't try to merge with my master branch then it should be relatively stress free to keep in sync even if you rebase force/push etc

@JosephWright tex is more fun

@DavidCarlisle Yes: what's all this static and .h file business ...

@JosephWright .h are the cpp pre-processor header files, they really are like tex:-)

$ grep pdf.*minor *.c? | wc -l
41

@DavidCarlisle github.com/josephwright/texlive-source/tree/PDF-2.0

@JosephWright ^^ ouch pdf minor version is used all over including files derived from poppler, I wonder if the upstream poppler code has already been updated...

@DavidCarlisle Perhaps ...

@JosephWright thanks

@DavidCarlisle Except you have one place to say the arguments, another to then set up the function ... it's weird

@DavidCarlisle Yes, I know!!

@DavidCarlisle I'm doing pdftex.web and files that it uses ... follow the commits ;)

@JosephWright yes I was just looking what was in texk/web2c/pdftexdir

@DavidCarlisle Ah, right

@DavidCarlisle I think I said on the TL list a while ago that this could be tricky tricky work

@DavidCarlisle Can you see where read_image() is defined? I see it used in pdftex.web but ... I don't know where it comes from!

@DavidCarlisle Ah, it's readimage ...

@JosephWright I was just looking,.. where is the name introduced? so how come that's read_image when seen from web

@DavidCarlisle writeimg.c

@DavidCarlisle I don't get it ... but it seems one can drop _

@JosephWright looking at tangle, but it's getting late

@DavidCarlisle Yup, don't worry about it

@ Single-character identifiers represent themselves, while longer ones
appear in |byte_mem|. All must be converted to uppercase,
with underlines removed. Extremely long identifiers must be chopped.

@ The original \PASCAL\ compiler was designed in the late 60s, when six-bit
character sets were common, so it did not make provision for lowercase
letters. Nowadays, of course, we need to deal with both capital and small
letters in a convenient way

7 bit ascii with both upper and lower case is so modern....

@DavidCarlisle Did you forget a link to a question in your comment about the closed "Weakness of LaTeX" question?

@DavidCarlisle I think a lot of those files are unused ... only seem to need one

It's impressive how much space a small TeX file uses with tracing turned on.

-rw-r--r-- 1 faheem faheem 434M Oct 21 03:14 bmc2.unsent_draft.log