ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: MkIV and DVI output
Date: Sat, 12 Apr 2008 09:13:07 +0200	[thread overview]
Message-ID: <48006103.9030000@wxs.nl> (raw)
In-Reply-To: <fe8d59da0804110910t2bf283f6v1c7074e92d398bad@mail.gmail.com>

luigi scarso wrote:
> On Fri, Apr 11, 2008 at 5:36 PM, Hans Hagen <pragma@wxs.nl> wrote:
>> luigi scarso wrote:
>>  >>  at some point i will redo the backends, but i wonder if it really makes
>>  >>  sense to support dvi any longer; i'd rather prepare for future formats
>>  > xps ?
>>
>>  mars
> A very nice subject to discuss here at pdf/a conference with Leonard Rosenthal
> (why use a pdf format for archiving, and in the same moment push mars?
> mars can be  XML->PDF->XML)
> But I did'nt want to do that.
> I have talkd last year in italy with Olaf Drümmer, he said the mars is
> still an experiment .
>  From my point of view xml is better for long term archiving.

xml is to bulky for an output format (apart from the slower parsing), so 
  i wonder if it is that good as format for final products; of course 
xml may be handier to manipulate afterwards (which is something we 
somethines need to do with third party inclusions) but that can be 
crippled by encriptions, compression etc; in my opinion xml should be 
readable and this somewhat conflicts with compression and binary chunks 
(fonts) and encryption etc .. in that case one gets angle brackets 
instead of objects and the rest stays the same (a bit comparable with 
svg, which just packages huge amounts of path info in attributes (kind 
of rediculous to use attributes for that); xml is nice, but nor for 
everything

we'll see

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-04-12  7:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11  9:28 Wolfgang Schuster
2008-04-11  9:45 ` Hans Hagen
2008-04-11 14:34   ` luigi scarso
2008-04-11 14:55     ` Martin Schröder
2008-04-11 23:20       ` luigi scarso
2008-04-11 15:24     ` Olivier Guéry
2008-04-11 16:04       ` Taco Hoekwater
2008-04-12  7:16       ` Hans Hagen
2008-04-12 10:43         ` Olivier Guéry
2008-04-11 15:36     ` Hans Hagen
2008-04-11 16:10       ` luigi scarso
2008-04-12  7:13         ` Hans Hagen [this message]
2008-04-13 13:01   ` Mojca Miklavec
2008-04-14  9:06     ` Wolfgang Schuster

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=48006103.9030000@wxs.nl \
    --to=pragma@wxs.nl \
    --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).