From: "'William Lupton' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Handling binary format of an old word processor
Date: Thu, 13 Jul 2023 19:28:57 +0100 [thread overview]
Message-ID: <CAEe_xxgArqRo2zf5+QDvhhT7U3ZLz8gH4me9LXBiN_di2qF2DQ@mail.gmail.com> (raw)
In-Reply-To: <6019A3AE-5A17-4857-A428-5B2C5F7AB879-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2173 bytes --]
I think you need to use a custom reader. Here's a link to the appropriate
bit of the appropriate page.
https://pandoc.org/custom-readers.html#bytestring-readers
On Thu, 13 Jul 2023, 14:11 Trevor Jenkins, <bslwannabe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> I have a group of files created long ago with a word processor for the BBC
> Micro. The word processor(WordWide/WordWisePlus), which originated in the
> late 1980s, saved documents in a sort of binary format in that some 7-bit
> printable characters have the eighth bit set to indicate that the character
> was preceded on screen by a carriage return. Other old ASCII control codes
> such as SI and SO were used for italics (I think). There are also
> encapsulated Epson dot-matrix setup sequences at the start of the files.
> Had a few read throughs of the Pandoc/Lua filter documentation but simply
> cannot get my head around how these documents could be processed using a
> Lua filter for pandoc to convert what is essentially a stream of 8-bit
> bytes into a form that can be used to convert to a modern format.
>
> Would appreciate some pointers to how to handle this task using pandoc and
> Lua? Otherwise I will have write some one-off throw away C code that does
> not help me in using Lua for future tasks.
>
> Regards, Trevor.
>
> <>< Re: deemed!
>
> --
> 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/6019A3AE-5A17-4857-A428-5B2C5F7AB879%40gmail.com
> .
>
--
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/CAEe_xxgArqRo2zf5%2BQDvhhT7U3ZLz8gH4me9LXBiN_di2qF2DQ%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 3111 bytes --]
next prev parent reply other threads:[~2023-07-13 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 13:10 Trevor Jenkins
[not found] ` <6019A3AE-5A17-4857-A428-5B2C5F7AB879-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-13 18:28 ` 'William Lupton' via pandoc-discuss [this message]
[not found] ` <CAEe_xxgArqRo2zf5+QDvhhT7U3ZLz8gH4me9LXBiN_di2qF2DQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-15 8:38 ` Trevor Jenkins
[not found] ` <D9A14D6A-896B-4B36-BFF3-002AEFC083EB-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-16 9:17 ` 'William Lupton' via pandoc-discuss
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=CAEe_xxgArqRo2zf5+QDvhhT7U3ZLz8gH4me9LXBiN_di2qF2DQ@mail.gmail.com \
--to=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).