ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: scarso luigi <scarsoluigi@libero.it>
Subject: Re: DocBookInConTeXt customization?
Date: 13 Dec 2002 13:57:21 +0100	[thread overview]
Message-ID: <1039784241.25107.339.camel@luigis.logo.net> (raw)
In-Reply-To: <20021212201146.GB1033@scaprea>

> I agree with this point of view: formatting preferences are expressed
> by customizing style sheets. 

Maybe an example can help: <imagedata> has width and height attributes
that are, in my point of view, formatting preferences:  a user should be
use these and not manipulate the style sheet (for example by imposing a
fit for every image in the style sheet).

But, again for example, variations like bold etc are not into semantic
of docbook: a xml document can use proc.instructions
or role attr. (ex. <para role="bold" >) to carry this informations to
(ConTeXt) engine, but they
still remains specific for that engine with a style sheet and there are
no guarantees  that they will be understand by a different engine.

This actually is a limit of docbook in portability : if a user make a
xml document with a bold specification in somepoint (with role or
proc.instr.)  he may expect that bold will be renderer by every engine,
but it's not true.

Perhaps the questions is how to fill the empties in docbook (infact, we
have got xml element for sectioning, tables, images etc) by a simple way
for a normal user or, put in another way, if a feature is in xml DocBook
you should be use it, if no ask yourself if it's needed and, if yes use
a xml construct (from a standard set)  to signalling this to ConTexT
engine; but in the last case you loose portability.

or not ?


luigi 

  reply	other threads:[~2002-12-13 12:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-08 15:12 Gour
2002-12-08 15:32 ` Bruce D'Arcus
2002-12-08 19:54   ` Gour
2002-12-08 20:38     ` Bruce D'Arcus
2002-12-08 20:48       ` Gour
2002-12-08 21:09         ` Bruce D'Arcus
2002-12-08 21:14           ` Gour
2002-12-09 20:09     ` Simon Pepping
2002-12-10 16:53       ` Gour
2002-12-10 17:04         ` Bruce D'Arcus
2002-12-10 17:49         ` Hans Hagen
2002-12-11 20:46         ` Simon Pepping
2002-12-12 10:34           ` Gour
2002-12-12 11:41             ` Bruce D'Arcus
2002-12-12 12:31               ` Gour
2002-12-12 13:29                 ` scarso luigi
2002-12-12 13:49                   ` Bruce D'Arcus
2002-12-12 14:22                     ` scarso luigi
2002-12-12 20:11                     ` Simon Pepping
2002-12-13 12:57                       ` scarso luigi [this message]
2002-12-13 14:32                         ` Hans Hagen
2002-12-17 20:54                         ` Simon Pepping
2002-12-18 17:42                           ` scarso luigi
2002-12-18 19:56                             ` Simon Pepping
2002-12-19 12:54                               ` scarso luigi
2002-12-19  8:34                             ` Hans Hagen
2002-12-12 20:05                   ` Simon Pepping
2002-12-08 20:46   ` Hans Hagen
2002-12-08 21:16     ` Gour

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=1039784241.25107.339.camel@luigis.logo.net \
    --to=scarsoluigi@libero.it \
    --cc=ntg-context@ntg.nl \
    /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).