Jump to content

 
Photo

fixing split text blocks in FreeHand

- - - - -

  • Please log in to reply
2 replies to this topic

#1
Dennis McClendon

Dennis McClendon

    Hall of Fame

  • Validated Member
  • PipPipPipPipPipPipPip
  • 1,083 posts
  • Gender:Male
  • Location:Chicago
  • Interests:map design, large-scale maps of cities
  • United States

Perhaps I’m not the only dinosaur still using FreeHand, so I thought I’d share a trick I came up with over the weekend. In files coming over from Illustrator format (such as those exported from GIS), there’s often a problem with labels being broken into pieces because of the different ways that Illustrator and FreeHand handle kerning of text. So a label such as “Taurus Ave” will break into five labels, because of kerning after the T and before the A and v.

I went all the way back to ArcGIS and edited the attribute table (in Excel and Notepad) to substitute unusual characters for the ones giving me the most problems: & for T, # for W, ^ for V, and % for Av. Because kerning around those non-alphabetic characters is not common, the words including them survived the trip through Illustrator and into FreeHand, where it was a simple matter to use Text Find and Replace to correct them back to the proper spelling. You do have to be careful not to use + or other characters that have special meaning in Excel.
Dennis McClendon, Chicago CartoGraphics
chicagocarto.com

#2
M.Denil

M.Denil

    Key Contributor

  • Validated Member
  • PipPipPip
  • 56 posts
  • United States

Good idea.
If one could work out a system using non-kerning and non-magic characters, then a coder/decoder could be built into a ring one could wear on one's finger....

If it is the kerning that mucks things up, couldn't exporting in a monospaced face work too?

#3
rudy

rudy

    Ultimate Contributor

  • Validated Member
  • PipPipPipPipPipPip
  • 740 posts
  • Gender:Male
  • Location:Canada
  • Canada

We've used a similar approach when exporting Freehand files to Illustrator. It is the kerning that gives us grief so we've done similar letter/symbol substitutions to get around the problem.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

-->