TeX, LaTeX and Friends

@Raaja "an error" is too vage. But I fighted yesterday with image magick too. I had to install the newest ghostscript (9.27) as the older clashed with something 9.27 related elsewhere (probably in my tex system).

Raaja

9:10 AM

Yes I understand, the error is as I put in my now deleted question: imgconvert.exe: FailedToExecuteCommand `"gswin32c.exe" -q -dQUIET -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=500000000 -dAlignToPixels=0 -dGridFitTT=2 "-sDEVICE=pngalpha" -dTextAlphaBits=4 -dGraphicsAlphaBits=4 "-r300x300" "-sOutputFile=C:/Users/raganapa/AppData/Local/Temp/magick-6020G_ZdFqEvca0b%d" "-fC:/Users/raganapa/AppData/Local/Temp/magick-6020Ja_-4A-nliql" "-fC:/Users/raganapa/AppData/Local/Temp/magick-6020DIUmHx71fHlH"' (The system cannot find the file specified.

This is wacky yet extremely cool: github.com/dzhang314/YouTubeDrive

Raaja

9:25 AM

@UlrikeFischer Finally after a hard fought battle, fixed it. By setting the exact path instead of just a pointer.

@UlrikeFischer, @JosephWright : Just learned that dvipdfmx in TL19 adds the special pdf:pageresources that adds stuff to the page resources dict of the current and all following pages. Thus, it is the direct counterpart of pdftex's \pdfpageresources.

9:43 AM

@AlexG oh good. Do you know something about creating appearance stream for checkboxes? I have here a bug report where it looks as if I need sensible objects: github.com/ho-tex/hyperref/issues/94

@AlexG Hmm, have to think whether we simply require TL'19 for dvipdfmx support of page stuff

@JosephWright yes.

@UlrikeFischer Probably easiest: we are looking at new stuff, and there are limits to engine support here

@UlrikeFischer Now, how do we test for that: I guess matching engine version

@AlexG Is it documented?

9:59 AM

@JosephWright texdoc dvipdfmx, p. 22

@AlexG Excellent

@AlexG As I've just said to @UlrikeFischer, my feeling for expl3 is we use this and document that pre-TL'19 we don't support page resources in the dvipdfmx route

@JosephWright But for the current page's resources, there is the named object @resources, we can put content to via \special{pdf:put @resources ...}. This has been available since dvipdfm already.

@AlexG I don't see many users trying to use a brand new expl3 along with an old tex system so I don't see a point to add lots of alternative routes (in hyperref I still find switches to "if package older than 2010 ...").

@JosephWright looking at your spotcolor question: Imho the name of the separation color space should be different to the name of the color.

@UlrikeFischer Quite

@AlexG Yes true, but like @UlrikeFischer says we end up with code-path issues

@UlrikeFischer Could be, but Javier is not using /ColorSpace ... he does things a slightly odd way, and I'd like to know why

10:24 AM

@AlexG none of my friends have Signal... :(

@PauloCereda No problem. The most important: they avoid W'app.

@AlexG ooh

10:58 AM

@UlrikeFischer As the reporter says, the Appearnce stream is missing for the "Yes" state, but hyperref must provide one. Yet it works in AR as is....

@AlexG yes, I got this. I'm only wondering how at best to create the stream (and with which content).

@UlrikeFischer let me think about it ...

@AlexG hyperref uses in some places type1-ZapfDingbats but I'm not quite sure if this is really suitable today....

@UlrikeFischer It is a required viewer built-in font. Appearances should therefore easily to be created using this font.

11:23 AM

@AlexG yes, I know that it works, but it is today the "state of the art" default font for this sort of things? Would e.g. Acrobat itself use it to setup a checkbox?

11:59 AM

@UlrikeFischer I tried with AA XI. It uses ZapfDingbats

1:16 PM

\pdfcompresslevel=0 %
\pdfobjcompresslevel=0 %
% 'new'
\newcount\colornumber
\pdfobj reserveobjnum
\colornumber=\pdflastobj
% 'write'
\immediate\pdfobj useobjnum\colornumber
  {
    [
      /Separation /BarTone\string#20555\string#20GN /DeviceCMYK
      << /C0 [0 0 0 0] /FunctionType 2 /C1 [0.8 0.2 0.5 0.3] /Domain [0 1] /N 1 >>
    ]
  }
\expandafter\pdfpageresources\expandafter
  {\expanded{/ColorSpace << /foo \the\colornumber\space 0 R >> }}
Hello
\pdfliteral{/foo cs /foo CS 1 sc 1 SC}
Hello world

@UlrikeFischer ^^^

2:08 PM

@UlrikeFischer Use \pdfxform to create an Appearance from savebox content. Example using pdfbase commands and Fontawesome:

\documentclass{article}

\usepackage{fontawesome5}
\usepackage{pdfbase}

\ExplSyntaxOn
\let\pbsPdfXform\pbs_pdfxform:nnnnn
\let\pbsPdfLastXform\pbs_pdflastxform:
\let\pbsPdfAnnot\pbs_pdfannot:nnnn
\def\pbsAppendToFields{\pbs_appendtofields:n{\pbs_pdflastann:}}
\ExplSyntaxOff

\begin{document}
\sbox{0}{\faIcon[regular]{square}}\pbsPdfXform{0}{1}{}{}{0}\edef\OffAppearance{\pbsPdfLastXform}%
\sbox{0}{\faIcon[regular]{check-square}}\pbsPdfXform{0}{1}{}{}{0}\edef\OnAppearance{\pbsPdfLastXform}%
\makebox[1.6ex][l]{\rule{0pt}{1.6ex}\leavevmode\pbsPdfAnnot{1.6ex}{1.6ex}{0pt}{%

@AlexG thanks. And I see the first real use case for the expl3 driver code lurking here. I wonder if I will dare ;-) @JosephWright

2:39 PM

@JosephWright looks good (but I have no idea what the dictionary is actually doing ;-)).

3:03 PM

@UlrikeFischer It's the fallback CMYK version

3:25 PM

2

@DavidCarlisle ^^ look they mapped some of the emacs keybindings!

@PauloCereda must be rubbish, there is no duck in the most useful emoji.

@UlrikeFischer ooh :)

yo'

@UlrikeFischer ducks are expected to be emacs users: You get a duck by pressing all five emoji keys simultaneously.

@UlrikeFischer I have just uploaded an updated media9/pdfbase to CTAN. (Forms example didn't work with xelatex/dvipdfmx.)

3:42 PM

@AlexG what was wrong?

In the dvipdfmx special for producing the XObject, a \space was missing after dimension expressions.

Also pushed to gitlab.

4:22 PM

@UlrikeFischer So for spot colours we need an interface to control the /ColorSpace entry in \pgfpageresources, I guess.

@JosephWright I'm working on this. For the document it is already there, for page wise setting I'm just looking at the shipout code.

7:05 PM

> Project Campfire is deprecated

@PauloCereda Oopsie

TeXnician

@PauloCereda Have you seen some activities going on (at that warm and sunny place)? ;)

@TeXnician OOH AN ISLAND

TeXnician

@PauloCereda Yes, an island with marmots and other beings :)

@TeXnician I see what you did there. :) Thank you! <3

TeXnician

7:09 PM

@PauloCereda Well, unfortunately I have not had time to reply to your last email but I will soon :)

@TeXnician no worries, pal. :)

Skillmon

@PauloCereda what is project campfire? I don't know why, but since it is deprecated I'm sad. I like camp fires.

@Skillmon It's the native Windows boot on Macs, IIRC. @JosephWright am I correct?

@Skillmon <3

Skillmon

@PauloCereda since it's about Windows, I suddenly lost interest :)

@Skillmon I can relate :)

Alan Munn

7:51 PM

@PauloCereda @Skillmon No it was to allow Chromebooks to boot to Windows. Nothing to do with Macs I don't think.

Faheem Mitha

9:57 PM

Hi folks. I'm running Debian testing/Buster. Which will eventually (soon) be Debian 10.

But the TeX Live version here is apparently a prerelease.

root@orwell:/home/faheem# apt-cache policy texlive-binaries
texlive-binaries:
  Installed: 2018.20181218.49446-1
  Candidate: 2018.20181218.49446-1
  Version table:
     2019.20190507.51032-1 1
          1 deb.debian.org/debian experimental/main amd64 Packages
     2018.20181218.49446-2 50
         50 deb.debian.org/debian unstable/main amd64 Packages
 *** 2018.20181218.49446-1 500
        500 deb.debian.org/debian buster/main amd64 Packages
        100 /var/lib/dpkg/status

So, is it worth upgrading to the version in experimental to get the "proper" TeX Live 2019 release?