Russ Allbery wrote:
(\[xx] is a groff extension to the language.)
Is \(lq portable? It does the same thing.
--
Nicolas
(I read mailing lists through Gmane. Please don't Cc me on replies; it makes
me get one message on my newsreader and another on email.)
--
To UNSUBSCRIBE, email to
Nicolas Alvarez nicolas.alva...@gmail.com writes:
Russ Allbery wrote:
(\[xx] is a groff extension to the language.)
Is \(lq portable? It does the same thing.
I'm not sure. It's not one of the documented special characters available
in CSTR #54, which is the gold standard, so one would have
Jakub Wilk wrote:
* Nicolas Alvarez nicolas.alva...@gmail.com, 2009-11-17, 13:45:
In the manpage I wrote, I wanted to use English guillemets (‘’). This
lead to errors and I gave up, replacing them by `'. Guess what? Groff
understood what I wanted and put nice Unicode guillemets in the ouptut!
I
Nicolas Alvarez nicolas.alva...@gmail.com writes:
What about double quotes?
quilt's manpage renders like this in the man viewer: ``pushed on the stack''
I looked at the source and the .1 file has exactly those characters too. So
what should it have to get them converted into nice-looking
Russ Allbery wrote:
Nicolas Alvarez nicolas.alva...@gmail.com writes:
What about double quotes?
quilt's manpage renders like this in the man viewer: ``pushed on the
stack''
I looked at the source and the .1 file has exactly those characters too.
So what should it have to get them
Nicolas Alvarez wrote:
Regardless, I'm sure I have seen some manpages that do show Unicode quotes
in the man reader. Of course, I can't find any example now :(
Got it; those manpages use \[lq] and \[rq]. They are correctly converted to
either “” or depending on the locale.
--
Nicolas
(I
Nicolas Alvarez nicolas.alva...@gmail.com writes:
Russ Allbery wrote:
Nicolas Alvarez nicolas.alva...@gmail.com writes:
What about double quotes?
quilt's manpage renders like this in the man viewer: ``pushed on the
stack''
I looked at the source and the .1 file has exactly those
Nicolas Alvarez nicolas.alva...@gmail.com writes:
Nicolas Alvarez wrote:
Regardless, I'm sure I have seen some manpages that do show Unicode
quotes in the man reader. Of course, I can't find any example now :(
Got it; those manpages use \[lq] and \[rq]. They are correctly converted
to
Hi Rogério,
Em Wed, Nov 18, 2009 at 07:33:22AM -0200, Rogério Brito escreveu:
| Date: Wed, 18 Nov 2009 07:33:22 -0200
| From: Rogério Brito rbr...@ime.usp.br
| To: debian-mentors@lists.debian.org
| Subject: Re: Writing manpages (was: Re: Man and UTF-8.)
|
| I guess that I only have two options
On Wed, Nov 18, 2009 at 05:30:33AM -0200, Rogerio Brito wrote:
On Nov 17 2009, Roger Leigh wrote:
However, TTBOMK UTF-8 manpages should be OK as well, though I have
found some issues with more esoteric characters. I would suggest
reporting bugs or contacting the maintainer or groff
Le Wed, Nov 18, 2009 at 05:30:33AM -0200, Rogério Brito a écrit :
But what do you people use to edit manpages that you maintain
frequently?
Dear Rogério,
I found jEdit (http://www.jedit.org/) quite convenient to write and modify
Docbook XML manpages. It is not packaged in Debian, but
Hi, Joachim.
On Nov 18 2009, Joachim Wiedorn wrote:
Am Wed, 18 Nov 2009 05:30:33 -0200 schrieb Rogério Brito rbr...@ime.usp.br:
But what do you people use to edit manpages that you maintain
frequently?
I find the simplest way is to use *ManEdit*.
Is this the same as gmanedit (that's the
2009/11/18 Rogério Brito rbr...@ime.usp.br:
On Nov 18 2009, Joachim Wiedorn wrote:
I find the simplest way is to use *ManEdit*.
Is this the same as gmanedit (that's the only one that seems to be
available in the archives)? I remember having used it some ages ago and
I wasn't impressed, but
Rogério Brito rbr...@ime.usp.br writes:
With TeX, BTW, we have some extensions (or even reimplementations) that
allow us to type things in UTF-8 directly, instead of using escape
sequences like in older TeX (e.g., Rogério instead of Rog\'erio, in
utf-8 or in latin1, though some care should be
Le Tue, Nov 17, 2009 at 05:31:29AM -0200, Rogério Brito a écrit :
On Nov 17 2009, Charles Plessy wrote:
Is there a way to put an indication in the manpage source code for the
nroff parser, that the UTF-8 encoding is used?
I don't know the answer to that. OTOH, if you only need to use
* Charles Plessy ple...@debian.org, 2009-11-17, 22:53:
In the manpage I wrote, I wanted to use English guillemets (‘’). This
lead to errors and I gave up, replacing them by `'. Guess what? Groff
understood what I wanted and put nice Unicode guillemets in the ouptut!
I am quite amazed, even if
Jakub Wilk wrote:
* Charles Plessy ple...@debian.org, 2009-11-17, 22:53:
In the manpage I wrote, I wanted to use English guillemets (‘’). This
lead to errors and I gave up, replacing them by `'. Guess what? Groff
understood what I wanted and put nice Unicode guillemets in the ouptut!
I am quite
* Nicolas Alvarez nicolas.alva...@gmail.com, 2009-11-17, 13:45:
In the manpage I wrote, I wanted to use English guillemets (‘’). This
lead to errors and I gave up, replacing them by `'. Guess what? Groff
understood what I wanted and put nice Unicode guillemets in the ouptut!
I am quite amazed,
On Tue, Nov 17, 2009 at 10:53:52PM +0900, Charles Plessy wrote:
Le Tue, Nov 17, 2009 at 05:31:29AM -0200, Rogério Brito a écrit :
On Nov 17 2009, Charles Plessy wrote:
Is there a way to put an indication in the manpage source code for the
nroff parser, that the UTF-8 encoding is used?
Jakub Wilk uba...@users.sf.net writes:
* Nicolas Alvarez nicolas.alva...@gmail.com, 2009-11-17, 13:45:
And sometimes annoying. I have seen command examples in manpages that
used fancy Unicode quotes, and didn't work when copied and pasted
into a shell.
Blame the one who wrote a buggy
Ben Finney ben+deb...@benfinney.id.au writes:
Jakub Wilk uba...@users.sf.net writes:
* Nicolas Alvarez nicolas.alva...@gmail.com, 2009-11-17, 13:45:
And sometimes annoying. I have seen command examples in manpages that
used fancy Unicode quotes, and didn't work when copied and pasted into
a
Roger Leigh rle...@codelibre.net writes:
Ye gods, that's nasty. Should be removed IMO, since '`' is not and
never was an opening single quotation mark.
It is in the *roff language, similar to how '' is an opening or closing
quotation mark in TeX. Just because most of the characters in *roff
Russ Allbery r...@debian.org writes:
You would have needed to take it up with Joseph Ossanna and Brian
Kernighan, since *roff has worked this way since the beginning of the
formatting language.
Note that “blame the makers of groff” is *not* what I'm saying; they
make their decisions in the
Ben Finney ben+deb...@benfinney.id.au writes:
Russ Allbery r...@debian.org writes:
You would have needed to take it up with Joseph Ossanna and Brian
Kernighan, since *roff has worked this way since the beginning of the
formatting language.
Note that “blame the makers of groff” is *not* what
On Nov 17 2009, Russ Allbery wrote:
It is in the *roff language, similar to how '' is an opening or closing
quotation mark in TeX.
Just as an addendum, in TeX, `` is the opening (double) quotation mark
and '' is the closing quotation mark. Similarly, ` is the opening
single quotation mark and
On Nov 17 2009, Roger Leigh wrote:
However, TTBOMK UTF-8 manpages should be OK as well, though I have
found some issues with more esoteric characters. I would suggest
reporting bugs or contacting the maintainer or groff upstream if
you run into problems here.
OK, since the project strongly
Hello,
Am Wed, 18 Nov 2009 05:30:33 -0200 schrieb
Rogério Brito rbr...@ime.usp.br:
But what do you people use to edit manpages that you maintain
frequently?
I find the simplest way is to use *ManEdit*.
At the beginning you can get templates for the structure of the man
page. There are
Dear mentors,
for a program with no upstream manual page, I generated one stub with help2man,
which unfortunately duplicated the program's output, and tidied the source by
manual editing. But I run into another problem: unicode characters in the nroff
source get corrupted. Is there a way to put
Hi, Charles.
On Nov 17 2009, Charles Plessy wrote:
Is there a way to put an indication in the manpage source code for the
nroff parser, that the UTF-8 encoding is used?
I don't know the answer to that. OTOH, if you only need to use accented
latin characters, you can use something like this:
29 matches
Mail list logo
