You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "Counting.png" (pre-rendered "Counting.htm") is so notoriously large (~ 1.33 MiB):
[ Did some palette optimization (merge similar colors and limit color space): <&>now ~ 647.17 KiB</&>. [1] ]
Why not consider have it converted to SVG?
Did considered, but to no avail.
In brief, current SVG definition has broken support for text type contents:
Primarily, it's missing support for content of non-fixed (undetermined) size (i.e. no wrapping and overflow handling): which is typically the case for texts.
.
It also lacks support for many CSS properties: which makes table rendering a bit bothersome.
Of course, vectorizing the PNG is also an option.
I'm just not interested to bother.
=== Further reading ===
SVG doesn't seem to be well-designed to be used in Plain Text:
Cannot be properly parsed without uttering that verbose (and much meaningless) `xmlns="http://www.w3.org/2000/svg"`...
And the very dumbfounding "d" graphic path definition...
Such "image"... What difference is it of between a fully-fledged web app?
Image that requires an interaction engine to properly render?..
Interactive-Image in HTML... Who invented it?
The "Counting.png" (pre-rendered "Counting.htm") is so notoriously large (~ 1.33 MiB):
[ Did some palette optimization (merge similar colors and limit color space): <&>now ~ 647.17 KiB</&>. [1] ]
Why not consider have it converted to SVG?
Did considered, but to no avail.
In brief, current SVG definition has broken support for text type contents:
Primarily, it's missing support for content of non-fixed (undetermined) size (i.e. no wrapping and overflow handling): which is typically the case for texts.
.
It also lacks support for many CSS properties: which makes table rendering a bit bothersome.
Of course, vectorizing the PNG is also an option.
I'm just not interested to bother.
=== Further reading ===
SVG doesn't seem to be well-designed to be used in Plain Text:
Cannot be properly parsed without uttering that verbose (and much meaningless) `
xmlns="http://www.w3.org/2000/svg"
`...And the very dumbfounding "d" graphic path definition...
See also:
https://github.com/MasterInQuestion/talk/discussions/15#discussion-6022492 ("SVG")
[ [1]
Did further optimization using WebP: finally ~ 278.18 KiB.
More details: https://github.com/MasterInQuestion/attach/commit/401c58fc3a56d265feadda567f02d79de93ff10c#Counting ]
The text was updated successfully, but these errors were encountered: