Converting from yaml no longer possible

Converting from yaml no longer possible

[John Lapeyre]

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

With pandoc 2.2.1, the following would work

pandoc --pdf-engine=xelatex  mydocdata.yml -o outputdoc.tex 
--template=input.pandoc.tex


Here input.pandoc.tex is a highly customized template. All the variables to 
fill in are defined in mydocdata.yml

With pandoc 2.9.2.1, I get the error

 [WARNING] Could not deduce format from file extension .yml
   Defaulting to markdown


Apparently, yaml is not supported as an input format. Does anyone know a 
way to get the same effect with recent versions of pandoc ?


-- 
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/0540a74b-0bc7-46ce-bc0c-4fb0579a1e5a%40googlegroups.com.

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

Re: Converting from yaml no longer possible

[Brandon Keith Biggs]

[-- Attachment #1: Type: text/plain, Size: 2271 bytes --]

def getRefHypPair(content):
"""Return list of strings of REFs and HYPs from .dtl file"""
ref_hyp_pair = []
for i in content:
# the if statement skips the header row
if 'CONFUSION PAIRS' in i:
continue
#print(i[-1].strip())
if '==>' in i[-1]:
#This first split takes the pair only
i = i.split("->")[1]
# you don't need the [-1], i is a string now. (I took the -1 away)
# when you run it, you can remove ref_hyp_pair[0].lower() by doing the
.lower() here.
# you can remove the ==>
ref_hyp = i.strip().lower().split(" ==> ")
ref_hyp_pair.append(ref_hyp)
return ref_hyp_pair

Brandon Keith Biggs <http://brandonkeithbiggs.com/>


On Thu, Apr 16, 2020 at 8:04 PM John Lapeyre <john.lapeyre-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> With pandoc 2.2.1, the following would work
>
> pandoc --pdf-engine=xelatex  mydocdata.yml -o outputdoc.tex
> --template=input.pandoc.tex
>
>
> Here input.pandoc.tex is a highly customized template. All the variables
> to fill in are defined in mydocdata.yml
>
> With pandoc 2.9.2.1, I get the error
>
>  [WARNING] Could not deduce format from file extension .yml
>    Defaulting to markdown
>
>
> Apparently, yaml is not supported as an input format. Does anyone know a
> way to get the same effect with recent versions of pandoc ?
>
>
> --
> 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/0540a74b-0bc7-46ce-bc0c-4fb0579a1e5a%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/0540a74b-0bc7-46ce-bc0c-4fb0579a1e5a%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAKAWQkUyr%2Bj5-9ioeVeSd%3DyR0g2Kwz4oOpMmhX4cMKCz_7jq5Q%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 3870 bytes --]

Re: Converting from yaml no longer possible

[Brandon Keith Biggs]

