ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: John Haltiwanger <john.haltiwanger@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Seeking a Deeper ConTeXt: Questions for Initializing
Date: Tue, 26 May 2009 17:26:25 -0400	[thread overview]
Message-ID: <4c1f1f860905261426n5c982a04qd3d81c894ca22e63@mail.gmail.com> (raw)
In-Reply-To: <loom.20090526T154839-810@post.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 980 bytes --]

>
>
> In any case, I'd worry less about the technology, and more about what you
> need
> from it. That will make it easier to figure out which approach is best.
>
> Bruce
>
>
>
Markdown with RDFa on the side will suit quite nicely, thanks to pandoc. The
desire for semantical documents sounds like it will be resolved sooner or
later with Tagged PDF. Until then the semantics can reside outside the PDF
in my case. I consider it only a "need" inasmuch as I am an archivist by
archetype, and so the idea of the best looking documents (the PDFs) being
also the most monolithic just goes against my natural grain. For now it is
not an urgency, but I do thank you all for the advice and comments!

The markdown solution is doubly good because now I see a way to incorporate
conTeXt in a web project that centers on language The better rendered the
text, the better the project. Ah, the universal adoption of TeX in
everything I do may not be far off ;)

Regards,

John C. Haltiwanger

[-- Attachment #1.2: Type: text/html, Size: 1311 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
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-26 21:26 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 [this message]
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
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=4c1f1f860905261426n5c982a04qd3d81c894ca22e63@mail.gmail.com \
    --to=john.haltiwanger@gmail.com \
    --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).