From: wd@denx.de (Wolfgang Denk)
To: linux-arm-kernel@lists.infradead.org
Subject: [Celinux-dev] PDF documentation
Date: Tue, 16 Oct 2012 16:35:22 +0200 [thread overview]
Message-ID: <20121016143522.086F2204292@gemini.denx.de> (raw)
In-Reply-To: <CAE7jHC83biZy7TNYSr+-X85tpenqtAHuwSO47Q-6+XRF0fUxLA@mail.gmail.com>
Dear Constantine Shulyupin,
In message <CAE7jHC83biZy7TNYSr+-X85tpenqtAHuwSO47Q-6+XRF0fUxLA@mail.gmail.com> you wrote:
>
> I have some questions and ideas about documentation in PDF format.
> During embedded SW development I often work with documentation,
> especially datasheets in PDF format. I have some issues with such
> documentation. It is not so easy to manage a lot of PDF documents
> sometimes with strange code in file names. It is not easy to store
> and share links to documentation.
PDF has a lot of advantages in many situations, but I agree that it is
also non-perfect for many other use cases.
> Questions:
> - have same issues with PDF documentation and datasheets?
> - do you think documentation and datasheets in HTML format on a site
> can be more useful than PDF?
HTML is really useful in a web browser only.
For documentation of the U-Boot boot loader we use a very different
approach: documentation is created, stored and edited in a wiki
(using FosWiki, see http://foswiki.org/). This has the advantage that
you can make it either easily editable to the community, or put
arbitrary access restrictions to it by using wiki user / group access
permissions. In combination with some plugins (like TocPlugin,
BookmakerPlugin and PublishPlugin) we can then "linearize" the entries
in the wiki to generate a "book" which can be read both online (as
HTML) or offline (by publishing the content as a linerarized, single
HTLP, plain text, PDF and/or PostScript document).
To give you a feeling how this works, please see for example
http://www.denx.de/wiki/view/DULG/Manual?stickboard=m28
http://www.denx.de/wiki/publish/DULG/DULG-m28.html
http://www.denx.de/wiki/publish/DULG/DULG-m28.ps
and http://www.denx.de/wiki/publish/DULG/DULG-m28.pdf
[Actually this documentation does much more behind the scenes; all
examples in this documentation come from include files which are
automatically generated from our regression test suite (DUTS); so the
procedure is to come up with a new software version, run the test
suite over it, upload the generated log files to the web server, and
voila, there is a new version of the documentation matching exactly
the new software version.]
And the nice thing is: all this is based on free software only...
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
One difference between a man and a machine is that a machine is quiet
when well oiled.
next prev parent reply other threads:[~2012-10-16 14:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 13:22 PDF documentation Constantine Shulyupin
2012-10-16 13:57 ` [Celinux-dev] " Bill Traynor
2012-10-16 14:05 ` Peter Stuge
2012-10-17 13:24 ` Constantine Shulyupin
2012-10-17 16:51 ` Peter Stuge
2012-10-17 19:26 ` Constantine Shulyupin
2012-10-17 22:04 ` [Celinux-dev] " Tim Bird
2012-10-17 22:29 ` Constantine Shulyupin
2012-10-17 22:19 ` Russell King - ARM Linux
2012-10-17 22:25 ` Peter Stuge
2012-10-17 22:29 ` Russell King - ARM Linux
2012-10-17 22:40 ` Peter Stuge
2012-10-18 5:20 ` [Celinux-dev] " Geert Uytterhoeven
2012-10-16 14:35 ` Wolfgang Denk [this message]
2012-10-16 18:32 ` Tim Bird
2012-10-17 10:12 ` Wolfgang Denk
2012-10-17 13:36 ` shiraz hashim
2012-10-16 14:45 ` Mikael Pettersson
2012-10-18 13:27 ` Alexander Holler
2012-10-18 13:55 ` Jon Loeliger
2012-10-18 14:00 ` Grant Edwards
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=20121016143522.086F2204292@gemini.denx.de \
--to=wd@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).