public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "\"Ilija Kocho [Илија Кочо]\"" <ilijak@siva.com.mk>
To: bob.brusa@gmail.com, ecos discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] How to read ecos docs given in sgml-format
Date: Mon, 20 Jan 2014 11:29:00 -0000	[thread overview]
Message-ID: <52DD0898.3080308@siva.com.mk> (raw)
In-Reply-To: <52D6CC97.9080303@gmail.com>

Hi Bob

I have a little comment on your remark regarding SGML format used by
eCos documentation (AKA DocBook).

On 15.01.2014 18:59, Bob Brusa wrote:
>
>
> 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?

It may look arcane to you, but it's widely used ref: http://docbook.org
(though it would have been better if it was XML version).
I would encourage you to try editing some eCos doc page (or even produce
your own). It's not so hard, and you'll see the first advantage vs some
kind of Office - you can use your favourite text editor. Other advantage
is ability for versioning with common version control system. You'll
discover more once you try it.

Regards

Ilija

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      parent reply	other threads:[~2014-01-20 11:29 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
2014-01-20 11:29 ` "Ilija Kocho [Илија Кочо]" [this message]

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=52DD0898.3080308@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --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).