From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Bob Brusa <bob.brusa@gmail.com>
Cc: ecos discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] How to read ecos docs given in sgml-format
Date: Wed, 15 Jan 2014 19:09:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1401152127340.4960@foo.bar.baz> (raw)
In-Reply-To: <52D6CC97.9080303@gmail.com>
On Wed, 15 Jan 2014, Bob Brusa wrote:
> Hi,
> the make pdfa4 command that should generate pdfs from sgml when
Hi Bob,
Check first, Do you able to get eCos documentation in HTML format?
(minimal requirements: jade, docbook, docbook-dsssl). Chdir in R/W
directory and type
sh $ECOS_REPOSITORY/../doc/sgml/makemakefile
make html
To get PDF outputs you have to install `jadetex' and its dependencies.
> I could not find an alternative to the above (mean - converting sgml
> to a pdf - sgml in a text editor or browser is ugly). It seems, no
> reasonable reader exists for the sgml format. This lets me wunder why
> the documentation is presented in this now arcane format. Why not
> include these files as open data text (odt) as used by e. g.
> OpenOffice?
I do not think that is good idea to distribute official documentation in
any editable form. More on that, every eCos documentation file warn you
Distribution of substantively modified versions of this document is
prohibited without the explicit permission of the copyright holder.
Distribution of the work or derivative of the work in any standard
(paper) book form is prohibited unless prior permission is obtained
from the copyright holder.
Of course, if you can get HTML, then you would lanch <set>Office, open
any html file and save it in desired format. You would use CL tools to
convert HTML in other texts or blobs using some of the converters, but
read above.
> Well, back to the problem: Has anybody a hint why the sgml to pdf
> fails? Thanks and best regards,
Never try to get eCos PDF on Cygwin. But, I have no problem with PDF
generation under Linux (some not every hour updated release :-) with
jadetex.
HTH
Sergei
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2014-01-15 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 17:59 Bob Brusa
2014-01-15 19:09 ` Sergei Gavrikov [this message]
2014-01-20 11:29 ` "Ilija Kocho [Илија Кочо]"
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=alpine.DEB.2.00.1401152127340.4960@foo.bar.baz \
--to=sergei.gavrikov@gmail.com \
--cc=bob.brusa@gmail.com \
--cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).