Bug 1375 - String.StartsWith() returns incorrect result with certain unicode characters
Summary: String.StartsWith() returns incorrect result with certain unicode characters
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib ()
Version: 2.10.x
Hardware: PC All
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2011-10-09 06:53 UTC by mbbugreport545
Modified: 2012-02-20 10:07 UTC (History)
2 users (show)

Tags: string comparison, unicode characters
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description mbbugreport545 2011-10-09 06:53:25 UTC
String.StartsWith() and possibly other methods returns the wrong result when the argument string contains certain unicode characters.

$ mono --version
Mono JIT compiler version 2.10.5 (tarball Mon Sep  5 20:45:01 UTC 2011)

csharp> "d.a".StartsWith("d.\u07B0", StringComparison.Ordinal);

Incorrect results:

csharp> "d.a".StartsWith("d.\u07B1", StringComparison.Ordinal);
csharp> "d.a".StartsWith("d.\u07B1", StringComparison.OrdinalIgnoreCase);
csharp> "d.".StartsWith("d.\u1701", StringComparison.Ordinal);
Comment 1 Marek Safar 2012-02-20 10:07:56 UTC
This issue seems to be fixed in master