Remove uninformative entries from glossary. #14075
Conversation
Remove some entries in the glossary which are only referred to once, in the usage tutorial (note that the usage tutorial explitictly explains the terms "raster" and "vector" graphics just before the renderer table.
|
I'm unsure about this. What is the criterion for "uninformative"? IMHO it doesn't hurt to have e.g. AGG in the glossary. I cannot judge the real value of the glossary. It's difficult to find navigating the website and does only pop up in the search below code documentation (so is typically off-screen). OTOH why not leave it? |
|
It's not as if the current entry for AGG really provides much information. I was thinking of starting to use the glossary to document some matplotlib-specific jargon (e.g. the anatomy of matplotlib tutorial). |
This is a very good idea. Something like this is really missing. We should agree what should be contained in the glossary and what not. IMO image formats and python libraries can really go. I would still keep AGG, Cairo and FreeType for now as they may not be known to the average python user. In particular the former two are difficult to google. |
<
8000
/tr>
|
feel free to push a partial revert, then. |
|
My only contribution here is to undo some changes of the original commit. Since what goes in is only a subset of the original commit, I feel that I'm still legitimated for formal approval. |
Remove some entries in the glossary which are only referred to once, in
the usage tutorial (note that the usage tutorial explitictly explains
the terms "raster" and "vector" graphics just before the renderer table.
PR Summary
PR Checklist