[asterisk-bugs] [Asterisk-GUI 0015238]: HTML encoding

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15238 
====================================================================== 
Reported By:                psztoch
Assigned To:                awk
====================================================================== 
Project:                    Asterisk-GUI
Issue ID:                   15238
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk GUI Version:       SVN 
Asterisk Version:           1.6.1-rc1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2009-05-31 17:01 CDT
Last Modified:              2009-06-01 06:30 CDT
====================================================================== 
Summary:                    HTML encoding
Description: 
There is not any parameters for html page encoding.
A lot of systems works on UTF-8.

In example:
linux-server-config-UTF-8
vs
windows-client-InternetExplorer-default-CP1250/ISO-8859-2

Please, add to htmls:
<meta http-equiv="Content-type" content="text/html;charset=..." />
====================================================================== 

---------------------------------------------------------------------- 
 (0105827) davidw (reporter) - 2009-06-01 06:30
 https://issues.asterisk.org/view.php?id=15238#c105827 
---------------------------------------------------------------------- 
If it really isn't providing this information in either meta or a real HTTP
headers, it is in breach of HTML 4's specification, which says that there
is no default character set, which puts you at the mercy of browser
heuristics.

I haven't used the GUI, but if it is sending Appendix C XHTML 1.0, it also
needs the character set in the XML processing instruction, unless it is
UTF-8.  If it is sending HTML, the / should not be present. In my view,
best current practice is to send HTML 4.01, not Appendix C XHTML 1.0. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-01 06:30 davidw         Note Added: 0105827                          
======================================================================