Bug #49971 [Com]: Cyrillic characters from MSSQL coming up as questionmarks

Edit report at http://bugs.php.net/bug.php?id=49971&edit=1 ID: 49971 Comment by: dukiii at yahoo dot com Reported by: odbc at ikiliekki dot org Summary: Cyrillic characters from MSSQL coming up as questionmarks Status: Open Type: Bug Package: ODBC related Operating System: Windows server 2003 SP2 PHP Version: 5.3.0 Block user comment: N Private report: N New Comment: I have the same problem. Linux: OpenSuse 11.2 FreeTDS version 0.82-1.1 PHP 5.3.1 Server version: Apache/2.2.13 (Linux/SUSE) Windows XP Professional: MSSQL Server Express 2005 I'm using "native" connection - mssql_connect(SERVER, USER, PASSWORD); here is output: ------------------------- ID_DC ID_DOC ID_ATTR VALUE 291 50 17 404-78/10-IV 291 50 20 2010-12-10 00:00:00.000 291 50 28 ????? - ???? - ????? 291 50 34 ????? - ???? - ????? 291 470 27 50 ------------------------- ????? should be cyrilic characters. Text shows correctly in microsoft tools, such as ms sql server management studio express. Previous Comments: ------------------------------------------------------------------------ [2009-10-23 12:56:54] odbc at ikiliekki dot org Description: ------------ I have some Russian text in mssql, with fieldtype nvarchar(50). This text shows correctly in microsoft tools, such as ms sql server management studio express. Querying the data with ODBC [ odbc_connect("DRIVER={SQL Server};Server=<ip>;Database=<db>;Charset=UTF-8",<user>,<pass>); ] results in questionmarks apart from ASCII characters in the same contents. (Such as "test ????") I've tried setting collates, languages and such in SQL server and in queries (SET LANGUAGE N'Russian'). Wiresharking the data from webserver (IIS) to browser shows that it's questionmarks and not just being rendered wrong. Expected result: ---------------- test &#1088;&#1077;&#1084;&#1077;&#1085; Actual result: -------------- test ????? ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/bug.php?id=49971&edit=1