search

RittmanMead / md_to_conf

Markdown to Confluence import
MIT License
231 stars 84 forks source link

Fixed & and " escaping #3

Closed mineshpatel1 closed 9 years ago

mineshpatel1 commented 9 years ago

That solves the problem with your doc not uploading but also allows those characters to render properly in fenced code blocks.

I tried to allow user spaces, but using ~minesh.patel I was getting 404 errors. Will have to look into why that is.

Also, I can't pull into develop - as one doesn't exist.

rmoff commented 9 years ago

I've created a develop branch - pull to it, or just merge it (you should rights), and then through to master because i'm happy with this new version, it's great :)

On 26 January 2015 at 18:31, mineshpatel1 notifications@github.com wrote:

That solves the problem with your doc not uploading but also allows those characters to render properly in fenced code blocks.

I tried to allow user spaces, but using ~minesh.patel I was getting 404 errors. Will have to look into why that is.

Also, I can't pull into develop - as one doesn't exist.

You can view, comment on, or merge this pull request online at:

https://github.com/RittmanMead/md_to_conf/pull/3 Commit Summary

  • Added new code and document. Archived deprecated code.
  • Fixed some issues with escaping special characters.
  • Removed temporary file.
  • Updated to read block quotes as information macros.
  • Updated Documentation
  • Updated script to fix quote and ampersand escaping. Attempted to allow personal space to be used but this did not work.

File Changes

Patch Links:

— Reply to this email directly or view it on GitHub https://github.com/RittmanMead/md_to_conf/pull/3.

Robin Moffatt Principal Consultant M: +44 7841 207 265 • E: robin.moffatt@rittmanmead.com S: robinmoffatt • T: @rmoff www.rittmanmead.com

Registered Office : Suite B, First Floor, Moore House, 11 - 13 Black Lion Street, Brighton, BN1 1ND, United Kingdom

Company No. : 6032852 VAT No. : 900 3839 48

Please note that this email communication is intended only for the addressee and may contain confidential or privileged information. The contents of this email may be circulated internally within your organisation only and may not be communicated to third parties without the prior written permission of Rittman Mead Consulting. This email is not intended nor should it be taken to create any legal relations, contractual or otherwise.