ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Idris Samawi Hamid ادريس سماوي حامد" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: need defaults for \definehighlight
Date: Sun, 08 Feb 2015 15:42:19 -0700	[thread overview]
Message-ID: <op.xtrf0sm4fkrasx@ishamid-pc> (raw)
In-Reply-To: <54D7DA70.8060908@wxs.nl>

On Sun, 08 Feb 2015 14:51:44 -0700, Hans Hagen <pragma@wxs.nl> wrote:

> On 2/8/2015 8:08 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
>
>> Ok. It's clear that I'm doing a lot of guessing, so question: Can you
>> specify exactly what does *not* get tagged in xml-export? What exactly
>> do we need to worry about? Then we can go from there...
>
> everything that has some structure or meaning gets tagged
>
> font/colors have no meaning they're appearance so they don't get tagged

Ok, but here: http://wiki.contextgarden.net/Export it says,

======
Also note that switches like \em don’t translate into output structure,  
you need to \definehighlight[emph][style=italic] and use as  
\emph{emphasized}.
======

Now \em does have structural meaning (emphasis) so either the wiki is  
wrong or we have some inconsistency here -)

> highlights are for the few things left ... but often one can also use  
> \startelement for that

Do you have any good examples for using \start-stopelement? Thanks and

Best wishes
Idris
-- 
Idris Samawi Hamid
Professor of Philosophy
Colorado State University
Fort Collins, CO 80523
___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2015-02-08 22:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-07  1:07 Idris Samawi Hamid ادريس سماوي حامد
2015-02-07 12:53 ` Hans Hagen
2015-02-07 19:33   ` Idris Samawi Hamid ادريس سماوي حامد
2015-02-07 19:34     ` Idris Samawi Hamid ادريس سماوي حامد
2015-02-08 12:56   ` Keith J. Schultz
2015-02-08 14:01     ` Hans Hagen
2015-02-08 14:40       ` Idris Samawi Hamid ادريس سماوي حامد
2015-02-08 17:38         ` Hans Hagen
2015-02-08 19:08           ` Idris Samawi Hamid ادريس سماوي حامد
2015-02-08 21:51             ` Hans Hagen
2015-02-08 22:42               ` Idris Samawi Hamid ادريس سماوي حامد [this message]
2015-02-09 13:34               ` Keith Schultz
2015-02-09 13:46                 ` Wolfgang Schuster
2015-02-08 19:17         ` Wolfgang Schuster
2015-02-08 19:28           ` Idris Samawi Hamid ادريس سماوي حامد
2015-02-08 23:42       ` Keith Schultz
2015-02-09  8:03         ` Hans Hagen
2015-02-08 14:24     ` Idris Samawi Hamid ادريس سماوي حامد
2015-02-08 18:51     ` Wolfgang Schuster
2015-02-09  8:46     ` Alan BRASLAU

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=op.xtrf0sm4fkrasx@ishamid-pc \
    --to=ishamid@colostate.edu \
    --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).