Cannot handle filenames containing spaces about docx2gfm HOT 4 CLOSED

This breaks ANY file name on Windows.

from docx2gfm.

Thanks for reporting the issue @Arghriffic.

I haven't tested on Windows, so I wouldn't be surprized if there were some issues on that OS.

Can you confirm what exactly is breaking things in WIndows?
Also I deployed a new version (0.3.0) yesterday, in case you want to test with that.

from docx2gfm.

Thanks for reporting the issue @Arghriffic.

I haven't tested on Windows, so I wouldn't be surprized if there were some issues on that OS.

Can you confirm what exactly is breaking things in WIndows? Also I deployed a new version (0.3.0) yesterday, in case you want to test with that.

Any file you try to open results in a pandoc "openBinaryFile: does not exist (No such file or directory)" it does not matter what the name is. Spaces, no Spaces, single quotes, double quotes. Completely breaks it.

from docx2gfm.

Hm, interesting.

The way that docx2gfm calls pandoc is this:
pandoc '<your-file-here>' --wrap=none --atx-headers -f docx -t markdown-bracketed_spans-link_attributes-smart-simple_tables -s

I can only speculate what might cause this.

1: Would you mind trying that out directly, to see if that works?
I a wondering if maybe on Windows the pandoc CLI options are different? Although that would be surprizing.

2: Which ruby version are you using, so that I can test with that too?

Thanks again for the bug report and for your help in debugging this.

from docx2gfm.