ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: Alan Braslau <braslau.list@comcast.net>,
	Rik Kabel <context@rik.users.panix.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: future versions
Date: Wed, 25 Jul 2018 19:01:21 +0200	[thread overview]
Message-ID: <7583d908-7472-1470-dcdb-4fbde6d13d9f@xs4all.nl> (raw)
In-Reply-To: <20180725101810.532e12ca@poo.hsd1.co.comcast.net>

On 7/25/2018 6:18 PM, Alan Braslau wrote:
> On Wed, 25 Jul 2018 09:50:58 -0400
> Rik Kabel <context@rik.users.panix.com> wrote:
> 
>> On 7/25/2018 04:19, Henning Hraban Ramm wrote:
>>> Am 2018-07-25 um 03:29 schrieb Rik Kabel
>>> <context@rik.users.panix.com>:
>>>> I would ask for more stylistic or semantic tagging to be added to
>>>> the XML export. A good example is that of bibliographies, where
>>>> font styles carry significant semantic meaning (depending on the
>>>> standard used: italic for book titles, ibold or talic for volume
>>>> and issue numbers, and so on.) The xml output reflects none of
>>>> this.
>>>>
>>>> I do not know whether one would want stylistic tagging (italic,
>>>> bold, ...) or semantic (booktitle, issue number). In either case,
>>>> they could be implemented as highlights or tagged elements, both
>>>> of which are currently carried through, and the user could then
>>>> apply the appropriate styling with css or other transformation
>>>> mechanisms.
>>> Generally, you get stylistic tagging by using \definehighlight.
>>> I replaced \em and \bf by \emph{} and \strong{} in my projects.
>>>
>>> Didn’t try real bibliographies or xml input yet, but I guess you
>>> can change the setup to use those.
>>
>> \definehighlight does not (by default) nest. You can handle this to
>> some degree in css or xslt for XML exports, but it is not an
>> acceptable replacement for font switches with pdf output. And since
>> the syntax for highlights ( \highlight{text} ) differs from that for
>> font switches ( {\highlight text} ), it is not simply a matter of
>> different environments for each output format, although perhaps
>> \groupedcommand might help (I have not tried this).
>>
>> But that is in some ways beside the point. A user should not have to
>> find and modify every instance in the source where such setups occur.
>> When exports or tagging are enabled, it would be good if this were
>> automatically done.
>>
> 
> Do you know about
> 
> \savebtxdataset
>    [default]
>    [bibliography.xml]
>    [alternative=xml,
>     criterium=all]
> 
> You can thus save your bibliography data for use, rather than or in
> addition to the rendered list.
I'll upload a beta with

- tagged publications
- embedded bib data in xml format and bibtex format

that should be enough for postprocessing magic. Of course we cannot 
catch cases where users mess around with specific setups which is no big 
deal as fo rexporting purposes one can use a simple standard style.

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2018-07-25 17:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 18:43 Hans Hagen
2018-07-24 19:07 ` Hans van der Meer
2018-07-24 20:35   ` Pablo Rodriguez
2018-07-24 20:30 ` Pablo Rodriguez
2018-07-24 21:02 ` Idris Samawi Hamid ادريس سماوي حامد
2018-07-24 23:21   ` Hans Hagen
2018-08-21  8:00     ` future versions - synctex Procházka Lukáš Ing.
2018-08-21  8:33       ` Hans Hagen
2018-08-21 13:04         ` Aditya Mahajan
2018-08-21 13:19           ` Hans Hagen
2018-08-21 14:46             ` Aditya Mahajan
2018-08-21 15:17               ` Hans Hagen
2018-07-25  1:29 ` future versions Rik Kabel
2018-07-25  8:19   ` Henning Hraban Ramm
2018-07-25 13:50     ` Rik Kabel
2018-07-25 16:06       ` Hans Hagen
2018-07-25 16:18       ` Alan Braslau
2018-07-25 17:01         ` Hans Hagen [this message]
2018-07-25 11:36   ` Hans Hagen
2018-07-25  7:45 ` Robert Zydenbos
2018-07-25 10:03   ` Richard Mahoney | Indica et Buddhica
2018-07-25 12:50     ` Hans Hagen
2018-07-25 13:12       ` Weber, Matthias
2018-07-25 17:50         ` Hans Hagen
2018-07-25 20:22           ` Henning Hraban Ramm
2018-07-25 11:38   ` Hans Hagen

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=7583d908-7472-1470-dcdb-4fbde6d13d9f@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=braslau.list@comcast.net \
    --cc=context@rik.users.panix.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).