No, that is not correct. The fundamental issue is the size of the
compressed file. And this is an issue with documentation, not with
arbitrary graphics. The matplotlib images in the Sage documentation do not
involve millions of lines of svg code. The svg files are small to start
with and
On Wed, Jun 28, 2023 at 6:17 PM Dima Pasechnik wrote:
> are there any setbacks in using svg nowadays?
>
>
The only fundamental issue is file size. It's proportional to the number of
elements you want to plot. So, e.g. when there are a million points, you
end up with a million lines of text in
On Wed, 28 Jun 2023, 17:13 John H Palmieri, wrote:
> I think this should be discussed at sage-devel.
>
are there any setbacks in using svg nowadays?
> On Wednesday, June 28, 2023 at 8:49:51 AM UTC-7 vdelecroix wrote:
>
>> I agree with Marc that svg is almost always preferable than png for
>>
As far as I can tell it is a choice that is being made at various places in
the sage_docbuild module to use png as the default image format. But I
haven't been able to find exactly where. One place appears to be line 117
in src/sage_docbuild/conf.py, but that is not the only place.
- Marc
I think this should be discussed at sage-devel.
On Wednesday, June 28, 2023 at 8:49:51 AM UTC-7 vdelecroix wrote:
> I agree with Marc that svg is almost always preferable than png for
> graphics : it scales and compresses. Thanks for raising the issue.
>
> Do you have a concrete proposal for
I agree with Marc that svg is almost always preferable than png for
graphics : it scales and compresses. Thanks for raising the issue.
Do you have a concrete proposal for making the change png -> svg
happen? I guess there is a lot of files that would be involved in the
transition.
Vincent
On
Details really do matter. The devil is in them. Here is one which makes a
major difference to my efforts to distribute Sage. I hope that I can
convince people to pay attention to it.
DETAIL: An svg image can be compressed very efficiently and will look good
at all resolutions. A png image
