MySQL Bugs: #14282: manual.chm file charset is wrong

Bug #14282	manual.chm file charset is wrong
Submitted:	25 Oct 2005 7:51	Modified:	14 Dec 2005 19:51
Reporter:	Lu Tao	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Packaging	Severity:	S3 (Non-critical)
Version:	5.0.15	OS:	Windows (windows)
Assigned to:		CPU Architecture:	Any

Description:
The charset of html in manual.chm
should be utf-8
but it is shift_jis now
so that some charactors cannot display correctly such as '\'.
and the manual is old, in
D.1.1. Changes in release 5.0.15 (Not yet released)
but it released at oct 24th actully.
http://dev.mysql.com/doc/refman/5.0/en/news-5-0-x.html
said D.1.2 Changes in release 5.0.15 (19 October 2005: Production) 

How to repeat:
open the manual.chm ,MySQL 5.0 Reference Manual
press right key of mouse and select view source
you will see
<html><head><meta http-equiv="Content-Type" content="text/html; charset=shift_jis">
go to Appendix D. MySQL Change History

Press ctrl+F keyin \ in the editbox and press ok(my language is chinese)

Suggested fix:
should be utf-8

Can you try the 5.0 CHM manual available here?

http://dev.mysql.com/doc/

the refman-5.0-en.chm on http://dev.mysql.com/doc/ are much older than
the manual.chm in mysql-noinstall-5.0.15-win32.zip
refman-5.0-en.chm  says
C.1.1. Changes in release 5.0.12 (Not yet released)
By the way,the manual.chm in mysql-noinstall-5.0.15-win32.zip
lost Index too

Thank you for a bug report. 

Yes, charset=shift_jis is clearly visible in the source.
Yes, it is not up to date. In section 1.1. "About This Manual", one may read:

"This is the Reference Manual for the MySQL Database System, Version 5.0, up to Release 5.0.13-rc."

As for "lost Index" - it is a know problem. See http://bugs.mysql.com/bug.php?id=14483 for details.

The 5.0 CHM manual has been updated at:

http://dev.mysql.com/doc/

It should have index/search and is current for 5.0.16.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".