Re: future versions

[Hans Hagen <j.hagen@xs4all.nl>]

On 7/25/2018 3:50 PM, Rik Kabel 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).
font switches using 'style' are bound to a structural element

> 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.
you can't expect reliable structure from non-structured input so if you 
want an export that is ok, the penalty is proper structuring

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
___________________________________________________________________________________