Re: Ascii bookmarks

Hi Joseph

All the entries can get an ascii number according to the position
in the tree, and later, John will be able to re-arrange
the folders, and the numbering system will change accordingly.

That's automatic, don't have to do anything.

For longer articles, with subsections, one needs a way to
extend the system into it.

To mark your article as one with subsections, place
$.$.$ at the head of the page.

Then whenever you have a section heading, such as
1.2.4.
or whatever
prefix it with $.

$.1.2.4.

Whenever you refer to a section, use
$$1.2.4

e.g.
See $$1.2.4

Now, suppose you have gaps in your numbering system:

1.2.3
1.2.5
1.4
1.6

or something

If you do them as
$.1.2.3
$.1.2.5
$.1.4
$.1.6.1
$.1.6.2

then the gaps can be filled in by changing all the numbers
like this
$.1.2.3
$.1.2.4
$.1.3
$.1.4.1
$.1.4.2

That's possible to do, just by checking the number of dots in each
section label.

If you want to leave any gaps in the numbering system,
place
$.$.ok

at the head of the file

If you need to use any of these sequences in the file to mean something
else, such as in an ascii diagram, you can switch the numbering of
sub sections off using

$$off

then on again using

$$on

Also with a large article, it might be useful to have the whole process
automated, especially if you often insert or remove sections.

In that case, it might be useful to use ascii bookmarks instead.

They work just like the section headings, but you use, say,
$.trines

where you would have
$.1
before.

If you want it to be a second layer of nesting down in the numbering system,
use
$.$.trines

and so on.

To refer to it, use $$trines,

One could refer to it as $$.$.trines, but the short form seems better, as
then you can change it's level of nesting without changing all the links
to it.

Either will work - when evaluating whether two bookmarks are the same,
the program can just ignore any $.$. prefixes in either.

Is this perhaps clearer?

Say if you can anticipate anything about it that might be
tricky to use, or have any ideas for it.

Plus if one is thinking of using this system, one could try it out on a
few shorter articles first and see how it turns out, before trying
it on something more extensive.

Again, test of system will be when a few docs.have been ascii numbered,
and we will see how it is working.

Robert

--- In tuning@y..., "Robert Walker" <robert_walker@r...> wrote:

/tuning/topicId_19782.html#19782

>
> Is this perhaps clearer?
>
> Say if you can anticipate anything about it that might be
> tricky to use, or have any ideas for it.
>

This explanation is absolutely clear. So far, the articles in the
FILES section are pretty short, but, I imagine if Margo Schulter
submits something, we can try out this ascii reference system...

Thanks again!

______ _____ ____ _
Joseph Pehrson