-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maybe make inkscapearea=page the default? #37
Comments
I will think about it. I also wanted to point out that the desired default behaviour can be achieved very easily by running |
For completeness: another question over at tex.sx. |
Just saw another one. |
Well, this default setting was probably a bad design decision. I actually can't remember, if this was already in the package, when I took over the maintenance or if it was an imprudent choice by myself. Nevertheless, as it is now out there like it is quite a long time, I won't change it as this could break a lot of existing documents. But once I find some time, I will place at least a highlighted note at the beginning of the documentation. |
I understand. Backward compatibility is one of LaTeX's great strengths, though this dogma has been softened quite a bit in recent years (and rightfully so). In this particular case I would argue that the change is worth the trouble, as the vast majority of users will want to crop their images only on occasion and not by default. Ideally, this would be combined with other breaking changes, but I'm not aware of any that are planned / that would be useful. I won't argue it beyond this post, but one possible way of softening the transition would be a deprecation cycle like
|
It has always confused me that the default for
inkscapearea
isdrawing
and notpage
. To me,page
is the obvious choice. To my knowledge, all other contexts in whichsvg
s are used (e.g. websites) use the page as the bounding box for the drawing. That is to say, users will likely expect that behavior. After all, that's its whole purpose. Usingdrawing
means discarding information on how the drawing should be displayed that was provided by its creator. The aliasescrop
andnocrop
illustrate this quite well: I find it pretty weird for an image inclusion mechanism to crop the image by default.Especially in the context of LaTeX, I often need to make use of the page boundaries. An example is when I have multiple drawings that should be displayed next to / above each other. Then I can create
svg
s with identical sizes (or at least aspect ratios) without worrying about the precise drawing size and just scale them identically in LaTeX.It gets even messier when LaTeX code is involved. As an example, consider the following drawing.
![image](https://user-images.githubusercontent.com/23075534/102352926-b34aa000-3fa8-11eb-8c15-5488316af093.png)
![image](https://user-images.githubusercontent.com/23075534/102353260-1c321800-3fa9-11eb-8f27-8c6d5370b5d3.png)
Including this with the
drawing
option cannot yield anything sensible. Thepage
option preserves the intention of the creator (frame added in LaTeX):All in all, this seems like a really strange default choice to me and I would argue for changing it. It isn't a super pressing issue (there are two questions caused by it on tex.sx for now) but I think
page
would be a much better default.I do realize, of course, that this would mean breaking backward compatibility, which is unfortunate. If other things doing that are also in the works, I would love to see this change included in the next major release, though.
Files used for illustration:
geometric_series.svg
svg_test.tex
The text was updated successfully, but these errors were encountered: