GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||
GeezerVison is showing github.com — Reduce numerical precision in Type 1 fonts by jkseppan · Pull Request #18080 · matplotlib/matplotlib Conversation
|
| as_string = '[' + ' '.join(str(x) for x in array) + ']' | ||
| return as_string.encode('latin-1') | ||
| return ( | ||
| '[' + ' '.join(f'{x:.5g}' for x in array) + ']' |
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
perhaps .5f instead?
(I'm currently away from doing real reviewing so don't wait for me, but the PR certainly looks reasonable.)
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I cannot comment on g vs. f, but I would prefer
| '[' + ' '.join(f'{x:.5g}' for x in array) + ']' | |
| '[%s]' % ' '.join(f'{x:.5g}' for x in array) |
which is slightly more readable IMHO. But I won't block over this.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
(the problem with 'g' is exponent notation: does postscript actually support notation such as '1e4'? (I don't know))
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Postscript supports exponent notation:
NumbersNumbers in the PostScript language include signed integers, such as
123 –98 43445 0 +17
reals, such as
–.002 34.5 –3.62 123.6e10 1E–5 –1. 0.0
and radix numbers, such as
8#1777 16#FFFE 2#1000
https://www.adobe.com/content/dam/acom/en/devnet/actionscript/articles/psrefman.pdf page 27
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Ah, that's fine then.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I thought we should keep a small number of significant digits instead of just rounding to a fixed number of decimals. But on second thought there is little point, since the scale is fixed: fonts are written in terms of 1000 or 1024 units as the side of the design square, so the values on the diagonal are around 0.001. The off-diagonal values are either zero or of similar magnitude as 0.001, otherwise there is no visible effect. We can as well use %f.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
This avoids exponential notation (which is supported by PS but who knows how all the different parsers react to it) and trailing zeros, so we don't unnecessarily increase the size of fonts that have a nice [0.001 0 0 0.001] matrix. Encapsulate the formatting operation in a cbook function and give it a unit test.
|
Thanks @jkseppan ! Have not heard from you in a while, I hope you and your family are doing well. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
Error with greek letters in pdf export when using usetex=True and mathptmx
There was an error while loading. Please reload this page.