public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Melroch <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Writing custom filter in python to remove non-breaking spaces
Date: Sat, 5 Aug 2017 10:45:54 +0200	[thread overview]
Message-ID: <CADAJKhCedoDRvxGke5Ymnn8Ompj28EMf1ufiAG1JsDzL5B1y8w@mail.gmail.com> (raw)
In-Reply-To: <4abb2571-34b8-4e49-a189-05632083aab9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2273 bytes --]

With some fonts LibreOffice renders nbspaces way too narrow or too wide,
and maybe Word does the same to the extent that they use the same
algorithms. It is arguably a bug to let the width of the \xa0 character in
the font determine how an nbspace is rendered but there you have it. The
best solution is often to double all nbspaces as too wide spaces may look
better than too narrow ones.

Den 5 aug 2017 00:10 skrev "Kolen Cheung" <christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:

> But I still want to reiterate my original point, only if the original
> source is problematic, one wants to remove/replace the non-breaking space.
> I recall when I processed some doc files, seems like Word has been trying
> to be too smart, there are many non-breaking space that shouldn't be there
> (if my memory serves me well).
>
> Otherwise, replacing non-breaking space to space is basically wrong in
> typography (another example is "1-2" vs "1–2"). In other words, you're
> destroying the information the original author has carefully put in there.
>
> --
> 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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/pandoc-discuss/4abb2571-34b8-4e49-a189-05632083aab9%
> 40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhCedoDRvxGke5Ymnn8Ompj28EMf1ufiAG1JsDzL5B1y8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 3345 bytes --]

      parent reply	other threads:[~2017-08-05  8:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02  9:05 Karim Mohammadi
     [not found] ` <3be5ee09-90dc-41ad-a368-9298b965dfaa-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-02 14:09   ` John MacFarlane
     [not found]     ` <20170802140916.GF38349-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-08-03  4:55       ` Karim Mohammadi
     [not found]         ` <cc13bbea-06e5-422b-bcdd-cd9ba1c4cf95-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-03  6:11           ` Andrew Dunning
2017-08-03 22:29   ` Kolen Cheung
     [not found]     ` <f0bb6fae-6104-4efc-840d-34fd19b02840-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-04 18:58       ` Melroch
     [not found]         ` <CADAJKhBEZ8-BdJTQRJE4M2nettrGKhf1xYzqBYs=pe=_DAodpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-04 22:03           ` Kolen Cheung
2017-08-04 22:09           ` Kolen Cheung
     [not found]             ` <4abb2571-34b8-4e49-a189-05632083aab9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-05  8:45               ` Melroch [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=CADAJKhCedoDRvxGke5Ymnn8Ompj28EMf1ufiAG1JsDzL5B1y8w@mail.gmail.com \
    --to=melroch-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).