are living in KDE cvs under:
kdesdk/debian
kdetoys/debian
koffice/debian
Some (such as the kdesdk man pages) are quite explicit, others (such as
the kdetoys pages) do little more than describe command-line options and
show you the way to the HTML/DocBook docs.
Feel free to use them; I'm happy t
On Friday 04 May 2001 10:00, Lauri Watts wrote:
> Hi,
>
> We recently gained some volunteers to write man pages for the console/daemon
> KDE apps, and so we've been doing some experimentation with DocBook to set
> this up.
Hi Lauri,
What's the status of these e
Hi,
I wanted to thank you all for the man pages you sent me, or pointed me to in
the KDE CVS.
We're just working out the implementation details at the moment, but we
should have it all sorted out within another few days. I'll convert the
existing man pages and set up the locations
al pages. A cursory search through our CVS finds me a
> > handful of these, three in the kdebase module to be precise.
>
> I have a set of man pages written for all the apps in kdesdk and koffice. In
> particular this includes every command-line utility in kdesdk (of which there
> I don't know how the Debian system works. Is it possible to create a patch
> that can be applied to the original man pages when the Debian packages are
> created?
Yes, certainly; I would be happy with this for the Debian-specific amendments.
> I would be extremely happy fo
I've been volunteered to be the debian man pages writer/coordinator, though
as far as I know, I'm the only one doing it :-) I'll send you a quick
followup email with the man pages I've written so far attached (I don't want
to clutter the list), but you should be war
On Friday 04 May 2001 10:27, Ben Burton wrote:
> I have a set of man pages written for all the apps in kdesdk and koffice.
> In particular this includes every command-line utility in kdesdk (of which
> there are many). You can find them all in the CVS under kdesdk/debian/*.1
>
the kdebase module to be precise.
I have a set of man pages written for all the apps in kdesdk and koffice. In
particular this includes every command-line utility in kdesdk (of which there
are many). You can find them all in the CVS under kdesdk/debian/*.1 (and
koffice/debian/*.1).
Aspects o
Hi,
We recently gained some volunteers to write man pages for the console/daemon
KDE apps, and so we've been doing some experimentation with DocBook to set
this up.
We are specifically not wanting to use *roff as a source format, because
we've gone to some lengths to automate an
ns about
man pages so duplicate work can be prevented?
Thx,
Achim
--
To me vi is Zen. To use vi is to practice zen. Every command is
a koan. Profound to the user, unintelligible to the uninitiated.
You discover truth everytime you use it.
-- [EMAIL PROTECTED]
Thanks! I didn't know that, I'll rip those out of the konq man page, seperate
them, and
edit the ones I've done to refer to them. Luckily I've only got about five
done so far.
Lets see, at this rate, I'll be done with the kde man pages just in time for
Gnome and
KDE
On Friday 13 April 2001 04:02, Ivan E. Moore II wrote:
> >
> > Do you have a "template" or something we can work off of? If you had a
> > standard
>
> here is one for konqueror I just threw together..probably still needs some
> tweaks...but it's short sweet and to the point.
FWIW the QT and K
On Sun, Apr 15, 2001 at 10:29:57PM -0600, David Bishop wrote:
> Okay, so I've got artsc-config, artsd, artscat, and artsdsp done. However,
> I'm stuck on artsplay. What does it do, exactly? There is no documentation
> on it (duh) and afaict, it doesn't support any sort of commandline help
> s
Okay, so I've got artsc-config, artsd, artscat, and artsdsp done. However,
I'm stuck on artsplay. What does it do, exactly? There is no documentation
on it (duh) and afaict, it doesn't support any sort of commandline help
switch (--help, -h, -?, and --h don't work). Using a google search, I
kdemultimedia:
E: noatun: binary-without-manpage noatun
E: mpeglib: binary-without-manpage yaf-cdda
E: mpeglib: binary-without-manpage yaf-mpgplay
E: mpeglib: binary-without-manpage yaf-splay
E: mpeglib: binary-without-manpage yaf-tplay
E: mpeglib: binary-without-manpage yaf-vorbis
E: mpeglib: bin
Just run 'man ./filename.1'. It will read the man page just like it was
system-wide.
I'm working on organizing that list Ivan sent out, and will repost it minus the
dupes
and grouped in a little bit.
On Fri, Apr 13, 2001 at 10:26:31PM +1000, David Kempe wrote:
> On Friday 13 April 2001 13:12, D
On Friday 13 April 2001 13:12, David Bishop wrote:
>3) A (probably) short list of people willing to help out
Add me to that list, however How do we test the man page from Ivan's template
once we have written it? I think the syntax is easy enough, I just want to
know what its going to look like i
> 1) A list of the packages that we need to do this for
I can easily do this with lintian. :) once 2.2-alpha1 is out the door
I'll create a list of all binaries that need man pages.
Ivan
--
Ivan E. Moore II
[EMAIL PROTECTED]
http://snowcrash.tdyc.com
G
On Thursday 12 April 2001 20:02, Ivan E. Moore II wrote:
> > Do you have a "template" or something we can work off of? If you had a
> > standard
>
> here is one for konqueror I just threw together..probably still needs some
> tweaks...but it's short sweet and to the point.
>
> Ivan
So, call to ar
>
> Do you have a "template" or something we can work off of? If you had a
> standard
here is one for konqueror I just threw together..probably still needs some
tweaks...but it's short sweet and to the point.
Ivan
--
Ivan E. Moore II
[EMAIL PROTECTED]
http://snowcrash.tdyc.
man page..and just install konqueror
you don't get the man page...
plus I also think that some binaries should have their own man page...
and other's will definatly need common man pages
kfmclient,konqueror,khelpcenter - all should have a common man page IMO
dcopser
On Thu, Apr 12, 2001 at 03:50:48PM -0600, Ivan E. Moore II wrote:
> Ok...so as I work on these 2.2 packages one of the policy bits that is still
> yet to be dealt with is man pages. According to policy every binary must
> have a manpage. (even if there is a common one which others link
not to have to learn docbook for just a few
> man
> pages, but I'm fine with making up descriptions and copying/pasting
> command-line
> info). Thanks!
I will create one.
Ivan
--
Ivan E. Moore II
[EMAIL PROTECTED]
http://snowcrash.tdyc.com
GPG KeyID=90BCE0DD
Do you have a "template" or something we can work off of? If you had a
standard
file that I could then plug in different binary names and info, that would help
out immensly (i.e., I'd prefer not to have to learn docbook for just a few man
pages, but I'm fine with making
Ok...so as I work on these 2.2 packages one of the policy bits that is still
yet to be dealt with is man pages. According to policy every binary must
have a manpage. (even if there is a common one which others link to) Well
KDE doesn't do man pages...they do docbook...so I need help.
Hello,
How do I generate search index (in KDE help) for UNIX man pages. I have
unstable debian, with htdig installed. When I press the button "update
index" in KDE help, the scope section has "man pages" and "info pages"
grayed out. I don't know if this function
26 matches
Mail list logo
