@nbro if it has text in it, it's usually best to avoid bitmap image formats (but if you are scaling the image down, then resolution _increases so why is it "poor"
@nbro latex really doesn't care, it just needs to know the size, but if you choose to input svg and output pdf, then something has to convert svg to pdf, it does not happen by magic.
@Skillmonlikestopanswers.xyz er yes but PDF or EPS would keep it as text which is better still
@nbro latex accepts any form understood the system you are using, pdflatex understands svg if you use inclusesvg, if you are using dvisvg then it inputs svg
@nbro that isn't how software works. saying something should happen isn't the same as making it happen, and why should it happen, why svg, not tiff or giff or windows metafile (all of which some latex systems support and some do not) you happen to want svg today but that doesn't mean that the latex executable should incorporate an SVG rendering system that compiles on every platform that supports tex.
@nbro you are blurring them by generating bitmaps, latex is not involved. Do you have to make SVG, can't you save to PDF from the original application?
btw, is it possible to disable the sound notification when someone tags me here? I get a loud irritable sound when someone tags me cuz usually I am listening to music
@DavidCarlisle Yes, I think so. I think I can save to pdf directly
@nbro matplotlib supports saving to PDF, even while using LaTeX to render your labels. And if you use the correct preamble-settings in matplotlib your figures will look just as if they were created only for your document.
@nbro I think I have an answer somewhere about the way I use it, let me dig.
@nbro well generate pdf then, as if you generate svg you just need to convert it in to pdf later if you want it to be in a PDF document. Again that is nothing to do with latex, just a fact of life SVG can't be inlined into a PDF you need to convert it to PDF to include it.
% \begin{macro}{\frame}
%
% The following definition of |\frame| was written by Pavel Curtis
% (Extra space removed 14 Jan 88)
% RmS 92/08/24: Replaced occurrence of |\@halfwidth| by |\@wholewidth|
% \begin{macrocode}
\DeclareRobustCommand\frame[1]{%
\leavevmode
\hbox{%
\hskip-\@wholewidth
\vbox{%
\vskip-\@wholewidth
\hrule \@height\@wholewidth
\hbox{%
\vrule\@width\@wholewidth
#1%
\vrule\@width\@wholewidth}%
\hrule\@height\@wholewidth
@DavidCarlisle Framing is one thing I've heavily changed revised; that would have to be agreed on (basically, I think \fboxrule should not overlap with text)
@DavidCarlisle I did a version using coffins, but there are two issues: the sinner pos argument, and the fact that \vcenter aligns to math axis not current reference point
@DavidCarlisle Yes: see the comments in \hbox_frame:nnn: I've added the width of the rule to the sep, then used that to work out where the 'content' should be
% \begin{function}{\hbox_frame:nnn, \hbox_frame:nVV}
% \begin{syntax}
% \cs{hbox_frame:nnn} \Arg{content} \Arg{thickness} \Arg{border}
% \end{syntax}
% Inserts the \meta{content} in a horizontal box which will bear a frame of
% \meta{thickness}. A \meta{border} is left between the \meta{content} and
% the frame. The frame will overprint any part of the \meta{content} which
% lies outside of the bounding box at natural size (\emph{i.e.}~the frame is
% printed \enquote{after} the \meta{content}). The apparent size of the
> While reimaginings of Sherlock Holmes are a dime a dozen, the Conan Doyle Estate had a particular issue about this version. The estate filed a lawsuit against Netflix, saying that because the film depicts Sherlock Holmes as having emotions — yes, you read that right — it violates copyright, since they claim that the character only has emotions in the stories published between 1927-1928, which still belong to the estate.
@DavidCarlisle With the 'classical' implementation, the rule overlaps the start of the text; at present, the xbox one moves the text along so (here) there is no overlap
@DavidCarlisle I've interpreted l as 'Starting at the left side of the rule + sep combo': classical approach only accounts for the sep
@JosephWright I'll have to look what we say I suppose its OK if the width argument is specified as being the outer total width, but it seems a bit useless, and it means the default is not \width:
@JosephWright not a bug, just mis-remembered the rules, usrguide says "Note that it is the total width of the framed box, including the frame, which is set to |\totalheight|. "
@UlrikeFischer Oh, I did that :) The version I have draws the frame after the content is placed
@DavidCarlisle Ah, so I need to adjust: cool
@DavidCarlisle That's OK, that's what I do, it's about how you align the 'content' with the 'rules' - I'll read the implementations again and see if I can track down the differences
@DavidCarlisle ^^^ Point there is that this sets the content in kerns of length 2 * <sep>, whereas I went for 2 * (<sep> + <rule>), which felt more natural
@JosephWright yes I will dig out a 2.09 version later see what it did, for framebox the 2e extensions should just have been \height and friends, and color safety but it's possible we dropped something there....
@egreg -- Well, AMS-TeX was contracted, i.e., paid for, and so was the conversion of AMS-TeX to amsmath. Both took substantial time and effort, and developing LAMS-TeX was about the same order of magnitude. Remember that TeX development was supported by grants; only after its release to the world was it declared free to use. And the *TeXbook" is still not free; see the text at the top of texbook.tex.
@DavidCarlisle I was looking at the dimensions of the pagecolor stuff, currently the rule uses \pdfpagewidth, and when I did set this to \paperwidth in dvips.def dvilualatex errored ;-(.
@DavidCarlisle nowhere yet. I was wondering which length to use at best. I mean can I rely on \paperwidth being equal to \pdfpagewidth e.g. with pdflatex? I often don't change \paperwidth but only the pdf commands if I want to change the mediabox.
define "rely" this is likely to bite you (but you maym not care) \AtBeginDocument{% % If a package has changed \mag, assume it knows what it is doing % and leave page size alone
@UlrikeFischer but otherwise pdftex.def sets the primitive to \paperwidth or \stockwidth (for memoir) question is for memoir if the stock is bigger than the logical paper size and you use \pagecolor, which size gets coloured..
@UlrikeFischer but if dvips.def is being used for dvilualtex it should probably have that whole setting block from luatex.def in addition to its traditional \special{papersize=\the\paperwidth,\the\paperheight}%
@DavidCarlisle well I think one should try to color the "maximum", so the MediaBox, page color should color the page. If people wants some smaller area, they can add custom background pictures (including ducks). So I'm trying to decide how to get this size at best.
MathB.in is a website meant for sharing snippets of mathematical text with others on the web. This is a pastebin for mathematics. URL: http://mathb.in/ I am looking for some good alternative websites to MathB.in
@raf -- This is the first time I've looked at MathB.in. Instructions are generated with, I presume, something like Markdown. It doubles backslashes, which in a TeX context is lethal. I've encountered this before, and it was the cause of many wasted hours. Unfortunately, I don't know any fix to that, or any alternative websites. (I'll try to post a bug report, but may not be successful.)
@DavidCarlisle -- I didn't say that code you might enter is wrong. What I mean is that, if you look at the tutorial, the instructions shown as "text" rather than "input" show double backslashes. Hardly good fodder for newbies.
@PauloCereda Legitimate question. Regardless of the fact that this representation is foolish: Because it looks beautiful (and because a user asked for this representation)
@JosephWright I reverted the checkin really as the unused option list code is tricky and can break things (and it's not clear what used means in a kv context) but if we literally just saved the lists then packages could revert their option list to the original version before processing options, so it would only affect that package
@DavidCarlisle imho we should do it, it would give packages which wants to handle keyval a fighting chance ... (my example was from a real question: someone complained that the schule package didn't work).