On 14.08.2013 23:42, Thomas Åkesson wrote:
On 14 aug 2013, at 20:47, Mattias Engdegård matti...@bredband.net wrote:
12 aug 2013 kl. 12.38 skrev Julian Foad:
Hi James. I have one thing to throw into the mix, which you might be
interested in looking at. I experimented a few months ago with
12 aug 2013 kl. 12.38 skrev Julian Foad:
Hi James. I have one thing to throw into the mix, which you might
be interested in looking at. I experimented a few months ago with
generating both the C help strings and man pages from an XML source
file. My patch to do this is attached; it is
On 14 aug 2013, at 20:47, Mattias Engdegård matti...@bredband.net wrote:
12 aug 2013 kl. 12.38 skrev Julian Foad:
Hi James. I have one thing to throw into the mix, which you might be
interested in looking at. I experimented a few months ago with generating
both the C help strings and
: man pages for Subversion
On Fri, 9 Aug 2013 11:21:23 +0300
Daniel Shahaf danie...@elego.de wrote:
1. Get the sources for 1.9
2. Examine svn_cl__cmd_table
3. Prepare a doc build tree that creates two things:
a. man pages
b. plain text for --help, one file per subcommand
On Fri, 9 Aug 2013 11:21:23 +0300
Daniel Shahaf danie...@elego.de wrote:
1. Get the sources for 1.9
2. Examine svn_cl__cmd_table
3. Prepare a doc build tree that creates two things:
a. man pages
b. plain text for --help, one file per subcommand
The plain
every
format language,
Bert From: James K. Lowden
Sent: 10/08/2013 05:23
To: Daniel Shahaf
Cc: dev@subversion.apache.org
Subject: Re: man pages for Subversion
On Fri, 9 Aug 2013 11:21:23 +0300
Daniel Shahaf danie...@elego.de wrote:
1. Get the sources for 1.9
2. Examine svn_cl__cmd_table
3
James K. Lowden wrote on Thu, Aug 08, 2013 at 22:25:08 -0400:
Stefan Sperling s...@elego.de wrote:
If you manage to generate both the compiled-in strings and the man
pages (on UNIX only) from the same source format during the build,
Im happy with that. If you manage to generate man pages
On Fri, 9 Aug 2013 11:21:23 +0300
Daniel Shahaf danie...@elego.de wrote:
1. Get the sources for 1.9
2. Examine svn_cl__cmd_table
3. Prepare a doc build tree that creates two things:
a. man pages
b. plain text for --help, one file per subcommand
The plain text
On Thu, Aug 08, 2013 at 08:58:29AM +0300, Daniel Shahaf wrote:
James K. Lowden wrote on Wed, Aug 07, 2013 at 20:13:16 -0400:
1. Keep the man pages in mdoc format as the souce code.
2. Convert svn foo --help and svn help foo to invoke man(1), as
git does. Or use groff to generate plain
On Wed, 07 Aug 2013, James K. Lowden wrote:
If HTML is desired, there are a couple of options. I haven't used it,
but troff2page sounds nice.
http://www.ccs.neu.edu/home/dorai/troff2page/index.html#node_toc_start
GNU troff also supports HTML output, but I haven't had great luck with
it.
For
On Thu, Aug 08, 2013 at 09:20:16AM +0200, Alan Barrett wrote:
On Wed, 07 Aug 2013, James K. Lowden wrote:
If HTML is desired, there are a couple of options. I haven't used it,
but troff2page sounds nice.
http://www.ccs.neu.edu/home/dorai/troff2page/index.html#node_toc_start
GNU troff also
On Thu, 8 Aug 2013 08:58:29 +0300
Daniel Shahaf danie...@elego.de wrote:
Perhaps this is a good time to point out that you were writing man
pages for 1.7, which is in Security fixes only mode. The supported
release is 1.8 and trunk (where new development should be targeted)
is 1.9.
1.
On Wed, Aug 07, 2013 at 12:07:08AM -0400, James K. Lowden wrote:
http://www.schemamania.org/svn/man1/
e.g. http://www.schemamania.org/svn/man1/svn-propset.pdf
I offer the above mdoc man pages to the Subversion project as a token
of my appreciation, and in the hope they'll be included in
Stefan Sperling wrote on Wed, Aug 07, 2013 at 11:27:13 +0200:
On Wed, Aug 07, 2013 at 12:07:08AM -0400, James K. Lowden wrote:
The pages represent perhaps 30 hours of work. The --help text was
processed through the bin/manualize Perl script to create a rough
mdoc draft. Then individual
James K. Lowden wrote on Wed, Aug 07, 2013 at 00:07:08 -0400:
The final result is surely a derived work, but it's not clear to me if
the --help text is copyrighted. I am prepare to assign it as befits
the project, if need be.
The ASF never requires copyright assignment. However, license
James K. Lowden wrote on Wed, Aug 07, 2013 at 00:07:08 -0400:
I offer the above mdoc man pages to the Subversion project as a token
of my appreciation, and in the hope they'll be included in future
versions.
Thanks!
The pages represent perhaps 30 hours of work. The --help text was
On Wed, 7 Aug 2013 12:45:36 +0300
Daniel Shahaf danie...@elego.de wrote:
Then individual sections were edited by hand, sometimes to
put finishing touches on the formatting, sometimes to clarify the
text.
How can we incorporate that into the dev cycle?
if manual tweaks are required, we
. Lowden
Sent: 08/08/2013 02:13
To: Daniel Shahaf
Cc: dev@subversion.apache.org
Subject: Re: man pages for Subversion
On Wed, 7 Aug 2013 12:45:36 +0300
Daniel Shahaf danie...@elego.de wrote:
Then individual sections were edited by hand, sometimes to
put finishing touches on the formatting, sometimes
Bert Huijben wrote on Wed, Aug 07, 2013 at 19:13:53 -0700:
Subversion is used on far more platforms than that have a default 'man'
support. Breaking support for Windows, OS/2 and Netware is not an
option.
Why are you even worried about that? No one is going to break support
for Windows.
On Thu, Aug 08, 2013 at 08:35:14AM +0300, Daniel Shahaf wrote:
I have no idea what you're talking about. What is the problem on
windows and how does a canonical format fix it?
Never mind, I see what you mean now (JAmes' suggestion to generate help output
from nroff source)
James K. Lowden wrote on Wed, Aug 07, 2013 at 20:13:16 -0400:
On Wed, 7 Aug 2013 12:45:36 +0300
Daniel Shahaf danie...@elego.de wrote:
Then individual sections were edited by hand, sometimes to
put finishing touches on the formatting, sometimes to clarify the
text.
How can we
21 matches
Mail list logo