public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Enrico Mattia Salonia <mattia.salonia1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pandoc-Latex-Environment to docx does not work
Date: Mon, 14 Aug 2023 20:43:58 -0700 (PDT)	[thread overview]
Message-ID: <a52de802-1083-43e0-a302-42af9079779fn@googlegroups.com> (raw)
In-Reply-To: <629a3b14-2dbd-41b2-bca1-da3bed43bf67n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

For whom might be interested, I managed to preserve theorem like 
environments from markdown to docx using the statement 
<https://github.com/dialoa/statement> filter. Just employ the syntax

Definition.

: This is a brover.

More instructions in the page of the filter.

On Wednesday, 9 August 2023 at 00:06:35 UTC+10 Paul Kelleher wrote:

> Any docx environment is limited by what can be done with the reference doc 
> styles. I believe the 'Definition' environment in the stock docx reference 
> doc is just a bold title and then maybe an indented definition. I'm not 
> sure. I myself am not well versed on what can be done with docx styles, but 
> that's what you'll have to play around with.
>
> On Monday, August 7, 2023 at 5:27:19 AM UTC-5 Enrico Mattia Salonia wrote:
>
>> Thank you for your help! I tried removing the pandoc-latex-environment 
>> arguments in the YAML but still it does not get the environment, it just 
>> reproduces the text inside it. Are you suggesting that I can format a 
>> reference docx such that the syntax
>>
>> ::: {.definition}
>>
>> My definition.
>>
>> :::
>>
>> is processed by pandoc as a "Definition" environment?
>>
>>
>> On Saturday, 5 August 2023 at 00:36:10 UTC+10 Paul Kelleher wrote:
>>
>>> Oops, except: I'm not sure how best to handle the desired {.definition} 
>>> environment when converting to docx. I suspect you'll have to set up a 
>>> style in a reference docx file. Look for "--reference-doc=" here 
>>> <https://pandoc.org/MANUAL.html#options-affecting-specific-writers> for 
>>> more about that. 
>>>
>>> On Friday, August 4, 2023 at 9:33:19 AM UTC-5 Paul Kelleher wrote:
>>>
>>>> Omit the "pandoc-latex-environment" arguments in the YAML and I think 
>>>> the conversion to docx should work just fine. For cross-referencing 
>>>> equations I highly recommend the pandoc-crossref filter. 
>>>>
>>>> On Friday, August 4, 2023 at 9:20:31 AM UTC-5 Christophe Demko wrote:
>>>>
>>>>> Hi, I'm the creator of the pandoc-latex-environment. This filter is 
>>>>> for pdf output using LaTeX (or beamer). For docx, you have to use another 
>>>>> way.
>>>>>
>>>>> Le vendredi 4 août 2023 à 13:34:46 UTC+2, Enrico Mattia Salonia a 
>>>>> écrit :
>>>>>
>>>>>> When converting markdown to docx latex environments disappear and 
>>>>>> only the text inside them is retained. Conversion from markdown to pdf 
>>>>>> works fine.
>>>>>>
>>>>>> I am using --filter pandoc-latex-environment. The following is an 
>>>>>> extract of the .md
>>>>>>
>>>>>> ---
>>>>>> title: Hi
>>>>>> author: Brover
>>>>>> pandoc-latex-environment:
>>>>>>   df: [definition]
>>>>>>   prop: [proposition]
>>>>>>   proof: [proof]
>>>>>> ---
>>>>>>
>>>>>> ::: {.definition}
>>>>>>
>>>>>> A profile of actions $a \in A$ constitute a **Nash Equilibrium** if
>>>>>>
>>>>>> $$u_i \left( r_i \left(a_i, a_{-i} \right) \right) \geq u_i \left( 
>>>>>> r_i \left(a^{\prime}_i, a_{-i} \right) \right)$$
>>>>>>
>>>>>> for all agents $i \in N$ and actions $a_i, a_i^{\prime} \in A_i$.
>>>>>>
>>>>>> :::
>>>>>>
>>>>>> Should I use a different syntax or the filter is not enough?
>>>>>>
>>>>>

-- 
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/a52de802-1083-43e0-a302-42af9079779fn%40googlegroups.com.

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

      parent reply	other threads:[~2023-08-15  3:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 11:34 Enrico Mattia Salonia
     [not found] ` <75bf54f4-42e5-4f7e-954b-87a69d8d9057n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-08-04 14:20   ` Christophe Demko
     [not found]     ` <d35fe810-926a-462a-8ebf-64deeed7a289n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-08-04 14:33       ` Paul Kelleher
     [not found]         ` <6893cb2b-681e-4ed8-ae92-b4ce13dd4d4an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-08-04 14:36           ` Paul Kelleher
     [not found]             ` <87d4342c-ecd0-4ff2-9323-e124280b8da7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-08-07 10:27               ` Enrico Mattia Salonia
     [not found]                 ` <89746b58-348c-408b-9c06-37074cad444an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-08-08 14:06                   ` Paul Kelleher
     [not found]                     ` <629a3b14-2dbd-41b2-bca1-da3bed43bf67n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-08-15  3:43                       ` Enrico Mattia Salonia [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=a52de802-1083-43e0-a302-42af9079779fn@googlegroups.com \
    --to=mattia.salonia1-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).