Possible to use raw_attribute to insert an index entry?

Possible to use raw_attribute to insert an index entry?

[Paul Potts]

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

Hello,

I am looking for a way to mark index entries in my Markdown text, which 
will wind up in the output when the output is .docx.

Looking at the manual example of inserting a page break, with:

```{=openxml}
<w:p>
<w:r>
<w:br w:type="page"/>
</w:r>
</w:p>
```

This works OK for me; if I generate a .docx file, it has a page break in 
place of that block, while if I generate an .html file, there's nothing 
there. That's exactly how I want it to work.

I'd like to do something like:

The kids spent January 1st assembling a giant ```{=openxml} 
<text:a><text:alphabetical-index-mark-start>LEGO 
Ninjago<text:alphabetical-index-mark-end></text:a>``` LEGO Ninjago movie set

That doesn't work right at all. I'm really speculating here, because I was 
not able to find any similar examples. So I'm probably way off base, but 
what I'm trying to do is mark index entries, in a way that will be 
invisible if the output is HTML, so that the generated .docx file is ready 
to index.

Basically, I'm trying to make a book-length .docx file out of text in a 
number of Markdown files and I'd like to do as little finishing work in 
Word or OpenOffice as possible.

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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/b88f670b-509b-43bc-9c88-15fa01493c65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: Possible to use raw_attribute to insert an index entry?

[John MacFarlane]

You should add the index entries using Word, then
inspect the openxml it produces.

Paul Potts <paul-2ivHbsYhlDHrG+TUHvIryNi2O/JbrIOy@public.gmane.org> writes:

> Hello,
>
> I am looking for a way to mark index entries in my Markdown text, which 
> will wind up in the output when the output is .docx.
>
> Looking at the manual example of inserting a page break, with:
>
> ```{=openxml}
> <w:p>
> <w:r>
> <w:br w:type="page"/>
> </w:r>
> </w:p>
> ```
>
> This works OK for me; if I generate a .docx file, it has a page break in 
> place of that block, while if I generate an .html file, there's nothing 
> there. That's exactly how I want it to work.
>
> I'd like to do something like:
>
> The kids spent January 1st assembling a giant ```{=openxml} 
> <text:a><text:alphabetical-index-mark-start>LEGO 
> Ninjago<text:alphabetical-index-mark-end></text:a>``` LEGO Ninjago movie set
>
> That doesn't work right at all. I'm really speculating here, because I was 
> not able to find any similar examples. So I'm probably way off base, but 
> what I'm trying to do is mark index entries, in a way that will be 
> invisible if the output is HTML, so that the generated .docx file is ready 
> to index.
>
> Basically, I'm trying to make a book-length .docx file out of text in a 
> number of Markdown files and I'd like to do as little finishing work in 
> Word or OpenOffice as possible.
>
> 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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/b88f670b-509b-43bc-9c88-15fa01493c65%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Re: Possible to use raw_attribute to insert an index entry?

[Paul Potts]

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

On Monday, October 1, 2018 at 5:56:17 PM UTC-4, John MacFarlane wrote:
>
>
> You should add the index entries using Word, then 
> inspect the openxml it produces.
>

I made a simple Word file with just the text "one two three four five" and 
turned "three" into an index entry. I get this for the "two three four."

two three</w:t></w:r><w:r><w:fldChar 
w:fldCharType="begin"/></w:r><w:r><w:instrText xml:space="preserve"> XE 
"</w:instrText></w:r><w:r 
w:rsidRPr="00F0606A"><w:instrText>three</w:instrText></w:r><w:r><w:instrText 
xml:space="preserve">" </w:instrText></w:r><w:r><w:fldChar 
w:fldCharType="end"/></w:r><w:r><w:t xml:space="preserve"> four

That's pretty horrible.

Creating a similar file with OpenOffice and saving it in .odt format 
produces something much more legible:

<text:p text:style-name="Standard">two three 
<text:alphabetical-index-mark-start 
text:id="IMark113120816"/>four<text:alphabetical-index-mark-end 
text:id="IMark113120816"/> five six</text:p>

So I'm going to try some experiments with .odt format. I'm not sure how I 
would generate the unique identifier or whatever it is in the "IMark" field 
but I'll see what I can figure out.

Thanks,

Paul
  
Paul Potts <pa...-2ivHbsYhlDHrG+TUHvIryNi2O/JbrIOy@public.gmane.org <javascript:>> writes: 

