This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Character set for libstdc++ manual
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Martin von Gagern <Martin dot vGagern at gmx dot net>
- Cc: Jonathan Wakely <jwakely dot gcc at gmail dot com>, libstdc++ at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Fri, 28 Dec 2012 14:06:03 -1000 (TAHT)
- Subject: Re: Character set for libstdc++ manual
- References: <4F8866B5.3080506@gmx.net> <alpine.LNX.2.00.1206101235530.7564@zbenl.fvgr> <CAH6eHdQScd4pXY8aJNwYR5RAJJ_7wp8tz7BuMd52kFd9P5P2Xw@mail.gmail.com> <4FD4D352.7080501@gmx.net>
Hi Martin,
On Sun, 10 Jun 2012, Martin von Gagern wrote:
> On 10.06.2012 15:39, Jonathan Wakely wrote:
>> I had a quick look at telling docbook stylesheets to add the charset,
>> or not output utf8, and couldn't see how to do it. Maybe Benjamin
>> knows.
> If that should prove difficult, there are at least two alternatives:
>
> 1. Server configuration: have Apache serve those files with the
> HTTP-Header "Content-Type: text/html; charset=utf-8" by adding the
> configuration directive "AddDefaultCharset utf-8" to a suitable config
> file, e.g. a .htaccess file if you want this setting to be local to that
> part of the directory tree.
> See http://httpd.apache.org/docs/2.0/mod/core.html#adddefaultcharset
>
> 2. Postprocessing: You can use e.g. recode to convert UTF-8 codepoints
> to HTML entities by issuing "recode ..HTML <Filesâ>". Of course, you
> could also patch in the "<meta â>" tag in such a postprocessing step.
I have seen a fair amount of changes being made to our libstdc++
manuals recently thanks to Benjamin, Jonathan and others.
Has this problem been resolved for you now, or is it still open?
(If it's the latter, I think I'll go the brute force route and
implement option 1 above per your recommendation now.)
Gerald