Copy-edit the "fonts in pdf and postscript" table.#30569
Conversation
|
👍 modulo placating the linter . I think we should go with adding a |
Might be worth switching the table to a list-table since most of the sentences are long? |
|
It would be nice if sphinx-gallery authorized this file to just be a .rst (which would get properly highlighted in the editor and not be subject to irrelevant python linting rules. (@timhoffm IIRC you interact a bit with the s-g team, perhaps you have an opinion there?) |
Remove unnecessary info snippets e.g. re: fractal rendering (this isn't a table for font designers); merge Type 42 entry together with TrueType (they are essentially the same technology).
As of today sphinx-gallery does not support this (see https://sphinx-gallery.github.io/stable/syntax.html#plain-rest-examples). I'm not clear whether that's a fundamental design decision or whether it's just not implemented. Technically, that would be perfectly possible. It just slightly complicates the processing in that you have to skip the right parts of the example build. What you could try as a workaround is making a placeholder .py file and include an .rst May need some fiddling to get the path to the rst file right. Alternatively, just include the table as a separate .rst file or use a list table as suggested by @story645. |
Remove unnecessary info snippets e.g. re: fractal rendering (this isn't a table for font designers); merge Type 42 entry together with TrueType (they are essentially the same technology).
PR summary
PR checklist