Brett on 22 Aug, 2017 07:06 PM
This is most likely a Google Docs problem. Google Docs isn't a plain
text editor, it works with an XML-based rich text. Only converting it to
plain text will allow processing through Markdown apps, and it doesn't
make that terribly easy without giving up ALL styling.
My suggestion would be to not work in Google Docs if you want to export
through Marked. If you need the collaborative aspects, you can use
Quip.com, which has built-in Markdown export for documentation. Might be
worth looking into.
Brett on 22 Aug, 2017 07:09 PM
Oh, and specifically regarding code, the PDF format in general is likely
going to cause issues with anything it sees as a line break (or soft
wrap) when copying. The best bet would be to use the \ continue syntax
for shells like bash, and wrap the lines at less than page width, e.g.:
This format-preserved output window, whether Windows Shell, C++, Python, Bash, etc... is probably NOT able to be reproduced through PDF, correct? I am now starting to realize why so many software products provide their 'Help' documents in HTML format.
If this becomes my case and I decide to start providing my guides in HTML format, would Marked help me accomplish these windows with preserved formatting?