 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nathan Kopp wrote:
> What would be the desired format for MegaPov documentation for Windows and
> Unix?
Plain text (.txt) with references to the included images (if any), and HTML
that incorperates the images with the text.
David
--
Keeper of the family pets.
"You want fish? I got fish. I got fish, and eels, and turtles, and snails, and
frogs, and dragons and cats..."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Bob Hughes wrote:
>
> Win. HTML.
> Couldn't some sort of generic html be made as a single page (file)?
>
I agree. HTML. Anything that can run a web browser can read HTML,
making it almost as universal as plain text, and that way it can
be downloaded or made available online that way (which would allow
for better distribution of updates if needed). All I ask is an
index alphabetized by feature with links to the appropriate
sections. Then in wouldn't matter if the file was all in one or
split by, for example, what patches the features came from.
The only gripe I have currently is I have to rummage around
for a while to find the feature I want to experiment with, but
the actual HTML presentation is just fine.
Charles
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Rich wrote:
> rmu### [at] t-online de (Ralf Muschall) wrote in <388E4B7E.2DAE21BC@t-
> online.de>:
>
> >Nathan Kopp schrieb:
> >
> >> I guess I worded that poorly. I was hoping for answers like:
> >> "I use unix, and I'd like _____."
> >> or
> >> "I use Windows, and I'd like ______."
>
> I use Windows, Amiga, Lynix and Mac. HTML would be my choice above
> all others! <smile> I really don't see how HTML is a bad choice for
> printing. All it takes is a bit of pre-planning; put each page in a fixed
> width table, so the format when printed will look exactly like the format
> on screen, and make sure each page will fit on a printed page.
No
nononononooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
arggggggggggghhhhhhhhhhhhhhh!!!!!!!!!!
Heeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeelp.
Sorry. It's just that fixed width tables in HTML should be avoided at all
costs. You probably don't know how many pixels to set it to match my fonts to
make things work. Also, MSIE does horrible things to font sizes, but Netscape
does not. Also, even MSIE is maybe 10% off on font sizes between Mac and
Windows...
Also, I think HTML is a good choice, but that the crud that MS Word puts out
and calls HTML is not.
--
"My new computer's got the clocks, it rocks
But it was obsolete before I opened the box" - W.A.Y.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ron Parker wrote:
>
> PDF is the thing to use if you're going for printed material and you insist
> on a layout-based format. It supports hyperlinks, it is always the same
> layout, and it has good print quality. Unfortunately, Acrobat's not available
> for the Amiga.
>
I just found a link to a perl library that supports the creation of pdf
documents:
http://www.pdflib.com
It's in a beta state but a very good german computer magazine publisher
made a very good article about it.
Marc
--
Marc Schimmler
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ken wrote in message <388B878C.B511D811@pacbell.net>...
>.txt is fine by me.
What sensible answer.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sun, 23 Jan 2000 15:35:55 -0500, Nathan Kopp <Nat### [at] Koppcom> wrote:
>
>What would be the desired format for MegaPov documentation for Windows and
>Unix?
>
>Available formats to choose from:
>
>WordPerfect
>MS Word 97
>MS Word (simple, read by WordPad)
>PostScript
>PDF (only if I can generate it with free tools)
>HTML (export from MS Word)
>Some other format that I could easily generate from a MS Word file using
>free tools.
ASCII rocks.
--
Cheers
Steve email mailto:sjl### [at] ndirectcouk
%HAV-A-NICEDAY Error not enough coffee 0 pps.
web http://www.ndirect.co.uk/~sjlen/
or http://start.at/zero-pps
5:24am up 1 day, 3:54, 4 users, load average: 2.01, 2.03, 2.00
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
>I develop on a Windows computer. Are there free tools available for me to
>use easily DocBook? Also, the Smellenbergh brothers work primarily on the
>Mac, so free Mac tools are necessary as well.
>
>If that is possible, could you please point me a the general direction to
>get started. I've been to a few websites about DocBook, SGML, and XML, and
>they all provided far too much information to be useful for me (I don't have
>three years to learn a new tool for creating the MegaPov 0.4 documentation.)
>;-) You can email me with your reply or just post it here. I'll get it
>either way.
>
>Otherwise, we'll probably end up using HTML as the primary format and
>converting from that to other formats.
Whatever you end up with producing it'd also be really good if you could
include a zipped up plain text version, it's so versatile and doesn't
require heavy duty software like web browsers.
Call me regresive if you like but I'm moving away from GUI stuff at a
high speed, plain text doesn't get broken or misinterpreted the way
other formats do.
--
Cheers
Steve email mailto:sjl### [at] ndirectcouk
%HAV-A-NICEDAY Error not enough coffee 0 pps.
web http://www.ndirect.co.uk/~sjlen/
or http://start.at/zero-pps
5:24am up 1 day, 3:54, 4 users, load average: 2.01, 2.03, 2.00
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
> I use Windows, Amiga, Lynix and Mac. HTML would be my choice above
>all others! <smile> I really don't see how HTML is a bad choice for
>printing. All it takes is a bit of pre-planning; put each page in a fixed
>width table, so the format when printed will look exactly like the format
>on screen, and make sure each page will fit on a printed page. Use this
>template for every page, and all you have to worry about is what to write,
>not how to format it.
> Hyperlinks are, by far, more important to me than pretty printouts
>anyway. If you want to get fancy, some simple scripts can be created to do
>searches on the HTML pages that will work on any modern browser. But a
>well thought out contents page is fine.
Nothing worse than a helpdesk call caused by someone trying
to print a 60 page document that's using American page sizes.
Please don't inflict this on us.
--
Cheers
Steve email mailto:sjl### [at] ndirectcouk
%HAV-A-NICEDAY Error not enough coffee 0 pps.
web http://www.ndirect.co.uk/~sjlen/
or http://start.at/zero-pps
5:24am up 1 day, 3:54, 4 users, load average: 2.01, 2.03, 2.00
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sun, 23 Jan 2000 15:35:55 -0500, "Nathan Kopp" <Nat### [at] Koppcom>
wrote:
>
>What would be the desired format for MegaPov documentation for Windows and
>Unix?
How about a manpage? <grin>
Peter Popov
pet### [at] usanet
ICQ: 15002700
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Peter Popov <pet### [at] usanet> wrote:
: How about a manpage? <grin>
Not a bad suggestion, after all.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
