2 ms·
If you're using a browser that supports @font-face, you're looking at Nokia Pure. From http://brandbook.nokia.com/generated_files/pub_module/css/c373.css http:/
by scott_s 16y ago
If you're using a browser that supports @font-face, you're looking at Nokia Pure. From http://brandbook.nokia.com/generated_files/pub_module/css/c373.css http://brandbook.nokia.com/generated_files/pub_module/css/c3...:
@font-face {
font-family: 'Nokia Pure Text';
src: url('/other_files/Brand_Book_v2.2_2011/Fonts/puretext/nokiapuretext-webfont.eot');
src: url('/other_files/Brand_Book_v2.2_2011/Fonts/puretext/nokiapuretext-webfont.eot?iefix') format('eot'),
url('/other_files/Brand_Book_v2.2_2011/Fonts/puretext/nokiapuretext-webfont.woff') format('woff'),
url('/other_files/Brand_Book_v2.2_2011/Fonts/puretext/nokiapuretext-webfont.ttf') format('truetype'),
url('/other_files/Brand_Book_v2.2_2011/Fonts/puretext/nokiapuretext-webfont.svg#webfont4UxFerZx') format('svg');
font-weight: normal;
font-style: normal;
}
Chrome supports @font-face, so kwantam is looking at Nokia Pure. I think that CSS feature goes a long way in dealing with the problems you listed - at least for webpages.