Closed (fixed)
Project:
Advanced Forum
Version:
6.x-1.0-rc1
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
26 Feb 2009 at 03:25 UTC
Updated:
20 Mar 2009 at 04:40 UTC
Not sure how to fix this, or even if its really a big issue, but its something to be aware of atleast.
afaik, most Drupal files are in UTF-8 and the output generally expects that too.
I found this out when I inserted a — into a tpl.php file instead of the html code (mdash) and the output was � instead of what I had expected.
Comments
Comment #1
michelleI've never heard of this before and never had a problem with it. I did hunt through my editor and found where I could change it to UTF-8 and have done so, so any file I edit will get fixed. But I really don't feel like opening and re-saving every file in the project. Maybe for 2.x. I'll leave this open for a while just in case someone knows a command that will batch switch them all.
Michelle
Comment #2
michelleWell, I tried. I went thru and converted every file in the D6 branch to UTF-8. And CVS totally freaked out. I had to download a fresh checkout to fix it. Looks like CVS can't handle that change. Maybe I can get it fixed when I branch to 2.x but it won't be happening now.
Sorry,
Michelle
Comment #3
naheemsays commentedthe current contents of the files are currently ok and will not break with the characters that are currently in there, so all you really need to do is put a note somewhere that if the people modify the template files (and put them in their theme folders), if they use non ANSI characters, they will need to change character encoding.
That should cover all the bases. Thanks for trying though.
Comment #4
michelleOk, I'll add it into the docs. Thanks.
Michelle
Comment #5
michelleAdded the note and linked back to this issue. Changed the title so it doesn't look so silly in the handbook link.
Michelle