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/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.Not only is this problem not insurmountable, it's mostly solved. For websites, HTML5 @font-face is the solution. For distributing documents, PDF has it handled. The only piece of the puzzle that isn't here yet is creating documents with a font you don't actually have — and that space, I think, is intentionally left blank.
This is an insurmountable problem with branded fonts; they only work if you load the branded font on every computer that will ever brush up against it. This means your Word documents will look like crap when you send them to an outside company. This means your web site that proudly uses the font will look like... umm... some generic sans-serif font when you use it on your web page.
The problem is insurmountable because, to fix the problem, you will have to convince everybody in the world to install it on their machine, which will require you to release the font for unrestricted use. A custom company-branded font with unrestricted use is an oxymoron.