DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=44027>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44027 ------- Additional Comments From [EMAIL PROTECTED] 2007-12-28 17:24 ------- There's actually no obstacle with processing httpd.conf as utf-8 today. However, it means that any typical editor would be at a loss to display the document if it contained both utf-8 strings and iso-8859 encoded strings, since they are mutually exclusive (some code points in iso-8859 cannot be rendered in utf-8, while utf-8 codes are gibberish inspected with an iso-8859 code page). On the win32 platform, the conf file is already interpreted as utf-8 for purpose of path names, resource (file) names, etc. But as a new feature, I'd recommend creating new ServerNameIDNA and ServerAliasIDNA directives, to avoid ambiguity. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
