public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "r.d.go...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <r.d.goulding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Normalizing spaces in italics
Date: Fri, 1 Jul 2022 09:36:19 -0700 (PDT)	[thread overview]
Message-ID: <bd84993b-b1cd-4128-aab2-ce1eff2c9768n@googlegroups.com> (raw)


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

I am a bit sloppy typing italics in my wordprocessor, and generally only 
turn off the italics after I hit the space at the end of the word, so I end 
up with markdown output that looks like this (when I convert from rtf to 
md):

Strictly speaking the qualities that are imposed by the *logos *of a 
certain thing are the *activities *of the *logos*

This looks ugly when I open it up in Emacs etc. I can fix these with regex 
replace in Emacs; but I thought pandoc had normalization by default now, 
which is supposed to fix these kinds of stylistic errors? I tried passing 
the markdown again through pandoc, to generate markdown, but it made no 
difference.

-- 
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/bd84993b-b1cd-4128-aab2-ce1eff2c9768n%40googlegroups.com.

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

             reply	other threads:[~2022-07-01 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 16:36 r.d.go...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [this message]
     [not found] ` <bd84993b-b1cd-4128-aab2-ce1eff2c9768n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-02  8:49   ` BPJ
     [not found]     ` <CADAJKhCj=dCQ+1BkzkK7++bJn8ajpKkbxYHYVrHaC_NRjVQ15Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-02 21:13       ` r.d.go...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2022-07-05  8:26       ` John MacFarlane

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=bd84993b-b1cd-4128-aab2-ce1eff2c9768n@googlegroups.com \
    --to=r.d.goulding-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).