Changes between Version 12 and Version 13 of NameSuggestions
- Timestamp:
- Sep 6, 2006, 1:57:52 PM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NameSuggestions
v12 v13 1 1 = In search of a better name for Markup = 2 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. Note especially that there is another Python project for generating HTML called markup at [http://markup.sourceforge.net/]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. Note also that there is another Python project for generating HTML called markup at [http://markup.sourceforge.net/]. Another problem is that a future version of Markup will include a simple text-based template engine (see #47), which isn't really related to markup. 4 4 5 5 This page should serve to collect the various name suggestions. 6 6 7 Please note that there are several aspects to the project name:7 Please also note that there are several aspects to the project name: 8 8 * The project name as used in the logo, website and when referring to the project in general. 9 9 * The name of the python package. … … 101 101 - cboos 102 102 103 ''Well, but Markup '''is''' mostly about Markup, just not exclusively. So we'd have to use something like XAJM (XAJM Ain't Just Markup) :-P[[BR]] -- cmlenz'' 104 105 == “Textyr” == 106 107 From ''texere'' (latin: “weaving”) and ''texture'', with a '''y''' thrown in for the connection to Python and better uniqueness for search engines. The name is intended to suggest that the package is about “weaving text [output for the web]”. 108 109 ''(suggested by Christopher Lenz, who isn't convinced of the suggestion but wanted to write it down here anyway ;)'' 110 103 111 ---- 104 112 == About the ''<markup/>'' Logo ==