ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Arthur Reutenauer <arthur.reutenauer@normalesup.org>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Seeking a Deeper ConTeXt: Questions for	Initializing
Date: Mon, 25 May 2009 20:21:06 +0200	[thread overview]
Message-ID: <20090525182106.GA27724@phare.normalesup.org> (raw)
In-Reply-To: <4c1f1f860905251109n35ea99d6ib4960f14f24df7ec@mail.gmail.com>

> Nice, glad to hear it. Also of interest are new semantic tagging facilities
> for PDF in the newest proposal for ISO 32000, mentioned by an Adobe engineer
> in the comments of this blog entry
> http://digitalcuration.blogspot.com/2009/04/semantically-richer-pdf.html

  If you mean Leonard Rosenthol's comment at
http://digitalcuration.blogspot.com/2009/04/semantically-richer-pdf.html?showComment=1239112800000#c5624378574116031944
the general issue is Tagged PDF.  It's not really supported yet in any
variant of TeX, but there is an active group working on it at River Valley
Technologies (http://lists.river-valley.com/cgi-bin/mailman/listinfo/tex).
I haven't been following closely, but there's definitely progress.

	Arthur
___________________________________________________________________________________
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:[~2009-05-25 18:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-24 17:17 John Haltiwanger
2009-05-24 18:35 ` Henning Hraban Ramm
2009-05-25 16:30   ` John Haltiwanger
2009-05-25 16:39     ` Hans Hagen
2009-05-25 16:53       ` John Haltiwanger
2009-05-25 16:59         ` Hans Hagen
2009-05-26 15:54       ` Bruce D'Arcus
2009-05-26 21:26         ` John Haltiwanger
2009-05-26 22:08           ` luigi scarso
2009-05-26 23:07           ` Bruce D'Arcus
2009-05-25 16:50     ` Wolfgang Schuster
2009-05-25 17:00       ` John Haltiwanger
2009-05-25 17:12         ` Mohamed Bana
2009-05-25 17:24         ` Hans Hagen
2009-05-25 17:51           ` John Haltiwanger
2009-05-25 18:00             ` Arthur Reutenauer
2009-05-25 18:09               ` John Haltiwanger
2009-05-25 18:21                 ` Arthur Reutenauer [this message]
2009-05-25 18:24                   ` John Haltiwanger
2009-05-25 18:55                 ` Hans Hagen
2009-05-25 21:09                   ` luigi scarso
2009-05-25 21:14                     ` Hans Hagen
2009-05-25 21:16                     ` Arthur Reutenauer
2009-05-25 20:25             ` Mohamed Bana
2009-05-25 21:02               ` John Haltiwanger
2009-05-26 22:27               ` Wolfgang Schuster
2009-05-25 17:23     ` Arthur Reutenauer
2009-05-25 18:26     ` Aditya Mahajan
2009-05-25 18:35       ` John Haltiwanger

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=20090525182106.GA27724@phare.normalesup.org \
    --to=arthur.reutenauer@normalesup.org \
    --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).