Font Query re Q1 2016 SP1

5 posts, 1 answers
  1. Jon
    Jon avatar
    813 posts
    Member since:
    Oct 2008

    Posted 25 Feb Link to this post

    Hi Ivan

    With the latest release (and recent internal builds) I have noticed that the navigation font being displayed in chrome is quite different to that of IE.  Chrome seems to be a somewhat bold while IE is a fairly skinny one. Attached image showsIE rendering on left and Chrome on right.

    Is Chrome rendering it with Roboto while IE isn't?  I've tried to use the css property browsers but they aren't telling me what the actual font being rendered is :(

    Regards

    Jon

  2. Ivan Zhekov
    Admin
    Ivan Zhekov avatar
    539 posts

    Posted 01 Mar Link to this post

    Hello, Jon.

    Initially, we load only WOFF2 fonts from Google servers and those unfortunately are not supported in IE browsers. For R2 release, we'll include WOFF fonts which work on IE9-11 and EOT font which works on IE8.

    Regards,
    Ivan Zhekov
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Jon
    Jon avatar
    813 posts
    Member since:
    Oct 2008

    Posted 01 Mar in reply to Ivan Zhekov Link to this post

    Hi Ivan,

    Ah got you,  I use Icomoon to generate a custom font and it does all the font types,  the difference in size between WOFF and WOFF2 is massive so I can't say I blame you on that. Shame that IE persists in being a retrograde browser (consistent if nothing else!).

    I presume that I could just use the font manually then?  If so which one is it as there are a lot of variants?

    Regards

    Jon

  5. Answer
    Ivan Zhekov
    Admin
    Ivan Zhekov avatar
    539 posts

    Posted 03 Mar Link to this post

    Jon,

    the following snippet is directly from our stylesheets:

    @font-face {
        font-family: 'Roboto';
        font-style: normal;
        font-weight: 400;
        src: url(https://fonts.gstatic.com/s/roboto/v15/5YB-ifwqHP20Yn46l_BDhA.eot);
        src: local('Roboto'),
            local('Roboto-Regular'),
            url(https://fonts.gstatic.com/s/roboto/v15/2UX7WLTfW3W8TclTUvlFyQ.woff) format('woff'),
            url(https://fonts.gstatic.com/s/roboto/v15/CWB0XYA8bzo0kSThX0UTuA.woff2) format('woff2');
        unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2212, U+2215, U+E0FF, U+EFFD, U+F000;
    }
    @font-face {
        font-family: 'Roboto';
        font-style: normal;
        font-weight: 500;
        src: url(http://fonts.gstatic.com/s/roboto/v15/RxZJdnzeo3R5zSexge8UUfY6323mHUZFJMgTvxaG2iE.eot);
        src: local('Roboto Medium'),
            local('Roboto-Medium'),
            url(https://fonts.gstatic.com/s/roboto/v15/RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff) format('woff'),
            url(https://fonts.gstatic.com/s/roboto/v15/RxZJdnzeo3R5zSexge8UUVtXRa8TVwTICgirnJhmVJw.woff2) format('woff2');
        unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2212, U+2215, U+E0FF, U+EFFD, U+F000;
    }

    I went ahead it to our stylesheets. Unfortunately, it was after this week's internal build, but you can download next week's internal build. If the end result is satisfactory to you, you can use the snippet above as a temporary solution. Just don't forget to remove it once R2 is out.

    Regards,
    Ivan Zhekov
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  6. Jon
    Jon avatar
    813 posts
    Member since:
    Oct 2008

    Posted 03 Mar in reply to Ivan Zhekov Link to this post

    Thanks very much Ivan.  That works very well, such a visual improvement :)

    Best Regards

    Jon

Back to Top
UI for ASP.NET Ajax is Ready for VS 2017