[-- Attachment #1: Type: text/plain, Size: 2554 bytes --]

Sorry, sent to the wrong email.

Brandon Keith Biggs <http://brandonkeithbiggs.com/>


On Thu, Apr 16, 2020 at 8:21 PM Brandon Keith Biggs <
brandonkeithbiggs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> def getRefHypPair(content):
> """Return list of strings of REFs and HYPs from .dtl file"""
> ref_hyp_pair = []
> for i in content:
> # the if statement skips the header row
> if 'CONFUSION PAIRS' in i:
> continue
> #print(i[-1].strip())
> if '==>' in i[-1]:
> #This first split takes the pair only
> i = i.split("->")[1]
> # you don't need the [-1], i is a string now. (I took the -1 away)
> # when you run it, you can remove ref_hyp_pair[0].lower() by doing the
> .lower() here.
> # you can remove the ==>
> ref_hyp = i.strip().lower().split(" ==> ")
> ref_hyp_pair.append(ref_hyp)
> return ref_hyp_pair
>
> Brandon Keith Biggs <http://brandonkeithbiggs.com/>
>
>
> On Thu, Apr 16, 2020 at 8:04 PM John Lapeyre <john.lapeyre-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> wrote:
>
>> With pandoc 2.2.1, the following would work
>>
>> pandoc --pdf-engine=xelatex  mydocdata.yml -o outputdoc.tex
>> --template=input.pandoc.tex
>>
>>
>> Here input.pandoc.tex is a highly customized template. All the variables
>> to fill in are defined in mydocdata.yml
>>
>> With pandoc 2.9.2.1, I get the error
>>
>>  [WARNING] Could not deduce format from file extension .yml
>>    Defaulting to markdown
>>
>>
>> Apparently, yaml is not supported as an input format. Does anyone know a
>> way to get the same effect with recent versions of pandoc ?
>>
>>
>> --
>> 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/0540a74b-0bc7-46ce-bc0c-4fb0579a1e5a%40googlegroups.com
>> <https://groups.google.com/d/msgid/pandoc-discuss/0540a74b-0bc7-46ce-bc0c-4fb0579a1e5a%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/CAKAWQkWzm9taFOii00KXizb%3Dr5rDKDz7K-2304DADLk6or1vww%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 4526 bytes --]

Re: Converting from yaml no longer possible

[John MacFarlane]

If the YAML is pandoc markdown metadata, between

---

and

...

you can just add -f markdown.

John Lapeyre <john.lapeyre-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> With pandoc 2.2.1, the following would work
>
> pandoc --pdf-engine=xelatex  mydocdata.yml -o outputdoc.tex 
> --template=input.pandoc.tex
>
>
> Here input.pandoc.tex is a highly customized template. All the variables to 
> fill in are defined in mydocdata.yml
>
> With pandoc 2.9.2.1, I get the error
>
>  [WARNING] Could not deduce format from file extension .yml
>    Defaulting to markdown
>
>
> Apparently, yaml is not supported as an input format. Does anyone know a 
> way to get the same effect with recent versions of pandoc ?
>
>
> -- 
> 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/0540a74b-0bc7-46ce-bc0c-4fb0579a1e5a%40googlegroups.com.

Re: Converting from yaml no longer possible

[John Lapeyre]

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

Yes, I intend the file with YAML to be pandoc markdown metadata.  I have 
had --- and --- surrounding all the content, except some comments at the 
end (with # as the comment character)
I replaced the final --- with ... and verified with pandoc 2.2.1 that the 
document produced is identical.

However, I am unsure where to put "-f markdown". I tried putting it in 
various places. For example, if the first two lines of the YAML document are
---
-f markdown

Then, pandoc 2.9.2.1 gives this message "[WARNING] Could not parse YAML 
metadata at line 6 column 1: did not find expected <document start>"

So instead, I tried using "-f markdown" on the command line. In this case, 
pandoc 2.9.2.1 gives this warning:
[WARNING] Could not parse YAML metadata at line 953 column 1: Duplicate key 
in mapping: Scalar (Pos {posByteOffset = 16004, posCharOffset = 15999, 
posLine = 386, posColumn = 0}) (SUnknown Nothing "educationtitle")

There are 951 lines in the file.

In both of the two latter cases, it appears that none of the metadata is 
read; the tex document is written as if all variables were the empty string.

I then tried removing most of the data from the YAML file and I find that 
pandoc 2.9.2.1, with "-f markdown" on the command line  *does* make the 
expected substitutions using the small amount of data in the YAML file. I 
see at least two possibilities: 1) My big metadata file is not legal YAML, 
but was accepted by older versions of pandoc. 2) My big metadata file is 
legal YAML, but there is a bug in newer versions of pandoc.

In any case, is the following true ? One can create a document from only a 
pandoc YAML metadata file and a custom template if one specifies "-f 
markdown" on the command line.

On Friday, April 17, 2020 at 9:31:15 AM UTC-7, John MacFarlane wrote:
>
>
> If the YAML is pandoc markdown metadata, between 
>
> --- 
>
> and 
>
> ... 
>
> you can just add -f markdown. 
>
> John Lapeyre <john....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <javascript:>> writes: 
>
> > With pandoc 2.2.1, the following would work 
> > 
> > pandoc --pdf-engine=xelatex  mydocdata.yml -o outputdoc.tex 
> > --template=input.pandoc.tex 
> > 
> > 
> > Here input.pandoc.tex is a highly customized template. All the variables 
> to 
> > fill in are defined in mydocdata.yml 
> > 
> > With pandoc 2.9.2.1, I get the error 
> > 
> >  [WARNING] Could not deduce format from file extension .yml 
> >    Defaulting to markdown 
> > 
> > 
> > Apparently, yaml is not supported as an input format. Does anyone know a 
> > way to get the same effect with recent versions of pandoc ? 
> > 
> > 
> > -- 
> > 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/0540a74b-0bc7-46ce-bc0c-4fb0579a1e5a%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/7a408d67-fe8d-4809-a5b0-a75824347b2f%40googlegroups.com.

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

Re: Converting from yaml no longer possible

[John MacFarlane]

Put -f markdown on the command line.


