[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: new KDE Development book
From:       Alex <suy21 () lycos ! es>
Date:       2003-07-18 14:46:15
[Download RAW message or body]

El Viernes, 18 de Julio de 2003 08:01, Ralf Nolden escribió:
> As I haven't taken care of any publisher who'll do hard prints I guess
> that'll come over time. The License for the book will be the GNU Free
> Documentation License, which is because my manuals in KDevelop were GPL
> licensed and I had to buy myself a hard copy of my own work. Which sucked
> as well :-)

In my opinion, GPL is a better license for a technichal book. FDL has some 
points that are thought to protect opinions of the author, and that make it 
"not so free" for some purposes (you know, those threads in debian-legal).

If you decide to license as GPL, I can afford paying a copy for me, and 
another for you ;-).

> - C++
> - Qt 3.2
> - KDE 3.2
> - KDE/Qt development tools, debugging
> - KDE/Qt translation tools
> - writing DocBook manuals

That sounds simply great :-). Covering C++ will be difficult, but I suppose 
you will write only about the relation between Qt and C++ (use of new and 
delete, inheritance, etc.).

Translation, maybe is less important. I know some non-programmers who are 
translating without any problems. Preparing an application for translation, 
is different; that is important, of course.

> Specifically the book will cover KDevelop 3 as well as one big chunk of it
> so we can reuse the book for the KDevelop manuals and ship it with KDevelop
> directly (even though the debian package for the book will end up in
> non-free, see recent discussions about the FDL).

What a pity :-(, but hey, it's your work, license as you like ;-).

> For the book to come forward, I'll use docbook myself and I would like to
> re-use Lauri's docbook manuals on how to write good documentation. The
> question is: where to put the docbook files so we have a buildsystem around
> it and can have anyone participate in writing it so we can use CVS plus
> when certain chapters are finished translators can translate it, and how we
> get it published directly during the process of writing it on
> developer.kde.org so anyone can review the book and send in patches ?

What's wrong with KDE's or Kdevelop's CVS? If don't, what about a project in 
sourceforge or BerliOS?

IIRC, with docbook you can use several files, and with a Makefile, create a 
HTML output.

Best regards.

-- 
Alex (a.k.a. suy) - GPG ID 0xAA8D2A01
http://lacurva.net/ - Jabber ID: suy@es.tipic.com
<Tali> be vewwy vewwy qwuiet .. I'm huntin wuntime ewwos

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]