public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] How to read ecos docs given in sgml-format
@ 2014-01-15 17:59 Bob Brusa
  2014-01-15 19:09 ` Sergei Gavrikov
  2014-01-20 11:29 ` "Ilija Kocho [Илија Кочо]"
  0 siblings, 2 replies; 3+ messages in thread
From: Bob Brusa @ 2014-01-15 17:59 UTC (permalink / raw)
  To: ecos discuss

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-01-20 11:29 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-01-15 17:59 [ECOS] How to read ecos docs given in sgml-format Bob Brusa
2014-01-15 19:09 ` Sergei Gavrikov
2014-01-20 11:29 ` "Ilija Kocho [Илија Кочо]"

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).