Re: What Pandoc does not cover, yet.

[Paulo Ney de Souza <pauloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

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

On Fri, Sep 9, 2022 at 3:31 AM BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> Den fre 9 sep. 2022 03:09Paulo Ney de Souza <pauloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:
>
>> One of the beauties of Pandoc is the architecture that allows for very
>> easy
>> expansion and that shows on the number of (ever increasing) formats
>> supported.
>>
>> That made me wonder what formats Pandoc does not cover, yet! I kind of
>> know two of them:
>>
>> The Rocket eBook (RB) format of the first eBook reader:
>>
>>      https://docs.fileformat.com/ebook/rb/
>>
>> The Compiled HTML (CHM) that Microsoft used a huge lot for documentation:
>>
>>       https://en.wikipedia.org/wiki/Microsoft_Compiled_HTML_Help
>>
>
> Aren't these of historical interest only? (Although they might make sense
> as source formats.)
>

Not just historical. There is a large amount of material that has been
issued in these two formats and not re-issued in anything after that... so
from the point of view of preservation I would thik it is quite important.
Microsoft introduced CHM about 1996 and was the precursor of the Microsoft
Reader .lit format. Their Press for the first years of eBook publication
used only CHM. Most eBooks of that era are available in CHM only.

Calibre used to do RB but support for it was dropped recently. I am not
sure why. Pandoc already supports a number of eBooks formats: ePub2, ePub3,
HTML, FB2,... and with probably little work could support most others: LRF,
LIT, Topaz, SNB, MOBI, AZW3, AZW4, BOOK, KFX,  HTMLZ, PDB,.... It is true
that Calibre supports many of these, but any modifications on a Reader
because of variation on input, is much easier on Pandoc than on Calibre.


>
>> What other file formats you would like to see being supported by Pandoc?
>>
>
> Perl's Pod documentation format. I have been working on a custom writer
> and am almost there. It mostly just needs documentation (which I by
> occupational injury am very picky about) and a way to make some things
> configurable when implemented as a custom writer rather than as a filter
> mogrifying plain output (Question to Albert: are metadata available to
> custom writers?)
>
> A reader would be nice although Pod::Pandoc <
> https://metacpan.org/pod/Pod::Pandoc> sort of fills that niche (and
> Pandoc::Elements would probably need some updating, which I as the main
> contributor am as guilty as anybody of not doing!) Since Pod in principle
> is extensible I would like a reader which is smart enough to turn
> nonstandard commands and formatting codes into Pandoc Divs and Spans, and a
> convention like
>
>
That is great! Can't wait to see it.

Paulo Ney

-- 
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/CAFVhNZMG5zg2kBrHvd3SKco2mmhdbB%3DEHdTBS6E4b6DN7Eur7w%40mail.gmail.com.

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