[Doc-SIG] Re: text markups
Harry George
hgg9140@seanet.com
Mon, 31 Jan 2000 19:30:19 -0800
Here is some "pod" style encoding, with SDF extensions. The translator
is written in python (this is test01 for that package). It handles
tables, nested lists, table-of-contents and indexes, and links. Output
is to HTML, Latex, and Docbook. Would this be of interest?
=========================================
=include default_cfg.pdx
=cfg
title = test01
desc=hello, world
author = Harry George
author_email = hgg9140@seanet.com
owner = @author@
toc_p=0
=end cfg
=include article_style.pdx
=def greeting = hello
=def expand_p = 0
Hello: @greeting@, world
=def expand_p = 1
Hello: @greeting@, world
Hello. B<hello>, C<hello>, I<hello>, U<hello>.
=for html <FONT COLOR="RED">
This should be red.
=for html <FONT COLOR="BLACK">
and this is back to black.
Here are some escaped chars:
E<lt>, E<gt>, E<amp>, E<quot>, E<lb>.
=center
This is will be centered.
As will this (using a skipped line).
=end center
But not this.
=center
This is will be centered.<BR>As will this (using a break).
=end center
But not this.
======================================
> ------------------------------------------------------------------------
> Today's Topics:
>
> 1. Re: Monty: A structured text syntax idea (Greg Ward)
> `
> ------------------------------------------------------------------------
>
> Subject: Re: [Doc-SIG] Monty: A structured text syntax idea
> Date: Mon, 31 Jan 2000 09:21:01 -0500
> From: Greg Ward <gward@cnri.reston.va.us>
> To: doc-sig@python.org
> References: <3.0.6.32.20000129102716.009cd5c0@gpo.iol.ie>
>
> On 29 January 2000, Sean Mc Grath said:
> > """
> > idea:
> > para:
> > I was editing some text in Python emacs mode the
> > other day.
> > para:
> > I got to thinking how Python mandatory indentation
> > emph:
> > removes
> > much of the need for delimiters
>
> Auughh!!! Shades of troff here. (That's not a good thing.) Newlines
> are a fine delimiter in a programming language, where the semantic
> chunks tend to be on the order of 20-60 characters, and we need all the
> help we can get to guide our eyes. Natural language can have much
> smaller semantic chunks -- eg. emphasized words -- so artificially
> splitting lines so often is a waste of vertical real-estate.
>
> I think I'll wait for whatever Moshe proposes... (I just hope it uses
> something B<sensible> to emphasise text... >grin<)
>
> Greg
--
Harry George
hgg9140@seanet.com