ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: getting inside xhtml / mkii
Date: Thu, 15 May 2008 15:52:35 +0200	[thread overview]
Message-ID: <115224fb0805150652r52668c00h24d68e06661ed646@mail.gmail.com> (raw)
In-Reply-To: <482C3A27.9000304@jhnet.nl>

On Thu, May 15, 2008 at 3:27 PM, Jelle Huisman <jelle@jhnet.nl> wrote:
> Wolfgang Schuster wrote:
>> You're misusing the div element for something it is not meant, could
>> you use h1 ... elements in your html and map them to ConTeXt's own
>> header commands.

> Yes, I know that the xhtml is not very nice (if only I could write my
> own xml...) The situation is that I get this file from a customer and I
> want to avoid having to reformat it (for compatibility reasons). That's
> why I try to make it work, but it seems I'm out of luck here... :-(

It's not impossible but a pain to achive with MkII, I made a example
but it did not really woth because the XML-Environment for div is
overloaded with the first chapter and you will loose the selection dependent
on the value for class.

\defineXMLenvironment [div] [class=]
  {%\bgroup
   \processaction
     [\XMLpar{div}{class}{}]
     [letHead=>\def\next{\defineXMLargument[div]{\chapter}}]%
   \next}
  {%\egroup
   }

\starttext

\startXMLdata
<body class="dicBody">
  <div class="letHead">
    <div class="letter">A a</div>
  </div>
</body>
\stopXMLdata

\stoptext

If you want to do this project you should consider switching
to MkIV with it's XML setups, they are more powerfull in this
case and sometimes easier to write.

Wolfgang
___________________________________________________________________________________
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-05-15 13:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08 21:32 Jelle Huisman
2008-05-08 21:55 ` Hans Hagen
2008-05-09  8:59   ` Jelle Huisman
2008-05-09  9:30     ` Wolfgang Schuster
2008-05-09  9:56       ` Jelle Huisman
2008-05-09 10:06         ` Wolfgang Schuster
2008-05-09 12:53           ` Jelle Huisman
2008-05-09 13:14             ` Wolfgang Schuster
2008-05-09 13:57               ` Jelle Huisman
2008-05-09 13:05           ` Hans Hagen
2008-05-09 13:54             ` Jelle Huisman
2008-05-15 11:33             ` Jelle Huisman
2008-05-15 13:07               ` Wolfgang Schuster
2008-05-15 13:27                 ` Jelle Huisman
2008-05-15 13:52                   ` Wolfgang Schuster [this message]
2008-05-15 19:54                     ` Jelle Huisman
2008-05-16  9:54                       ` Wolfgang Schuster
2008-05-16 10:19                         ` Jelle Huisman
2008-05-16 10:25                           ` Wolfgang Schuster
2008-05-16 10:41                             ` Jelle Huisman

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=115224fb0805150652r52668c00h24d68e06661ed646@mail.gmail.com \
    --to=schuster.wolfgang@googlemail.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).