Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.5.0a1

Request #4960 support for different encoding
Submitted: 2005-08-01 09:58 UTC
From: jacekp at poczta dot wprost dot pl Assigned: ashnazg
Status: Closed Package: PhpDocumentor
PHP Version: Irrelevant OS: Irrelevant
Roadmaps: 1.5.0a1    
Subscription  


 [2005-08-01 09:58 UTC] jacekp at poczta dot wprost dot pl
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).

Comments

 [2007-05-07 11:34 UTC] tacker (Markus Tacker)
+1 for this.
 [2007-07-19 19:19 UTC] alekswhite (Aleksandr Belonogov)
+1 for this.
 [2007-10-25 16:18 UTC] olivierg (Olivier Guilyardi)
+1 here too
 [2007-10-29 11:42 UTC] matejpuntar (Matej Puntar)
+1 from me too
 [2007-10-29 15:46 UTC] cellog (Greg Beaver)
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
 [2010-11-15 12:26 UTC] mekras (Mikhail Krasilnikov)
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.
 [2011-08-22 02:54 UTC] miau (Koji Ando)
 [2011-08-22 03:09 UTC] miau (Koji Ando)
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)
 [2011-09-02 17:16 UTC] drunkenstranger (Drunken Stranger)
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.
 [2011-09-02 20:35 UTC] drunkenstranger (Drunken Stranger)
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"}
 [2011-09-02 20:39 UTC] drunkenstranger (Drunken Stranger)
 [2012-03-13 10:15 UTC] drunkenstranger (Drunken Stranger)
May I ask one question: suggested charset patch works fine. Why you wont fix it to repository?
 [2012-09-01 02:38 UTC] ashnazg (Chuck Burgess)
-Roadmap Versions: 1.5.0a1 +Roadmap Versions: 1.4.5
 [2012-09-01 02:38 UTC] ashnazg (Chuck Burgess)
-Roadmap Versions: 1.4.5 +Roadmap Versions: 1.5.0a1
 [2012-09-02 00:58 UTC] ashnazg (Chuck Burgess)
-Status: Open +Status: Closed -Assigned To: +Assigned To: ashnazg
Including miau's patch in 1.5.0a1.