From: Michael Tokarev <mjt@tls.msk.ru>
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 2/2] Run pod2man with --utf8 option to enable utf8 in manpages
Date: Sun, 11 Mar 2012 13:57:24 +0400 [thread overview]
Message-ID: <4F5C7704.4090907@msgid.tls.msk.ru> (raw)
In-Reply-To: <1328192202-23450-2-git-send-email-mjt@msgid.tls.msk.ru>
Ping? It's been more than a month since this patch has been posted.
Maybe it is a good candidate for -trivial queue?
Thanks,
/mjt
On 02.02.2012 18:16, Michael Tokarev wrote:
> This option makes no difference for manpages which contains only
> ascii chars. But for manpages with actual UTF8 characters (qemu
> docs contains these), this change allows to see real characters
> instead of mojibakes or substitutes.
>
> Signed-off-By: Michael Tokarev <mjt@tls.msk.ru>
> ---
> Makefile | 9 +++++----
> 1 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 2560b59..737cda2 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -337,28 +337,29 @@ QMP/qmp-commands.txt: $(SRC_PATH)/qmp-commands.hx
> qemu-img-cmds.texi: $(SRC_PATH)/qemu-img-cmds.hx
> $(call quiet-command,sh $(SRC_PATH)/scripts/hxtool -t < $< > $@," GEN $@")
>
> +POD2MAN = pod2man --utf8
> qemu.1: qemu-doc.texi qemu-options.texi qemu-monitor.texi
> $(call quiet-command, \
> perl -Ww -- $(SRC_PATH)/scripts/texi2pod.pl $< qemu.pod && \
> - pod2man --section=1 --center=" " --release=" " qemu.pod > $@, \
> + $(POD2MAN) --section=1 --center=" " --release=" " qemu.pod > $@, \
> " GEN $@")
>
> qemu-img.1: qemu-img.texi qemu-img-cmds.texi
> $(call quiet-command, \
> perl -Ww -- $(SRC_PATH)/scripts/texi2pod.pl $< qemu-img.pod && \
> - pod2man --section=1 --center=" " --release=" " qemu-img.pod > $@, \
> + $(POD2MAN) --section=1 --center=" " --release=" " qemu-img.pod > $@, \
> " GEN $@")
>
> fsdev/virtfs-proxy-helper.1: fsdev/virtfs-proxy-helper.texi
> $(call quiet-command, \
> perl -Ww -- $(SRC_PATH)/scripts/texi2pod.pl $< fsdev/virtfs-proxy-helper.pod && \
> - pod2man --section=1 --center=" " --release=" " fsdev/virtfs-proxy-helper.pod > $@, \
> + $(POD2MAN) --section=1 --center=" " --release=" " fsdev/virtfs-proxy-helper.pod > $@, \
> " GEN $@")
>
> qemu-nbd.8: qemu-nbd.texi
> $(call quiet-command, \
> perl -Ww -- $(SRC_PATH)/scripts/texi2pod.pl $< qemu-nbd.pod && \
> - pod2man --section=8 --center=" " --release=" " qemu-nbd.pod > $@, \
> + $(POD2MAN) --section=8 --center=" " --release=" " qemu-nbd.pod > $@, \
> " GEN $@")
>
> dvi: qemu-doc.dvi qemu-tech.dvi
next prev parent reply other threads:[~2012-03-11 9:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1328192202-23450-1-git-send-email-mjt@tls.msk.ru>
2012-02-02 14:16 ` [Qemu-devel] [PATCH 2/2] Run pod2man with --utf8 option to enable utf8 in manpages Michael Tokarev
2012-02-02 14:32 ` Peter Maydell
2012-02-02 14:46 ` Michael Tokarev
2012-02-02 14:49 ` Peter Maydell
2012-02-02 14:54 ` Michael Tokarev
2012-03-11 9:57 ` Michael Tokarev [this message]
2012-02-02 14:16 [Qemu-devel] [PATCH 1/2] Support @documentencoding in scripts/texi2pod.pl Michael Tokarev
2012-03-11 9:56 ` Michael Tokarev
2012-03-12 8:21 ` Stefan Hajnoczi
2012-03-12 10:14 ` Michael Tokarev
2012-03-12 10:33 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F5C7704.4090907@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.