WDP7 Doesn't like certain characters in new font

Hey everyone, weird problem I am having.

I am a huge fanboy of fonts and use a large variety of custom fonts in my work.

Well, I am recently got a new one, it's called 'Urban Sketch'.

Anyway, I was trying for a while to use this font on a new webpage, and it took me a long time to realize what was going on.

Every time I attempt to enter the character M or W, I get a fatal error reading "Access Violation at _______ " and am forced to close the program.

I am sure it does this with more characters but I don't feel like going through them all seeing which makes me crash, lol.


Has anyone ever heard of this happening before? I have re-installed the font but no dice.

I also tried the font in another program (word) and it worked fine.

What's my WDP7 have against Urban Sketch? :'(


Here's a link to the font if anyone wanted to try to replicate the problem-

http://www.dafont.com/urban-sketch.font

The most likely cause of the problem is the complexity of the characters in the Urban Sketch font. They take up a lot of resources and unless you are using a 64-bit version of Windows and have at least 4GB of RAM you will have issues using that font. See the attached images to see how Urban Sketch font differs from a "normal" font like Arial.

BTW the use of non-web-safe fonts is not a wise decision. Unless the person viewing your web page has the exact same font (similarly named fonts won't work) they will be substitued with a web safe font by their browser.

Convert your fonts to editable shapes or group the text. This will create a bitmap of the text when you publish your site. Otherwise, you might be the only person who sees the actual font.

Hmm, thanks for pointing that out, I didn't realize how complex the font was. If that is the case, I will try it on my other machine (8GB memory on a 64Bit version of Windows 7) to see if I get the same problem.

And yes, I put my non-websafe fonts into groups with other non-websafe font objects that way they publish as a bitmap ;) The way Xara reminds you that you have non-rasterized non-websafe fonts in your project before you upload is very handy.

http://www.tilthenight.com

I was under the impression that Xara is a 32bit app and can't use more ram

John that is true but Windows 7 64-bit will provide the resources (if enough RAM is available) for a used font and the application using it.

On a 32bit version of Windows the resources used by a font can/will take away resources for an application. Xara will see it no longer has available memory for its use and report an error when it tries to access what was but is no longer available memory addresses.

That makes sense