| | 1 | = In search of a better name for Markup = |
| | 2 | |
| | 3 | Many people have commented that “Markup” is a bad name for a project, mainly because it's very difficult to search for using Google et al. |
| | 4 | |
| | 5 | == “pyMarkup” == |
| | 6 | |
| | 7 | Suggested by Christian Boos [http://groups.google.com/group/markup-discuss/browse_thread/thread/b9d4cb7fcdd08072 here]: |
| | 8 | |
| | 9 | > pyMarkup? |
| | 10 | > |
| | 11 | > Pretty standard for a Python library to have a "py" prefix, and you |
| | 12 | > don't really give up the Markup name. |
| | 13 | > Also, would be pretty straightforward to top google results for it (54 |
| | 14 | > hits so far...). |
| | 15 | |
| | 16 | Response by [http://www.cmlenz.net/ Christopher Lenz]: |
| | 17 | |
| | 18 | > I'm not a fan of such prefixed names (!WinFoo, KFoo, GFoo, iFoo, etc). |
| | 19 | > IMHO those fall in the "cheesy" category ;-) |
| | 20 | > Exceptions are bindings or Python versions of some product, but |
| | 21 | > otherwise I think it's rather ugly. |
| | 22 | |
| | 23 | == “Markhor” == |
| | 24 | |
| | 25 | See [http://groups.google.com/group/markup-discuss/browse_thread/thread/b9d4cb7fcdd08072 this post] by [http://matt-good.net/ Matt Good] to the [MailingList mailing list]: |
| | 26 | |
| | 27 | > In relation to the "Goat" suggestion Chris mentioned on IRC "Markhor" |
| | 28 | > which is a type of goat. Incidentally the name comes from the Persian |
| | 29 | > word for "snake eater", so it has a sort-of tie-in to Python. Though |
| | 30 | > as Christian later that O'Reilly is using wild goats on its covers for |
| | 31 | > Ruby on Rails-related books: |
| | 32 | > http://www.oreilly.com/catalog/rubyrails/ |
| | 33 | |
| | 34 | ''In this context, “Goat” was proposed on the thread by Ethan Fremen (“what happens to a kid when it grows up :)“.)'' |