> Hello, 
> 
> I am looking for a way to mark index entries in my Markdown text, which 
> will wind up in the output when the output is .docx. 
> 
> Looking at the manual example of inserting a page break, with: 
> 
> ```{=openxml} 
> <w:p> 
> <w:r> 
> <w:br w:type="page"/> 
> </w:r> 
> </w:p> 
> ``` 
> 
> This works OK for me; if I generate a .docx file, it has a page break in 
> place of that block, while if I generate an .html file, there's nothing 
> there. That's exactly how I want it to work. 
> 
> I'd like to do something like: 
> 
> The kids spent January 1st assembling a giant ```{=openxml} 
> <text:a><text:alphabetical-index-mark-start>LEGO 
> Ninjago<text:alphabetical-index-mark-end></text:a>``` LEGO Ninjago movie 
set 
> 
> That doesn't work right at all. I'm really speculating here, because I 
was 
> not able to find any similar examples. So I'm probably way off base, but 
> what I'm trying to do is mark index entries, in a way that will be 
> invisible if the output is HTML, so that the generated .docx file is 
ready 
> to index. 
> 
> Basically, I'm trying to make a book-length .docx file out of text in a 
> number of Markdown files and I'd like to do as little finishing work in 
> Word or OpenOffice as possible. 
> 
> 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-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org 
<javascript:>. 
> To view this discussion on the web visit 
https://groups.google.com/d/msgid/pandoc-discuss/b88f670b-509b-43bc-9c88-15fa01493c65%40googlegroups.com. 

> For more options, visit https://groups.google.com/d/optout. 

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/e39dc095-cc88-49c5-ae3d-eee17512b5e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: Possible to use raw_attribute to insert an index entry?

[bwhelm]

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

I have a pandoc filter that I use primarily for adding comments to 
documents, but I also use it for things like cross-references and index 
entries. I just played around with indexing in docx a bit to see if I can 
get it to work, and it *seems* to work OK on simple documents. You might 
check it out here:

<https://github.com/bwhelm/Pandoc-Comment-Filter>

The syntax is to add `[INDEX ENTRY]{.i}` to a markdown file, which will 
produce this xml that Word will recognize as an index entry:

<w:r><w:fldChar w:fldCharType="begin" /></w:r><w:r><w:instrText 
xml:space="preserve"> XE &quot;</w:instrText></w:r><w:r><w:instrText>INDEX 
ENTRY</w:instrText></w:r><w:r><w:instrText xml:space="preserve">&quot; 
</w:instrText></w:r><w:r><w:fldChar w:fldCharType="end" /></w:r>

I don't know if that's the right way to do it, and it won't handle fancier 
types of index entries that Word can do (with main- and sub-entries, with 
specially formatted page numbers, etc.), but it's at least a proof of 
concept. I'd welcome any improvements to the filter as a pull request.

Incidentally, here's the relevant bits taken out of the luafilter:

~~~ {.lua}
local DOCX_TEXT = {}
DOCX_TEXT.i = {}
DOCX_TEXT.i.Open = '<w:r><w:fldChar 
w:fldCharType="begin"/></w:r><w:r><w:instrText xml:space="preserve"> XE 
"</w:instrText></w:r><w:r><w:instrText>'
DOCX_TEXT.i.Close = '</w:instrText></w:r><w:r><w:instrText 
xml:space="preserve">" </w:instrText></w:r><w:r><w:fldChar 
w:fldCharType="end"/></w:r>'
function handleInlines(span)
    local spanType = span.classes[1]
    if spanType == "i" then
        -- Process indexing ...
        if FORMAT == 'docx' then
            print(span.content)
            return docx(
                DOCX_TEXT.i.Open ..
                pandoc.utils.stringify(span.content) ..
                DOCX_TEXT.i.Close)
        else
            return {}
        end
    end
end

local COMMENT_FILTER = {
    {Span = handleInlines}
}

return COMMENT_FILTER
~~~

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/4cb35271-a7aa-4f41-8ee7-da2d35612e92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: Possible to use raw_attribute to insert an index entry?

[Paul Potts]

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

