Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > So here it is: a perl script that does a good job on many .txt files in > Documentation/, although for some it deviates from "make man"'s output, > and for others it is outright broken. It is meant to be run in > Documentation/. > > My intention is not to fix the script for all cases, but to make patches > to Documentation/*.txt themselves, so that they are more consistent (and > incidentally nicer to the script). How you spend your time is up to you, but I need to wonder... - Is "man" format important for msysGit aka Windows environment? I had an impression that their helpfile format were closer to "html" output. - Does it make sense in the longer term for us to maintain in-house documentation tools? Can we afford it? It appears that we heard about breakages for every minor docbook updates, and it is really appealing if we do not have to rely on xsl toolchain for manpage generation. But if patching the text means making it compatible with the in-house script _and_ incompatible with AsciiDoc, hmmm... - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
