Is being worked on at the wiki: http://www.haiku-os.org/wiki/index.php?title=HaikuUserBook
If you can find the time to contribute, that would be great. There’s also Haiku (Developer) Book, for the more development orientated among us.
"User Book" looks a bit wrong. "User Manual" is better,
but it sounds a bit too technical. "Guide" is more friendly.
I suggest naming them "The Haiku User’s Guide"
and “The Haiku Developer’s Guide”.
Let’s not cling to a “BeBook”-ish name for nostalgic reasons, unless it works.
(The BeBook name worked, in its context of the BeOS and the BeBox.)
In everyday conversations you could call them the useguide and the devguide, or "the guide(s)".
(If you hate spelling things out.)
When you go to a bookstore to find out about a subject, you usually look for a ‘handbook’.
So:
Haiku Users Handbook
Haiku Developers Handbook
Purposeless wrote:
When you go to a bookstore to find out about a subject, you usually look for a 'handbook'.
Depends on how much you want to find out about a subject. I would get a handbook only if I needed to reference something.
Let’s check my Webster Dictionary:
handbook - a book capable of being conveniently carried as a ready reference
guidebook - a book of information for travelers
manual - a book that is conveniently handled
guide - something that provides a person with guiding information
book - a long written or printed literary composition
In my opinion,
Haiku User Manual
Haiku User Handbook
Haiku User Guidebook
Haiku User Guide
are all appropriate. Most people are only going to us it as a reference. I have yet to see somebody read through a whole user manual.
However, if the second is to be more than a reference. That somebody could learn to program for haiku by reading the entire thing. I would say it should either be
Haiku Developer’s Guide
Haiku Developer’s Book
I prefer Guide on that one since it could also be used as a reference. It sounds to me, using the term "Guide" is a happy medium between all the terms. The big question I have is how these terms are used in other countries.
Quote:
The big question I have is how these terms are used in other countries.
This is a very important point. Do we have anyone who can elaborate on this?
jonas.kirilla wrote:
"User Book" looks a bit wrong. "User Manual" is better, but it sounds a bit too technical. "Guide" is more friendly.I suggest naming them "The Haiku User’s Guide"
and "The Haiku Developer’s Guide".Let’s not cling to a "BeBook"-ish name for nostalgic reasons, unless it works.
(The BeBook name worked, in its context of the BeOS and the BeBox.)In everyday conversations you could call them the useguide and the devguide, or "the guide(s)".
(If you hate spelling things out.)
I prefer manual for the user ____ and Guidebook or Handbook for the Developer _____.
So what is the verdict?
Should we have a poll?
We need to move forward on this.
:!:
Haiku: How To.
noisetonepause wrote:
Haiku: How To.
I suggest UserGuide and Handbook as actual names for the pages. Links can be more elaborate, like this;