<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Wiki Markup Language: What You See Is&#8230; Messy</title>
	<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/</link>
	<description>Weblog about the Citizendium project and its Citizens.</description>
	<pubDate>Mon, 08 Sep 2008 02:17:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Larry Sanger</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40713</link>
		<author>Larry Sanger</author>
		<pubDate>Fri, 12 Oct 2007 15:49:03 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40713</guid>
					<description>It just has to be done right.  I've used a WYSIWYG wiki when teaching philosophy of law -- it didn't go very well, I'm sorry to admit.  The wiki markup isn't the main thing that makes the system apparently hard to master; the concepts and functions, however encoded, is the problem, and there's no way to make those less difficult.

If we do create a WYSIWYG editing system, I'd be in favor of a split-screen system, which still requires people to write the wiki code, but which automatically, using an AJAX tool, displays what the editing does on-the-fly.  I imagine this would be &lt;i&gt;relatively&lt;/i&gt; easy.  The hard part comes in when you have people editing the "display" version -- which is very hard to make look exactly like the real display version -- and producing clean, editable, standard wiki code.  I'm not saying it can't be done (probably, someone's already done it; I don't know, I haven't kept up with that), I'm just saying that it's incredibly hard.</description>
		<content:encoded><![CDATA[<p>It just has to be done right.  I&#8217;ve used a WYSIWYG wiki when teaching philosophy of law &#8212; it didn&#8217;t go very well, I&#8217;m sorry to admit.  The wiki markup isn&#8217;t the main thing that makes the system apparently hard to master; the concepts and functions, however encoded, is the problem, and there&#8217;s no way to make those less difficult.</p>
<p>If we do create a WYSIWYG editing system, I&#8217;d be in favor of a split-screen system, which still requires people to write the wiki code, but which automatically, using an AJAX tool, displays what the editing does on-the-fly.  I imagine this would be <i>relatively</i> easy.  The hard part comes in when you have people editing the &#8220;display&#8221; version &#8212; which is very hard to make look exactly like the real display version &#8212; and producing clean, editable, standard wiki code.  I&#8217;m not saying it can&#8217;t be done (probably, someone&#8217;s already done it; I don&#8217;t know, I haven&#8217;t kept up with that), I&#8217;m just saying that it&#8217;s incredibly hard.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Stephen Ewen</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40747</link>
		<author>Stephen Ewen</author>
		<pubDate>Fri, 12 Oct 2007 19:22:09 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40747</guid>
					<description>Actually, Mediawiki does support a WYSIWYG editor--sort of.  See http://en.citizendium.org/wiki/CZ:Enhancing_your_editing_with_javascript_extensions#wikEd

Other than that, I completely agree that the Mediwiki software has a needless learning curve.  I am no techno-dummy but it took me a month to get a good handle on some stuff.  The ability to make basic templates have come only recently to me.  

Indeed, contributing an article should be as easy to use as a basic word processor.</description>
		<content:encoded><![CDATA[<p>Actually, Mediawiki does support a WYSIWYG editor&#8211;sort of.  See <a href="http://en.citizendium.org/wiki/CZ:Enhancing_your_editing_with_javascript_extensions#wikEd" rel="nofollow">http://en.citizendium.org/wiki/CZ:Enhancing_your_editing_with_javascript_extensions#wikEd</a></p>
<p>Other than that, I completely agree that the Mediwiki software has a needless learning curve.  I am no techno-dummy but it took me a month to get a good handle on some stuff.  The ability to make basic templates have come only recently to me.  </p>
<p>Indeed, contributing an article should be as easy to use as a basic word processor.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Phil Deets</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40762</link>
		<author>Phil Deets</author>
		<pubDate>Fri, 12 Oct 2007 21:08:14 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40762</guid>
					<description>Personally, I don't like the split screen idea as it would take too much space. I would guess that a customized version of TinyMCE would work well.</description>
		<content:encoded><![CDATA[<p>Personally, I don&#8217;t like the split screen idea as it would take too much space. I would guess that a customized version of TinyMCE would work well.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Chris D</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40777</link>
		<author>Chris D</author>
		<pubDate>Fri, 12 Oct 2007 22:36:47 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40777</guid>
					<description>I agree with the first point.  It does take a while to figure out the markup and some may well give up before they get to that point.  The talk page comment seems a long similar lines.  But IRC?  Not sure how anyone needs IRC to edit the encyclopedia. What CZ and WP really need is a docum,ent converter that can take a standard rtf file and change it into wikimark up. Then authors can work off line and edit on which ever program they feel most comfortable.  Likewise a wikimark up to rtf converter would make it easy for authors to download the text of any article and work in their preferred environment. I have no idea if this is possible but I suspect it will stop people complaining about the wiki environment (these comments made on the assumption that a WYSIWYG will not be supported in the near future).</description>
		<content:encoded><![CDATA[<p>I agree with the first point.  It does take a while to figure out the markup and some may well give up before they get to that point.  The talk page comment seems a long similar lines.  But IRC?  Not sure how anyone needs IRC to edit the encyclopedia. What CZ and WP really need is a docum,ent converter that can take a standard rtf file and change it into wikimark up. Then authors can work off line and edit on which ever program they feel most comfortable.  Likewise a wikimark up to rtf converter would make it easy for authors to download the text of any article and work in their preferred environment. I have no idea if this is possible but I suspect it will stop people complaining about the wiki environment (these comments made on the assumption that a WYSIWYG will not be supported in the near future).</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Stephen Ewen</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40780</link>
		<author>Stephen Ewen</author>
		<pubDate>Fri, 12 Oct 2007 22:51:02 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40780</guid>
					<description>What if we used something like http://www.fckeditor.net/ - a WYSIWYG editor?</description>
		<content:encoded><![CDATA[<p>What if we used something like <a href="http://www.fckeditor.net/" rel="nofollow">http://www.fckeditor.net/</a> - a WYSIWYG editor?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Stephen Ewen</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40781</link>
		<author>Stephen Ewen</author>
		<pubDate>Fri, 12 Oct 2007 22:52:14 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40781</guid>
					<description>Sorry to post again.  Here is a demo: http://www.fckeditor.net/demo</description>
		<content:encoded><![CDATA[<p>Sorry to post again.  Here is a demo: <a href="http://www.fckeditor.net/demo" rel="nofollow">http://www.fckeditor.net/demo</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Stephen Ewen</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40785</link>
		<author>Stephen Ewen</author>
		<pubDate>Fri, 12 Oct 2007 23:24:31 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40785</guid>
					<description>This would work, too: http://www.jspwiki.org/wiki/WikiWizard</description>
		<content:encoded><![CDATA[<p>This would work, too: <a href="http://www.jspwiki.org/wiki/WikiWizard" rel="nofollow">http://www.jspwiki.org/wiki/WikiWizard</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Mike Johnson</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40796</link>
		<author>Mike Johnson</author>
		<pubDate>Sat, 13 Oct 2007 00:32:38 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40796</guid>
					<description>All very interesting comments. I just have a general personal anecdote to add. 

Most wiki neophytes I show Citizendium to really like our articles, and they seem to agree that our expertise and real name systems make lots of sense. Then I show them the page editing screen, and they get that glassy, 'too techie for me' look in their eyes. Their enthusiasm just drains. It's been really frustrating.</description>
		<content:encoded><![CDATA[<p>All very interesting comments. I just have a general personal anecdote to add. </p>
<p>Most wiki neophytes I show Citizendium to really like our articles, and they seem to agree that our expertise and real name systems make lots of sense. Then I show them the page editing screen, and they get that glassy, &#8216;too techie for me&#8217; look in their eyes. Their enthusiasm just drains. It&#8217;s been really frustrating.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Nick</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40818</link>
		<author>Nick</author>
		<pubDate>Sat, 13 Oct 2007 02:12:09 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40818</guid>
					<description>The FckEditor people have already started a project to integrate it with MediaWiki. http://mediawiki.fckeditor.net/index.php/Main_Page</description>
		<content:encoded><![CDATA[<p>The FckEditor people have already started a project to integrate it with MediaWiki. <a href="http://mediawiki.fckeditor.net/index.php/Main_Page" rel="nofollow">http://mediawiki.fckeditor.net/index.php/Main_Page</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Stephen Ewen</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40873</link>
		<author>Stephen Ewen</author>
		<pubDate>Sat, 13 Oct 2007 07:31:39 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40873</guid>
					<description>Nick, that's great news, thanks for the info. :-)

Mike, I for one think we should seek to make contributing to the wiki as easy as possible technically, and systemically so.</description>
		<content:encoded><![CDATA[<p>Nick, that&#8217;s great news, thanks for the info. <img src='http://blog.citizendium.org/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Mike, I for one think we should seek to make contributing to the wiki as easy as possible technically, and systemically so.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: David Gerard</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40904</link>
		<author>David Gerard</author>
		<pubDate>Sat, 13 Oct 2007 13:27:43 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40904</guid>
					<description>Yeah. FCKeditor looks like the best prospect for a WYSIWYG MediaWiki editor at present. I was desperately after one for the work wiki, but it's not ready yet. But I hold out hope for the near to medium future.

The main problem is that MediaWiki wikitext does not have a defined syntax - the definition is quite literally the PHP code - and is mathematically impossible to put into EBNF. (Many have tried, got to 95% and realised it wasn't actually possible.) So there are no alternate parsers, and no WYSIWYG can cover the lot. But 95% coverage in a WYSIWYG editor should get most of the useful bits.</description>
		<content:encoded><![CDATA[<p>Yeah. FCKeditor looks like the best prospect for a WYSIWYG MediaWiki editor at present. I was desperately after one for the work wiki, but it&#8217;s not ready yet. But I hold out hope for the near to medium future.</p>
<p>The main problem is that MediaWiki wikitext does not have a defined syntax - the definition is quite literally the PHP code - and is mathematically impossible to put into EBNF. (Many have tried, got to 95% and realised it wasn&#8217;t actually possible.) So there are no alternate parsers, and no WYSIWYG can cover the lot. But 95% coverage in a WYSIWYG editor should get most of the useful bits.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: David Gerard</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40906</link>
		<author>David Gerard</author>
		<pubDate>Sat, 13 Oct 2007 13:41:59 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40906</guid>
					<description>And on the IRC one, I think Jason is just plain wrong.

(a) IRC is damn useful, but you do not in any way have to be on IRC to be a productive Wikipedia editor, admin or even arbitrator. And many aren't and won't be.

(b) I find it hard to conceive how any Internet idiot can lower the world's collective IQ with instant messaging, but thinking people who would want to contribute to an encyclopedia can't. And IRC is just IM based around chatrooms instead of one-to-one. If you can use Trillian or GAIM/Pidgin, you can use IRC.</description>
		<content:encoded><![CDATA[<p>And on the IRC one, I think Jason is just plain wrong.</p>
<p>(a) IRC is damn useful, but you do not in any way have to be on IRC to be a productive Wikipedia editor, admin or even arbitrator. And many aren&#8217;t and won&#8217;t be.</p>
<p>(b) I find it hard to conceive how any Internet idiot can lower the world&#8217;s collective IQ with instant messaging, but thinking people who would want to contribute to an encyclopedia can&#8217;t. And IRC is just IM based around chatrooms instead of one-to-one. If you can use Trillian or GAIM/Pidgin, you can use IRC.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Stephen Ewen</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40935</link>
		<author>Stephen Ewen</author>
		<pubDate>Sat, 13 Oct 2007 19:50:43 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40935</guid>
					<description>I am rather stunned that David defends IRC backrooms as a legitimate part of the governance of WP.  

For anyone who wishes to test FckEditor on their wiki, go to http://mediawiki.fckeditor.net/index.php/Sandbox</description>
		<content:encoded><![CDATA[<p>I am rather stunned that David defends IRC backrooms as a legitimate part of the governance of WP.  </p>
<p>For anyone who wishes to test FckEditor on their wiki, go to <a href="http://mediawiki.fckeditor.net/index.php/Sandbox" rel="nofollow">http://mediawiki.fckeditor.net/index.php/Sandbox</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Anthony.Sebastian</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40948</link>
		<author>Anthony.Sebastian</author>
		<pubDate>Sat, 13 Oct 2007 20:56:20 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-40948</guid>
					<description>Regarding Chris Day's idea of a software document converter (e.g., .RTF to WikiEditor), as an immediate stopgap solution, we might ask for volunteers to serve as human document converters.  Volunteer MediaWiki whizzes, who would find converting a snap.  Remember the first computers: humans.

That CZ service would allow potential authors starting new articles to submit in .rtf or .doc/.docx, etc.  Academics, for example, often write their articles in MS Word, using EndNote or Reference Manager to "cite-while-you-write" and when fiished have the program automatically format the bibliography. Personally, I find using the MediaWiki editor for source-citing a huge barrier to productivity, including even starting a new article.

The DocumentConveters could handle submitted edits the same way.

Who would volunteer? Or know someone whom thy could ask if they would volunteer?  What ideas do you have to improve this idea?  Why would this not work?  Let me know here or at my Talk page: http://en.citizendium.org/wiki/User:Anthony.Sebastian</description>
		<content:encoded><![CDATA[<p>Regarding Chris Day&#8217;s idea of a software document converter (e.g., .RTF to WikiEditor), as an immediate stopgap solution, we might ask for volunteers to serve as human document converters.  Volunteer MediaWiki whizzes, who would find converting a snap.  Remember the first computers: humans.</p>
<p>That CZ service would allow potential authors starting new articles to submit in .rtf or .doc/.docx, etc.  Academics, for example, often write their articles in MS Word, using EndNote or Reference Manager to &#8220;cite-while-you-write&#8221; and when fiished have the program automatically format the bibliography. Personally, I find using the MediaWiki editor for source-citing a huge barrier to productivity, including even starting a new article.</p>
<p>The DocumentConveters could handle submitted edits the same way.</p>
<p>Who would volunteer? Or know someone whom thy could ask if they would volunteer?  What ideas do you have to improve this idea?  Why would this not work?  Let me know here or at my Talk page: <a href="http://en.citizendium.org/wiki/User:Anthony.Sebastian" rel="nofollow">http://en.citizendium.org/wiki/User:Anthony.Sebastian</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Aleta Curry</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41030</link>
		<author>Aleta Curry</author>
		<pubDate>Sun, 14 Oct 2007 20:49:45 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41030</guid>
					<description>I'm going to disagree with the assumption that it's the code that's making people reluctant to participate--and by that I mean the INITIAL participation.

I'm not a computer person, and I don't like things that make my life difficult, so I know whereof I speak.

People my age can remember having to learn all sorts of "impossible" code:  Wordperfect and stand-alone word processors and stuff.  You had to learn how to change tape in your brain the way you change tapes when you switch languages.

"Kids" don't seem to be afraid of anything--if you need to use a computer, VCR (oh, sorry--DVD to you lot--I still have VCR stuff)--ask a 10-year-old.

If you're a member of any kind of onlne forum, you have to learn non-wysiwyg stuff.

So who are the reluctant ones?  Is it a 20-something group? or a 50-something plus group?

Really, it's when things get hard that I glaze over.  Or get annoyed because I've got too many demands on my time to mess with code. 

The fact is, you can start an article on CZ by picking a subject, clicking the start article button, typing away, and then hitting SAVE.

*That's* what we need to tell people.

If they are not able to (or they just don't *@#$%^&#38;* feel like bothering with) [[code(computer)&#124;formatting their work]] well, by gum that's just fine, there are people who actually *like* doing that sort of thing.

If they learn basic formatting but metadata pages and {{subpages}} make them glaze over, well, again, let them leave it alone till they're good and ready.

To use Mike's example, maybe we need a here's-what-we-show-newbies-page that just has typed text and the result?</description>
		<content:encoded><![CDATA[<p>I&#8217;m going to disagree with the assumption that it&#8217;s the code that&#8217;s making people reluctant to participate&#8211;and by that I mean the INITIAL participation.</p>
<p>I&#8217;m not a computer person, and I don&#8217;t like things that make my life difficult, so I know whereof I speak.</p>
<p>People my age can remember having to learn all sorts of &#8220;impossible&#8221; code:  Wordperfect and stand-alone word processors and stuff.  You had to learn how to change tape in your brain the way you change tapes when you switch languages.</p>
<p>&#8220;Kids&#8221; don&#8217;t seem to be afraid of anything&#8211;if you need to use a computer, VCR (oh, sorry&#8211;DVD to you lot&#8211;I still have VCR stuff)&#8211;ask a 10-year-old.</p>
<p>If you&#8217;re a member of any kind of onlne forum, you have to learn non-wysiwyg stuff.</p>
<p>So who are the reluctant ones?  Is it a 20-something group? or a 50-something plus group?</p>
<p>Really, it&#8217;s when things get hard that I glaze over.  Or get annoyed because I&#8217;ve got too many demands on my time to mess with code. </p>
<p>The fact is, you can start an article on CZ by picking a subject, clicking the start article button, typing away, and then hitting SAVE.</p>
<p>*That&#8217;s* what we need to tell people.</p>
<p>If they are not able to (or they just don&#8217;t *@#$%^&amp;* feel like bothering with) [[code(computer)|formatting their work]] well, by gum that&#8217;s just fine, there are people who actually *like* doing that sort of thing.</p>
<p>If they learn basic formatting but metadata pages and {{subpages}} make them glaze over, well, again, let them leave it alone till they&#8217;re good and ready.</p>
<p>To use Mike&#8217;s example, maybe we need a here&#8217;s-what-we-show-newbies-page that just has typed text and the result?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Chris D</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41044</link>
		<author>Chris D</author>
		<pubDate>Sun, 14 Oct 2007 23:45:28 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41044</guid>
					<description>Stephen I don't think David is defending IRC, he just says it is useful but good editors do not need it to be productive.</description>
		<content:encoded><![CDATA[<p>Stephen I don&#8217;t think David is defending IRC, he just says it is useful but good editors do not need it to be productive.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Yuval Langer</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41076</link>
		<author>Yuval Langer</author>
		<pubDate>Mon, 15 Oct 2007 09:59:18 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41076</guid>
					<description>I really like the What You See Is What You Meant [1] way of doing things. Take 
LyX [2] for example (maybe the only example there is?).
Everything is about meaning and not styling. You don't have to worry about how 
things will look like on paper or on the HTML page. You don't have to worry 
about spacing or fonts or bolding or italising words. You just mark blocks of 
words or lines meaningfully, like "paragraph" (instead of font size 10) 
or "title" (instead of font size 30) or "Emphasis" (instead of bold). The 
engine that process the lyx format decides how the end format will be 
stylized according to standard rules. This lets CZ the freedom to change the 
style of its HTML pages without actually changing by hand each and every 
page. You also have a good mechanism for citations and notes.

I think the cz-tools team should check it up.

[1] http://en.wikipedia.org/wiki/WYSIWYM
[2] http://www.lyx.org/

Thank you.</description>
		<content:encoded><![CDATA[<p>I really like the What You See Is What You Meant [1] way of doing things. Take<br />
LyX [2] for example (maybe the only example there is?).<br />
Everything is about meaning and not styling. You don&#8217;t have to worry about how<br />
things will look like on paper or on the HTML page. You don&#8217;t have to worry<br />
about spacing or fonts or bolding or italising words. You just mark blocks of<br />
words or lines meaningfully, like &#8220;paragraph&#8221; (instead of font size 10)<br />
or &#8220;title&#8221; (instead of font size 30) or &#8220;Emphasis&#8221; (instead of bold). The<br />
engine that process the lyx format decides how the end format will be<br />
stylized according to standard rules. This lets CZ the freedom to change the<br />
style of its HTML pages without actually changing by hand each and every<br />
page. You also have a good mechanism for citations and notes.</p>
<p>I think the cz-tools team should check it up.</p>
<p>[1] <a href="http://en.wikipedia.org/wiki/WYSIWYM" rel="nofollow">http://en.wikipedia.org/wiki/WYSIWYM</a><br />
[2] <a href="http://www.lyx.org/" rel="nofollow">http://www.lyx.org/</a></p>
<p>Thank you.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Anthony Sebastian</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41328</link>
		<author>Anthony Sebastian</author>
		<pubDate>Tue, 16 Oct 2007 18:35:19 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41328</guid>
					<description>Aleta Curry, I believe you have oversimplified.  

You say: "The fact is, you can start an article on CZ by picking a subject, clicking the start article button, typing away, and then hitting SAVE."  That prescription would not help if the article you start has images, citations, color fonts, special characters and tables, just to mention a few items.

I speak from personal experience as well.</description>
		<content:encoded><![CDATA[<p>Aleta Curry, I believe you have oversimplified.  </p>
<p>You say: &#8220;The fact is, you can start an article on CZ by picking a subject, clicking the start article button, typing away, and then hitting SAVE.&#8221;  That prescription would not help if the article you start has images, citations, color fonts, special characters and tables, just to mention a few items.</p>
<p>I speak from personal experience as well.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: David Gerard</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41476</link>
		<author>David Gerard</author>
		<pubDate>Wed, 17 Oct 2007 01:40:19 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41476</guid>
					<description>Stephen, I don't quite see how you get "David defends IRC backrooms as a legitimate part of the governance of WP" from "you do not in any way have to be on IRC to be a productive Wikipedia editor, admin or even arbitrator. And many aren’t and won’t be."</description>
		<content:encoded><![CDATA[<p>Stephen, I don&#8217;t quite see how you get &#8220;David defends IRC backrooms as a legitimate part of the governance of WP&#8221; from &#8220;you do not in any way have to be on IRC to be a productive Wikipedia editor, admin or even arbitrator. And many aren’t and won’t be.&#8221;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Robert W King</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41527</link>
		<author>Robert W King</author>
		<pubDate>Wed, 17 Oct 2007 02:34:17 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41527</guid>
					<description>David- 

Anyone who seriously knows what IRC is really like would never suggest it as a serious conversation environment for anything, let alone real academic and intelligent conversation.</description>
		<content:encoded><![CDATA[<p>David- </p>
<p>Anyone who seriously knows what IRC is really like would never suggest it as a serious conversation environment for anything, let alone real academic and intelligent conversation.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Mike Johnson</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41577</link>
		<author>Mike Johnson</author>
		<pubDate>Wed, 17 Oct 2007 04:02:20 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41577</guid>
					<description>I'm sure part of this disagreement about IRC as a valid context in which to discuss important things stems from Calacanis's framing of the issue, which, though interesting, doesn't strike me as particularly nuanced.</description>
		<content:encoded><![CDATA[<p>I&#8217;m sure part of this disagreement about IRC as a valid context in which to discuss important things stems from Calacanis&#8217;s framing of the issue, which, though interesting, doesn&#8217;t strike me as particularly nuanced.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: David Gerard</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41699</link>
		<author>David Gerard</author>
		<pubDate>Wed, 17 Oct 2007 15:28:55 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-41699</guid>
					<description>In practice it's most useful for administrative tasks or when you have a problem or conflict that needs dealing with right away. But it's not *necessary*.

For editorial tasks, I agree: it's not the right format. But Jason is just wrong in asserting that IRC is an editorial part of Wikipedia.</description>
		<content:encoded><![CDATA[<p>In practice it&#8217;s most useful for administrative tasks or when you have a problem or conflict that needs dealing with right away. But it&#8217;s not *necessary*.</p>
<p>For editorial tasks, I agree: it&#8217;s not the right format. But Jason is just wrong in asserting that IRC is an editorial part of Wikipedia.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Stephen Ewen</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-42040</link>
		<author>Stephen Ewen</author>
		<pubDate>Thu, 18 Oct 2007 08:26:11 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-42040</guid>
					<description>David, perhaps you might need to get a good 'ol pseudonym at WP, lay aside your position at WP, and hang out in the trenches of WP.  &lt;I&gt;IRC is the grease of Wikipedia tribalism.&lt;/I&gt;  Those that do not participate and won't frequently have a very special name: victims, i.e., victims of that tribalism.  Even Jimbo has gotten caught with in unflattering positions trying to call forth the backend troops.

Back to the other matters of Jason's post, I have to say that the more I read over at the MediaWiki wiki, and at the COmmons, and see get poo-pooed all of the feature requests that would make the software &lt;I&gt;easy&lt;/I&gt; to use, the more I think he is right.  Of course, I must confess my skepticism over the fact that much of anything will ever come out of any open source movement that is &lt;i&gt;really&lt;/I&gt; user-friendly.  Why would it be?  The other geeks are their real "customer base".

More and more I feel there simply must be some better option than MediaWiki for collaborative publishing.</description>
		<content:encoded><![CDATA[<p>David, perhaps you might need to get a good &#8216;ol pseudonym at WP, lay aside your position at WP, and hang out in the trenches of WP.  <i>IRC is the grease of Wikipedia tribalism.</i>  Those that do not participate and won&#8217;t frequently have a very special name: victims, i.e., victims of that tribalism.  Even Jimbo has gotten caught with in unflattering positions trying to call forth the backend troops.</p>
<p>Back to the other matters of Jason&#8217;s post, I have to say that the more I read over at the MediaWiki wiki, and at the COmmons, and see get poo-pooed all of the feature requests that would make the software <i>easy</i> to use, the more I think he is right.  Of course, I must confess my skepticism over the fact that much of anything will ever come out of any open source movement that is <i>really</i> user-friendly.  Why would it be?  The other geeks are their real &#8220;customer base&#8221;.</p>
<p>More and more I feel there simply must be some better option than MediaWiki for collaborative publishing.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Doug Holton</title>
		<link>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-56014</link>
		<author>Doug Holton</author>
		<pubDate>Sun, 02 Dec 2007 07:23:10 +0000</pubDate>
		<guid>http://blog.citizendium.org/2007/10/12/wiki-markup-language-what-you-see-is-messy/#comment-56014</guid>
					<description>Definitely you need to enable a WYSIWYG editor.  I'm a phd, using and programming computers for decades, but editing an article with references and so forth is painful.  I learned how to do it by digging all over the site, but I'm probably going to forget it before editing next time.

Also, I just created an article, and had to edit 4 pages to get it to be "correct" - the talk page, the metadata page, and some kind of "Approval" page.</description>
		<content:encoded><![CDATA[<p>Definitely you need to enable a WYSIWYG editor.  I&#8217;m a phd, using and programming computers for decades, but editing an article with references and so forth is painful.  I learned how to do it by digging all over the site, but I&#8217;m probably going to forget it before editing next time.</p>
<p>Also, I just created an article, and had to edit 4 pages to get it to be &#8220;correct&#8221; - the talk page, the metadata page, and some kind of &#8220;Approval&#8221; page.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
