Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert docx into Markdown #1

Closed
DinisCruz opened this issue Oct 31, 2014 · 3 comments
Closed

Convert docx into Markdown #1

DinisCruz opened this issue Oct 31, 2014 · 3 comments
Milestone

Comments

@DinisCruz
Copy link

i.e. this file OWASP_ASVS_Version_2.docx

@danielcuthbert
Copy link
Collaborator

help me understand why? is there that much of a demand for this? the reason word was chosen is that it's universally used in organisations. Whilst I dont have the cycles to look at converting, if there is a demand and someone is willing, then i'm all for that.

@DinisCruz
Copy link
Author

The main reason is too allow easy collaboration (and version control) when
writing and updating the document

And ideally the full workflow would be automated in a CI like workflow (see
here how I did it for the books I'm currently writing:
http://blog.diniscruz.com/2014/04/workflow-to-create-new-leanpub-book.html?m=1
)
On 1 Nov 2014 15:42, "Daniel Cuthbert" notifications@github.com wrote:

help me understand why? is there that much of a demand for this? the
reason word was chosen is that it's universally used in organisations.
Whilst I dont have the cycles to look at converting, if there is a demand
and someone is willing, then i'm all for that.


Reply to this email directly or view it on GitHub
#1 (comment).

@xetch
Copy link

xetch commented Jul 19, 2015

+1

tghosth pushed a commit that referenced this issue Jan 26, 2019
Merge upstream changes
tghosth pushed a commit that referenced this issue Dec 8, 2019
tghosth added a commit that referenced this issue Aug 27, 2024
* define acronyms where possible

* slash replaced with "or"

* Refactor certain requirements (#1)

* Refactor certain requirements

* Split guidance for malformed messages and packets

---------

Co-authored-by: Josh Grossman <tghosth@users.noreply.github.com>
tghosth added a commit that referenced this issue Aug 27, 2024
* define acronyms where possible

* slash replaced with "or"

* Refactor certain requirements (#1)

* Refactor certain requirements

* Split guidance for malformed messages and packets

---------

Co-authored-by: Josh Grossman <tghosth@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants