Bug#380574: stx2any: man pages missing a bit of formatting.

2006-08-15 Thread Panu Kalliokoski
On Sun, Jul 30, 2006 at 03:09:33PM -0700, Robin Lee Powell wrote:
 Ideally, there would be a man-page specific Diversion that would
 define that section and could have in it the stuff catman needs,
 i.e.:
 foo \- build foo files

While looking for this, I noticed that the only standard dash in this
position is really \-, that is, the minus sign.  (Why this is so, beats
me, because the line is not a mathematical expression.)  So it seems
that I will have to build some support for man NAME description lines
after all, because stx2any does not have standard support for minus
signs in man (or any other format, for that matter).

However, I will still do this in a way that does not decrease the
usability of -Tman output for other purposes.  So it will probably be a
w_manheader macro or something like that.

Panu

-- 
personal contact:   [EMAIL PROTECTED], +35841 5323835
technical contact:  [EMAIL PROTECTED], http://www.iki.fi/atehwa/
PGP fingerprint:0EA5 9D33 6590 FFD4 921C  5A5F BE85 08F1 3169 70EC
Please consider membership of http://www.hospitalityclub.org/!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#380574: stx2any: man pages missing a bit of formatting.

2006-08-15 Thread Robin Lee Powell
On Tue, Aug 15, 2006 at 12:12:45PM +0300, Panu Kalliokoski wrote:
 On Sun, Jul 30, 2006 at 03:09:33PM -0700, Robin Lee Powell wrote:
  Ideally, there would be a man-page specific Diversion that would
  define that section and could have in it the stuff catman needs,
  i.e.:
  foo \- build foo files
 
 While looking for this, I noticed that the only standard dash in
 this position is really \-, that is, the minus sign.  (Why this is
 so, beats me, because the line is not a mathematical expression.)
 So it seems that I will have to build some support for man NAME
 description lines after all, because stx2any does not have
 standard support for minus signs in man (or any other format, for
 that matter).
 
 However, I will still do this in a way that does not decrease the
 usability of -Tman output for other purposes.  So it will probably
 be a w_manheader macro or something like that.

That's totally fine by me, as long as it's documented somewhere.
Thanks!

-Robin


-- 
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/
Reason #237 To Learn Lojban: Homonyms: Their Grate!
Proud Supporter of the Singularity Institute - http://singinst.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#380574: stx2any: man pages missing a bit of formatting.

2006-08-09 Thread Panu Kalliokoski
On Sun, Jul 30, 2006 at 03:09:33PM -0700, Robin Lee Powell wrote:
 The man macros do not include .SH Name at the top, which means that
 we get errors like:
 mandb: warning: /usr/man/man3/mooix-long.scm.3: whatis parse for 
 mooix-long.scm(3) failed

Good point, but I never intended stx2any to include all man page
specific form automatically.  It would probably be nice to have .SH NAME
in the template, but that would seriously cripple the usability of the
man output for anything _else_ than man pages.

I admit, though, that maybe it should be made clearer in the
documentation that you have to put ! NAME and a properly formatted
name line in the source.  At the moment, all the documentation says (on
the man page of stx2any) is:

 manproduces man macro output.  This output is usable as a man
page directly (of course, you should adhere to  the  ordi-
nary man page conventions), or can be fed to troff / groff
for formatting to e.g. postscript.

Here ordinary man page conventions refers to normal man section
headers, providing metadata such as the man section number and so on.  I
can clarify this in the next release.  For an example of writing man
pages with stx2any, please see the source for its own man page at
/usr/share/doc/stx2any/stx2any.txt.gz.

Panu

-- 
personal contact:   [EMAIL PROTECTED], +35841 5323835
technical contact:  [EMAIL PROTECTED], http://www.iki.fi/atehwa/
PGP fingerprint:0EA5 9D33 6590 FFD4 921C  5A5F BE85 08F1 3169 70EC


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#380574: stx2any: man pages missing a bit of formatting.

2006-07-30 Thread Robin Lee Powell
Package: stx2any
Version: 1.55-1
Severity: normal


The man macros do not include .SH Name at the top, which means that
we get errors like:

mandb: warning: /usr/man/man3/mooix-long.scm.3: whatis parse for 
mooix-long.scm(3) failed

Ideally, there would be a man-page specific Diversion that would
define that section and could have in it the stuff catman needs,
i.e.:

foo \- build foo files

-Robin

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-vserver
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages stx2any depends on:
ii  m41.4.4-1a macro processing language

Versions of packages stx2any recommends:
ii  python2.3.5-11   An interactive high-level object-o
ii  tidy  20051018-1 HTML syntax checker and reformatte
ii  w3m   0.5.1-4WWW browsable pager with excellent

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]