From: "E. Castedo Ellerman" <castedo-HtDYFTekaG5BDgjK7y7TUQ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: New research document technology using Pandoc
Date: Mon, 6 Nov 2023 08:48:41 -0800 (PST) [thread overview]
Message-ID: <c2bb9f54-688f-4980-93a5-7df651306075n@googlegroups.com> (raw)
In-Reply-To: <CAKOoOVV69XSKPTGAuXzZ5UVyLG=j0J_vUwMq5O9D69hLbo0rFg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2799 bytes --]
Thank you for asking! I have added a new page https://try.perm.pub/tools/
to answer half-ish of your questions. I'll answer below in this message too.
On Monday, November 6, 2023 at 3:43:50 AM UTC-5 Guillaume Dehaene wrote:
After spending 15mins reading through the doc at try.perm.pub and the
"manifesto" on perm.pub itself, I'm still a bit confused about some of the
key details of the project:
- what exactly is the overarching aim? As far as I can tell, this
constructs an arxiv-like structure of versioning for technical documents,
but hosting is decentralized (perm.pub only hosts links?) ?
"Decentralized arxiv-like hosting" is a good description. For those
familiar with PubMed Central, I like the playful name "PubMe Decentral".
But I've avoided the term "decentralized" for a variety of reasons.
Regarding overarching aim, I'm not sure at what level or time scale to
answer that question. Similar to how for HTML I have a hard time answering
what is HTML's overarching aim.
- what formats can I use to author to perm.pub? Having read the two latex
based examples, I guess latex works, but can I do markdown?
Realistically, I would stick to either LaTeX or Markdown, at least for now.
Those are the two source formats I am using.
Can I do quarto (an opinionated extension of pandoc markdown, www.quarto.org
)?
I have not started testing and using Quarto but I plan to before the end of
the year. Quarto will probably work well.
Can I do docx / openofficewrite like some teams like to do? since I know
this is based on pandoc, I guess it's going to be somewhat flexible, but
with restrictions at some key points.
I have tested generating a Baseprint snapshot from a LibreOffice doc,
thanks to Pandoc, but I doubt many will find this approach satisfactory. I
might be biased because I generally avoid word processors. My hunch is that
if somebody likes using a word processor, they probably will find this tech
in its current state too user-unfriendly. But in the future, maybe it will
be different.
If anybody would like to be a be a trial user of using a word processor for
baseprints, I'm more than happy to help collaborate. We can document in
what ways this tech falls short of being user-friendly enough, which I
suspect it does.
Best regards
Guillaume
--
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/c2bb9f54-688f-4980-93a5-7df651306075n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4161 bytes --]
prev parent reply other threads:[~2023-11-06 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 14:33 E. Castedo Ellerman
[not found] ` <83c21ee1-e4cd-45bb-88f5-285c24a28e52n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-06 8:43 ` Guillaume Dehaene
[not found] ` <CAKOoOVV69XSKPTGAuXzZ5UVyLG=j0J_vUwMq5O9D69hLbo0rFg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-06 16:48 ` E. Castedo Ellerman [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=c2bb9f54-688f-4980-93a5-7df651306075n@googlegroups.com \
--to=castedo-htdyftekag5bdgjk7y7tuq@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).