Skip to main content
Home Forums Silverlight Programming Programming with .NET - General Using Font Family Tahoma
12 replies. Latest Post by Eloff on July 19, 2009.
(1)
WiproSachin
Member
323 points
87 Posts
07-14-2008 1:05 PM |
Hi,
I need to use Tahoma As Font Family for Textblock
<
But it not coming in Tahoma.
Please Help.
Bill Reiss
Contributor
4818 points
913 Posts
07-14-2008 1:41 PM |
Tahoma is not one of the built in fonts for Silverlight:
http://msdn.microsoft.com/en-us/library/system.windows.media.fontfamily(VS.95).aspx
SteveWong
6323 points
1,281 Posts
07-14-2008 8:40 PM |
include it in your project first
07-14-2008 9:08 PM |
SteveWong: include it in your project first
This is a risky suggestion. As I understand it, the font licenses on Windows don't allow for you to redistribute the font. Now if you could find a freeware or royalty free redistributable version of Tahoma, then you could include that one.
07-15-2008 1:14 AM |
of course, you should have the permission for distribution of the FontFamily which is also a remind from MSDN
07-15-2008 1:17 AM |
Does any one have Free Tahoma font. Please provide me the link as MS Tahoma is non shareable . Hope to get Tahoma inside silverlight by end of silverlight 2 final release.
Regards
Sachin
stefan.j...
61 points
28 Posts
07-17-2008 8:34 AM |
If I unstand this right, embedding might be OK:
http://www.microsoft.com/typography/fonts/font.aspx?FID=19&FNAME=Tahoma%20Bold&FVER=2.30http://www.microsoft.com/typography/TrueTypeEmbedding.mspx
07-17-2008 8:56 AM |
Stefan,
Thanks for the link.
It's hard to get a clear answer on this sort of stuff, it would be great if we could get an official stance from MS on embedding system fonts in Silverlight. When fonts are embedded in a Word doc, they're not in a readily consumable format, even with docx, you can't just rename it to a ZIP and grab the font because the font file is obfuscated, most likely to prevent someone from doing just that. In a Silverlight app, the font file is not obfuscated, so this could be a difference.
If this is an issue which makes it so that we can't legally embed font files, Microsoft should probably add obfuscated font support to Silverlight.
07-17-2008 9:02 AM |
Bill
I'm waiting for a response of a PSFD Task to Microsoft. I'll let you know, when I get the answer.
Stefan
07-17-2008 9:04 AM |
Ok great thanks, I'm also checking through one of my Microsoft contacts.
08-05-2008 5:33 AM |
I've got an answer:
It's not allowed to deploy Tahoma. You have to buy a license from http://www.ascendercorp.com/inquiry.aspx?Ref=Microsoft
Unfortunatly my contact person said there will be no new fonts in the final version.
08-06-2008 8:40 AM |
Great work Stefan......
Eloff
139 points
114 Posts
07-19-2009 9:30 AM |
Your Microsoft guy decided not to make work and trouble for him/herself by just telling you no. The reality is very different, if you read on: http://www.microsoft.com/typography/RedistributionFAQ.mspx It says: Embedding allows fonts to travel with documents. Most fonts distributed with Microsoft products allow embedding. To check a font's embedding permissions, right-click on the font file and choose 'Properties'. There are 4 levels of embedding permissions: 'Print and preview' fonts can be embedded in a document, provided the user reading the document cannot edit the content of the document. 'Editable' fonts can be embedded within content that can be edited by the user. 'Installable' fonts within a document may be permanently installed by the user reading the document or a client application. In practice, installable fonts are treated like editable fonts by most client applications. 'No embedding permissions' prevent fonts from being embedded in a document. Tahoma is marked as 'Editable', (At least it is on my Vista Ultimate machine), which means go ahead and embed it. Btw, you can specify Tahoma for the font and it should work if it's available on the user's system (i.e. no embedding required) according to: http://msdn.microsoft.com/en-us/library/cc189010(VS.95).aspx There's no mention made that you are required to obfuscate the font, but the reality there as well is that silverlight fonts are obfuscated! You cannot use a font that's simply in the XAP file, I know because Microsoft changed that at the last minute for Silverlight 2 RTM, and I'm still miffed about it. Fonts must be embedded in an assembly (required something like Reflector to be able to extract them.) [Rant] It makes life hard for people wanting to use other fonts with dynamic languages that have no compiled assemblies to compile fonts into. (It also means that if you want to load fonts dynamically you have to create assemblies dynamically, which cannot be unloaded - resulting in a huge memory leak.) [/Rant] -Dan