Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 for Bug 37467 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 14474 [details]
"No data is available for encoding 720" because Mono does not yet support codepage 720 for "System.Text.Encoding.GetEncoding(720)"
## Regression status: not a regression
BAD: Mono 4.2.2 (explicit/7b87787)
BAD: Mono 4.0.5 (detached/1d8d582)
BAD: Mono 3.12.1 (detached/0849ec7)
## Steps to replicate
Attempt to run the following line in Mono:
> $ csharp
> Mono C# Shell, type "help;" for help
> Enter statements below.
> csharp> System.Text.Encoding.GetEncoding(720)
> System.NotSupportedException: No data is available for encoding 720.
> at System.Text.Encoding.GetEncoding (Int32 codepage) [0x00000] in <filename unknown>:0
> at <InteractiveExpressionClass>.Host (System.Object& $retval) [0x00000] in <filename unknown>:0
> at Mono.CSharp.Evaluator.Evaluate (System.String input, System.Object& result, System.Boolean& result_set) [0x00000] in <filename unknown>:0
> at Mono.CSharpShell.Evaluate (System.String input) [0x00000] in <filename unknown>:0
## Result with .NET on Windows
System.Text.Encoding.GetEncoding(720) returns without error:
This is quite similar to Bug 31588, but for a different encoding.
*** Bug 37465 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 54665 ***