Chinese translation has garbage for index entries (also Mif2Go issue)
Hello I'm reviewing Chinese Simplified files returned from my Chinese translator and everything is fine except for the index entries displayed as garbage in the marker dialog. In the generated index, the text appears to be Chinese after updating the book. Upon conversion to HTML Help 1.x output, the *.hhk file contains garbage characters for the index entries. The original files I sent are Framemaker 7.2 format and these were saved as MIF before sending. He translated them using Trados 2006 and returned the files again in MIF format. We are working on an English Windows XP. Upon return of the files, we attempted migrating the files to Help 1.X output using Mif2Go but the index entry output in the *.hhk file was garbage. As a test, we saved the files in FM 8.0 p277 format and the index entries were garbage (mostly question marks) in the marker dialog and generated index. As expected, after Mif2Go conversion *.hhk file shows entries as garbage. ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: Chinese translation has garbage for index entries (also Mif2Go issue)
I had some problems with Chinese characters on a recent FM9.0p255 translation job (6 weeks ago). I wasn't converting files to HTML or using Mif2Go, so some of my issues are not parallel, but make sure you check to ensure: - the actual font being used is installed on your system - the language is set correctly in all book files. I'm using Windows 7 Ultimate 64bit, so again, we're not apples to apples, but does XP have the option to install additional languages? I found that when I installed Chinese (Simplified, PRC), many - but not all - of my issues went away. Alison From: framers-boun...@lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Celine Deguire Sent: May 17, 2011 1:18 PM To: framers@lists.frameusers.com Subject: Chinese translation has garbage for index entries (also Mif2Go issue) Hello I'm reviewing Chinese Simplified files returned from my Chinese translator and everything is fine except for the index entries displayed as garbage in the marker dialog. In the generated index, the text appears to be Chinese after updating the book. Upon conversion to HTML Help 1.x output, the *.hhk file contains garbage characters for the index entries. The original files I sent are Framemaker 7.2 format and these were saved as MIF before sending. He translated them using Trados 2006 and returned the files again in MIF format. We are working on an English Windows XP. Upon return of the files, we attempted migrating the files to Help 1.X output using Mif2Go but the index entry output in the *.hhk file was garbage. As a test, we saved the files in FM 8.0 p277 format and the index entries were garbage (mostly question marks) in the marker dialog and generated index. As expected, after Mif2Go conversion *.hhk file shows entries as garbage. ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: Chinese translation has garbage for index entries (also Mif2Go issue)
On Tue, 17 May 2011 16:18:24 -0400, Celine Deguire celdegu...@gmail.com wrote: I'm reviewing Chinese Simplified files returned from my Chinese translator and everything is fine except for the index entries displayed as garbage in the marker dialog. That should not happen. In Frame 7.2, Simplifiesd Chinese is encoded as the double-byte code page 936, GBK. That's the same as the rest of the text encoding, so it should look like Chinese, not garbage. In the generated index, the text appears to be Chinese after updating the book. Upon conversion to HTML Help 1.x output, the *.hhk file contains garbage characters for the index entries. You need the most recent Mif2Go DLLs and EXEs, from our Dropbox site, for this to work. Since you are a registered user of Mif2Go, you can access those. (Sorry, no demo versions of them yet.) You also must have the ICU DLLs from our site. In addition, you need to make a few .ini settings not in the previous User's Guide, like: [MSHtmlHelpOptions] ; HelpFileLanguage = LCID to put in project file, default is for : US English. HelpFileLanguage = 0x804 Chinese (Simplified) [HtmlOptions] ; IndexSortType = Numeric (default, code-point order), ; Lexical (using MS strcoll functions), or ; Alpha (sort accented letters as though they are unaccented). IndexSortType=Lexical ; IndexSortLocale = language to use for sorting index. ; When IndexSortType is Lexical, default is current ; OS country setting. Uses MS language names. ;IndexSortLocale=Chinese (Simplified) As a test, we saved the files in FM 8.0 p277 format and the index entries were garbage (mostly question marks) in the marker dialog and generated index. As expected, after Mif2Go conversion *.hhk file shows entries as garbage. You may have experienced a Frame bug there. When Frame converts a pre-8.0 file to 8 or later, it converts the content to Unicode in UTF-8 encoding. However, we recently found that the index markers are not converted correctly, at least for Japanese and probably for all DBCS encodings (Chinese, Korean). Instead of converting character by character, Frame converts byte by byte, encoding each byte of each double-byte character in UTF-8 individually. This is not valid in any sense, and is not a recoverable error. You can either replace all index entries by hand with new ones *created* in Frame 8, or stay with 7 forever. We have not investigated what Frame 8+ does with index entries when saving back to FM7, but it may yield unexpected results, like the garbage you observed in the FM7 files you got back from the translator... If you could send us a page from one of the files you got back, with an index entry, in FM 7 MIF, we can look at the encoding more closely. It's easy to spot the double-encoding when you know exactly what you are looking for. HTH! -- Jeremy H. Griffith, at Omni Systems Inc. jer...@omsys.com http://www.omsys.com/ ___ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Chinese translation has garbage for index entries (also Mif2Go issue)
Hello I'm reviewing Chinese Simplified files returned from my Chinese translator and everything is fine except for the index entries displayed as garbage in the marker dialog. In the generated index, the text appears to be Chinese after updating the book. Upon conversion to HTML Help 1.x output, the *.hhk file contains garbage characters for the index entries. The original files I sent are Framemaker 7.2 format and these were saved as MIF before sending. He translated them using Trados 2006 and returned the files again in MIF format. We are working on an English Windows XP. Upon return of the files, we attempted migrating the files to Help 1.X output using Mif2Go but the index entry output in the *.hhk file was garbage. As a test, we saved the files in FM 8.0 p277 format and the index entries were garbage (mostly question marks) in the marker dialog and generated index. As expected, after Mif2Go conversion *.hhk file shows entries as garbage. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.frameusers.com/pipermail/framers/attachments/20110517/34fbb253/attachment.html>
Chinese translation has garbage for index entries (also Mif2Go issue)
I had some problems with Chinese characters on a recent FM9.0p255 translation job (6 weeks ago). I wasn't converting files to HTML or using Mif2Go, so some of my issues are not parallel, but make sure you check to ensure: - the actual font being used is installed on your system - the language is set correctly in all book files. I'm using Windows 7 Ultimate 64bit, so again, we're not apples to apples, but does XP have the option to install additional languages? I found that when I installed "Chinese (Simplified, PRC)", many - but not all - of my issues went away. Alison From: framers-bounces at lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Celine Deguire Sent: May 17, 2011 1:18 PM To: framers at lists.frameusers.com Subject: Chinese translation has garbage for index entries (also Mif2Go issue) Hello I'm reviewing Chinese Simplified files returned from my Chinese translator and everything is fine except for the index entries displayed as garbage in the marker dialog. In the generated index, the text appears to be Chinese after updating the book. Upon conversion to HTML Help 1.x output, the *.hhk file contains garbage characters for the index entries. The original files I sent are Framemaker 7.2 format and these were saved as MIF before sending. He translated them using Trados 2006 and returned the files again in MIF format. We are working on an English Windows XP. Upon return of the files, we attempted migrating the files to Help 1.X output using Mif2Go but the index entry output in the *.hhk file was garbage. As a test, we saved the files in FM 8.0 p277 format and the index entries were garbage (mostly question marks) in the marker dialog and generated index. As expected, after Mif2Go conversion *.hhk file shows entries as garbage. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.frameusers.com/pipermail/framers/attachments/20110517/8fcdd2bc/attachment.html>
Chinese translation has garbage for index entries (also Mif2Go issue)
On Tue, 17 May 2011 16:18:24 -0400, Celine Deguire wrote: >I'm reviewing Chinese Simplified files returned from my Chinese translator >and everything is fine except for the index entries displayed as garbage in >the marker dialog. That should not happen. In Frame 7.2, Simplifiesd Chinese is encoded as the double-byte code page 936, GBK. That's the same as the rest of the text encoding, so it should look like Chinese, not garbage. >In the generated index, the text appears to be Chinese >after updating the book. Upon conversion to HTML Help 1.x output, the *.hhk >file contains garbage characters for the index entries. You need the most recent Mif2Go DLLs and EXEs, from our Dropbox site, for this to work. Since you are a registered user of Mif2Go, you can access those. (Sorry, no demo versions of them yet.) You also must have the ICU DLLs from our site. In addition, you need to make a few .ini settings not in the previous User's Guide, like: [MSHtmlHelpOptions] ; HelpFileLanguage = LCID to put in project file, default is for : US English. HelpFileLanguage = 0x804 Chinese (Simplified) [HtmlOptions] ; IndexSortType = Numeric (default, code-point order), ; Lexical (using MS strcoll functions), or ; Alpha (sort accented letters as though they are unaccented). IndexSortType=Lexical ; IndexSortLocale = language to use for sorting index. ; When IndexSortType is Lexical, default is current ; OS country setting. Uses MS language names. ;IndexSortLocale=Chinese (Simplified) >As a test, we saved the files in FM 8.0 p277 format and the index entries >were garbage (mostly question marks) in the marker dialog and generated >index. As expected, after Mif2Go conversion *.hhk file shows entries as >garbage. You may have experienced a Frame bug there. When Frame converts a pre-8.0 file to 8 or later, it converts the content to Unicode in UTF-8 encoding. However, we recently found that the index markers are not converted correctly, at least for Japanese and probably for all DBCS encodings (Chinese, Korean). Instead of converting character by character, Frame converts byte by byte, encoding each byte of each double-byte character in UTF-8 individually. This is not valid in any sense, and is not a recoverable error. You can either replace all index entries by hand with new ones *created* in Frame 8, or stay with 7 forever. We have not investigated what Frame 8+ does with index entries when saving back to FM7, but it may yield unexpected results, like the garbage you observed in the FM7 files you got back from the translator... If you could send us a page from one of the files you got back, with an index entry, in FM 7 MIF, we can look at the encoding more closely. It's easy to spot the double-encoding when you know exactly what you are looking for. HTH! -- Jeremy H. Griffith, at Omni Systems Inc. http://www.omsys.com/
Frame PDF
I upgraded to FrameMaker 10 and Acrobat X. It seems that Distiller has been lost. How do I download and install distiller? Thank you. Bob Leif rleif at rleif.com office: 619 582-0437 on travel -- next part -- An HTML attachment was scrubbed... URL: <http://lists.frameusers.com/pipermail/framers/attachments/20110517/8e07ad9e/attachment.html>
