Segoe UI italic looks bold

Question

I style a part of the page in "font-style: italic" and see the font (Segoe UI) is rendered in much bolder style than the rest of the page. Is there only a bold-italic version of the font installed in Win8.1?

Answer 1

Hi pkursawe,

I think its a normal behavior in WinJS.

Take a look at my test result, italic and bold-italic is totally different thing.

But actually when I test the same thing with IE, I can find the result almost same:

Anyway thanks for your feedback.

--James

---

<THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
Thanks
MSDN Community Support

Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

Answer 2

James, your samples look ok to me. In my app however, italic looks bolder than the normal font.

And those are both h2 element in a Listview with the same font-weight of 200. Just one with the italic style applied.

And as you can also see, the smaller texts look ok. Could you test it on your side with 20pt font-size please?

Answer 3

Oops, Can you share your code with us?

--James

---

<THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
Thanks
MSDN Community Support

Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

Answer 4

Sure, easy to reproduce actually.

http://1drv.ms/WOzDjj

Answer 5

Thanks for your package. I can see this by <h2> tag. I'm using <p> tag:

    <p style="font-style: italic; font-family:'Segoe UI'">I am italic</p>
    <p>I am normal</p>
    <p style="font-weight:bold">I am bold</p>
    <p style="font-weight: bold; font-style: italic">I am bold-italic</p>

I mean if you use "font-size" instead of <h2>, it would be better:

    <p style="font-style:italic; font-size:40px">10:30</p>
    <p style="font-size:40px">10:30</p>

--James

---

<THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
Thanks
MSDN Community Support

Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

Answer 6

For semantic reasons I would like to keep h2. What is the problem here?

Answer 7

Good question. Looks like a bug.

Will fire to Seniors. The thing works fine with IE.

--James

---

<THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
Thanks
MSDN Community Support

Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

Answer 8

James, any news on that? You marked this as answered. I think that might confuse others if the issue is not really resolved, as your own footer clearly states. I too often came here and saw threads marked as "answered" when in fact an answer was not given (to the OP question).

Answer 9

Hello pkursawe,

I would agree what you mentioned here: the issue is not resolved.

We can reproduce the issue and we can confirm something wrong with the <h2> tag, but I cannot give any quick fix solution for that because the issue might related with render engine. I already submitted this to our seniors, and they will check for that. Sorry I can only help with so far.

To raise it via http://wpdev.uservoice.com/forums/110705-dev-platform is also suggested. 

I mark my reply here so that others may know this is a issue and do not spend time on finding the solution. If my mark make you unsatisfied, I would like to unmake it. Thanks for your understanding.

--James

---

<THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
Thanks
MSDN Community Support

Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

Answer 10

I think we can leave it marked for now and change to the real answer once the bug has been fixed.

I will raise the issue over at uservoice too to get more exposure.