From: Bob Brusa <bob.brusa@gmail.com>
To: ecos discuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] How to read ecos docs given in sgml-format
Date: Wed, 15 Jan 2014 17:59:00 -0000 [thread overview]
Message-ID: <52D6CC97.9080303@gmail.com> (raw)
Hi,
the make pdfa4 command that should generate pdfs from sgml when launched
in ..opt/ecos/doc/sgml/user-guide produces a long list of errors only.
Here is an excerpt:
jade:introduction.sgml:154:19:E: element "PRODUCTNAME" undefined
jade:introduction.sgml:156:5:E: element "PARA" undefined
jade:introduction.sgml:156:18:E: element "PRODUCTNAME" undefined
jade:introduction.sgml:159:20:E: element "PRODUCTNAME" undefined
jade:introduction.sgml:161:5:E: element "PARA" undefined
jade:introduction.sgml:161:18:E: element "PRODUCTNAME" undefined
jade:introduction.sgml:172:22:E: element "PRODUCTNAME" undefined
jade:introduction.sgml:176:13:E: element "PRODUCTNAME" undefined
jade:introduction.sgml:177:35:E: element "PRODUCTNAME" undefined
jade:introduction.sgml:180:13:E: element "PRODUCTNAME" undefined
jade:introduction.sgml:181:20:E: element "PRODUCTNAME" undefined
jade:introduction.sgml:182:9:E: there is no attribute "LINKEND"
jade:introduction.sgml:182:25:E: element "XREF" undefined
jade:introduction.sgml:184:5:E: element "PARA" undefined
jade:introduction.sgml:185:13:E: element "PRODUCTNAME" undefined
jade:introduction.sgml:191:13:E: element "PRODUCTNAME" undefined
jade:introduction.sgml:193:13:E: element "PRODUCTNAME" undefined
and finally it outputs:
jade -o ecos-user-guide-a4.tex -t tex -V tex-backend -d
../../../packages/pkgconf/ssa4.dsl#print user-guide.sgml
../../../packages/pkgconf/rules.doc:143: recipe for target
'ecos-user-guide-a4.pdf' failed
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?
Well, back to the problem: Has anybody a hint why the sgml to pdf fails?
Thanks and best regards,
Robert
--
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 reply other threads:[~2014-01-15 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 17:59 Bob Brusa [this message]
2014-01-15 19:09 ` Sergei Gavrikov
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=52D6CC97.9080303@gmail.com \
--to=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).