From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
"Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: xhtml export internal command \dostarttaging modify display and other XML/XHTML attributes
Date: Fri, 10 Apr 2020 16:29:53 +0200 [thread overview]
Message-ID: <feb2cf24-8140-c830-e028-227e538527f9@xs4all.nl> (raw)
In-Reply-To: <E672E1B0-7127-41E3-B3DE-F11C4BED62C0@uni-bonn.de>
On 4/10/2020 3:09 PM, Thomas A. Schmitz wrote:
>
>
>> On 10. Apr 2020, at 14:49, Christoph Hintermüller <christoph@out-world.com> wrote:
>>
>> Please increase the USB of ConTeXt by improoving the xml/xhtml exporter
>> backend by allowing modules to hook into it, defining how the contotent
>> should be processed and what css attributes the corresponding tags
>> should receive.
>>
>> Second i noticed that even in verbatim the line numbers are not on the
>> line they number but are, due to late injections printed on an empty
>> line in xhtml. Needs improvement here too.
>>
>>
>> All the above and some more forces me to push my plans to publish my
>> lecture notes on programming as pdf and epub to likely next year. And
>> helping in Improvement is for now not an option too me for now, exempt
>> maybe lateron in testing.
>>
>>
>> Happy Easter.
>
> What, precisely, was the point of this long message?
Indeed. the exporter is just a reconstructor of content so the better
structured, the better the export, and the trickier the rendering the
worse. Also, one can if needed add tags, add attributes etc etc but
don't expect me to keep track of all modules and user stuff and add
export specififcs. Of course I can make some aspects better but i never
needed epub so far.
Then, given an export, one can use xslt or whatever, of have one's own
css as there is no common ground for rendering idiologies. Ever yuser
wants something different.
That said: the best multi-output stuff comes from good neutral input and
for instance xml is more suitable for that than tex encoded input. I'm
currently doing just that: making some css for rather extensive kind of
free xml based content (mostly because i have nothing better todo right
now).
In the end it all boils down to 'does it pay off' in terms of
'useability', 'neccessity' and 'the fun of it'. We're talking of free
software so no one can demand something, only request.
Suggestion for Christoph: look at what Thomas has done for a long time
now: one input (often quite advanced) and multiple output for publishing
ane educational purposes. And it looks pretty good too.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-04-10 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 13:56 Christoph Hintermüller
2020-04-08 9:52 ` Christoph Hintermüller
2020-04-10 12:49 ` Christoph Hintermüller
2020-04-10 13:09 ` Thomas A. Schmitz
2020-04-10 14:29 ` Hans Hagen [this message]
2020-04-10 16:11 ` Christoph Hintermüller
2020-04-10 21:26 ` Christoph Hintermüller
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=feb2cf24-8140-c830-e028-227e538527f9@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=thomas.schmitz@uni-bonn.de \
/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).