s \(aq not work with AT&T troff? Is there some alternative way
I can mark it up instead?
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
at.
Anyway, any guidance/suggestions on what would be best to have the
stylesheet generating for Eastern European languages would be
appreciated.
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/
smime.p7s
Description: S/MIME cryptographic signature
Steve Izma <[EMAIL PROTECTED]>, 2008-02-26 11:14 -0500:
> On Tue, Feb 26, 2008 at 02:01:57PM +0900, Michael(tm) Smith wrote:
> > Subject: Re: [Groff] nroff vs. troff conditional using escapes?
> >
> > So I think what would actually best for me to try to do is have
>
"Michael(tm) Smith" <[EMAIL PROTECTED]>, 2008-02-26 13:06 +0900:
[quoting Ralph]
> > Use Werner's macro idea but maybe add in
> >
> > .tr aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpPqQrRsStTuUvVwWxXyYzZ
> > .tr aabbccddeeffgghhiijjkkllmmnnooppqqrrssttuu
orresponding EB (which ends that diversion again).
Yeah, not sure what I was doing wrong before, but I must have
corrected it because I'm not getting that message any longer.
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/
smime.p7s
Description: S/MIME cryptographic signature
nerating output from XSLT is not much fun at all.
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/
smime.p7s
Description: S/MIME cryptographic signature
ment.
Is that safe in groff? I know it's now safe to have space at the
end of lines, but is it safe to have it at the beginning of line?
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/
smime.p7s
Description: S/MIME cryptographic signature
(because, as I mentioned in my reply to Werner, using a
request can cause undesirable white space to be injected between
the string and surrounding punctuation).
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/
smime.p7s
Description: S/MIME cryptographic signature
parens before and after the word "Description".
Hence my question about whether there really is no way I could use
a set of escapes instead of a request...
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/
smime.p7s
Description: S/MIME cryptographic signature
d HTML
markup). Anyway, I can see how to get my stylesheet to generate
this just as easily as generating inline markup.
And I am learning some general things from your answers (in this
case, how to handle multiple arguments for a macro), so if your
patience holds out, I promise my questions will ge
mpt at a pseudo representation.)
So my use case is just that I'd like to have an uppercase/all-caps
version of the string in nroff/TTY output, but a normal version of
the same string in troff/PS output.
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/
smim
> \M[yellow]\h'1n'\v'-.5v'\D'P \\n(BWu 0 0 \\n(BHu -\\n(BWu 0 0 -\\n(BHu'\M[]
> .in 0
> .sp -.5v
> .nf
> .BX
> .in
> .sp .5v
> .fi
> ..
> .sp 3c
> .ll 4c
> Some text.
> Some text.
> Some text.
> Some text.
> .in +1n
rt for it was added in the
other DocBook processing toolchains. So main reason I want to try
to add support for it if I can is just for feature parity with
those.
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/
smime.p7s
Description: S/MIME cryptographic signature
"Michael(tm) Smith" <[EMAIL PROTECTED]>, 2008-02-22 21:54 +0900:
> ... But I can't seem to actually test it because I'm not getting
> boxed text in PS output even with the unmodified B1/B2 macros --
> though I do get it as expected in TTY output.
After doing
Ted Harding <[EMAIL PROTECTED]>, 2008-02-22 11:33 -:
> As B1/B2 are written, they simply draw the box as a series of
> lines, using \D'l '. This does not create a "closed object"
> which can be filled.
>
> However, if you use \D'P ... ' you will draw a polygon which
> will be filled (\D'
text blocks are marked as such, this is doable. But
> there is no standard way to do so in man pages. However, the next
> groff release will propagate the `.EX/.EE' block for examples in man
> pages (this is in an-ext.tmac). You could redefine them accordingly.
OK, thanks
--Mik
hat really
helps to set the program listing off from the rest of text.
So I'm wondering if I might be able to achieve a similar effect in
the PS output from DocBook-generated man pages.
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/
smime.p7s
Desc
to ask some dumb questions without
bugging everybody on the mailing list would be helpful).
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/
smime.p7s
Description: S/MIME cryptographic signature
Clarke Echols <[EMAIL PROTECTED]>, 2008-02-21 07:04 -0700:
> Michael(tm) Smith wrote:
> > OK, I did now read the following in the that node:
> > [...] `gtroff' provides two built-in conditions `n'
> > and `t' for the `if', `ie', and `wh
ough about the distinction to know what to search for in the
index. I wouldn't have thought to search for "nroff mode", because
before Clarke pointed out the nroff/troff distinction, I didn't
know about it (yeah, I know this reveals I have some basic
ignorance about groff fundamentals)
to not
have the hacks I've got in their for console output affecting
other formats (in case somebody does actually want to generated a
PS or PDF file from on of the DocBookXSL-generated man pages).
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/
smime.p7s
Description: S/MIME cryptographic signature
osed within \{ and \} pairs for
> each .if condition.
>
> I'm not certain whether this is what you're looking for or not...
Yep, that's exactly what I was looking for. I read the groff info
node about conditionals, but just didn't know how to specify a
condition t
at
I'd like to do if possible is to wrap those \h escapes in
conditionals so that they have effect only in console output, but
not when generating PS output. So I'm wondering if there's a way I
can do that.
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbar
U+2010 for it instead of a
U+002D? (Some Unicode recommendation?)
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
http://sideshowbarker.net/
smime.p7s
Description: S/MIME cryptographic signature
7;t remember reading that one. Is it something that solves
this problem of multi-column tbl tables coming out looking so bad?
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
#x27;m sure I'll also need to
ask you some questions along the way. And I'll need some pointers
to pages to test with (existing pages that are using eqn).
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
rently does.
I don't know actually know if TQ solves that problem. But I'd sure
like to have something better -- regardless of how it it's
implemented.
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
Werner LEMBERG <[EMAIL PROTECTED]>, 2007-02-06 12:35 +0100:
> I still think that tables with T{...T} don't work well within man
> pages.
I see the specific problem in the example man page you attached,
and I've also seen the especially bad results produced when tables
have more than two columns.
"Eric S. Raymond" <[EMAIL PROTECTED]>, 2007-02-04 11:04 -0500:
> Michael(tm) Smith <[EMAIL PROTECTED]>:
> > is valid. It's not required to have content.
> > A instance won't generate validation errors.
>
> Huh? About a week ago I tried
alid. It's not required to have content.
A instance won't generate validation errors.
--Mike
--
Michael(tm) Smith
http://people.w3.org/mike/
.
I think the code point for backslash and yen symbol are the same
in (legacy) Japanese encodings. Or at least on Shift_JIS systems,
backslash /always/ shows up as yen symbol. Or maybe I don't know
what I'm talking about at all (I use ja_JP.UTF-8...)
--Mike
--
Michael(tm) Sm
Werner LEMBERG <[EMAIL PROTECTED]>, 2007-01-08 15:44 +0100:
[quoting me]
> > I have observed problems in some environments with display of lines
> > containing "\~" (which is why the DocBook manpages stylesheet
> > outputs "\" instead).
>
> Details, please.
Sorry, I don't have many. But for what
Werner LEMBERG <[EMAIL PROTECTED]>, 2007-01-08 08:02 +0100:
> > Werner Lemberg wanted to know the status of \~. I found 17 uses
> > within the groff documentation and 4 outside it. Of those 4, two
> > were errors. So it's not much needed for manual pages, which is a
> > good thing as it is not
my earlier message), there may be
some others.
If the DocBook DTD packager for a distro you're testing on hasn't
yet packaged 4.3 (which was released well over 2 years ago),
that's pretty bad (they should actually be packaging 4.4 or 4.5).
--Mike
--
Michael(tm) Smith
http://ww
Larry Kollar <[EMAIL PROTECTED]>, 2007-01-04 07:58 -0500:
> FO is sort of a "roach hotel" language in
> an XML sense -- once you have FO, you're not going to
> transform it to any other XML markup.
True, I guess that it's not likely that you'll be transforming it
to vocabularies other than FO. Th
Related to some current discussions on the list, I wanted to
mention a few projects I'm aware of that have authored their
man-page documentation in DocBook and used the DocBook Project
XSLT stylesheets to generate man-page output from them.
apt* utils (apt-get, apt-cache, aptitude, etc.)
bind9
Werner LEMBERG <[EMAIL PROTECTED]>, 2007-01-04 07:52 +0100:
> What I imagine is to conditionally tag the
> input for a certain output `device' (be it LaTeX, troff, or whatever).
> Such tags are ignored if the document is converted to a different
> device. The more such data is in the original inp
Gunnar Ritter <[EMAIL PROTECTED]>, 2007-01-03 19:55 +0100:
> As a troff user, my preference would actually be to have
> a collection of XSLT stylesheets, one for each of the
> supported XML input languages, and to have a common troff
> macro set to which all of these are transformed. This is
> bec
Gunnar Ritter <[EMAIL PROTECTED]>, 2007-01-03 18:30 +0100:
> The other side is that it is much easier to convert DocBook
> to troff directly.
True. And people familiar with LaTex and ConTeXt find it much
easier to convert DocBook to those formats directly. It makes
great sense if DocBook is the o
"Michael(tm) Smith" <[EMAIL PROTECTED]>, 2007-01-04 02:51 +0900:
> There is a alternative open-source DocBook-to-PDF/Postscript
> option that already produces better output than FOP in many cases.
> It's db2latex:
>
> http://db2latex.sourceforg
"Eric S. Raymond" <[EMAIL PROTECTED]>, 2007-01-03 12:48 -0500:
> Michael(tm) Smith <[EMAIL PROTECTED]>:
> > DocBook itself does not provide any means for marking up pages
> > breaks.
>
> There is a tag. I don't know wha the stylesheets
>
ne that might change it would be if XEP
were to be open-sourced. But I don't see that happening.
--Mike
--
Michael(tm) Smith
http://www.w3.org/People/Smith/
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
utput through "lynx -dump" (or
-dump through elinks or w3m). And that preserves any table layout
(I think lynx handles tables now -- if not, elinks and w3m do) and
URLs for hyperlinks.gg
--Mike
--
Michael(tm) Smith
http://www.w3.org/People/Smith/
for users to avoid
adding tables to their man pages.
--Mike
--
Michael(tm) Smith
http://www.w3.org/People/Smith/
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
resentation output from presentation-neutral XML markup
vocabularies like DocBook and TEI.
All we need are some better free-sofware XSL-FO engines.
Steve Cheng announced at one time that he was working on an XSL-FO
to roff engine. I don't know how far he managed to get.
--Mike
--
gt; techniques, and sheer bloody-minded persistence.
I'm not sure if I'm a DocBook maven but I will admit that I was
among those that didn't think it could be done well. But I have to
say now that I think doclifter is a mighty piece of work indeed.
--Mike
--
Michael(tm) Smith
http
"Eric S. Raymond" <[EMAIL PROTECTED]>, 2007-01-03 11:28 -0500:
> Michael(tm) Smith <[EMAIL PROTECTED]>:
> > The open-source XSL-FO engine project that truly deserves some
> > more help is Tony Graham's xmlroff:
> >
> > http://www.xmlroff.
d DocBook to man
mechanism -- with a minimal dependency on just one thing: an XSLT
1.0 engine. libxslt/xsltproc is packaged for every modern distro,
so that means that DocBook manpage stylesheet will is usable on
very modern distro (and will continue to be going forward).
--Mike
--
Mich
ee a day when any one markup system for
documentation is lingua-franca among most developers.
> HTML is not an answer because it is not widely understood among developers and
> is as much an assembly language as *roff and latex.
It seems to me there's not a whole lot to understand in
ould be HTML originally
generated from DocBook or generated by some other means or even
just authored directly in HTML), and "man " would just
cause a browser (be it a curses-based browser or a GUI one) to be
envoked and the page displayed in that.
--Mike
--
Michael(tm) Smith
http://www
p is Tony Graham's xmlroff:
http://www.xmlroff.org/
It's a C application that uses the GNOME Print library and GLib,
GObject and Pango libraries as its backend (it doesn't use *roff
at all except in its name). The only thing it lacks is some more
quot;RS/RE found
but can't determine intened semantics" (or whatever).
--Mike
--
Michael(tm) Smith
http://www.w3.org/People/Smith/
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
"Eric S. Raymond" <[EMAIL PROTECTED]>, 2007-01-03 07:17 -0500:
> Michael(tm) Smith <[EMAIL PROTECTED]>:
> > That was true prior to DocBook 4.3, but it's not true currently
> > (neither in DocBook 4 nor DocBook 5).
>
> Oh, good. I shall add sup
Zvezdan Petkovic <[EMAIL PROTECTED]>, 2006-12-23 15:06 -0500:
> I would classify myself as "skilled hands" too and I agree with your
> assessment of *roff and TeX (I used both extensively). However, I did
> write a 10 page technical document (34 with the appendices that simply
> include the files
f open-source applications who want to use XEP to
generate PDF/Postscript output of the documentation for their
applications.
--Mike
--
Michael(tm) Smith
http://www.w3.org/People/Smith/
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
Ted Harding <[EMAIL PROTECTED]>, 2006-12-23 00:48 -:
> Therefore my case for groff would not rest on man-pages. Indeed,
> if groff were superseded by something else for man-pages I would
> maintain that this would not diminsh the usefulness of groff,
> nor the necessity to keep it going.
>
>
lar processing application may or or may not render it with
an indent. It would be a mistake to assume that every processing
application will indent output.
--Mike
--
Michael(tm) Smith
http://www.w3.org/People/Smith/
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
t more. And it does it all using
just XSLT (as with the rest of the DocBook Project stylesheets).
Steve's tools partly rely on Perl and on a special
XML::Handler::SGMLSpl Perl module. All that you need to do DocBook
to man conversion using the manpages stylesheet is just an XSLT
engine and t
7;s tools partly rely on Perl and on a special
XML::Handler::SGMLSpl Perl module. All that you need to do DocBook
to man conversion using the manpages stylesheet is just an XSLT
engine and the DocBook Project stylesheets themselves.
--Mike
--
Michael(tm) Smith
http://www.w3.org/People/Smith/
lynx or
elinks or w3m. I'd think paging through a man page with one of
those would be much the same as you have with less(1) now. Except,
for one thing, you'd actually be able to follow inline hyperlinks.
--Mike
--
Michael(tm) Smith
http://www.w3.org/People/Smith/
___
bzip2recover
recovers data from damaged bzip2 files
...
So there's currently no need for man-page authors to follow a
"don't write multiple description lines" best practice.
--Mike
--
Michael(tm) Smith
http://www.w3.org/People/Smith/
Werner LEMBERG <[EMAIL PROTECTED]> writes:
> > The second instance of "Dr\(:oge" displays correctly, but the
> > "\fBDr\(:oge\fR" instance does not (depending on which X shell I try
> > it in, it either displays a replacement character, blank space, or
> > some other character).
> >
> > Is this a
I have a file containing the following and am viewing it with
groff 1.18.1 in an en_US.UTF-8 environment.
.SH "AUTHOR"
.PP
\fBSebastian\fR \fBDr\(:oge\fR
.sp -1n
.IP "" 3n
Author.
.SH "COPYRIGHT"
Copyright \(co 2005 Sebastian Dr\(:oge
The second instance of "Dr\(:oge" displays correctly, but the
Any guidance on how I might be able to get running headers for
tables in source marked up with the man macros?
The XSLT stylesheet I put together for converting HTML table
markup to tbl(1) markup is able to convert Thead instances into
the appropriate tbl/roff markup for indicating a running heade
I've written an XSLT stylesheet that converts HTML tables to
tbl(1) markup. A copy of it is attached. It's also online:
http://cvs.sourceforge.net/viewcvs.py/*checkout*/docbook/xsl/manpages/table.xsl
I welcome comments and suggestions (and bug reports) about it. It
works well for the test case
65 matches
Mail list logo
