Any updates about this?. I'm showing you the code so fix the issue. Please tell me what else you may need to carry this into the main tree.

TIA

Unfortunately the extension is currently unmaintained, so I don't think anybody is going to commit your patch in the nearest future.

i found this bug too, so code is like this:

$word = new COM("Word.Application", null, CP_UTF8);
$word->Visible = true;
$doc = $word->Documents->Add();
$word->Selection->TypeText( "UTF8 text here, russian in my case" );

In word appears "Normal text " + garbage.

can this be fixed in CVS ? i have to compile php on win32 by myself ;)

Assigned to the maintainer.

Any update on this bug? I still have the problem with PHP 5.2.3 and the changelog does not indicate any fix in 5.2.6.

It is very annoying to have a nice patch standing there still with no one to commit it to CVS.

I see same problem with ADODB.Connection and it's parameters.
When I use:

// init connection to DB
$dbc = new COM('ADODB.Connection',null,CP_UTF8);
$dbc->Open("PROVIDER=MSDASQL;Driver={SQL Server};Server=192.168.210.1;Database=test;UID=test;PWD=test");
// create command
$oCmd = new COM('ADODB.Command',null,CP_UTF8);
$oCmd->ActiveConnection = $dbc; // 
// Table test1 has one row c1 of type nvarchar(200)
$oCmd->CommandText = "INSERT INTO test1(c1) VALUES (?)";
$oCmd->CommandType = 1;
// Some UTF-8 string (length in characters is 15, 24 in bytes)
$val='ABCříšúěďáéóXYZ';
$len=strlen($val);
$p=$oCmd->CreateParameter('name',202,1,$len,$val);
$oCmd->Parameters->Append($p);
$oCmd->Execute();
// ADODB sends to DB nvarchar(24) which is length of string
// in bytes not characters, but data has 15 characters
// in UCS-2. So in database there is correct string, but there is
// some garbage after end of string

after 2,5 years, can someone just commit the patch I provided to cvs?. It's annoying to recompile any PHP version that comes out just for the sake of this nonsense. Take into account that any use of PHP+COM+multibyte stuff fails without this silly fix.

Thank you.

taking the hand on this one.

Hi,
i still have this bug in PHP Version 5.3.3

Is it so hard to commit this?

The patch is still missing in PHP 5.3.15 (I don't know why, the patch is working: thanks to fjortiz!)

So I compiled php_com_dotnet.dll that is compatible to http://windows.php.net/downloads/releases/php-5.3.15-nts-Win32-VC9-x86.msi

Download this compiled dll at http://www.agitos.de/pub/php-5.3.15-com_dotnet-patch.zip

I went to apply the patch and its already there in 5.3.18. Not sure when this was 
actually solved but the bug status needs updating.

Some update: while working with 5.3.28, it seems to work better now, but there is still a length-related bug inside.

While inserting from PHP strings with accents or spanish "ñ" char in MSSQL server through COM driver (utf8 encoded), it seems to insert properly, but if I inspect the last char in the column I find a "\0" at the last position, which makes all my "=" queries fail. 

"\0" is the C language string terminator so there is clearly some kind of memory allocation mismatch in the code. 

Oddly enough queries with "where column='textwithñfails'+char(0)" do work, so I'll use this trick as a workaround meanwhile.

This appears to be a duplicate of bug #66431, which is fixed as of
PHP 5.4.29 and 5.5.13, respectively.