Bug 13449 - Consolas font is unusable with Xamarin Studio 4.0.10
Summary: Consolas font is unusable with Xamarin Studio 4.0.10
Status: RESOLVED DUPLICATE of bug 11985
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 4.0.10
Hardware: PC Mac OS
: --- normal
Target Milestone: master
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2013-07-24 19:16 UTC by Val Savvateev
Modified: 2013-07-25 01:01 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Incorrect rendering of Consolas font (59.15 KB, image/png)
2013-07-24 19:16 UTC, Val Savvateev
Details


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 Developer Community or GitHub 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:
Status:
RESOLVED DUPLICATE of bug 11985

Description Val Savvateev 2013-07-24 19:16:31 UTC
Created attachment 4429 [details]
Incorrect rendering of Consolas font

Xamaring Studio 4.0.10 is rendering Consolas font incorrectly to the point that it is impossible to use for development. Please see attached screenshot for example.
Things are especially bad with punctuation characters (comma, dot, colon, semicolon) and parenthesis.
Comment 1 Mike Krüger 2013-07-25 01:01:29 UTC

*** This bug has been marked as a duplicate of bug 11985 ***