From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH/RFH] Mark user-manual as UTF-8
Date: Tue, 24 Jul 2007 10:50:31 -0400 [thread overview]
Message-ID: <20070724145031.GB24302@fieldses.org> (raw)
In-Reply-To: <7vwswqgs6c.fsf@assigned-by-dhcp.cox.net>
On Tue, Jul 24, 2007 at 12:46:35AM -0700, Junio C Hamano wrote:
> There have been several complaints against k.org's user-manual
> page. The document is generated in ISO-8859-1 by the xsltproc
> toolchain (I suspect this is because released docbook.xsl we use
> has xsl:output element that says the output is ISO-8859-1) but
> server delivers it with "charset=UTF-8", and all h*ll breaks
> loose.
>
> This attempts to force UTF-8 on the generating end.
Thanks for looking into this! I've seen what I assume is the same
problem sporadically before and been unsuccesful at finding the
source....
--b.
prev parent reply other threads:[~2007-07-24 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 7:46 [PATCH/RFH] Mark user-manual as UTF-8 Junio C Hamano
2007-07-24 8:53 ` Jeff King
2007-07-24 10:36 ` Wincent Colaiuta
2007-07-24 10:45 ` Thierry Parmentelat
2007-07-24 14:50 ` J. Bruce Fields [this message]
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=20070724145031.GB24302@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox