@DavidCarlisle Good Morning. In my home I do not have internet and I'm in the car when I connect through hotspots. If you notice I always connect at the same time in the evening when I can. When I write in the morning I'm in school.
@egreg, @Werner, @ChristianHupfer, @Bernard, @JosephWright @Mico and everybody Good morning and good work.
@TeXnician not at all. I deem it nearly impossible: I don't know what else I could do. Also it's a change that will require a lot of time. At least a couple of years
@DavidCarlisle but then they would blame me if hyperref is broken ;-). (I think I'm right, but it would be good if you check a bit my reasoning. All this string conversion is a bit confusing and I don't know exactly why xetex uses ascii-print and not pdfdoc in this place.)
@DavidCarlisle @JosephWright As you are just looking at the xetex driver anyway: is there a better ("more official") method for this tex.stackexchange.com/a/368848/2388
@UlrikeFischer probably more in the spirit of the original code would be to have a declared svg type instead of making .svg use the QTm type and then checking the extension later, the svg type could be the same as QTm except load the pdf where needed. But not tried coding anything:-)
@DavidCarlisle but this would assume that .svg should always use pdf as a fallback. But it could also be png or eps or .... Imho the setup in the question is rather local (e.g. the requirement that the .svg extension can't be removed).
@DavidCarlisle the "cast of thousands" yesterday reminded me to check the issue list but you can always ask if you see something that could be in my line.
@DavidCarlisle As we are doing a bit of driver work: I notice in my L3 notes that the XeTeX driver currently uses dvips-like colour specials, whereas dvipdfmx uses 'native' ones. Would you mind if I looked at pulling that into line?
@DavidCarlisle I see there is a comment about the older XeTeX back-end drivers and colour, but everyone is now using xdvipdfmx so that's not really relevant
@UlrikeFischer possibly. I only skimmed over the question. I'll look later (or you could add an issue at graphics-def github so it doesn't get lost)
@JosephWright feel free actually I have on my list of things to do one day to work out why xetex.def exists at all and isn't just (x)dvipdfm(x).def (or a copy of that for historical reasons)
@DavidCarlisle Thus-far, for the L3 version the only thing I know is different is that colour business (which doesn't actually need to be): graphics inclusion is the obvious place to look
@DavidCarlisle Well yes, and sort-of what I'm doing in the L3 file
@DavidCarlisle What's not clear is to what extend the image inclusion has to be different: I might try forcing the driver and seeing what happens :)
@DavidCarlisle Quick test: copied dvipdfmx.def to xdvipdfmx.def in a test location and removed the last part (about \mag and paper size). With the example below all is then well:
Not exactly, I did some background reading on what to choose and I decided against LyX, which should be the easiest option but causes some problems. I just downloaded TeXStudio.
I understand that there is separation of content from formatting.
@inquirius I would start with a basic document with the "book" or "article" class and without any titlepages per se. Unfortunately I don't have any suggestions for tutorials or similar things (in english) so I think it's best you familiarize with the basic way of doing things in LaTeX that way. The titlepage can always be done later.
I opened the article template in TeXStudio and I wrote some lorem impsum, it seems that it builds without problem so everything is installed correctly. Unsure how to customize the template though.
Thanks. There are some tricky parts e.g. I wanted to add a subtitle but that wasn't displayed correctly. Then I found that I have to change the class from article to scrartcl.
@inquirius Don't get me wrong, but that's not the best way to start using LaTeX. :) You are delving into deeper waters, it would be better to start with smaller chunks of code. Take a look at the link I posted. If you start from your final document, you will have a terrible experience, from end to end.
Got it. I'll just focus on writing the content in a thesis template and forget about the rest at the moment. If anything I'll learn how to write equations and do tables for now.
I suppose I wrote that papersize stuff at the end of xetex and dvipdfx.def but why `\@ifundefined{stockwidth}{%` in one and `\AtBeginDvi{% \begingroup \ifx\stockwidth\@undefined` in the other, i suppose I should check the mail from that time (not really looking now:-)
@DavidCarlisle Image size is detected differently in the two but to be honest I don't see a benefit of the primitive over the pipe shell escape here in most cases. One could do that conditionally ...
@DavidCarlisle @JosephWright That's what I wondered too. There are number of differences in the file types. Some of them I have never heard of. E.g. beside tiff and gif what about this pict, tga, jpf and mac type?
@DavidCarlisle I found a reference to some "macpaint" format: filext.com/file-extension/MAC, but I have no idea if it still exists (and if it works in a current xetex).
@JosephWright Apart from naming difference (JPEG/jpg, eps/ps) I think one should check bmp, gif and tiff. This are the graphics format not in pdflatex but in xetex.def where I occasionally see questions about. (I'm not saying that one should support them, but the decision to drop them should be concious and documentated.).
@JosephWright although as a matter of (original) policy the latex .def files should support any formats that are supported by the driver. (but I don't know if those old mac formats really are supported if you use xetex on a different platform)
@UlrikeFischer I guess if I were starting from scratch (so for expl3) a smaller more consistent set would be nice. However, we are not so what is important is whether there are technical reasons for needing entirely separate drivers.
@JosephWright There is the question if other packages load the drivers and if a name change can confuse something -- and how you want to name the combined driver-file.
@JosephWright I suspect even I could do it:-) not sure whether the l3build way would be to use the lfs stuff like xcopy/cp or simply pull in the files as lua strings and output them again, the latter probably?
@JosephWright in fact any difference can only be due to image size determination I guess since the actual inclusion has to be done by the driver in the end anyway.
@JosephWright yes I know there are other differences currently but they must be spurious surely, in the end all xetex can do is add \special that xdvipdfmx understands. ooh or is \XeTeXpdffile a custom whatsit in the dvi/xdv not a special
@JosephWright Yes. But identifying the xdv2pdf bits is perhaps not so easy. From the log-files it looks as the xdvipdfmx were added around 2006, so one would need quite old files.
@UlrikeFischer The point really is that the driver code in dvipdfmx.def seems to work unmodified, with only the coverage of some file types and the higher efficiency meaning that \XeTeXpicfile has a use. Beyond that it seems one can just use the same driver set up.
@UlrikeFischer xdv2pdf is mentioned in a comment about the colour specials:
%% 2006/07/19 [JK] Version v0.91 use \special{color ...} rather than
%% \special{x:textcolor ...} etc, for compatibility with
%% both xdv2pdf and xdvipdfmx drivers;
%% added .bmp to list of recognized graphics extensions
which is where I started with this (different colour specials from dvipdfmx mean there is some code in expl3 to adjust the 'native' set up)
@JosephWright hmm but I suspect it's the \def\c@lor@to@ps stuff in xetex.def that keeps pstricks happy, as that command not being defined is the usual sign of pstricks being used in the wrong context
@JosephWright oh it's in dvipdfm not xetex (buffers wrong way round) so the above isn't right as stated but possibly not completely wrong
Anyone knows how to get the same font weight in standalone figures and beamer (I'm using the hsrm template)? Setting my axis labels to bold is too thick, normal is too thin, and I don't see where this is adjusted in the beamer template.
@JosephWright did you notice the URL to the luaotfload github issue posted to texlive list ("(linebreak): invalid list tail, probably missing glue") some bounty wrapper trying to monetise other people's github issues?
@DavidCarlisle Intrigued by the issue, I've done a quick \tracingall. Not sure quite who is at fault: PStricks is using an internal from xcolor, and it's there that the internal from the driver is used.
@JosephWright I did some work making pstricks sit over the new 2e color/graphics before it was released, just as a proof of concept that it wasn't going to break everything
@PauloCereda I was coming home from work and I noticed a car that was going pretty slow. The woman driving was talking on the cell (obviously cell in hand) and smoking at the same time. Good thing that the motorway was straight. I then thought about draining batteries in cars too!
%% Any modified versions of this file must be renamed
%% with new filenames distinct from xcolor.sty.
but
%
% This file may be distributed and/or modified under the
% conditions of the LaTeX Project Public License, either version 1.2
% of this license or (at your option) any later version.
% The latest version of this license is in:
%
% latex-project.org/lppl.txt
%
% and version 1.2 or later is part of all distributions of LaTeX
% version 1999/12/01 or later.
@JosephWright yes just seemed a bit odd, it's not totally obvious that it's a github issue rather than posted to that site (although I didn't look that hard)
@CarLaTeX do you know by any chance any good electronics (diy&co.) store in Milan? I want to buy a photon board but it costs more in shipping than in "board" :)
@DavidCarlisle Thanks you, I managed to identify the cause of my problem using pdffonts and discovered the difference between Computer Modern Bright and Computer Modern Sans Serif.
/** XDV extension: Same as cmdXGlyphArray plus a leading array of UTF-16 characters
* that specify the "actual text" represented by the glyphs to be printed. It usually
* contains the text with special characters (like ligatures) expanded so that it
* can be used for text search, plain text copy & paste etc. This XDV command was
* introduced with XeTeX 0.99995 and can be triggered by <tt>\\XeTeXgenerateactualtext1</tt>.
* parameters: l[2] t[2l] w[4] n[2] xy[8n] g[2n] */
@ShreevatsaR thanks dvisvgm source has quite reasonable comments!
@DanielSank well you have removed all flexibility so you don't give tex many choices. (there are also lots of % missing although that unlikely to affect the vertical space.
I see that the code in many packages and examples contains percent signs % at the end of (many) lines. What are they used for? Do they affect the parsing of those lines?
I am unfortunately unsure of how "standard" to regard LaTeX packages. I'm uncalibrated as to whether asking questions which use packages without having read the package source is generally considered lazy.
@DanielSank import really??? anyway impossible to guess, make a proper complete example and ask as a question on th emain side, discussing code in chat doesn't really work well
@DanielSank the begin{enumerate} starts a new paragraph so the \\ is at the end of a paragraph which just forces an underfull hbox badness 10000 message I would guess
@DanielSank never use \\ at the end of a paragraph it is always wrong always gives an underfull hbox badness 10000 warning and bad output (the negative space in your fragment is trying to correct for that but for example will go very wrong at a page break)
@Moriambar yes they adapt, but not like tabularx, ty columns adjust to their content, roughly speaking columns with more data get wider. tx columns are not affected by the cell contents
99 times out of 100 it means you have \\ incorrectly placed at the end of a paragraph. But to dissect the message:
Underfull \hbox (badness 10000) in paragraph at lines 4--5
A box is underfull if there is not enough content to fill its stated size.
If you go \hbox to 5cm{A} then it makes...
The patch in the other answer probably ought to have worked but it turns out the division algorithm used isn't really that accurate in the case that it is scaling up, and as Stephen noticed if you simply let it scale, rounding errors make the table wider than the line and you get overfull box war...
@Moriambar artifically spreading out tables is a sin worse than vertical lines:-) the original motivation for TY was an automated typesetting pipeline where they wanted no human intervention if possible and the code should just do something sensible so small enough tables are set natural width, but large ones had some line breaking decisions made automatically
@DavidCarlisle well, ok, it was just to answer a question anyway ;) ps: the code in the answer you linked gave Arithmetic overflow. But again: thanks for explaining. I'm fine with that
@GustavoMezzetti upvote sure but downvote with no comment is just odd, if the intention is to encourage someone to correct the answer giving a hint what's wrong makes more sense surely?
@CarLaTeX It was mentioned in the answer: a plain TeX set of macros for doing quires. Nowadays there are much better methods, but that was nice because it was implemented in TeX.
I see that the code in many packages and examples contains percent signs % at the end of (many) lines. What are they used for? Do they affect the parsing of those lines?
How can I get a square root looking like these in LaTeX? Thanks!
[new picture]
Is there any package or a method to force LaTeX to keep floating environments like table and figure closer to where they are declared?
