Re: How to document software?
OK! Thank you!
URL: https://forum.audiogames.net/post/591637/#p591637
--
Audiogames-reflector mailing list
Audiogames-reflector@sabahattin-gucukoglu.com
https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: How to document software?
I mean, sure. Use whatever you like. I use mdbook for Synthizer, but if you want a single page manual Pandoc gets the job done fine.
URL: https://forum.audiogames.net/post/591633/#p591633
--
Audiogames-reflector mailing list
Audiogames-reflector
Re: How to document software?
So am I good in using Pandoc then?
URL: https://forum.audiogames.net/post/591631/#p591631
--
Audiogames-reflector mailing list
Audiogames-reflector@sabahattin-gucukoglu.com
https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Re: How to document software?
I wouldn't try to implement translation, I'd just rewrite the document in every language and provide links to the different manuals.
URL: https://forum.audiogames.net/post/591356/#p591356
--
Audiogames-reflector mailing list
Audiogames
How to document software?
Hello,I need to write a documentation for a software. The two candidates for the tool used are T2Tags and pandoc.I find Pandoc more flexible and T2T has the advantage of allowing me to create translatable documents. Can I implement I18N in Pandoc as well or should
