From: "R (Chandra) Chandrasekhar" <chyavana-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
Subject: Re: Syntax highlighting for English as a natural language
Date: Wed, 9 Dec 2020 14:28:16 +0530 [thread overview]
Message-ID: <5f60478d-2419-f154-9a37-b3df33c4e25e@gmail.com> (raw)
In-Reply-To: <67d88ac1-b144-2591-dd43-7e1afbf5bb89-Jdbf3xiKgS8@public.gmane.org>
On 08/12/2020 20:08, Daniel Staal wrote:
> On 12/8/20 7:59 AM, R (Chandra) Chandrasekhar wrote:
>>
>> Coming back to my question, my set of sentences to code in colour,
>> depending on its part of speech, is small and I can do it by hand. But
>> I need to do it in a fashion that allows the same pandoc-markdown
>> source file to produce PDF and HTML.
>>
>> For example, the sentence "I use Pandoc" might show up as:
>>
>> I (in blue colour for pronouns)
>> use (in green colour for verbs)
>> Pandoc (in red colour for nouns)
>>
>> How would I do this in pandoc-markdown (perhaps in a verbatim-like
>> environment) to get the same results for HTML and PDF?
>
> If you are willing to do all the work manually, and only need it in HTML
> and PDF: Use spans and CSS, and use HTML as the intermediary to PDF
> instead of LaTex. Either native HTML spans, or bracketed spans.
>
> Daniel T. Staal
>
That is what I ended up doing and it is quite satisfactory.
Thanks also for mentioning HTML to PDF: That is an option that did not
occur to me as I was fixated on LaTeX.
Chandra
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/5f60478d-2419-f154-9a37-b3df33c4e25e%40gmail.com.
prev parent reply other threads:[~2020-12-09 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 4:53 R (Chandra) Chandrasekhar
[not found] ` <9a7f850d-7335-074b-1527-8a578ed13741-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-12-08 9:23 ` BPJ
[not found] ` <CADAJKhAK=EWS0gTgqL=WpXTpWEK-AAKKASfxwgU4MSLgXtU=ig-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-12-08 10:45 ` ph...-jvooPmwWovGx7wk7FZxnQA@public.gmane.org
[not found] ` <c81b271c-5fa5-4e97-bf9b-a111efcc26d6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-08 13:47 ` R (Chandra) Chandrasekhar
[not found] ` <ea4fc1d6-e5a7-27c1-43b5-4a421b23d285-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-12-08 13:52 ` AW: " denis.maier-FfwAq0itz3ofv37vnLkPlQ
2020-12-08 12:59 ` R (Chandra) Chandrasekhar
[not found] ` <c1222fc6-4f1c-bb5e-c10b-ed44a3056067-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-12-08 14:38 ` Daniel Staal
[not found] ` <67d88ac1-b144-2591-dd43-7e1afbf5bb89-Jdbf3xiKgS8@public.gmane.org>
2020-12-09 8:58 ` R (Chandra) Chandrasekhar [this message]
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=5f60478d-2419-f154-9a37-b3df33c4e25e@gmail.com \
--to=chyavana-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=DStaal-Jdbf3xiKgS8@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).