From: mok@kde.ru To: Sergey G <cgss@pisem.net> Cc: kde-russian@lists.kde.ru Subject: [kde-russian] KDE book Date: Fri, 18 Jul 2003 23:54:12 +0400 Message-ID: <164182251964.20030718235412@dzogchen.ru> (raw) In-Reply-To: <1341169649.20030716192425@pisem.net> SG> Но вот у меня есть одно принципиальное замечание - N141. Там SG> говориться про критерий Limit. Мне кажеться, что ты ошибся, SG> изменив мой перевод в случае с параметром "!". Ты написал там, SG> что при использовании параметра ! "пакеты будут проходить SG> правило только тогда, когда ограничение не превышено". Насколько SG> я знаю, всё наоборот Посмотрю, спасибо. Вот, почитай свежие новости - чем ты сейчас занимаешься :) Я хочу подключить к этой работе ещё других людей, чтобы этот перевод был готов как можно быстрее. Гриша ======= Hi, I'll now proceed in writing a new KDE development book. Mainly because the old KDE 2 development book sucks in certain kind of ways and through the experience of participating on that book having to use DOC format and other things, I'll start basically from scratch. Any help in proof-reading and later in translation is very welcome. Example code is also nice to have :-) 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 :-) So, target is: FDL-licensed book that can be published on developer.kde.org, covering: - C++ - Qt 3.2 - KDE 3.2 - KDE/Qt development tools, debugging - KDE/Qt translation tools - writing DocBook manuals 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). 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 ? Forgot something: I'd like to have the KDE and Qt API included. I guess the Qt API docs and other docs are tricky because the copyright is with TT - but as Qt is GPL we could as well license the whole book (or the API part of the book which could be a separate book) GPL. The issue is now, how do we get docbook files out of the doxygen generated docs ? Any clues ? BTW: the copyright of the book should be with the KDE e.V. That allows it to continue further even when programmers stopped working on the book and aren't available anymore. Then the KDE e.V. can still publish it. I guess that's in everyone's interest; it should however have an authors section and a credits section like any other KDE program. Ralf Thanks, Ralf -- We're not a company, we just produce better code at less costs. -------------------------------------------------------------------- Ralf Nolden nolden@kde.org The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org
parent reply other threads:[~2003-07-18 19:54 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <1341169649.20030716192425@pisem.net>]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=164182251964.20030718235412@dzogchen.ru \ --to=mok@kde.ru \ --cc=cgss@pisem.net \ --cc=kde-russian@lists.kde.ru \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
рассылка русскоязычной группы пользователей и разработчиков KDE This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/kde-russian/0 kde-russian/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 kde-russian kde-russian/ http://lore.altlinux.org/kde-russian \ kde-russian@lists.kde.ru public-inbox-index kde-russian Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.kde-russian AGPL code for this site: git clone https://public-inbox.org/public-inbox.git