RE: Handling source files for translation to several languages
Hi Verner, You save a little money by converting the files to MIF, but it's not needed. Most LSPs will do that for you as part of the prep process. The Translator's Workbench uses the MIF files directly now and does not convert them to Word. I'm under the gun for a Friday deadline and will get back to you later on the tree structure. Cheers, Diane Gaskill = -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Andersen, Verner Engell VEA Sent: Tuesday, September 16, 2008 1:46 AM To: framers@lists.frameusers.com Subject: Handling source files for translation to several languages We are going to translate our FM books into several languages. We use unstructured Framemaker. Right now our directory structure looks as follows: Language folder - Text insets (corporate) (disclaimer, warranty, eula, terms of use) - Graphics (corporate) (logo, IVD, CE) - Text insets (product-specific) - Product manual folder - Framemaker files - PDF files - Graphics (language specific) - Graphics (product generic) Do you have a suggestion of how to handle the translation process? I know that the translators are to use a tag editor and that the files are to go into Trados. I suggest that the Framemaker files are converted to .mif and that the same folder structure is created in each language. I also suggest that we keep the same file names for graphics in all languages. How do you handle it all? Do you track changes between editions in the FM source file, use pdf comparison or a separate Word file, or something else? Do you write down each graphics which has been updated since the last edition? If you have a well-proven procdure for updating translated manuals I would be greatful. Med venlig hilsen - Best regards Verner Andersen Technical Writer Radiometer Medical ApS Phone +45 3827 3612 Fax +45 3827 2727 [EMAIL PROTECTED] Radiometer Medical ApS Akandevej 21 2700 Bronshoj Denmark Phone: +45 38 27 38 27 CVR: 27 50 91 85 This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately. ___ 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/dgcaller%40earthlink.net 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.
Handling source files for translation to several languages
We are going to translate our FM books into several languages. We use unstructured Framemaker. Right now our directory structure looks as follows: Language folder - Text insets (corporate) (disclaimer, warranty, eula, terms of use) - Graphics (corporate) (logo, IVD, CE) - Text insets (product-specific) - Product manual folder - Framemaker files - PDF files - Graphics (language specific) - Graphics (product generic) Do you have a suggestion of how to handle the translation process? I know that the translators are to use a tag editor and that the files are to go into Trados. I suggest that the Framemaker files are converted to .mif and that the same folder structure is created in each language. I also suggest that we keep the same file names for graphics in all languages. How do you handle it all? Do you track changes between editions in the FM source file, use pdf comparison or a separate Word file, or something else? Do you write down each graphics which has been updated since the last edition? If you have a well-proven procdure for updating translated manuals I would be greatful. Med venlig hilsen - Best regards Verner Andersen Technical Writer Radiometer Medical ApS Phone +45 3827 3612 Fax +45 3827 2727 verner.andersen at radiometer.dk Radiometer Medical ApS Akandevej 21 2700 Bronshoj Denmark Phone: +45 38 27 38 27 CVR: 27 50 91 85 This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.
Handling source files for translation to several languages
Hi Verner, You save a little money by converting the files to MIF, but it's not needed. Most LSPs will do that for you as part of the prep process. The Translator's Workbench uses the MIF files directly now and does not convert them to Word. I'm under the gun for a Friday deadline and will get back to you later on the tree structure. Cheers, Diane Gaskill = -Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers-bounces at lists.frameusers.com]On Behalf Of Andersen, Verner Engell VEA Sent: Tuesday, September 16, 2008 1:46 AM To: framers at lists.frameusers.com Subject: Handling source files for translation to several languages We are going to translate our FM books into several languages. We use unstructured Framemaker. Right now our directory structure looks as follows: Language folder - Text insets (corporate) (disclaimer, warranty, eula, terms of use) - Graphics (corporate) (logo, IVD, CE) - Text insets (product-specific) - Product manual folder - Framemaker files - PDF files - Graphics (language specific) - Graphics (product generic) Do you have a suggestion of how to handle the translation process? I know that the translators are to use a tag editor and that the files are to go into Trados. I suggest that the Framemaker files are converted to .mif and that the same folder structure is created in each language. I also suggest that we keep the same file names for graphics in all languages. How do you handle it all? Do you track changes between editions in the FM source file, use pdf comparison or a separate Word file, or something else? Do you write down each graphics which has been updated since the last edition? If you have a well-proven procdure for updating translated manuals I would be greatful. Med venlig hilsen - Best regards Verner Andersen Technical Writer Radiometer Medical ApS Phone +45 3827 3612 Fax +45 3827 2727 verner.andersen at radiometer.dk Radiometer Medical ApS Akandevej 21 2700 Bronshoj Denmark Phone: +45 38 27 38 27 CVR: 27 50 91 85 This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately. ___ You are currently subscribed to Framers as dgcaller at earthlink.net. Send list messages to framers at lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscribe at lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/dgcaller%40earthlink.net Send administrative questions to listadmin at frameusers.com. Visit http://www.frameusers.com/ for more resources and info.