At John Palmieri's suggestion, I am duplicating this message that I posted
on sage-release on this list:
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.
DET
On Wed, 2023-06-28 at 10:07 -0700, Marc Culler wrote:
>
> BOTTOM LINE: we get more than a 90% reduction in size simply by choosing to
> use the .svg extension when saving the plot instead of the .png extension.
>
SVG is the right choice for most graphics, but there are some practical
problems:
I am not proposing using gzipped svg for a normal sage build. I only want
to do it for the Sage_macOS app, which will have a simple self-contained
server running on the loopback interface that provides gzipped content
(with the Content-Encoding header set to "gzip"). Of course I would be
happ
I tried making this change (which would affect each ".. PLOT:" directive)
but the documentation failed to build:
diff --git a/src/sage_docbuild/conf.py b/src/sage_docbuild/conf.py
index 9b6b37480b..db33c4b1d6 100644
--- a/src/sage_docbuild/conf.py
+++ b/src/sage_docbuild/conf.py
@@ -115,7 +115,7
I think I may have found a resolution of this problem, that involves doing
almost nothing. It appears that sage_docbuild oftern builds image in all
three formats - svg, png and pdf. All three types get stored in the html
directory and the svg is duplicated:
find local/share/doc/sage/html/en -
Note: I had already compressed the .svg files, hence the .gz extension.
Before compression I get:
% find local/share/doc/sage/html/en -name 'chart-12*'
local/share/doc/sage/html/en/reference/manifolds/_images/chart-12.svg
local/share/doc/sage/html/en/reference/manifolds/sage/manifolds/chart-12.sv
This change should produce only the .svg files:
diff --git a/src/sage_docbuild/conf.py b/src/sage_docbuild/conf.py
index 9b6b37480b..b5d6815c76 100644
--- a/src/sage_docbuild/conf.py
+++ b/src/sage_docbuild/conf.py
@@ -128,7 +128,7 @@ from sage.all_cmdline import *
"""
plot_html_show_formats =
By the way, on my machine, local/share/doc/sage are almost identical sizes
in 10.1.beta3 and 10.1.beta4. I don't know what explains the difference
you're seeing.
On Wednesday, June 28, 2023 at 12:51:38 PM UTC-7 John H Palmieri wrote:
> This change should produce only the .svg files:
>
> diff --
Thank you! Probably it is my bug, or it is somehow triggered by my wierd
setup. That would probably mean some environment difference in the sage or
sage-env scripts, since those are basically the only things I have tinkered
with.
Can you verify that you do not see any image files in the top leve
On Wed, 2023-06-28 at 13:50 -0400, Michael Orlitzky wrote:
>
> * gzipped SVG doesn't work over the file:/// protocol in my firefox.
> This hasn't been a big enough problem for me yet to diagnose it,
> so I can't say how serious a problem it is. (I'll play around later
> today.)
Fire
One can always start a web server on localhost, instead of using file:/// :P
On Wed, Jun 28, 2023 at 11:16 PM Michael Orlitzky wrote:
>
> On Wed, 2023-06-28 at 13:50 -0400, Michael Orlitzky wrote:
> >
> > * gzipped SVG doesn't work over the file:/// protocol in my firefox.
> > This hasn't b
Right. That is what I will be doing.
- Marc
On Wed, Jun 28, 2023, 5:27 PM Dima Pasechnik wrote:
> One can always start a web server on localhost, instead of using file:///
> :P
>
> On Wed, Jun 28, 2023 at 11:16 PM Michael Orlitzky
> wrote:
> >
> > On Wed, 2023-06-28 at 13:50 -0400, Michael Orl
I confirm that I do not see any image files in
local/share/doc/sage/html/en/reference/manifolds/sage/manifolds. All of the
images (and all are in svg format) are in
local/share/doc/sage/html/en/reference/manifolds/_images/. These are copies
of files in
local/share/doc/sage/inventory/en/referen
On 2023-06-28 23:27:22, Dima Pasechnik wrote:
> One can always start a web server on localhost, instead of using file:/// :P
>
I know you're mostly joking, but that's not as easy as it sounds. To
start the local web server as a non-root user, you have to run it on
an unprivileged (i.e. not the def
Hi,
We spent six days for the preliminary discussion in the sage-devel thread
https://groups.google.com/g/sage-devel/c/OUnoroIf0qc
about choosing the keyword triggering block-scoped optional tag needed in
https://github.com/sagemath/sage/issues/35750
We now start the voting with the four cand
I vote for (A)
On Wed, Jun 28, 2023 at 7:40 PM Kwankyu Lee wrote:
> Hi,
>
> We spent six days for the preliminary discussion in the sage-devel thread
>
> https://groups.google.com/g/sage-devel/c/OUnoroIf0qc
>
> about choosing the keyword triggering block-scoped optional tag needed in
>
> https:/
(B) "requires"
On Thursday, 29 June 2023 at 12:40:07 pm UTC+10 Kwankyu Lee wrote:
> Hi,
>
> We spent six days for the preliminary discussion in the sage-devel thread
>
> https://groups.google.com/g/sage-devel/c/OUnoroIf0qc
>
> about choosing the keyword triggering block-scoped optional tag needed
17 matches
Mail list logo
