[REBOL] Re: RFC: make-doc-pro feature / glossary
From: nitsch-lists:netcologne at: 10-Jun-2002 14:40
Am Montag, 10. Juni 2002 10:32 schrieb Robert M. Muench:
> > -----Original Message-----
> > From: [rebol-bounce--rebol--com] [mailto:[rebol-bounce--rebol--com]]On Behalf Of
> > Volker Nitsch
> > Sent: Friday, June 07, 2002 6:35 PM
> > To: [rebol-list--rebol--com]
> > Subject: [REBOL] Re: RFC: make-doc-pro feature / glossary
> > i read a paragraph and think - hmm, is this a well known word?
> > and then describe it better. so i would like to have the special glossary
> > close. the "\glossary" needs a lot lines.
> > glossary?: an explanation of words.
> > paragraph?: a piece of related text.
> So your usage pattern is to put the glossary? stuff somewhere in the script
> and don't collect it in a special place? That makes sense as it follows the
> old C++ rule "declare just before first usage". I like it this way.
it could save clicks, and verifying which words have/need definitions.
> > I use make-doc primarily as text, with translation only occasianally.
> Really? Just for yourself or if you communicate with others too?
hmm.. i am not communication that much.
when, mostly email, which is text.
here i am starting marking headlines with "===" :)
also there are some RT-documents, partly text, partly html.
if carefull written, i can read text better.
> > it opens faster, i always change something and so on.
> I know, with IOS I thought about an desktop extension wherer you can edit a
> MDP file and get the translation automatically synced to all users. The
> source-code could only be on your system, or on the user's system that need
> to change the text as well. Robert
i would publish text too.
so its possible to write comments directly into the document.
then ios works similar to a wikki.
another point is, i am using an editor-extension
which collects "==="-lines in a text-list and finds them in editor on click.
similar to an html-index-frame, but with zero writing-effort.
suddenly using large text is pretty quick.
(unfortunally standalone, not plugged into desktop-editor)
so to me using text not only as source is an valid option.