World: r3wp

so I can say that each of them have is own duty asigned MD2 to release 
quick and not very very sofisticated text MDP for articles with more 
sophistication in it ...

NicomDoc is a step over this two that's sure but it's heavyly using 
html capabilities and adapting this to VID HUM HUM HUM

With actual parse token statement it's very hard ...

you can Dl it on http://rebol.dev.fr/view.php?sid=140(actual version 
is 1.3.3 see rebol script header for changelog )

GRaham note that I don't say I'm not interrested on making NicomDoc 
quick and easy editor but this format has too a lot of things to 
make a VID parse writer mad hehehehe or maybe I'm not enought skilled 
...

Its good to have competing mark-up languages ... they can all gain 
by learning from the strengths of the others.

HTML and VID are such different concepts that you can't easily start 
from a single "higher" dialect and make full use of both VID and 
HTML

MakeDocX {x=2 or Pro or blank)  gives you very little comtrol over 
the emitted HTML -- so it is less powerful but more generic....hence 
thoughts of PDF and other emitters.

NicomDoc is more powerful as a HTML generator but, as shadwolf says, 
not nearly so easy to VID....Though let's give it time to develop: 
it's only days old.

Mulch (my dialect) gives you total control over the HTML and CSS 
with almost zero chance of a VID version being possible..... http://www.rebol.org/cgi-bin/cgiwrap/rebol/boiler.r?display=mulch-help

Color Text (Rich Text). One week ago I talked to Carl here about 
various topics and reminded him of rich text, he said it is important, 
so I put together few notes we produced in the past and he noted 
that he has something slightly different in mind and that he may 
say publicly something to it, so let's hope he will do so ...

Pekr for coloring I think perf is vital

good perf are dependant of the main process performance

in actual way we have to parse the MDX(retake of sunanda notation 
see up)  file then create a page with will content style and data 
to so in this operating way making complicate conposing like a heavy 
colored text or a content linked table of content (=toc) will include 
a new parsing statement in the parsing statement this will increase 
a slow rendering process

New MDP-GUI version 1.3.4  you can down load it there --> http://rebol.dev.fr/view.php?sid=143

MDP-GUI v1.3.4 include a remade IHM a bug correction and the rendering 
of the list of content

I know that I'm making every day a new realease of an unstable project 
but this helps me to figure out for eventual bugs...

and this helps you to see what direction the MDP-GUI project is taking 
I hope this 1.3.4 version will be at your taste. :)

Okay, I downloaded makedoc2 from rebol.org the other day and I still 
haven't figured out how to create links. In makedoc all you did was 
"url=http://www.rebol.com"REBOL" " but that just shows up as text 
in makedoc2. Could you help me out?

I don't think you can in MakeDoc2.

Darn.

But the HTML tag <a> should work.

So, I could just edit the HTML file and add it afterwards?

Yes, or write <a href="http://www.rebol.com">REBOL</a>in your text.

It automaticly executes HTML?

Well, it just take it over to the output without processing it in 
any way, so it should work.

Nice. I didn't know that.

Like if you wanna write something in bold, you use <b>bold</b>.

Ah. This is where it pays off to know basic HTML. :)

:)

Thanks! I'll have to do that.

Problem is, if you wanna build a system to have other output than 
HTML.

True. That would be a little more difficult.

What about layouts? Do those work the same?

I've written a MakeDoc2 summary. Look here: http://home.tiscali.dk/john.niclasen/nicom-md2-spec.html

Cool. Now I have a reference!

Thanks again.

You're welcome!

Geomol is right I had to add the parsing of =url flag into the Ashley 
MD2-IDE rendering process to adapt it to the MDP format

I'm going on skivacation for a week, but I desided to put my work 
so far on the NicomDoc document format up on my website. It's NOT 
version 1.0 yet, so some features are not supported. I'll write a 
short specification in a moment.


Parsing a NicomDoc document to HTML goes in two passes, first the 
raw document is converted to RebXML format. This is done by this 
script:
http://home.tiscali.dk/john.niclasen/nicomdoc/nicomdoc.r


Next the RebXML version is converted to HTML. This is done with this 
script:
http://home.tiscali.dk/john.niclasen/nicomdoc/rebxml2html.r


I've also made a little script, that will do the whole conversion 
in one go by calling the other scripts. It works much like calling 
makedoc2.r, and it can be found here:
http://home.tiscali.dk/john.niclasen/nicomdoc/ndoc.r


Those of you, who want to work with this format, e.g. make VID output, 
should work from the RebXML version of the document (after first 
parsing from raw document to RebXML with the first script), because 
this script handle all the complicated rules, so the RebXML version 
is much easier to work with.

Specification here: http://home.tiscali.dk/john.niclasen/nicomdoc/NicomDoc.html

Example of use: http://home.tiscali.dk/john.niclasen/nicomdoc/example.txt

And the output: http://home.tiscali.dk/john.niclasen/nicomdoc/example.html

Notice! As this is not version 1.0 of NicomDoc, some things will 
probably change. The namespace might change. Example: I use 'p' for 
paragraph in the RebXML version to make it short (also if someone 
wants to make XML output, which is bloated), but I might change it 
to have a more saying name for a paragraph. And URL keyword might 
go away and be replaced by a more general term like a reference.

It's of course possible to make XML output of a NicomDoc document 
by first parsing it with nicomdoc.r and then use http://home.tiscali.dk/john.niclasen/rebxml/rebxml2xml.r
on the RebXML version. And back again with http://home.tiscali.dk/john.niclasen/rebxml/xml2rebxml.r

wikiDoc = makeDoc with dokuwiki syntax; 
http://www.rowery.olsztyn.pl/wspolpraca/rebol/wikiDoc/

and wiki rendering like to ... it's closer from IRC or chat or web 
php/forum it include Smyleys ;)

It could be included to rebforum work  As soon we restart working 
on it ... we are waiting for rendering  for Ritch Text enhancement 
 (TDM) to rework on it

I love the way makedoc2.r shows the out of place markups...so you 
can see why something didn't work...for example, if you do a # without 
the para...it shows the out of place # in the html

makes it REAL easy to fix ML typos.

has there been any ways suggested with making colspans in tables? 
otherwise I would suggest a:

\colspan

col1

col2

col3

/colspan


tag. Just build the table as normally and enclose the columns you 
want in a specific row with those tags.

It's tricky to make tables easy to produce for the writer, and at 
the same time give opportunities to have colspan and rowspan. And 
do we have the need to have tables within tables? That'll just make 
it even more complicated. I guess, learning by doing is a good way 
to figure it out. (That's one idea behind my NicomDoc format. To 
try things out.)

I suggested this, if tables were to continue with their current syntax 
in makedoc2. The syntax has the advantage, I think, that cell contents 
can be complex or almost an entire document in itself, but bigger 
tables are hard to overview in text. I don't think this tag will 
cause the current method to become that much more complex.

Do one knows why "=url" is not part of makedoc 2.6 (nor 2.5) ??

you can inline the HTML, I discovered...

sure but why the =url as been retire for it ? it simplifies the creation 
of links