@Moriambar Ciao! All together to Answer the Unanswered party! By chance, it starts right after the end of the Champions League finals, otherwise, someone wouldn't have taken part to it :)
@Moriambar For what the event is, look here: tex.meta.stackexchange.com/questions/7165/…. For the Champions League, I know about it because I work 8 hours a day with two Juve fans!
@DavidCarlisle One thing I'm still not 100% about is whether to use XForms to cache images when using (x)dvipdfmx. The pdfTeX driver does this, and it is workable for dvipdfmx, but would mean altering all of the scaling code ...
@JosephWright we went through hoops deciding on whether to do that for pdftex (I think the underlying code wasn't that stable originally so things kept changing) It's been a while since I looked at that but I assume it can make big savings in the relatively rare case that the same image is used several times in the same document (page backgrounds and headers etc)
@DavidCarlisle Yes: I did test it (dvipdfmx) and it works as advertised: one copy of the image. What's important if you do that is that the image is 'the same' each time. For dvipdfmx that would mean altering the clipping/scaling/... to use the pdftex.def approach. Probably zero-risk but then the pay-off is low (not that many docs use repeated images ...)
@JosephWright yes I think the motivating example at the time was a corporate logo in a page head on every page, but I don't see that much in tex documents and they tend to be small anyway, so I think the feature sounds more useful than it is (and it makes the code harder to read)
@DavidCarlisle I suspect post-processing is likely to pick this up anyway
@DavidCarlisle For pdftex.def it's long-standing so best kept I
@DavidCarlisle What about bbox data? That's cached in current dvipdfmx.def (to avoid multiple calls to extractbb) as well as more-or-less by pdftex.def (as the image itself is cached).
@DavidCarlisle Perhaps I'll back-out in the L3 experiments on that basis
@DavidCarlisle What's notable is that this has zero impact on dvips or dvipdfmx or XeTeX, so suggests it's not generally vital: I guess I favour one set of functions which apply everywhere ...
I have a problem with that latest version of babel (3.10). If I compile this file:
\documentclass{article}
\usepackage[ukenglish]{babel}
\pagestyle{empty}
\begin{document}
Hello world!
\end{document}
Then I get the message
LaTeX Error: Command \setlocale already defined.
Why is that?
@JosephWright oh build.lua install doesn't unpack the new graphics:-) (hmm might be easier to just do that by hand if I want those to be installed into latex/graphics from here)
(/home/davidc/texmf/tex/latex/graphics-def/pdftex.def
! Illegal parameter number in definition of \Gread@pdftex.
<to be read again>
2
l.154 \PackageError{pdftex.def}{File `#2
' not found}%
?
@JosephWright I think graphics needs gin@log something like
+% \begin{macro}{\Gin@log}
+% \changes{v1.2a}{2017/06/01} {New macro} In the standard interface
+% this prints to the log but can be changed via keys in \textsf{graphicx}.
+% \begin{macrocode}
+\let\Gin@log\wlog
+% \end{macrocode}
+% \end{macro}
+%
Hi. Anyone with Apache experience? I would like to enable file download (e.g. rar, zip) but also disabling directory listing at the same time. I couldn't do that without enabling directory listing enabled. Any suggestion?
@cempro Oh I am afraid you poked the wrong audience here. :) We are the TeX blokes. In any case, take a look at your httpd.conf, the file is usually well commented and it might be a matter of tweaking things to your own desire. :)
@cempro this is an odd place to ask:-) but there shouldn't be any relation between directory listing and files, so log as you use the full url to the hidden zip file. Are you sure it's not blocked for other reasons (eg explicitly blocking zip is not uncommon)
I want to disable directory browsing of /galerias folder and all subdirectories
Index of /galerias/409
* Parent Directory
* i1269372986681.jpg
* i1269372986682.jpg
* i1269372988680.jpg
if I enable Indexes option under the directory tag (httpd.conf), everything works. Should I leave indexes option there and create a seperate .htconf for the subdirectory?
This is fixed with the latest API build. (No app update required.)
Non-ASCII tags are allowed on a per-site basis. When the app went to sanitize the tag for search, it checked against the API site, which doesn't have non-ASCII tags so it removed every non-ASCII character and in the first case e...
@JosephWright I started to debug a bit but I suspect I'm out of sync somewhere for example I get ! Undefined control sequence. <argument> \Grot@sin for the above, could trace that back but no point if I have the wrong files anyway:-) Does the above work for you?
@DavidCarlisle One thing that we might also do is swap .png and .pdf: I can't be the only person who things the vector format should be checked first ...
@JosephWright oh Ok you've made it install graphics.sty in graphics-def Ok for testing I guess, I just need to remove /home/davidc/texmf/tex/latex/graphics/graphics.sty as that's masking the one in /home/davidc/texmf/tex/latex/graphics-def/graphics.sty
@DavidCarlisle Yes, just for testing: remember I plan to 'throw away' the dev branch once everything is ready (and tidy up the commits, so they will say something like 'Heavily revised drivers')
@JosephWright yes I just mention it as if (as i have) you ever do a build install in required/graphics then it's a bit arbitrary which one gets used. But anyway I just deleted the duplicates for now.
@JosephWright one thing i was never sure of looking at HO's comments about some things added for plain was if I should just extend miniltx or if peopele are rellying on the exact versions there, things like % * Implementation of \providecommand is insufficient in miniltx.tex seem a bit odd if I have write access to all files...
@DavidCarlisle The ones I've found are problematic are the lack of \on@line and \MessageBreak, both of which are provided by infwarerr (so are in pdftex.def)
@DavidCarlisle In light of github.com/latex3/graphics-def/issues/4, I guess I need to add something for nat<thing> and the bb options, or perhaps we just ignore the entire 'these keys are daft' issue ...
@DavidCarlisle If we do want to disable keys, perhaps best to do it by having a generic function in graphicx, but I'm not entirely sure this is the right approach. For example, if you set page for a bitmap it's just ignored, which is to me reasonable.
@egreg Indeed
@DavidCarlisle I see \\ strikes (yet) again: it's there just to be a rep-farm for you, isn't it ;)
oh perhaps that's OK, it's just a default default so gets fixed up by the standard graphics.cfg usually
@JosephWright taking to myself but pinging you:-)
@JosephWright \on@line I could easily add to miniltx, \MessageBreak is a bit tricker safe enough to add some groups to \def\PackageError#1#2#3{\errhelp{#3}\errmessage{#1: #2}} to set newlinechar to be ^^J and \MessageBreak to use that?
@JosephWright If there is some package I can attach through a local tree I can test the drivers and tell when something explodes ... or do they need new formats?
@UlrikeFischer they don't need a new format just any input path that puts that code in front of the code on latex/graphics, latex/graphics-def and plain/graphics-pln
@UlrikeFischer then just see if anything involving colour or graphics still works;-)
@DavidCarlisle That's easy, I only need a texmf-tree with the files. (and with texlive and the new auxtree option of tlmgr it should also be easy for others to tests).
@DavidCarlisle Installing new files is not the difficult part, it is removing them when they are no longer needed -- every few weeks I find some old long forgotten file lurking in my local texmf and grinning evily.
@DavidCarlisle Btw: I didn't know that Humbug came from the english into the german.
@JosephWright perhaps although I'd be tempted to just make \messageBreak` be \space as a fallback rather than defining \PackageError in the driver files
@PauloCereda I do hope you are working to base 256
@JosephWright I don't think it would be too bad to define them as space and empty if not already defined it's only the log file and only for people using plain who update latex/graphics-def but not plain/graphics-pln and that's not going to be many people