Hi Alison, No, I am only familiar with a MIF8/FM8 workflow in this translation case. Perhaps Jeremy knows? Best regards, Mats Broberg
________________________________ From: Alison Carrico [mailto:[EMAIL PROTECTED] Sent: Wed 2008-03-12 17:45 To: Broberg, Mats; framers@lists.frameusers.com Subject: RE: Possible MIF -> FM bug in FM 8.02 (p273) This could end up being an issue for my company. Do you know if it happens with v7 MIFs when opened with v8? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Broberg, Mats Sent: Sunday, March 09, 2008 3:47 AM To: framers@lists.frameusers.com Subject: RE: Possible MIF -> FM bug in FM 8.02 (p273) Jeremy, Thanks, good to hear you could replicate the behavior on your side. Now we definitely can remove the word "Possible" from the topic title... I will talk to our vendors and see if they can use this workaround. In the meantime, I hope that the men and women at Adobe understands how serious this bug is and will provide a patch as soon as possible. Thanks for the test work you did, Jeremy! Best regards, Mats Broberg www.flirthermography.com ________________________________ From: Jeremy H. Griffith [mailto:[EMAIL PROTECTED] Sent: Sun 2008-03-09 05:53 To: framers@lists.frameusers.com Cc: Broberg, Mats Subject: Re: Possible MIF -> FM bug in FM 8.02 (p273) On Fri, 7 Mar 2008 16:24:48 +0100, "Broberg, Mats" <[EMAIL PROTECTED]> wrote: >Concise problem statement: >Opening edited (translated) MIF files in FrameMaker 8 causes some >of the extended characters disappear. Text containing extended >characters for different languages are missing characters in >FrameMaker, although all characters are present in the MIF file. >The missing characters follow no particular pattern, most of the >time all characters are there. We can confirm this bug in Frame 8.0p273. In your test case, the last UTF-8 character was dropped; the others were kept. We investigated a bit further and may have a workaround for you. We noticed the string content was fairly long, at 214 bytes (counting the five UTF-8 instances as two bytes each). While that doesn't exceed the 254-byte limit, we thought it would be worth examining. When we cut the string into three ParaLines as Frame would, where the first two were about 100 bytes each, all characters remained. We understand that a TM tool is generating the MIF. Is there a way to limit the maximum line length it allows in a single <String> to, say, 128? The length doesn't really matter to Frame, since the line breaks are reset anyway upon loading the MIF. HTH! -- Jeremy H. Griffith, at Omni Systems Inc. <[EMAIL PROTECTED]> http://www.omsys.com/ _______________________________________________ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/acarrico%40adamsglob alization.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info. _______________________________________________ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
