From: "Arsène du Caucase" <botsana88-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Line blocks (for verses) useless on Android after converting to epub
Date: Fri, 23 Dec 2016 15:43:47 -0800 (PST) [thread overview]
Message-ID: <5b99bf5a-6cb6-4166-a22f-f59d7d9338ab@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1157 bytes --]
Hi, guys
the following structure:
Tirintirin tarapara...
| Oh, thy welcomed answer
| Is very much appreciated
And then again tirintirin tarapara...
Gives me very bad look after pandoc conversion to epub on Android readers
such as Moon Reader FBreader Coolreader and others, so that:
Tirintirin tarapara...
Oh, thy welcomed answer. Is very much appreciated
And then again tirintirin tarapara...
The problem is definitely not version of readers or settings, tried to
explore any kind of possible action
Would could possibly be a problem and how to avoid it?
Thanks a lot
--
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/5b99bf5a-6cb6-4166-a22f-f59d7d9338ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1866 bytes --]
next reply other threads:[~2016-12-23 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 23:43 Arsène du Caucase [this message]
[not found] ` <5b99bf5a-6cb6-4166-a22f-f59d7d9338ab-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-12-24 4:21 ` 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=5b99bf5a-6cb6-4166-a22f-f59d7d9338ab@googlegroups.com \
--to=botsana88-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).