[Tickets #7805] Re: Charset trouble when saving page names in db backend

bugs at horde.org bugs at horde.org
Tue Dec 30 04:00:07 UTC 2008


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7805
------------------------------------------------------------------------------
  Ticket             | 7805
  Updated By         | lfbm.andamentos at gmail.com
  Summary            | Charset trouble when saving page names in db backend
  Queue              | Wicked
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Chuck Hagenbuch
------------------------------------------------------------------------------


lfbm.andamentos at gmail.com (2008-12-29 23:00) wrote:

The trouble is $page variable in Wikilink.php returns the page name  
just fine: 'Tributário', but the $list array, which is pulled from  
$this->getConf('pages') returns the page name as 'Tribut�rio',  
thus making the test "$exists = in_array($page, $list)" fail (line 76  
of Wikilink.php).

The page_name, after the patch provided in this bug report, is saving  
correctly in the db (like 'Tributário'). The table's default charset  
is latin1.

Asking on #php, I was told I should change de charset of the table's  
fields to UTF-8.

I'm confused, because fields on my turba_objects table, for example,  
are also latin1 and I never had trouble concerning arbitrary  
characters on them. And, on the other hand, phpMyAdmin are capable of  
displaying the page_names on wicked_pages table just fine, what makes  
me guess this is something that can be handled on the fly, through  
php, without any db fields attributes changing.

If that's the case, is this a task for wicked or for Text_Wiki? Or  
should I really change the db field charset?






More information about the bugs mailing list