Starrett's FAQ

I notice that John Starrett has put his "guitar refretting" FAQ in
the FILES section of the Tuning List in TWO versions.

This seems like a great idea... There's BOTH the text version AND
the webpage, so the editor can use BOTH... one for the HTML tree and
the other text FAQ, of course, for the ascii...

Oh... I'm sure everyone has seen that in the FILES section, all the
FAQs, naturally, go under the directory FAQ... That's pretty obvious.

Thanks, John! It looks great!

__________ _______ _____ _
Joseph Pehrson

Hi John, and Joseph

> I notice that John Starrett has put his "guitar refretting" FAQ in
> the FILES section of the Tuning List in TWO versions.

> This seems like a great idea... There's BOTH the text version AND
> the webpage, so the editor can use BOTH... one for the HTML tree and
> the other text FAQ, of course, for the ascii...

Yes, that's great.

I'm now planning to have an ascii tree as well as an html one for the
on-site tree.

If you do two versions of a file, then the program doesn't need to convert
them, and can just put the appropriate one in the appropriate tree.

It will show just the html one in the work in progress tree (or could
do both, but I think that will work best)

This can all be completely automatic. When parsing the database to make
it into the trees, and to decide where all the files are to go on the site,
it will detect that there are two names with the same author and file name
one with extension .txt (or optionally, no extension) and one with extension
.htm

So it will easily figure out where they need to go.

However, it needs to know about the files to put them into the tree.

So, could you do entries for both?

The table headings were a bit unclear, and I've changed the first two
to

Parent folder | Short descr. for new entry or child folder

The first field needs to be an appropriate folder for it to go in
- e.g.
Microtonal Instruments
(say)

Then the description, exactly as you have it in the table.

Then for the url you need to give the url to the file in
the files area.

This url is used verbatim in the data file for the "work in progress" tree,
and will be used by the program for ftp when it needs to find the original file
in order to make the on-site trees.

I'll wait until you've done that before updating the "work in progress" tree,
to make it as much as possible like the real thing.

Thanks!

Robert

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

/tuning/topicId_19750.html#19754

> Hi John, and Joseph
>
> > I notice that John Starrett has put his "guitar refretting" FAQ in
> > the FILES section of the Tuning List in TWO versions.
>
> > This seems like a great idea... There's BOTH the text version AND
> > the webpage, so the editor can use BOTH... one for the HTML tree
and the other text FAQ, of course, for the ascii...
>
> Yes, that's great.
>
> I'm now planning to have an ascii tree as well as an html one for
the on-site tree.
>
> If you do two versions of a file, then the program doesn't need to
convert them, and can just put the appropriate one in the appropriate
tree.
>

> It will show just the html one in the work in progress tree (or
could do both, but I think that will work best)
>
> This can all be completely automatic. When parsing the database to
make it into the trees, and to decide where all the files are to go
on the site, it will detect that there are two names with the same
author and file name one with extension .txt (or optionally, no
extension) and one with extension .htm
>
> So it will easily figure out where they need to go.
>
> However, it needs to know about the files to put them into the tree.
>
> So, could you do entries for both?
>

Hi Robert. If I'm not mistaken, John Starrett's FAQ entry uses a
directory that has a space... so we're getting Guitar%20Refretting
and so forth, and I believe you said you CAN'T use that, correct??

John will have to change that directory and put an underscore in it,
correct?? I have no access to his directory, so I can't do it
myself... so until John does that we can't make a URL link...

Unfortunately, I'm not following AT ALL your system of ascii
references using "$". It seems inconsistent, but it may be that I'm
just not "getting" it. Is there another way of explaining it a bit
more "gently..."?

Thanks!

______ _____ ____ _
Joseph Pehrson