Description: ------------ currently there is no way to specify different encoding for resulting documentation. Javadoc has --charset switch, which is propagated into resulting HTML (as Meta header).

+1 for this.

+1 for this.

+1 here too

+1 from me too

please stop voting with comments. We have 1 active developer. If you want the feature faster, attach a patch. +1 will not speed things up. Thanks

I'm using some temporary solution for HTML templates. I've found and changed "charset=iso-8859-1" to "charset=UTF-8" (all my sources are in UTF) in files of template I use. Actually I made a new template with charset I needed.

Added patch add-charset-switch.

I've written a patch to add --charset switch. Since the default value of --charset switch is "iso-8859-1", it is backward compatible except for 3 templates that don't have the Content-type meta element. (HTML:Smarty:default, HTML:Smarty:PHP and CHM:default:default)

This patch works only with sources text. Tutorials and RIC still won't shows correctly. For tutorials shows correctly if you completely comment or remove this code: // fix 1151650 if (stristr($ret, "utf-8") !== "") { $ret = utf8_decode($ret); } I still don't understand how to fix RIC.

I found root of my problem with cyrillic charset in RIC. Open your ric.tpl file and find this string: {include file="header.tpl"} <h1 align="center">{$name}</h1> <pre> {$contents|htmlentities} </pre> {include file="footer.tpl"} htmlentities option escapes all cyrillic symbols, but do it wrong. So you can just remove it: {include file="header.tpl"} <h1 align="center">{$name}</h1> <pre> {$contents} </pre> {include file="footer.tpl"}

http://www.smarty.net/docsv2/en/language.modifier.escape.tpl Smarty documentation: escape modifier

May I ask one question: suggested charset patch works fine. Why you wont fix it to repository?

Including miau's patch in 1.5.0a1.