AmigaOS 3.1 Command Reference in AmigaGuide format

[modrobert]

Does anyone know where I can find the AmigaOS 3.1 (DOS) command reference in AmigaGuide format?

I found a really good one in HTML format here:
http://www.jaruzel.com/amiga/amiga-o...eference-help/

At the bottom of that page it reads "Converted from AmigaGuide ...", so assuming it originates from AmigaGuide format. I tried contacting the author of that page, but it failed. Also tried searching Aminet but could only find something for AmigaOS 2.x there.

I want to use this on my A1200, so AmigaGuide format is preferred.

[daxb]

You may try some of the html2guide converter on Aminet?

[EctoOne]

Try this https://aminet.net/package/docs/help/wb3guide

[modrobert]

Originally Posted by EctoOne

Try this https://aminet.net/package/docs/help/wb3guide

Thanks! Will check it out.

EDIT:

Unfortunately this only contains a list of the available AmigaDOS commands, not one page with a lot of info for each command like the HTML version I linked previously.

Originally Posted by daxb

You may try some of the html2guide converter on Aminet?

Found two different programs:
https://aminet.net/search?query=html2guide

Will try if any of them can convert this.

[EctoOne]

I found this one https://aminet.net/package/util/wb/Help
It's a bunch of separate files which seem to have additional info. It also comes with a search command/script but I haven't tried it.

[modrobert]

After cleaning up the HTML files a bit in Linux using 'sed' I managed to convert them to AmigaGuide format using this tool on my Amiga:
https://aminet.net/package/util/conv/HTML2Guide-1.2

I have uploaded the result to the Zone.

There is only one of the files with an icon (.info) and that's 'index.Guide' (the 'Index.Guide.info' file expects 'MultiView' in path to read the file). The rest of the '#?.Guide' files don't need be accessed directly.

[EctoOne]

Nice. I took some extra steps and merged all files into one. I can upload it if anyone is interested.

[mfilos]

Sure thing EctoOne

[modrobert]

Originally Posted by EctoOne

Nice. I took some extra steps and merged all files into one. I can upload it if anyone is interested.

Yes, please upload. Also, out of curiosity, how did you merge them (tools used)?

[EctoOne]

It was mainly some string replacement to make the links internal.
Then I removed the first two lines of the subfiles to not make them guides anymore.
And then I appended each subfile to the Index.

I included a small script with links to the two additional tools I used.

Edit: Just a note, the script probably won't work with other guides.

And it might actually be possible to delete the first two lines with Rep and LISTs %m attribute instead of using an extra tool. But whatever.

Edit: I was bored and changed the script to only require Rep.

[modrobert]

Originally Posted by EctoOne

It was mainly some string replacement to make the links internal.
Then I removed the first two lines of the subfiles to not make them guides anymore.
And then I appended each subfile to the Index.

I included a small script with links to the two additional tools I used.

Edit: Just a note, the script probably won't work with other guides.

And it might actually be possible to delete the first two lines with Rep and LISTs %m attribute instead of using an extra tool. But whatever.

Edit: I was bored and changed the script to only require Rep.

Thanks, works fine, better with one AmigaGuide file as opposed to over 100.

[EctoOne]

It depends. I'm using KarmaHelp which auto generates an index file for documents. Having separate files skips showing an extra index.
I just combined it to keep it stored somewhere else.

And I prefer using the guide files over the text files from the help package I linked because they look better. The text files aren't formatted properly.

[modrobert]

Originally Posted by EctoOne

It depends. I'm using KarmaHelp which auto generates an index file for documents. Having separate files skips showing an extra index.
I just combined it to keep it stored somewhere else.

And I prefer using the guide files over the text files from the help package I linked because they look better. The text files aren't formatted properly.

I see what you mean, e.g. to do something like 'man list' on the command line, where 'man' is a simple script, it's useful to have the one ".Guide" file for each command.