On 10 April 2012 08:07, Barry Haddow <[email protected]> wrote: > If we move to github, with the primary documentation written in Latex, then it > seems to make it harder to contribute. Not everyone knows Latex, it's harder > to link across documents with Latex, and you have to wait at least until you > check it in before you see how it affects the website. Wikis should make > collaborative editing easier, in a way that a document checked into source > control doesn't.
There's documentation "How to install & run" and then there's "How to get around known problems" documentation -- or "guides" and "FAQs", as it were. My vote is for Latex & generate a pdf for the guides, and the HTML webpage for the FAQ. As far as the difficulties of Latex & source control for the docs: 1) Which people -- realistically -- are going to add to the documentation? I'd wager that it's at best a subset of the folks who are on this mailing list, in which case learning enough Latex to change a paragraph in an existing doc is pretty minor compared to, oh, say, anything you've done with Moses already. 2) Once it hits steady-state, the documentation doesn't need to change very fast. Source control is fine for this. ~amittai _______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
