From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: 'Karl Weber' via pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Own syntax-highlighting not working properly
Date: Sun, 04 Oct 2020 08:26:18 -0700 [thread overview]
Message-ID: <m2r1qerp0l.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <8723849e-be6b-4571-b8ca-2ae76865bc42o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
"'Karl Weber' via pandoc-discuss"
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> writes:
> Hi,
>
> I am trying to build my own syntax-highlighting but it is not working
> properly. I have two problems, which are related to new *itemData* elements.
>
> (1) KDE-style XML syntax does not require a *defStyleNum* attribute in the
> *itemData* elements of the *itemDatas* group. It is also possible, to
> specify attributes like *bold="true"* *color="$AAAAAA"* directly in an
> *itemData* element.
>
> This, however, is not working with pandoc, so I wonder, if I make a mistake
> or whether this is not supported?
No, we don't support that. (We just ignore these additions.)
> (2) Link between *itemData* elements and styles in the themes file.
>
> The *idemData* elements usually contain *defStyleNum* attributes of the
> form e.g. *defStyleNum="dsKeyword"* The themes file (at least for pygments)
> however contains styles for e.g. *"Keyword"*.
>
> So, *my assumption* is, these specifications are related as follows: for
> every *defStyleNum="dsXYZ"* attribute in an itemData element I may specify
> style properties for *"XYZ"* in the themes file.
We actually have a hard-coded list of standard token types
(corresponding to defStyleNum values -- see TokenType at
https://hackage.haskell.org/package/skylighting-core-0.10.0.2/docs/Skylighting-Types.html)
If you've just invented your own, it won't work.
next prev parent reply other threads:[~2020-10-04 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 10:23 'Karl Weber' via pandoc-discuss
[not found] ` <8723849e-be6b-4571-b8ca-2ae76865bc42o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-10-04 15:26 ` John MacFarlane [this message]
[not found] ` <m2r1qerp0l.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-10-04 18:58 ` 'Karl Weber' via pandoc-discuss
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=m2r1qerp0l.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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).