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: tagging heads and empty output
Date: Fri, 03 Apr 2015 12:59:23 -0600	[thread overview]
Message-ID: <op.xwi5o9n4fkrasx@ishamid-pc> (raw)
In-Reply-To: <5517287D.2010305@wxs.nl>

Hi Hans,

On Sat, 28 Mar 2015 16:17:33 -0600, Hans Hagen <pragma@wxs.nl> wrote:

> On 3/28/2015 10:12 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
>> On Sat, 28 Mar 2015 07:34:32 -0600, Idris Samawi Hamid ادريس سماوي حامد
>> <ishamid@colostate.edu> wrote:
>>
>>> Dear gang,
>>> Two issues:
>>>
>>> 1. What is the proper way to tag heads in itemize? I do
>
> the next beta will provide
>
> <item head="yes">

===============
  <div class="itemgroup itemize symbol-n level-1">
   <div class="item head-yes">
    <div class="itemtag">1.</div>
    <div class="itemcontent">Head 1     <div  
class="break"><!--empty--></div>
Test 3</div>
   </div>
   <div class="item head-yes">
    <div class="itemtag">2.</div>
    <div class="itemcontent">Head 2     <div  
class="break"><!--empty--></div>
Test 4</div>
   </div>
  </div>
===============

Ok, but 'Head 1' and 'Head 2' are still not tagged, so we can't translate  
the actual head, e.g.,

\setupitemize[each][headstyle=bold]

into css, while leaving the paragraph after the break unaffected.

Current workaround:

==================
\definestartstop[heading][style=]

\startitemize[n]
\starthead {\startheading Head 1 \stopheading}

Test 1
\stophead
\starthead {\startheading Head 2 \stopheading}

Test 2
\stophead
\stopitemize
=================
  <div class="itemgroup itemize symbol-n level-1">
   <div class="item head-yes">
    <div class="itemtag">1.</div>
    <div class="itemcontent"><div class="construct heading">Head 1</div>     
<div class="break"><!--empty--></div>
Test 1</div>
   </div>
   <div class="item head-yes">
    <div class="itemtag">2.</div>
    <div class="itemcontent"><div class="construct heading">Head 2</div>     
<div class="break"><!--empty--></div>
Test 2</div>
   </div>
  </div>
===============

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-04-03 18:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-28 13:34 Idris Samawi Hamid ادريس سماوي حامد
2015-03-28 21:12 ` Idris Samawi Hamid ادريس سماوي حامد
2015-03-28 22:17   ` Hans Hagen
2015-04-03 18:59     ` Idris Samawi Hamid ادريس سماوي حامد [this message]
2015-04-08 16:18       ` Hans Hagen
2015-04-10 23:17         ` Idris Samawi Hamid ادريس سماوي حامد

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.xwi5o9n4fkrasx@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).