John Lapeyre <john.lapeyre-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Yes, I intend the file with YAML to be pandoc markdown metadata.  I have 
> had --- and --- surrounding all the content, except some comments at the 
> end (with # as the comment character)
> I replaced the final --- with ... and verified with pandoc 2.2.1 that the 
> document produced is identical.
>
> However, I am unsure where to put "-f markdown". I tried putting it in 
> various places. For example, if the first two lines of the YAML document are
> ---
> -f markdown
>
> Then, pandoc 2.9.2.1 gives this message "[WARNING] Could not parse YAML 
> metadata at line 6 column 1: did not find expected <document start>"
>
> So instead, I tried using "-f markdown" on the command line. In this case, 
> pandoc 2.9.2.1 gives this warning:
> [WARNING] Could not parse YAML metadata at line 953 column 1: Duplicate key 
> in mapping: Scalar (Pos {posByteOffset = 16004, posCharOffset = 15999, 
> posLine = 386, posColumn = 0}) (SUnknown Nothing "educationtitle")
>
> There are 951 lines in the file.
>
> In both of the two latter cases, it appears that none of the metadata is 
> read; the tex document is written as if all variables were the empty string.
>
> I then tried removing most of the data from the YAML file and I find that 
> pandoc 2.9.2.1, with "-f markdown" on the command line  *does* make the 
> expected substitutions using the small amount of data in the YAML file. I 
> see at least two possibilities: 1) My big metadata file is not legal YAML, 
> but was accepted by older versions of pandoc. 2) My big metadata file is 
> legal YAML, but there is a bug in newer versions of pandoc.
>
> In any case, is the following true ? One can create a document from only a 
> pandoc YAML metadata file and a custom template if one specifies "-f 
> markdown" on the command line.
>
> On Friday, April 17, 2020 at 9:31:15 AM UTC-7, John MacFarlane wrote:
>>
>>
>> If the YAML is pandoc markdown metadata, between 
>>
>> --- 
>>
>> and 
>>
>> ... 
>>
>> you can just add -f markdown. 
>>
>> John Lapeyre <john....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <javascript:>> writes: 
>>
>> > With pandoc 2.2.1, the following would work 
>> > 
>> > pandoc --pdf-engine=xelatex  mydocdata.yml -o outputdoc.tex 
>> > --template=input.pandoc.tex 
>> > 
>> > 
>> > Here input.pandoc.tex is a highly customized template. All the variables 
>> to 
>> > fill in are defined in mydocdata.yml 
>> > 
>> > With pandoc 2.9.2.1, I get the error 
>> > 
>> >  [WARNING] Could not deduce format from file extension .yml 
>> >    Defaulting to markdown 
>> > 
>> > 
>> > Apparently, yaml is not supported as an input format. Does anyone know a 
>> > way to get the same effect with recent versions of pandoc ? 
>> > 
>> > 
>> > -- 
>> > 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/0540a74b-0bc7-46ce-bc0c-4fb0579a1e5a%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/7a408d67-fe8d-4809-a5b0-a75824347b2f%40googlegroups.com.

Re: Converting from yaml no longer possible

[John MacFarlane]

John Lapeyre <john.lapeyre-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> So instead, I tried using "-f markdown" on the command line. In this case, 
> pandoc 2.9.2.1 gives this warning:
> [WARNING] Could not parse YAML metadata at line 953 column 1: Duplicate key 
> in mapping: Scalar (Pos {posByteOffset = 16004, posCharOffset = 15999, 
> posLine = 386, posColumn = 0}) (SUnknown Nothing "educationtitle")

Try looking at line 386 or thereabouts.  Do you have two keys
marked educationtitle?  That would be invalid YAML.  It could be
that the new YAML parser we're using is stricter.

Re: Converting from yaml no longer possible

[John Lapeyre]

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

 > Do you have two keys marked educationtitle?

Yes, this is exactly the problem. The YAML file is assembled from a perl 
script, which has a bug.  So two things have changed, 1) -f markdown must 
be specified explicitly 2) keys must be unique.
Now the output document is the same as before. Thanks.

On Thursday, April 16, 2020 at 8:04:08 PM UTC-7, John Lapeyre wrote:
>
> With pandoc 2.2.1, the following would work
>
> pandoc --pdf-engine=xelatex  mydocdata.yml -o outputdoc.tex 
> --template=input.pandoc.tex
>
>
> Here input.pandoc.tex is a highly customized template. All the variables 
> to fill in are defined in mydocdata.yml
>
> With pandoc 2.9.2.1, I get the error
>
>  [WARNING] Could not deduce format from file extension .yml
>    Defaulting to markdown
>
>
> Apparently, yaml is not supported as an input format. Does anyone know a 
> way to get the same effect with recent versions of pandoc ?
>
>
>

-- 
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/7b796e6c-ceec-4de8-942d-a004e0761afc%40googlegroups.com.

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