Manpage for inkview
Hi alltogether!
While building the debian package, lintian told me binary-without-manpage inkview
So yesterday in the evening I converted http://www.inkscape.org/cgi-bin/wiki.pl?Inkview into a small manpage to be included in the debian distro. It is attached, so you can use it if you want and change it or tell what to do better.
Best regards,
Wolfi
Cool, thanks Wolfram! It occurred to me that inkview would need a manpage when I was working on the mandrake package last night, so it's great to see one already. :-)
We may want to create a subdir in the codebase for collecting the manpages, as the top level dir is accumulating a lot of files.
Bryce
On Thu, 12 Feb 2004, Wolfram Quester wrote:
Hi alltogether!
While building the debian package, lintian told me binary-without-manpage inkview
So yesterday in the evening I converted http://www.inkscape.org/cgi-bin/wiki.pl?Inkview into a small manpage to be included in the debian distro. It is attached, so you can use it if you want and change it or tell what to do better.
Best regards,
Wolfi
Hi!
On Thu, Feb 12, 2004 at 10:44:53AM -0800, Bryce Harrington wrote:
Cool, thanks Wolfram! It occurred to me that inkview would need a manpage when I was working on the mandrake package last night, so it's great to see one already. :-)
We may want to create a subdir in the codebase for collecting the manpages, as the top level dir is accumulating a lot of files.
Having a man/ subdir seems reasonable to me. While we are at it, the attached patch updates the keybindings-section in the man-page. While doing it I saw that the header of this man-page claims to be "Automatically generated by Pod::Man v1.34, Pod::Parser v1.13". This isn't done during the compilation process from docbook or something else, is it? If it is not, I think we should remove the header. I also can't see the necessity of having a inkscape.1.in which is the same as inkscape.1. Can't we rename the file and skip the copy process in autogen.sh?
Best regards,
Wolfi
On Fri, 13 Feb 2004, Wolfram Quester wrote:
On Thu, Feb 12, 2004 at 10:44:53AM -0800, Bryce Harrington wrote:
Cool, thanks Wolfram! It occurred to me that inkview would need a manpage when I was working on the mandrake package last night, so it's great to see one already. :-)
We may want to create a subdir in the codebase for collecting the manpages, as the top level dir is accumulating a lot of files.
Having a man/ subdir seems reasonable to me.
Good deal - would you like to set it up?
While we are at it, the attached patch updates the keybindings-section in the man-page. While doing it I saw that the header of this man-page claims to be "Automatically generated by Pod::Man v1.34, Pod::Parser v1.13".
I wrote the original manpage in Perl's POD style and I think someone set up an automatic pod->man converter for it. That header gets automatically inserted, but I agree it needs to be stripped out. Perhaps there's a way to run sed against it?
This isn't done during the compilation process from docbook or something else, is it? If it is not, I think we should remove the header. I also can't see the necessity of having a inkscape.1.in which is the same as inkscape.1. Can't we rename the file and skip the copy process in autogen.sh?
Sounds good to me, although it makes me wonder if there's a processing step being skipped here?
Bryce
On Fri, 13 Feb 2004 09:26:03 -0800 (PST) Bryce Harrington <bryce@...1...> mused:
On Fri, 13 Feb 2004, Wolfram Quester wrote:
On Thu, Feb 12, 2004 at 10:44:53AM -0800, Bryce Harrington wrote:
Cool, thanks Wolfram! It occurred to me that inkview would need a manpage when I was working on the mandrake package last night, so it's great to see one already. :-)
We may want to create a subdir in the codebase for collecting the manpages, as the top level dir is accumulating a lot of files.
Having a man/ subdir seems reasonable to me.
Good deal - would you like to set it up?
I've put invkiew.1.in in 0.38cvs, but it needs to be added to 0.37cvs still. configure.in, Makefile.am were modified for this. I've put it in the main directory for now.
While we are at it, the attached patch updates the keybindings-section in the man-page. While doing it I saw that the header of this man-page claims to be "Automatically generated by Pod::Man v1.34, Pod::Parser v1.13".
I wrote the original manpage in Perl's POD style and I think someone set up an automatic pod->man converter for it. That header gets automatically inserted, but I agree it needs to be stripped out. Perhaps there's a way to run sed against it?
This isn't done during the compilation process from docbook or something else, is it? If it is not, I think we should remove the header. I also can't see the necessity of having a inkscape.1.in which is the same as inkscape.1. Can't we rename the file and skip the copy process in autogen.sh?
Sounds good to me, although it makes me wonder if there's a processing step being skipped here?
I've looked very briefly at manpage building and we better leave the building step in if someone wants to make use of that. Possibly there are some docbook autotools configuration macros which could build different formats. I wonder if docbook can convert our tutorial.svg to TeX ?
Johan
participants (3)
-
Bryce Harrington -
Johan Ceuppens -
Wolfram Quester