Home Dashboard Directory Help
Search

Old Style numerals are not rendered for runs containing only numbers by Bradley Grainger


Status: 

Closed
 as External Help for as External


6
0
Sign in
to vote
Type: Bug
ID: 545921
Opened: 3/30/2010 6:03:02 PM
Access Restriction: Public
2
Workaround(s)
view
2
User(s) can reproduce this bug

Description

The Typography.NumeralStyle="OldStyle" property is not respected by WPF 4 when the text being displayed consists solely of numbers and punctuation. It appears that Old Style numerals are only used when the run being formatted/displayed also contains letters.

While this is easiest to demonstrate with <TextBlock>, code that uses TextFormatter directly is also affected.
Details
Sign in to post a comment.
Posted by odd parity on 6/23/2010 at 5:27 AM
I am also experiencing this. This is a massive showstopper for us as our application is reports-centric and OpenType support was one of the reasons for us adopting WPF. We are experiencing the following:

- WPF seems to default to OldStyle, proportional numerals.
- We cannot change either Typography.NumeralStyle or Typography.NumeralAlignment on runs containing only numbers.
- As a result, our reports look horrible.

Is there a way for me to at least change the defaults so that we will have lining, tabular figures everywhere? The fact that Bradley's problem is changing _to_ OldStyle numerals would suggest this. As most runs that should have proportional figures also contain text this would be an acceptable workaround for us until a hotfix is available.
Posted by Microsoft on 6/15/2010 at 11:35 AM
Hi Bradley,

We've been able to determine that this issue is caused by a defect in a binary that ships as part of Windows. Unfortunately, there's no workaround. We're currently following up with the Windows team to see if they can produce a hotfix for this issue or fix it in their next release.

Thanks,
WPF Team
Posted by cz1984 on 4/3/2010 at 4:33 AM
I ran into the same problem using Typography.Variants of Subscript and Superscript and reported it a few days ago. Microsoft was able to reproduce the bug and is working on it. Looks like it affects all Typography attached properties. (E.g. Typography.Capitals of AllSmallCaps fails too.)
Posted by Microsoft on 3/31/2010 at 2:41 AM
Thanks for your feedback. We were able to reproduce the issue you are seeing. We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Sign in to post a workaround.
Posted by Bradley Grainger on 12/13/2012 at 8:34 PM
3) Install the Platform Update for Windows 7 SP1 that updates DirectWrite: http://support.microsoft.com/kb/2670838
Posted by Bradley Grainger on 11/29/2012 at 8:02 PM
1) Upgrade to Windows 8; it has a newer version of DWrite that doesn't have this bug.
2) IE10 updates the installed version of DWrite to the version shipped with Windows 8. Installing IE10 on Windows 7 will work around this bug.