Antti Korpi
Antti Korpi
I'd like to help here, but I don't have a Windows machine to test on. I tried creating a Windows build on AppVeyor in [this branch](https://github.com/anko/markdown-pdf/commit/8572c60c3759d46f94a6f0b80dfd75205f684146) a while ago (so...
PR #121 is essentially this change, so it may fix CSS too. We don't have a Windows CI yet: could a Windows user confirm?
I agree. This happens because the URL in parentheses is added [using CSS](https://github.com/alanshaw/markdown-pdf/blob/05985b3431e7c6117ce1c24c33421ab6b1a0b589/html5bp/css/main.css#L246-L248) to any ``. Implementation idea: Drop the CSS. Instead use [remark](https://github.com/wooorm/remark) to parse the markdown into [mdast](https://github.com/wooorm/mdast),...
Could you show a [minimal example](http://www.sscce.org/) of input that fails that way? How does the same CSS rule look in a web browser?
Hmm, I tried that text in `test.md` and CSS in `main.css` and ran this: ``` sh markdown-pdf --css-path main.css test.md ``` The output `test.pdf`'s text looks as I'd expect: ...
I used `node` 5.1.0, `markdown-pdf` 6.0.0, `phantomjs` 1.9.2, and a 64-bit Linux. You? I tried a few different fonts, paper sizes and page borders and just can't get that to...
> the css code isn't been efective with phantomjs 2.0 Works for me both with a manually installed phantomjs 2.0.0, and with 1.9.8 (which the [npm module called phantomjs](https://www.npmjs.com/package/phantomjs) installs;...
Having trouble reproducing this. This works for me: ``` $ uname Linux $ node --version v7.10.0 $ cd $(mktemp --dir) $ npm i markdown-pdf [ ... npm output ... ]...
@alanshaw > The original thought behind this was that if you were creating a thesis or a book or something you might want to have the chapters in separate markdown...
Not currently. At the moment, we don't have _any_ clickable links in output PDFs yet: that's issue #30. We're waiting on upstream [ariya/phantomjs](https://github.com/ariya/phantomjs) to release v2.0.1 which would enable this....