[issue7057] tkinter doc: more 3.x updates

Ezio Melotti report at bugs.python.org
Thu Oct 15 06:18:41 CEST 2009


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Here is an incomplete patch. I fixed all the markup errors, typos and
similar issues you mentioned and a few more that I noticed.

Someone that knows Tkinter better than me should take care of the
remaining issues, i.e.:
 * is Xlib still used?
 * bmp files on Windows
 * the section about Canvas

3.x specific issues:

1. In most of the places I think it's OK to use 'Tkinter' and use
:mod:`tkinter` only when referring specifically to the module. I also
fixed other :mod:`Tkinter` around in the Doc.

2. Both fixed.

3. Fixed. I also changed *tkinter* to :mod:`tkinter`. I don't know about
Xlib.

Not 3.x specific:

> 10. "Specifically, the man pages in the mann directory are most 
> useful."
> Is 'mann' literally correct? a typo? or meant to mean 'man#', where # 
> is a digit?

I used 'manN' and added the link you provided (even if right now the
site seems down so I can't verify if it's correct).

> 11. "Credits:
> Tkinter was written by Steen Lumholt and Guido van Rossum. 
> Tk was written by John Ousterhout while at Berkeley. "
> Except for the first two lines, the entries are in historical order, 
> so I would reverse the first two.
 
Done.

> 12. 24.1.6.6. Tk Option Data Types
> "To specify an X bitmap filename, give the full path to the file,
> preceded with an @, as in "@/usr/contrib/bitmap/gumby.bit"."
> *nix only? what about windows .bmp file?

Does someone know the answer?

> 13. (ttk section) 24.2.3.1. Standard Options
> "0, 1 or an empty is return." => "0, 1 or an empty string is 
> returned."

Fixed.

> PS. I like the colors of the option-description tables.

Thank Raymond for them.

----------
keywords: +patch
Added file: http://bugs.python.org/file15131/issue7057.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue7057>
_______________________________________


More information about the Python-bugs-list mailing list