Subject: Re: [Boost-build] New doc format.
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2018-02-11 05:52:29
On Fri, Jan 19, 2018 at 7:12 PM, Steven Watanabe via Boost-build <
> On 01/18/2018 09:42 PM, Rene Rivera wrote:
> > On Tue, Jan 16, 2018 at 1:13 PM, Rene Rivera <grafikrobot_at_[hidden]>
> >> On Tue, Jan 16, 2018 at 12:04 PM, Steven Watanabe via Boost-build <
> >> boost-build_at_[hidden]> wrote:
> >>> It's independent of the rewrite,
> >>> but it's something that I want to be implemented before
> >>> this goes live.
> >> Sure. I'll go research what options we have on that. In an ideal world
> >> could augment the default one it uses and push that upsream. As that
> way a
> >> bunch of other web contexts would get jam coloring.
> > OK, looked at the coloring.. Did the easiest attempt first. I
> implemented a
> > jam language coloring for highlight.js. And used that as the coloring for
> > the doc. And I did a partial tagging of the docs with the "[source,jam]"
> > attribute. Please take a look at the updated docs.
> It doesn't seem like it quite works:
> - The highlighting of keywords and rulenames seems
> be interfering with each other somehow.
I eventually fixed that in the HLJS custom highlight, but...
> - The comment/keyword/rule colors seem to be the same.
> Note: I can send you my emacs mode, which has the highlighting
> mostly correct, if that would help. I'm also willing to
> port one of my existing highlighters myself if you can point
> me to the system I need to implement.
I also implemented a Pygments custom lexer for the highlighting <
https://github.com/bfgroup/jam_pygments>. And switch the current styling to
looks like now red from here onwards <
-- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk