Quote
Originally posted by Tarnćlion Andiyarus:
**Not 'read' as in 'open', 'read' as in 'read'. He's commenting upon how hard it is to actually read the text in a PDF file, probably due to the fact that you have to zoom each file individually to read it properly. At least, I think that's what he means.:)
-Andiyar
**
OMG the horrors of having to use the magnifying glass tool!
Seriously, as long as we're on the subject, let me offer this piece of advice. When it comes time for you (you meaning everyone, not just the person I'm quoting above) to release your first CS game, you will want some kind of documentation. For a lot of people, this document will become their first impression of what you've created, therefore the more professional looking the document is, the greater the chance that your audience will react enthuastically to what they've just downloaded.
Anything longer or more involved than a simple progress log should be done in something more sophisticated than a simple text document. Web savy people should be able to create a very nice html formated manual full of graphics and links to take the reader anywhere he wants to go quickly. For the rest of us, (like myself) creating a PDF document is a good alternative.
When making these documents, remember that the details count. Don't spend six months or a year making a game and then only devote half and hour to the documentation. Proofread everything several times, make sure you have no spelling or grammar mistakes. And for the love of all that right and good, please please please use a front that is readable -- do not write a 20 page manual in Old English Text! For that matter, don't use an ugly system font like Geneva either. Nice serif fronts like TimesTen, Palatino, Caslon, and Veljovic are the easiest on the eyes for large bodies of text.
(/endrant)
------------------
--
Mauglir