LaTeX end document / endinput compliance

LaTeX end document / endinput compliance

[Luis Rivera]

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

Hello!

It seems that pandoc doesn't understand the `\end{document}` or `\endinput` 
instructions in the source code while converting LaTeX to other formats 
(I've tried docx or epub, for instance). How can I make it abide by these 
commands?

Thanks in advance,

Luis.

-- 
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/44a69616-a689-4fe8-9486-6beb8ae08f2d%40googlegroups.com.

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

Re: LaTeX end document / endinput compliance

[John MacFarlane]

Out of curiosity,  what do you have in your LaTeX document
after \end{document}?

Luis Rivera <jlrn77-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Hello!
>
> It seems that pandoc doesn't understand the `\end{document}` or `\endinput` 
> instructions in the source code while converting LaTeX to other formats 
> (I've tried docx or epub, for instance). How can I make it abide by these 
> commands?
>
> Thanks in advance,
>
> Luis.
>
> -- 
> 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/44a69616-a689-4fe8-9486-6beb8ae08f2d%40googlegroups.com.

Re: LaTeX end document / endinput compliance

[Luis Rivera]

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



On Friday, 4 October 2019 23:39:22 UTC-5, John MacFarlane wrote:
>
>
> Out of curiosity,  what do you have in your LaTeX document 
> after \end{document}? 
>
>
From the earliest days I put back there (as well as after \endinput) bits 
and pieces I don't want to discard, but don't make it to the final draft of 
the paper either. This way I don't clutter my directories with zettel, and 
I can find the discarded material for other purposes later. Then some 
people want opendoc/openxml copies for whatever reason, and then I found 
that the supposedly ignored materials pop up in the converted files.

BTW I also miss the ability to comment out material with the {comment} 
environment: but then regular %s do the job. 

Besides, the inability to handle materials this way with MarkDown is what 
keeps me from moving to that format altogether.

Cheers,

-- 
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/6bcd828b-6f90-45d4-a59f-f10b86dfb6f5%40googlegroups.com.

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

Re: LaTeX end document / endinput compliance

[Luis Rivera]

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

So, there is no know workaround about this issue? May I submit a feature 
request to the repo?

Confused,

On Saturday, 5 October 2019 12:37:43 UTC-5, Luis Rivera wrote:
>
>
>
> On Friday, 4 October 2019 23:39:22 UTC-5, John MacFarlane wrote:
>>
>>
>> Out of curiosity,  what do you have in your LaTeX document 
>> after \end{document}? 
>>
>>
> From the earliest days I put back there (as well as after \endinput) bits 
> and pieces I don't want to discard, but don't make it to the final draft of 
> the paper either. This way I don't clutter my directories with zettel, and 
> I can find the discarded material for other purposes later. Then some 
> people want opendoc/openxml copies for whatever reason, and then I found 
> that the supposedly ignored materials pop up in the converted files.
>
> BTW I also miss the ability to comment out material with the {comment} 
> environment: but then regular %s do the job. 
>
> Besides, the inability to handle materials this way with MarkDown is what 
> keeps me from moving to that format altogether.
>
> Cheers,
>
>

-- 
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/881d31da-683e-456f-aa3d-b46ef5809ef1%40googlegroups.com.

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

Re: LaTeX end document / endinput compliance

[John MacFarlane]

Yes, you can submit a feature request.

A workaround could be using sed to remove everything from the
input document after \end{document} before passing it to pandoc.

Luis Rivera <jlrn77-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> So, there is no know workaround about this issue? May I submit a feature 
> request to the repo?
>
> Confused,
>
> On Saturday, 5 October 2019 12:37:43 UTC-5, Luis Rivera wrote:
>>
>>
>>
>> On Friday, 4 October 2019 23:39:22 UTC-5, John MacFarlane wrote:
>>>
>>>
>>> Out of curiosity,  what do you have in your LaTeX document 
>>> after \end{document}? 
>>>
>>>
>> From the earliest days I put back there (as well as after \endinput) bits 
>> and pieces I don't want to discard, but don't make it to the final draft of 
>> the paper either. This way I don't clutter my directories with zettel, and 
>> I can find the discarded material for other purposes later. Then some 
>> people want opendoc/openxml copies for whatever reason, and then I found 
>> that the supposedly ignored materials pop up in the converted files.
>>
>> BTW I also miss the ability to comment out material with the {comment} 
>> environment: but then regular %s do the job. 
>>
>> Besides, the inability to handle materials this way with MarkDown is what 
>> keeps me from moving to that format altogether.
>>
>> Cheers,
>>
>>
>
> -- 
> 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/881d31da-683e-456f-aa3d-b46ef5809ef1%40googlegroups.com.

Re: LaTeX end document / endinput compliance

[Luis Rivera]

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

On the same train of thought, I wonder if a Lua filter would do the job (I 
have never used Lua, so this one seems like a gook chance to try).



On Monday, 21 October 2019 00:44:50 UTC-5, John MacFarlane wrote:
>
>
> Yes, you can submit a feature request. 
>
> A workaround could be using sed to remove everything from the 
> input document after \end{document} before passing it to pandoc. 
>
> Luis Rivera <jlr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <javascript:>> writes: 
>
> > So, there is no know workaround about this issue? May I submit a feature 
> > request to the repo? 
> > 
> > Confused, 
> > 
> > On Saturday, 5 October 2019 12:37:43 UTC-5, Luis Rivera wrote: 
> >> 
> >> 
> >> 
> >> On Friday, 4 October 2019 23:39:22 UTC-5, John MacFarlane wrote: 
> >>> 
> >>> 
> >>> Out of curiosity,  what do you have in your LaTeX document 
> >>> after \end{document}? 
> >>> 
> >>> 
> >> From the earliest days I put back there (as well as after \endinput) 
> bits 
> >> and pieces I don't want to discard, but don't make it to the final 
> draft of 
> >> the paper either. This way I don't clutter my directories with zettel, 
> and 
> >> I can find the discarded material for other purposes later. Then some 
> >> people want opendoc/openxml copies for whatever reason, and then I 
> found 
> >> that the supposedly ignored materials pop up in the converted files. 
> >> 
> >> BTW I also miss the ability to comment out material with the {comment} 
> >> environment: but then regular %s do the job. 
> >> 
> >> Besides, the inability to handle materials this way with MarkDown is 
> what 
> >> keeps me from moving to that format altogether. 
> >> 
> >> Cheers, 
> >> 
> >> 
> > 
> > -- 
> > 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-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pandoc-discuss/881d31da-683e-456f-aa3d-b46ef5809ef1%40googlegroups.com. 
>
>

-- 
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/b6342758-90c1-4e9a-82f1-b74947b7180f%40googlegroups.com.

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