From 5be47f013ebfc6d916f62911d328e24606c73b1e Mon Sep 17 00:00:00 2001 From: "jake%bugzilla.org" <> Date: Fri, 4 Apr 2008 11:46:39 +0000 Subject: Bug 201955 - The method for specifing a charset has changed now that we use CGI.pm for header output (bug 201816). --- docs/en/xml/installation.xml | 31 ++++++++++++++----------------- 1 file changed, 14 insertions(+), 17 deletions(-) diff --git a/docs/en/xml/installation.xml b/docs/en/xml/installation.xml index ffeab011a..b067ce413 100644 --- a/docs/en/xml/installation.xml +++ b/docs/en/xml/installation.xml @@ -1,5 +1,5 @@ - + Installation @@ -1036,24 +1036,21 @@ man 5 crontab installation has a good backup before making changes, and I recommend you understand what the script is doing before executing it. - - -bash# perl -pi -e "s/Content-Type\: text\/html/Content-Type\: text\/html\; charset=ISO-8859-1/i" *.cgi *.pl - + Telling Bugzilla to output a charset as part of the HTTP header is + much easier in version 2.18 and higher. Simply + locatate the following line in Bugzilla/CGI.pm: + + # Make sure that we don't send any charset headers + $self->charset(''); + + and change it to: + + # Send all data using the ISO-8859-1 charset + $self->charset('ISO-8859-1'); + - All this one-liner command does is search for all instances of - Content-type: text/html - - and replaces it with - Content-Type: text/html; charset=ISO-8859-1 - - . This specification prevents possible Javascript attacks on the - browser, and is suggested for all English-speaking sites. For - non-English-speaking Bugzilla sites, I suggest changing - ISO-8859-1, above, to - UTF-8. - Using <meta> tags to set the charset is not recommended, as there's a bug in Netscape 4.x which causes pages -- cgit v1.2.3-24-g4f1b