From: Stefan Weil <weil@mail.berlios.de>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH 3/8] Documentation: Use UTF-8 encoding and fix one wrong encoding
Date: Fri, 5 Feb 2010 23:52:00 +0100 [thread overview]
Message-ID: <1265410325-16433-3-git-send-email-weil@mail.berlios.de> (raw)
In-Reply-To: <1265410325-16433-2-git-send-email-weil@mail.berlios.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]
At least for Linux distributions UTF-8 is now standard,
so the QEMU documentation should use this encoding, too.
Even if there was currently only a single special character
using ISO-8859-1, this might change in the future.
So the texinfo keywords @documentlanguage and
@documentencoding now document the language and the
encoding. The special character was changed to UTF-8
(it could also have been changed to an x, but the
original cross looks really nice if it is displayed
correctly).
These changes fix the html presentation at
http://www.qemu.org/qemu-doc.html#SEC65
(ARM System emulator).
Signed-off-by: Stefan Weil <weil@mail.berlios.de>
---
qemu-doc.texi | 6 +++++-
qemu-tech.texi | 4 ++++
2 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/qemu-doc.texi b/qemu-doc.texi
index eba6437..84de318 100644
--- a/qemu-doc.texi
+++ b/qemu-doc.texi
@@ -1,6 +1,10 @@
\input texinfo @c -*- texinfo -*-
@c %**start of header
@setfilename qemu-doc.info
+
+@documentlanguage en
+@documentencoding UTF-8
+
@settitle QEMU Emulator User Documentation
@exampleindent 0
@paragraphindent 0
@@ -1831,7 +1835,7 @@ MV88W8xx8 Ethernet controller
@item
MV88W8618 audio controller, WM8750 CODEC and mixer
@item
-128×64 display with brightness control
+128Ã64 display with brightness control
@item
2 buttons, 2 navigation wheels with button function
@end itemize
diff --git a/qemu-tech.texi b/qemu-tech.texi
index 52560dc..2e2a081 100644
--- a/qemu-tech.texi
+++ b/qemu-tech.texi
@@ -1,6 +1,10 @@
\input texinfo @c -*- texinfo -*-
@c %**start of header
@setfilename qemu-tech.info
+
+@documentlanguage en
+@documentencoding UTF-8
+
@settitle QEMU Internals
@exampleindent 0
@paragraphindent 0
--
1.6.5
next prev parent reply other threads:[~2010-02-05 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 22:50 [Qemu-devel] [RFC] Documentation Stefan Weil
2010-02-05 22:51 ` [Qemu-devel] [PATCH 1/8] Documentation: Add build support for documentation in pdf format Stefan Weil
2010-02-05 22:51 ` [Qemu-devel] [PATCH 2/8] Documentation: Add direntry for info format Stefan Weil
2010-02-05 22:52 ` Stefan Weil [this message]
2010-02-05 22:52 ` [Qemu-devel] [PATCH 4/8] Documentation: Add some basic documentation on make targets Stefan Weil
2010-02-05 22:52 ` [Qemu-devel] [PATCH 5/8] Documentation: Fix item list Stefan Weil
2010-02-05 22:52 ` [Qemu-devel] [PATCH 6/8] Documentation: Enhance documentation (index, keywords) Stefan Weil
2010-02-05 22:52 ` [Qemu-devel] [PATCH 7/8] Documentation: Add monitor commands to function index Stefan Weil
2010-02-05 22:52 ` [Qemu-devel] [PATCH 8/8] Documentation: Add command line options " Stefan Weil
2010-02-10 19:30 ` [Qemu-devel] [PATCH 2/8] Documentation: Add direntry for info format Anthony Liguori
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=1265410325-16433-3-git-send-email-weil@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).