@@ -61,7 +61,7 @@ the renderer John has author Michael ?
6161the canvas John has author ?
6262the artist John has author ?
6363transforms Michael submitted John
64- documenting mpl Darren submitted ?
64+ documenting mpl Darren submitted John, Eric, Mike ?
6565coding guide John in review Eric
6666and_much_more ? ? ?
6767=============================== ==================== =========== ===================
@@ -238,67 +238,3 @@ include them as formal review notes.
238238 explanation of your BSD choice. Peripheral question: is
239239 there any problem with basemap's inclusion of
240240 sub-packages with the gamut of licenses, GPL to MIT?
241-
242-
243- usetex user's guide-- reviewed by JDH
244- -------------------------------------
245-
246- Review of :ref: `usetex-tutorial `:
247-
248- #. DONE - In the section on the ps distiller, you might mention that it is the
249- rasterization which some users find objectionable, and the distiller pram
250- (eg 6000) is a dpi setting for the rasterizer. Not everyone will
251- immediately grasp the controversy surrounding dumping high res bitmaps into
252- a ps file.
253-
254- #. DONE - ``= Possible Hangups = `` - this is moin, not rest. I have
255- fixed this already, just wanted to point it out. Also, for everything but
256- top level chapters, I refer ``Upper lower `` for section titles, eg
257- ``Possible hangups ``.
258-
259- #. DONE - in the troubleshooting section, could you add a FAQ showing how to
260- find their .matplotlib dir (matplotlib.get_data_path) and link to
261- it.
262-
263- I think you mean mpl.get_configdir. I added this to the faq/HOWTO, and
264- linked to it from usetex.rst and customizing.rst. I also added the
265- MPLCONFIGDIR environment variable to environment_variables_faq.rst.
266-
267- DONE - Also link to the PATH var and properly format
268- ``text.latex.preample ``.
269-
270- DONE - For the dirs, do we want `tex.cache ` or
271- ``tex.cache ``? I've been using the latter. We could use rest
272- specific markup for files and dirs, but I've been resisting goin
273- whle hog onthe markup... But we may eventually decide that is the
274- better choice.
275-
276- I think we should use the directive provided by sphinx::
277-
278- :file:`tex.cache`
279-
280- I don't think that looks too ugly in ascii, its clear what it means. If you
281- don't like it, I think we should use::
282-
283- ``tex.cache``
284-
285- which is formatted most
286- similarly to the :file: directive in html. Let me know if you don't want to
287- use the file directive.
288-
289- - JDH: let's go with the file directive.
290-
291- #. DONE - try and use internal reference links for every section and be
292- generous with the sections. Eg, I added a section headers and
293- internal linka for the postscript and unicode sections (we will
294- want to be able to refer people to these easily from FAQs and mail
295- list posts, etc)::
296-
297- .. _usetex-postscript:
298-
299- Postscript options
300- ==================
301-
302- Looks good!
303-
304- Thanks!
0 commit comments