On Sat, Oct 30, 2010 at 8:28 AM, Stefan Sperling <s...@elego.de> wrote: > On Fri, Oct 29, 2010 at 06:56:24PM +0200, Daniel Shahaf wrote: >> C. Michael Pilato wrote on Fri, Oct 29, 2010 at 12:01:41 -0400: >> > On 10/29/2010 11:57 AM, Stefan Sperling wrote: >> > > Thoughts? Comments? >> > >> > I've not reviewed your suggested help text. But merely seeing the size of >> > makes me wonder ... is it time for 'svn help SUBCOMMAND --verbose' ? >> >> Don't you think the help text you've written has outgrown being >> maintained as a string literal in some C source file? > > I've already been toying with the idea of moving the help texts into > their own file (e.g. help.c). The C strings defined in that file would > then be used by main.c. > > The file could possibly be auto-generated, but we'd have to be careful > not to make things harder for translators if we did that.
Would it be possible to define a simple markup format, and then just put these strings in a text file and process that, similar to what we do with our sql statements now. Is there a markup format which already exists which would suit this purpose? >> We could maintain it in *.txt/manpage/docbook format. If you'd like it >> to be shipped alongside our libraries/binaries, I'm sure that can be >> arranged... > > I'd like to keep the texts short enough so they can still be embedded > as C strings into the binary. Being constrained is a good thing because > I don't want the help texts to end up replacing the book. >
