public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Attribute-less Markdown from web page Html
Date: Fri, 28 Apr 2023 09:49:01 -0700	[thread overview]
Message-ID: <C0C55D35-D675-4B6E-8D1A-CACEF8F738D1@gmail.com> (raw)
In-Reply-To: <CA3F14A6-3BC2-47D2-9FDC-ED464D6CAF49-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org>

You would get different indentation with `-t commonmark`. markdown_strict follows the '4-space rule'.


> On Apr 26, 2023, at 4:59 PM, Oliver <news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org> wrote:
> 
> Thanks John
> 
> `-t markdown_strict-raw_html` does the trick for me!
> 
> One thing though with markdown_strict is odd: The text of lists is indented to the next 4-space column:
> 
> `-   list text`
> 
> Can I somehow tell the markdown_strict writer to use only _one_ space here:
> 
> `- list text`
> 
> Anyway, thousand time thanks for Pandoc!
> 
> 
> On 26 Apr 2023, at 15:39, John MacFarlane wrote:
> 
>> Turning off -link_attributes should do it, but looks like you tried that.
>> 
>> I'd have to look at an example of the input that produces this with these settings.
>> 
>> If you don't need fancy features, you could also try `-t commonmark` or `-t markdown_strict`.
>> 
>>> On Apr 25, 2023, at 5:32 PM, Oliver <news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org> wrote:
>>> 
>>> Hi all
>>> 
>>> I try to use Pandoc to convert web pages to markdown without all the class clutter like `{.underline}`, etc.
>>> 
>>> So I try
>>> 
>>> ```
>>> pandoc -f html -t markdown-raw_html-native_divs-native_spans-fenced_divs-header_attributes-auto_identifiers-inline_code_attributes-link_attributes-raw_attribute-simple_tables-multiline_tables-grid_tables page.html
>>> ```
>>> 
>>> and it works reasonably well, but I still get a bit of class clutter like
>>> 
>>> ```
>>> {.v-visible-sr .js-screen-reader-info}
>>> ```
>>> 
>>> or attributes like
>>> 
>>> ```
>>> {title="sometext“}
>>> ```
>>> 
>>> , both after links
>>> 
>>> How can I supress these?
>>> 
>>> I want really only the text and (image) links.
>>> 
>>> Any help much appreciated!
>>> 
>>> 
>>> -- 
>>> 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/8AD0B607-B556-48CC-83AA-7D0BACD3B8BE%40halloleo.hailmail.net.
>> 
>> -- 
>> 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/1E55C9DB-9A8C-4064-9927-2EC8B70076A0%40gmail.com.
> 
> -- 
> 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/CA3F14A6-3BC2-47D2-9FDC-ED464D6CAF49%40halloleo.hailmail.net.

-- 
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/C0C55D35-D675-4B6E-8D1A-CACEF8F738D1%40gmail.com.


  parent reply	other threads:[~2023-04-28 16:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26  0:32 Oliver
     [not found] ` <8AD0B607-B556-48CC-83AA-7D0BACD3B8BE-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org>
2023-04-26  5:39   ` John MacFarlane
     [not found]     ` <1E55C9DB-9A8C-4064-9927-2EC8B70076A0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-04-26 23:59       ` Oliver
     [not found]         ` <CA3F14A6-3BC2-47D2-9FDC-ED464D6CAF49-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org>
2023-04-28 13:56           ` Ian Cornelius
2023-04-28 16:49           ` John MacFarlane [this message]
     [not found]             ` <C0C55D35-D675-4B6E-8D1A-CACEF8F738D1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-04-28 22:14               ` Oliver
     [not found]                 ` <0B417699-0C93-4DBC-9B09-8C36B6F39B0F-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org>
2023-04-29  5:04                   ` John MacFarlane
     [not found]                     ` <A3814551-04F1-4FD2-B6CF-7B89E39D840A-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-04-29 14:01                       ` Oliver

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=C0C55D35-D675-4B6E-8D1A-CACEF8F738D1@gmail.com \
    --to=fiddlosopher-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).