0003400: Setting "unicode.semantics = on" in php.ini fails WordPress

Mantis - Quercus
Viewing Issue Advanced Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
3400		minor	always	03-20-09 06:43	03-20-09 06:45

Reporter:	dl	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	4.0.0
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:

Summary:	0003400: Setting "unicode.semantics = on" in php.ini fails WordPress
Description:	I am trying to run WordPress for a blog that uses Unicode strings. However, in the normal setup procedure for WordPress, on the first (and only) configuration screen - choosing a blog name that contains Unicode characters (e.g. "&0001494;&0001488;&0001514; &0001489;&0001491;&0001497;&0001511;&0001492;") results in the blog name appearing as question-marks after WordPress is installed. I figured this has something to do with Unicode support, so I tried using Quercus with a custom php.ini file and set "unicode.semantics = on". This, however, results in WordPress installation failing with the following error: /opt/SDK/domains/domain1/applications/j2ee-modules/blog/wp-load.php:43: Fatal Error: 'ABSPATH/wp-includes/classes.php' is not a valid path If the php.ini file exists, but that specific "unicode.semantics = on" line is omitted, the installation succeeds (however, the blog name issue happens). It seems as if setting unicode.semantics screws the working directory, or some other weird phenomena along these lines... I am attaching my WEB-INF directory (with web.xml and php.ini). Configuration: Linux Sun's Java EE5 SDK - latest version (GlassFish V2.1) Quercus - latest SVN version WordPress - latest version (2.7.1)
Steps To Reproduce:
Additional Information:
Relationships
Attached Files:	WEB-INF.zip [^] (1,152 bytes) 03-20-09 06:43

Notes