Search

Help Viewer low font quality by Azarien

Closed

2
0
Sign in
to vote
Type: Bug
ID: 771524
Opened: 11/18/2012 5:21:22 AM
Access Restriction: Public
0
Workaround(s)
1
User(s) can reproduce this bug
Source code samples in Help Viewer are rendered in a low quality font, that looks like some East Asian fonts (MS Mincho, MingLiU or SimSun), instead of a much better looking Consolas font.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Open Help Viewer 2.0
Navigate to any topic with a source code snippet.

Product Language

English

Operating System

Windows 7 SP1

Operating System Language

Polish

Actual results

Source code sample is typeset in a non-antialiased font of low readability, probably MS Mincho or MingLiU.

Expected results

Source code sample rendered in high-quality monospace font with ClearType support, for example Consolas, Courier New or Lucida Console.
File Attachments
File Name Submitted By Submitted On File Size  
tdi.png 11/19/2012 9 KB
Sign in to post a comment.
Posted by Sapien2 on 3/28/2013 at 6:12 AM
I have just updated my help collection to latest online version and the error still reproduces.
There is many discussions about this error ( http://social.msdn.microsoft.com/Forums/en-US/devdocs/thread/e14fd433-e342-4964-a327-cced2ae61e5c/ for example ) and it is really annoying.
The error reproduces when you try to use en-us help books with non-english windows locale. For example I am using Russian locale.
And I want to ask, why this bug report closed without any reason ?
Posted by Microsoft on 11/20/2012 at 12:15 PM
Greetings Azarien

Thank you for filling out a Connect bug for the Help viewer. The font display in Code Snippets for some locales is a known issue. This is a duplicate of a backlog item. The Help viewer supporting CSS files have Courier listed first, not a Unicode encoded font – which then changes the fallback logic that results in what is rendered.

Thank you,

Malcolm Dickson
IDE Experience PM
Posted by Microsoft on 11/20/2012 at 2:45 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Microsoft Visual Studio Connect Support Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 11/19/2012 at 9:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.