Received: (qmail 44122 invoked by uid 501); 24 Sep 2000 18:22:02 -0000
Message-Id: <20000924182202.44121.qmail@locus.apache.org>
Date: 24 Sep 2000 18:22:02 -0000
From: Martin Cermak <cermak@trimedia.cz>
Reply-To: cermak@trimedia.cz
To: submit@bugz.apache.org
Subject: Error in meta tag with charset causing problem with codepage decoding tools.
X-Send-Pr-Version: 3.110

>Number:         6570
>Category:       documentation
>Synopsis:       Error in meta tag with charset causing problem with codepage decoding tools.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          mistaken
>Submitter-Id:   apache
>Arrival-Date:   Sun Sep 24 11:30:02 PDT 2000
>Closed-Date:    Sun Feb 18 21:07:20 PST 2001
>Last-Modified:  Sun Feb 18 21:07:20 PST 2001
>Originator:     cermak@trimedia.cz
>Release:        1.3.12
>Organization:
>Environment:
Linux ripley 2.2.17 #7 Sun Sep 17 14:24:18 CEST 2000 i686 unknown
>Description:
There is an error in ${DocumentRoot}/index.html.cz
The meta tag with charset must be
<META HTTP-Equiv="Content-Type" Content="text/html; charset=iso-8859-2">

In 1.3.12 distribution is this wrong meta tag:
<META NAME="ContentType" CONTENT="text/html; charset=iso-8859-2">

Codepage decoding tools used in the Czech Republic then work wrong on this page
- they don't recognize the charset and conversion fails
>How-To-Repeat:
No need to repeat - it is just an error in meta tag.
>Fix:
change the line
<META NAME="ContentType" CONTENT="text/html; charset=iso-8859-2">
to the correct one:
<META HTTP-Equiv="Content-Type" Content="text/html; charset=iso-8859-2">

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: slive
State-Changed-When: Sun Feb 18 21:07:19 PST 2001
State-Changed-Why:

This is now fixed.  Sorry for the long delay.


>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]