Hello,
it seems that the portal is basically unable to process UTF-8 encoded database fields: the standard encoding is ISO-8859-1, with no way to change it. Now, is that a design decision or a bug? Can't it just read from a UTF-8 encoded field and then translate it to ISO-8859-1, which is conversely the charset I'm using so far due to ISP limitations?
cicciosprint
Member Since 05 Aug 2009Offline Last Active Aug 30 2009 02:58 AM



Find content
Not Telling
Display name history