Can't have spaces in font names

[mapserver-bot]

Reporter: karl-ms@sc.com
Date: 2006/09/12 - 16:29
Trac URL: http://trac.osgeo.org/mapserver/ticket/1908

This is probably more of a wish list item than a bug, but right now you can't have spaces in font names.

Here's how it bites me:  Say I am emitting an SVG file and then importing it into Illustrator, where I'll in 
turn save it as an AI file and send it off to be printed on a super high quality printer...

I'm using the Lucia Sans font and in my .map file, I call it lucidasans and in the fonts.txt fontset file, 
when rendering as a GIF with GD, it maps to a Lucida Sans truetype font and everything's fine.

But when generating an SVG file, the font in there is called "lucidasans" and then my Mac wants to find 
lucidasans and can't -- it needs "Lucida Sans" so then without asking it substitutes some other stupid 
font like Arial MT that doesn't have my airplane glyph in it, so all my little airplane symbols, rotated to 
show the aircraft's heading with variable drop shadows to indicate the altitude are instead rendered as 
question marks.

I don't have a simple backwards-compatible fix.  The simple non-backwards-compatible fix is to use a 
tab to separate the logical font name from the filename in the FONTSET file. I can, of course, edit or 
postprocess my SVG file to fix it.

[mapserver-bot]

Author: hobu
Date: 2007/08/07 - 23:55
Sliding forward to the next release...

[mapserver-bot]

Author: sdlime
Date: 2008/05/16 - 05:31
What if we supported quotes as a way to embed spaces? Or supported space, tab or comma delimited font files?

Steve

[mapserver-bot]

Author: tomkralidis
Date: 2008/06/24 - 06:06
+1 on quoting font names. We'll want to have backward compatibility for a couple of releases (i.e. check names the existing way, if no match then check for quoted).

[mapserver-bot]

Author: sdlime
Date: 2008/06/24 - 16:23
Pushing to 5.4 regardless of solution... (unless I have a epiphany tonite)

Steve

[mapserver-bot]

Author: dmorissette
Date: 2011/03/15 - 17:27
Closing WONTFIX: this is no longer an issue with Cairo rendering in 6.0 which embeds the characters as strokes in the output.