On Mon, Jan 12, 2009 at 2:53 AM, Werner F. Bruhin <[email protected]> wrote: > > Jorge Vargas wrote: >> Hi, We where working on updating the TurboGears2 sphinx sources and I >> found a lot of typo's that could be found by a spell checker, which >> got us thinking, Why not having a sphinx plugin to do this? Which in >> turn made me write this email. >> >> Has anyone else think about this? >> if so maybe someone has a private implementation you will want to share. >> If not just exactly how hard will it be to write it? >> any recommendations for a spell checking library? >> >> keep in mind I have never coded a sphinx plugin or interacted with a >> spell checking library, which makes this twice as interesting to work >> on. So with the right guidance I think I could make this happen. or >> should I just forget about this and use an external tool? >> > Isn't that more of a job for whatever editor you use? > yes indeed I use vi's spell checking which is awesome.
> I use UliPad (http://code.google.com/p/ulipad/ ) for the .rst files I > write and it obviously could be used for .py files. Written in Python > and wxPython. It uses the "enchant" spell checker, I use > pyenchant-1.4.2-py2.5.egg-info as I could not get 1.5.x to work. > that could be a good starting point. Although the original idea for the "plugin" was in the supervising mode for example it could generate warnings on build like warning doc.rst:60 'coulnd' may be misspelled Keep in mind that in midsize project lots of authors may write the docs so the plugin will be some sort of "automatic testing" for docs. > Werner > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en -~----------~----~----~----~------~----~------~--~---
