public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Alx Nbl <alxnbl-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Way to have markdown ==highlighting== show up as highlighting in .docx or .odt files?
Date: Sun, 2 Jan 2022 08:52:44 -0800 (PST)	[thread overview]
Message-ID: <c0083e12-4b71-4fd1-a701-f6ea922a1f98n@googlegroups.com> (raw)
In-Reply-To: <2cf7ddb7-c135-441c-8758-d780938bb5ffn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 3704 bytes --]

My use case is different from paulschi, in my case i am trying to convert 
docx into markdown and generating '== ==' syntax when there is higlighted 
text in the docx file.

On Sunday, January 2, 2022 at 3:09:42 PM UTC+1 Alx Nbl wrote:

> Hi all. The '== ==' syntax is also used by Joplin app. I would also be 
> very interested by such a feature.
>
> On Thursday, December 9, 2021 at 6:29:51 PM UTC+1 John MacFarlane wrote:
>
>>
>> On CriticMarkup, see
>>
>> https://github.com/jgm/pandoc/issues/2873
>> https://github.com/jgm/pandoc/issues/5430
>>
>>
>> Joseph Reagle <josep...-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:
>>
>> > BTW: If CommonMark or pandoc were to support highlight, I would then 
>> wonder why not support all of CriticMarkup, which supports highlight as 
>> `{== ==}` or `{>> <<}`. (It's a shame that we have two different syntaxes 
>> emerging for highlight.)
>> >
>> > On 21-12-09 11:10, John MacFarlane wrote:
>> >> 
>> >> If this is a syntax that is becoming common, we could consider
>> >> adding a markdown extension for it. You could open an issue on
>> >> our issue tracker.
>> >> 
>> >> Joseph Reagle <josep...-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:
>> >> 
>> >>> This is the first time I've encountered [this syntax][1] and it is 
>> not natively supported by pandoc. Or am I wrong and you are saying pandoc 
>> handles it when using the latex/PDF writer? (Or, are you saying Obsidian 
>> can export to PDF, but not Word?)
>> >>>
>> >>> I see there's been some discussion on the [CommonMark forum][2], but 
>> it doesn't look like you'd find an immediate solution.
>> >>>
>> >>> Using a filter or hacking something that converts `==foo==` to 
>> [foo]{.highlight} that is properly rendered in Word might be options.
>> >>>
>> >>> [1]: https://www.markdownguide.org/extended-syntax/#highlight
>> >>> [2]: 
>> https://talk.commonmark.org/t/highlighting-text-with-the-mark-element/840
>> >>>
>> >>> On 21-12-09 08:29, Paul wrote:
>> >>>> I use a lot of highlighting in my markdown editor Obsidian, but I 
>> was wondering if there's a way to have that highlighting show up in the 
>> Word or Libreoffice Writer files?
>> >>>>
>> >>>> Bold and italics work fine, as far as I can tell, and when 
>> converting to a pdf the highlighting transfers great. I gather, however, 
>> that the ==highlighting== is not standard in all markdown so is that the 
>> issue?
>> >>>
>> >>> -- 
>> >>> 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> >>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/pandoc-discuss/9995ee8a-295e-1836-5645-9bb5ff76445d%40reagle.org
>> .
>> >> 
>> >
>> > -- 
>> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/pandoc-discuss/9d89679a-94dc-2459-822f-93dbe4cbca57%40reagle.org
>> .
>>
>

-- 
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/c0083e12-4b71-4fd1-a701-f6ea922a1f98n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 6931 bytes --]

  parent reply	other threads:[~2022-01-02 16:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 13:29 Paul
     [not found] ` <b36d117c-bce8-4cda-acef-795fdc6d95dfn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-12-09 13:55   ` Joseph Reagle
     [not found]     ` <9995ee8a-295e-1836-5645-9bb5ff76445d-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-12-09 14:23       ` Paul
2021-12-09 16:10       ` John MacFarlane
     [not found]         ` <m2czm5ep3u.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-12-09 16:58           ` Paul
2021-12-09 17:11           ` Joseph Reagle
     [not found]             ` <9d89679a-94dc-2459-822f-93dbe4cbca57-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-12-09 17:16               ` Paul
2021-12-09 17:29               ` John MacFarlane
     [not found]                 ` <m2r1ald6vy.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2022-01-02 14:09                   ` Alx Nbl
     [not found]                     ` <2cf7ddb7-c135-441c-8758-d780938bb5ffn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-02 16:52                       ` Alx Nbl [this message]
     [not found]                         ` <c0083e12-4b71-4fd1-a701-f6ea922a1f98n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-21 13:21                           ` Emiliano
     [not found]                             ` <beef58d1-ac94-4f5a-9405-ecfbff6caa8cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-21 16:43                               ` John MacFarlane
2022-06-21 16:44                               ` -
     [not found]                                 ` <489be9a1-e45a-4bee-ab8d-ce83ca7ed292n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-22 14:10                                   ` Emiliano
     [not found]                                     ` <ba18ff15-897d-4a7f-bbd4-3735da206f1dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-22 17:44                                       ` BPJ
     [not found]                                         ` <CADAJKhCSGnvyAP=OSkNB_JRhwUgdtZ0Do8bNScw+b-aQDWwzWQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-23 11:14                                           ` Emiliano
     [not found]                                             ` <3316a007-a142-4d3d-a2f8-40befafb4249n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-23 19:06                                               ` BPJ
     [not found]                                                 ` <CADAJKhA3F-VC--BMe2mpERZr=LmXZFNE61EwvHmfk0dwYp_ALw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-23 19:45                                                   ` Emiliano
2022-06-24  8:46                                                   ` BPJ
     [not found]                                                     ` <CADAJKhAq4vmgvNP7VFduvLQ-EAPeGry+-gNcuFYJFpnDbZ02Bw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-24  9:04                                                       ` BPJ

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=c0083e12-4b71-4fd1-a701-f6ea922a1f98n@googlegroups.com \
    --to=alxnbl-re5jqeeqqe8avxtiumwx3w@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).