0011220: Illegal utf8 encoding Iván while running on Quercus

ID	Project	Category	View Status	Date Submitted	Last Update
0011220	mantisbt	installation	public	2009-11-26 17:25	2011-12-17 02:47

Reporter	anthropic	Assigned To
Priority	low	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	1.2.0rc2

Summary	0011220: Illegal utf8 encoding Iván while running on Quercus
Description	Quercus php engine can't handle the name Iván Oliva in the library/adodb/adodb.inc.php file, it doesn't like running the file with unicode characters in it. Changing it to Ivan allowed the file to process. It would be nice if compatibility with Quercus was maintained for people who want to use a better version of PHP than the php.net version.
Tags	No tags attached.

rombert 2009-11-26 17:37 reporter ~0023815	Quercus is not a supported platform I'm afraid. Out of curiosity, what OS and Quercus version have you used? I did try Quercus on Linux some time ago and it worked for the SOAP API.

anthropic 2009-11-26 20:12 reporter ~0023816	I develop in cfml using Railo and it comes with a version of Coucho Resin server with Quercus (once I added it to the config file for Resin). It is my understanding that it is the latest version of for all components at the time. In this case I know it is not supported, but if it is a case of simply doing a find and replace it will make a lot of lives easier. Quercus lists Mantis as a compatible application so it would be a shame to drop compatibility for the sake of a developer's name in a comment. As far as OS I am on Vista (please don't laugh I will upgrade to 7 soon).

rombert 2009-11-29 14:58 reporter ~0023821	I suggest opening this bug on the Quercus bug tracker, since it's their application which fails, even more so when MantisBT is supposed to be supported. Please reference the bug on this page as well, so we can track it. Out of curiosity, which page/operation triggers this failure?

anthropic 2010-07-13 01:15 reporter ~0026063	Sorry I never noticed your reply to the issue, I can't remember which page caused the issue, I think any that had to access the library/adodb/adodb.inc.php file. I haven't tested with the 1.2.1 release. I will try to find time to do so soon.