public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Convert unwrapped paragraphs to hard wrapped paragraphs when there's no blank lines.
Date: Fri, 27 Mar 2020 15:30:29 +0000	[thread overview]
Message-ID: <CAO2sX317wcDpD8e3OWg7_5UvxMWND7urVtyok-9i9Q=PBBZCFg@mail.gmail.com> (raw)

Okay, this isn't strictly an accessibility question, but I can't think
of any better place to ask and Google didn't help much.

I occasionally purchase eBooks from Smash Words as they're the only
eBook Store I know of that offers plain text along side the far too
prevalent for my liking PDF, ePub, and Kindle formats.

Problem is, their plain text eBooks are typically long enough Firefox
and Orca simply choke on them and they have paragraphs that are
unwrapped, which makes reading them with nano and SBL cumbersome.
Normally, I'd just use nano's justify command to hard wrap thewhole
file, but they lack blank lines between paragraphs, so Nano would
think the whole book a single paragraph.

So, does anyone know a way to automate inserting blank lines before
and after each line in a file that's too long to fit on the screen all
at once and then hard wrap those long lines?


             reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Linux for blind general discussion [this message]
 ` Linux for blind general discussion
   ` Convert unwrapped paragraphs to hard wrapped paragraphs whenthere's " Linux for blind general discussion
     ` Linux for blind general discussion
       ` Linux for blind general discussion
 ` Convert unwrapped paragraphs to hard wrapped paragraphs when there's " Linux for blind general discussion
   ` Linux for blind general discussion
     ` Linux for blind general discussion
 ` Convert unwrapped paragraphs to hard wrapped paragraphs when there'sno " Linux for blind general discussion

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='CAO2sX317wcDpD8e3OWg7_5UvxMWND7urVtyok-9i9Q=PBBZCFg@mail.gmail.com' \
    --to=blinux-list@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).