ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Christoph Hintermüller" <christoph@out-world.com>
To: ntg-context@ntg.nl
Subject: Re: xhtml export internal command \dostarttaging modify display and other XML/XHTML attributes
Date: Fri, 10 Apr 2020 14:49:36 +0200	[thread overview]
Message-ID: <d1628e68deff6526dde4fbadeb7e47e139ca5a46.camel@out-world.com> (raw)
In-Reply-To: <febafc9da242e259610acab8b0579caf7318aaa4.camel@out-world.com>

Hi again

On Wed, 2020-04-08 at 11:52 +0200, Christoph Hintermüller wrote:
> 
> I figured so far that 
> with the command 
> \setelementnature[<mytagid>][block]
> 
> I can change the css 'displayÄ attribute of my <mytag> to
> display=block
> in the *_templates.css output
> 
> But i did not manage so far to in addition set the 'white-space' css
> attribute of mytag to 'pre-wrap' 
> 
> I tried `\dosettagproperty` and `\setelementexporttag` commands but
> none of the gave me the expected result in the *_templates.css output
> for the xhtm export.
> 
> What other commands do i have to call first, after `\dostarttagged`
> to
> be able to use eg `dosettagproperty` to also set the 'white-space'
> css
> attribute accordingly and/or how is the related context/lua property
> called which will be than translated into `white-space=pre-wrap`. The
> css 'display' attribute is to be changed by changing the 'nature'
> property of the tag.
> 
> Is there anybody who can provide at least some hints which *.tex and
> *.lua source files to look at to figure myself. At least some
> orientation would already help.
> 

Nope there isn't most of the stuff is hardcoded into the backend
expoerter lua. Including template for custome css template which only
considers display (nature) settings. And spaces are striped in any
case. 
All in all the backend exporter seems up to now still handcrafted
experimental proof of concept. Which makes me quenstion my self why did
i switch from latex to context. The major and killer reason was single
source multiple formats. But the only fully functional format so far is
pdf/dvi/ps xhtml/xml/epub are only working for core stuff. All the nice
modules seem not to be supported at all by backend exporter. 

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.

Xristoph


___________________________________________________________________________________
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:[~2020-04-10 12:49 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 [this message]
2020-04-10 13:09     ` Thomas A. Schmitz
2020-04-10 14:29       ` Hans Hagen
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=d1628e68deff6526dde4fbadeb7e47e139ca5a46.camel@out-world.com \
    --to=christoph@out-world.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).