public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: ThomasH <therch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: word doc to md template
Date: Mon, 22 May 2023 01:43:26 -0700 (PDT)	[thread overview]
Message-ID: <0a8896ff-b031-4af9-9893-420738fbae75n@googlegroups.com> (raw)
In-Reply-To: <19fb6e9b-8d16-4bdb-a0c5-444ecffacbc9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2877 bytes --]

Here is my take:

1. It really depends on what you expect from " collaborate". We have a 
Github-like environment where we can edit .md files in the browser, make 
changes, then create a commit. You have to edit the .md files "in source", 
so no fancy WYSIWYG, no extras like comments, annotations or the like.

2. I think you have to keep in mind that Markdown is not really a layout 
format. Its strength are simplicity to mark up linear text, so you might 
have to give up on specific layout wishes going forward to that format.

3. The same applies to styling like fonts or font sizes, as far as I know. 
It might seem that Markdown is not the ideal format for your needs. - I'm 
not sure I understand your point concerning headings, but if you look into 
the documentation it probably says that H1 is used for the document title 
and all other headings are organized beneath it (i.e. starting from H2).

On Sunday, May 21, 2023 at 9:27:20 PM UTC+2 Mark Pinsley wrote:

> I am trying to convert from google docs, so far it looks like I need to 
> convert from a google doc to a word doc, and then convert again to MD
>
> A few questions:
> 1. One of the reasons I have started playing with MD, was to write oped 
> and blogs it seemed like a good way to write once and then output in many 
> files. Now I am starting to wonder if I am just better off using google 
> doc. It seems difficult to collaborate online with the MD editors that are 
> available online. How are you all using it
>
> 2. I am trying to create a press release template. I have attached a copy 
> of what it looks like in Word.  I tried converting it into a md template 
> but I can not figure out how to lay it out the same way. Also, does my 
> image have to be in the same folder as the md?
>
> I used the command: 
>  pandoc -s --wrap=none input.docx -t markdown -o output.md
>
> But when i convert it back to a docx or HTML it doesn't look anything like 
> the original. How would you save this doc as md, and how would you deal 
> with the picture?
>
> 3. Also since in my original document I used bold and font sizes, is there 
> a way to tell it what fonts should be what kind of heading. If you look at 
> the current heading of the document and convert it to markdown, the top 
> headers should he H1, H2, H3 but I didn't do it that way when I originally 
> created the google doc. Is there a fast way to fix this?
>
>
>
>

-- 
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/0a8896ff-b031-4af9-9893-420738fbae75n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3533 bytes --]

           reply	other threads:[~2023-05-22  8:43 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <19fb6e9b-8d16-4bdb-a0c5-444ecffacbc9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>]

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=0a8896ff-b031-4af9-9893-420738fbae75n@googlegroups.com \
    --to=therch-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).