On Monday, October 1, 2018 at 6:54:27 PM UTC-4, bwhelm wrote:
>
> I have a pandoc filter that I use primarily for adding comments to 
> documents, but I also use it for things like cross-references and index 
> entries. I just played around with indexing in docx a bit to see if I can 
> get it to work, and it *seems* to work OK on simple documents. You might 
> check it out here:
>
> <https://github.com/bwhelm/Pandoc-Comment-Filter>
>
> The syntax is to add `[INDEX ENTRY]{.i}` to a markdown file, which will 
> produce this xml that Word will recognize as an index entry:
>
> <w:r><w:fldChar w:fldCharType="begin" /></w:r><w:r><w:instrText 
> xml:space="preserve"> XE &quot;</w:instrText></w:r><w:r><w:instrText>INDEX 
> ENTRY</w:instrText></w:r><w:r><w:instrText xml:space="preserve">&quot; 
> </w:instrText></w:r><w:r><w:fldChar w:fldCharType="end" /></w:r>
>
> I don't know if that's the right way to do it, and it won't handle fancier 
> types of index entries that Word can do (with main- and sub-entries, with 
> specially formatted page numbers, etc.), but it's at least a proof of 
> concept. I'd welcome any improvements to the filter as a pull request.
>
> Incidentally, here's the relevant bits taken out of the luafilter:
>
> ~~~ {.lua}
> local DOCX_TEXT = {}
> DOCX_TEXT.i = {}
> DOCX_TEXT.i.Open = '<w:r><w:fldChar 
> w:fldCharType="begin"/></w:r><w:r><w:instrText xml:space="preserve"> XE 
> "</w:instrText></w:r><w:r><w:instrText>'
> DOCX_TEXT.i.Close = '</w:instrText></w:r><w:r><w:instrText 
> xml:space="preserve">" </w:instrText></w:r><w:r><w:fldChar 
> w:fldCharType="end"/></w:r>'
> function handleInlines(span)
>     local spanType = span.classes[1]
>     if spanType == "i" then
>         -- Process indexing ...
>         if FORMAT == 'docx' then
>             print(span.content)
>             return docx(
>                 DOCX_TEXT.i.Open ..
>                 pandoc.utils.stringify(span.content) ..
>                 DOCX_TEXT.i.Close)
>         else
>             return {}
>         end
>     end
> end
>
> local COMMENT_FILTER = {
>     {Span = handleInlines}
> }
>
> return COMMENT_FILTER
> ~~~
>

Oh, thank you!

Right now I think I'm going to focus on .odt since it looks simpler. But I 
was hoping I'd be able to do some kind of simple tag for an index entry in 
the Markdown and then use a Lua filter to generate the tags for the .odt. 
So I hope to use that as an example. I'll see how far I can get.

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/c6c5074a-0c64-4b42-a116-4997db739702%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: Possible to use raw_attribute to insert an index entry?

[Paul Potts]

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

On Monday, October 1, 2018 at 5:56:17 PM UTC-4, John MacFarlane wrote:
>
>
> You should add the index entries using Word, then 
> inspect the openxml it produces. 
>

Hmmm... I had posted a reply but for some reason the groups page is now 
saying it is deleted. I have no idea why.

Anyway, I'm doing what you suggested. What I discovered is that the .docx 
tags are very complex compared to the .odt tags so I'm going to try to 
stick with .odt and see if I can get that working.

Thanks,

Paul

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/cb3caa88-41f2-454c-a8bf-92184e369c43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: Possible to use raw_attribute to insert an index entry?

[Paul Potts]

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



On Monday, October 1, 2018 at 6:54:27 PM UTC-4, bwhelm wrote:
>
> I have a pandoc filter that I use primarily for adding comments to 
> documents, but I also use it for things like cross-references and index 
> entries. I just played around with indexing in docx a bit to see if I can 
> get it to work, and it *seems* to work OK on simple documents. You might 
> check it out here:
>
> <https://github.com/bwhelm/Pandoc-Comment-Filter>
>
> The syntax is to add `[INDEX ENTRY]{.i}` to a markdown file, which will 
> produce this xml that Word will recognize as an index entry:
>
> <w:r><w:fldChar w:fldCharType="begin" /></w:r><w:r><w:instrText 
> xml:space="preserve"> XE &quot;</w:instrText></w:r><w:r><w:instrText>INDEX 
> ENTRY</w:instrText></w:r><w:r><w:instrText xml:space="preserve">&quot; 
> </w:instrText></w:r><w:r><w:fldChar w:fldCharType="end" /></w:r>
>
> I don't know if that's the right way to do it, and it won't handle fancier 
> types of index entries that Word can do (with main- and sub-entries, with 
> specially formatted page numbers, etc.), but it's at least a proof of 
> concept. I'd welcome any improvements to the filter as a pull request.
>
> Incidentally, here's the relevant bits taken out of the luafilter:
>
> ~~~ {.lua}
> local DOCX_TEXT = {}
> DOCX_TEXT.i = {}
> DOCX_TEXT.i.Open = '<w:r><w:fldChar 
> w:fldCharType="begin"/></w:r><w:r><w:instrText xml:space="preserve"> XE 
> "</w:instrText></w:r><w:r><w:instrText>'
> DOCX_TEXT.i.Close = '</w:instrText></w:r><w:r><w:instrText 
> xml:space="preserve">" </w:instrText></w:r><w:r><w:fldChar 
> w:fldCharType="end"/></w:r>'
> function handleInlines(span)
>     local spanType = span.classes[1]
>     if spanType == "i" then
>         -- Process indexing ...
>         if FORMAT == 'docx' then
>             print(span.content)
>             return docx(
>                 DOCX_TEXT.i.Open ..
>                 pandoc.utils.stringify(span.content) ..
>                 DOCX_TEXT.i.Close)
>         else
>             return {}
>         end
>     end
> end
>
> local COMMENT_FILTER = {
>     {Span = handleInlines}
> }
>
> return COMMENT_FILTER
> ~~~
>

