3 ms·
Ah, good to know! Is that tooling public anywhere, or was it pretty tailor-made just for the Rust book?
by paholg 2y ago
Ah, good to know! Is that tooling public anywhere, or was it pretty tailor-made just for the Rust book?
- steveklabnik 2y agoBoth public and tailor-made: https://github.com/rust-lang/book/tree/main/tools https://github.com/rust-lang/book/tree/main/tools
- paholg 2y agoAwesome! You and Carol rock!
- steveklabnik 2y agoThanks! She gets 100% of the credit in this case though :)
- brnt 2y agoI can find here the process of converting docx to md, but not the reverse. I see the material is checked into the repo in both formats. Does that mean the docx's are your master, and you generate the markdown from it for diffing and building HTML? I'm investigating how to switch an organisation away from a docx-only mess of a documentation system, and it looks like you might have found a process that'd work for us, and let people keep using docx if they have to. I wonder what all those binary blobs do to the git repo though. Thanks for any info!
- steveklabnik 2y agoYou'd have to ask Carol, with the way we split the work, she handled all of this. From my perspective, the markdown was the master copy. Sorry I can't be of more help!