Automated Content Transformation Software
Home | 1-877-893-2967 | Support
Technical tidbits and other ideas at WebWorks
View by Blog
  • All WebWorks Blogs
  • Scenes from the Engine Room
  • Digital Publishing & Automation
  • blurnge
  • Unicorns and glitter!!
  • Technical Communication
  • Christopher Ward
Recent Posts
  • Related Links (DITA)
  • WebWorks FTP Deployment (Experimental)
  • But I’m not a developer!
  • Getting ePub output into iBooks on iPhone/iPad
  • Use JScript .NET instead
  • iBooks thoughts
  • Study Hall Makeup
  • Study Hall
  • Building New Stuff
  • __possible__: Google Docs in ePublisher
View by Category
  • ePublisher
  • framemaker
  • mobile
  • Round•Up
  • Uncategorized
  • video
View by Month
  • March 2011
  • December 2010
  • September 2010
  • August 2010
  • May 2010
  • March 2010
  • January 2010
  • November 2009
  • October 2009
  • January 2009
  • December 2008
  • October 2008
Blog Access
  • Log in
  • Entries RSS
  • Comments RSS
Subscribe to the Blog Feed

blurnge

Frame 7 to Frame 8 problem

We have discovered a kind of a nasty problem which occurs when you bring FrameMaker 7 documents created in some non-English locale, into FrameMaker 8.  This problem affects any text that is inserted into the FrameMaker 7 dialogs, such as the Paragraph Designer or the Marker dialog, under the non-English locale.  When the docs are pulled into FrameMaker 8 on an English system all of the content is converted to Unicode.  However, all of the text from the dialogs is not converted.  This means that things like the Index and the Paragarph style names are rendered as garbage characters (or probably more correctly, the raw bytes rendered as FrameRoman encoding).

Tags: framemaker
Posted in framemaker |

Leave a Reply


  • « Previous post
  • Next post »
This blog is protected by Dave's Spam Karma 2: 2085 Spams eaten and counting...