From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Dealing with wrapped atx headings from email
Date: Thu, 5 Dec 2019 12:41:01 -0500 [thread overview]
Message-ID: <06b1ce83-05e3-4fb4-11f5-2866cd5dcfd4@reagle.org> (raw)
In-Reply-To: <4868e6ed-cf44-e208-8f1b-5f4c7661f1e9-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
On 12/4/19 5:23 PM, Joseph Reagle wrote:
> #### **Do algorithms exhibit biases (intentional or otherwise) in online
> commerce?**
I suspect this problem is caused by the email client (GMail) -- not quoted-printable itself.
As I look at the email, the text/plain part doesn't have any soft wraps. So the text editor created the hard wrap in the following I think.
```
--000000000000c7df1f059725d814
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
...
# Reading Response Set Two
## Algorithmic discrimination
#### **Do algorithms exhibit biases (intentional or otherwise) in online
commerce?**
```
Confusingly, the HTML part had no evidence of the wrap before "commerce" and it nicely soft wraps the lines (ending with "=").
```
--000000000000c7df1f059725d814
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
... <div># Reading Response Set Two<br>## A=
lgorithmic discrimination<br>#### **Do algorithms exhibit biases (intention=
al or otherwise) in online commerce?**<br><br>Web search results can be for=
mulated around an individual=E2=80=99s personal information, such as prior =
searches, location, and online interests. Although online personalization c=
an be helpful, it also narrows searches to an extent where you are likely t=
o miss a large majority of results. According to the article on [Buzz
```
Pandoc could recover from this if markdown's headings required a blank line before and after, but since not, I think the mail client mangled the text and don't think it can be recovered...?
prev parent reply other threads:[~2019-12-05 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 22:23 Joseph Reagle
[not found] ` <4868e6ed-cf44-e208-8f1b-5f4c7661f1e9-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2019-12-05 17:41 ` Joseph Reagle [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=06b1ce83-05e3-4fb4-11f5-2866cd5dcfd4@reagle.org \
--to=joseph.2011-t1oy19wchswdnm+yrofe0a@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).