public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Chris Corbett <chrisacorbett-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: eliminate styles for docx
Date: Fri, 27 Sep 2019 07:22:20 -0700 (PDT)	[thread overview]
Message-ID: <16693d6e-9da7-426f-b44b-a3ca9c8076d4@googlegroups.com> (raw)
In-Reply-To: <bc70a725-5c2b-4ef5-aec9-ba9da8d56fcb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

I wanted to thank everyone for their answers.  The solution I went with is 
to add ~~~ at the beginning and end of the text file.  And then I just had 
to change the font and font size for one style within the reference docx.   

On Friday, September 20, 2019 at 3:35:19 PM UTC-5, Chris Corbett wrote:
>
> I'm a pandoc newbie and I've searched the group, but haven't found out how 
> to do what I want to do.
>
> I have a business application that is producing text file reports that are 
> sent to the printer using enscript which basically is sending it using a 
> single non-proportional font.   The code producing the report ensures that 
> everything has the correct alignment up by having the right amount of 
> spaces between each column.
>
> I have a requirement to convert this report to a docx file because we want 
> to have the ability to draw a signature on it.  So I'm using pandoc to do 
> that conversion.  But when I do that, I end up with a document with 
> multiple styles and its messing up all of the alignment.
>
> I've just spent the last couple of hours manipulating all of the styles 
> setup within my document.   But I'm not getting very far, very fast.  Is 
> there a way that I can add a tag to my input file to force pandoc to use a 
> single style for everything?  I'm not sure what is polite on this group, so 
> I'm not attaching anything.  But I would be happy to do so if it would help 
> anyone help me.
>
> Thanks!
>
>
>

-- 
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/16693d6e-9da7-426f-b44b-a3ca9c8076d4%40googlegroups.com.

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

      parent reply	other threads:[~2019-09-27 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20 20:35 Chris Corbett
     [not found] ` <bc70a725-5c2b-4ef5-aec9-ba9da8d56fcb-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-21 17:53   ` John MacFarlane
     [not found]     ` <m2o8zd35a6.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-21 21:20       ` Chris Corbett
2019-09-22 11:33   ` John Muccigrosso
2019-09-23 13:11   ` Emmanuel Charpentier
2019-09-27 14:22   ` Chris Corbett [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=16693d6e-9da7-426f-b44b-a3ca9c8076d4@googlegroups.com \
    --to=chrisacorbett-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).