OK, I have made some progress but I'm having difficulty with the Lua 
filter. I've basically tried to follow your example except modify the code 
to generate the simpler .odt index mark syntax. So I've got:

~~~
local random = math.random
local function uuid()
    local template ='xxxxxyyyyy'
    return string.gsub(template, '[xy]', function (c)
        local v = (c == 'x') and random(0, 0xf) or random(8, 0xb)
        return string.format('%x', v)
    end)
end

function handleInlines(span)
    local spanType = span.classes[1]
    if spanType == "i" then
        if FORMAT == 'odt' then
            local id_str = uuid()
            local open_str = '<text:alphabetical-index-mark-start 
text:id=\"' .. id_str .. '\" />'
            local close_str = '<text:alphabetical-index-mark-end 
text:id=\"' .. id_str .. '\" />'
            local ret_element = {c = open_str .. 
pandoc.utils.stringify(span.content) .. close_str}
            print (ret_element)
            for k,v in pairs(ret_element) do
                print(k)
                print(v)
            end
            local p_ret_element = pandoc.Str(open_str .. 
pandoc.utils.stringify(span.content) .. close_str)
            print (p_ret_element)
            for k,v in pairs(p_ret_element) do
                print(k)
                print(v)
            end
            return { ret_element }
        else
            return {}
        end
    end
end

local COMMENT_FILTER = {
    {Span = handleInlines}
}

return COMMENT_FILTER
~~~

In my Markdown source I've got [Lego Ninjago]{.i}

I've tried two approaches to create the return value of the handleinlines() 
function.

If I use return { p_ret_element} the filter runs, but the resulting .odt 
span looks like this:

    <text:span text:style-name="T1">&lt;text:alphabetical-index-mark-start 
text:id=&quot;093c999bba&quot; /&gt;Lego 
Ninjago&lt;text:alphabetical-index-mark-end text:id=&quot;093c999bba&quot; 
/&gt;</text:span>

In other words, it's converting the brackets and quotation marks and things 
like that entities, while I want them to be literal.

So I'm wondering what needs to be in the returned list. It looks like a 
table with one element named 'c.' But if I try making my own table and 
putting it in the list as the return value, pandoc doesn't like what it is 
getting back. Here's the output (from PowerShell):

table: 0000000004373080
c
<text:alphabetical-index-mark-start text:id="093c999bba" />Lego 
Ninjago<text:alphabetical-index-mark-end text:id="093c999bba" />
table: 0000000004373180
c
<text:alphabetical-index-mark-start text:id="093c999bba" />Lego 
Ninjago<text:alphabetical-index-mark-end text:id="093c999bba" />
Error running filter index_entries_odt.lua:
Could not read list: Could not get Inline value: Expected a string but got 
a nil

So Pandoc is expecting something that pandoc.Str produces, but I don't want 
the functionality of pandoc.Str to be applied to the string I've assembled. 
Any ideas? I hope that makes sense, and hope the formatting wasn't too 
butchered to be readable.

Thanks,

Paul

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/07ccaf96-d95d-44dd-8dd3-74f84e258e6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: Possible to use raw_attribute to insert an index entry?

[Paul Potts]

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

Thinking about it a little more, I guess it isn't pandoc.Str that is 
converting the characters to entities. It must be Pandoc itself doing this. 
So I'm wondering what I can return that would avoid this -- a different 
type of filter function?

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/f8b340ed-e114-48d9-99f9-2535f29ecaef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: Possible to use raw_attribute to insert an index entry?

[John MacFarlane]

Paul Potts <paul-2ivHbsYhlDHrG+TUHvIryNi2O/JbrIOy@public.gmane.org> writes:

> So Pandoc is expecting something that pandoc.Str produces, but I don't want 
> the functionality of pandoc.Str to be applied to the string I've assembled. 
> Any ideas? I hope that makes sense, and hope the formatting wasn't too 
> butchered to be readable.

Use pandoc.RawInline('opendocument', yourstring)

Re: Possible to use raw_attribute to insert an index entry?

[Paul Potts]

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

On Tuesday, October 2, 2018 at 6:08:34 PM UTC-4, John MacFarlane wrote:
>
> Paul Potts <pa...-2ivHbsYhlDHrG+TUHvIryNi2O/JbrIOy@public.gmane.org <javascript:>> writes: 
>
> > So Pandoc is expecting something that pandoc.Str produces, but I don't 
> want 
> > the functionality of pandoc.Str to be applied to the string I've 
> assembled. 
> > Any ideas? I hope that makes sense, and hope the formatting wasn't too 
> > butchered to be readable. 
>
> Use pandoc.RawInline('opendocument', yourstring) 
>
> AHA! Success! Thank you!

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/69fbd7ad-0f37-4b8f-b018-5cd8b9802fe6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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