Yes, conditional text could be the problem. It's really hard to tell without digging into the files.
Another possibility is if you jammed all the files into a single ZIP file without maintaining the relative paths when you sent them out to the translator. By the way, how many files are there? I just checked out the MIF idea. I was a bit simplistic in my explanation, but it is workable. The biggest hurdle is understanding how MIFs handle the directory structure. I say it's hard because it looks so different. It is logical and once you see the pattern it makes sense, but looks foreign. You almost have to think of it as an HTML format for describing the path to a file. The good news is that it will tell you exactly where Frame expects to find the cross reference and you can find the cross reference target by searching the MIF version. As I expected, you can use Frame's unique ID as the search string. The hard part is deciphering the paths and fixing the problem by either changing the path in the Xref or moving the files to where Frame expects to find them. Tom Johnson Technical Writer Microline Technology Corp. [EMAIL PROTECTED] +1 231 935 1585 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brierley, Sean Sent: Wednesday, December 13, 2006 12:38 PM To: tcp@techcommpros.com Subject: Re: [TCP] broken cross references Yuk. 1) You are using relative pathing, correct, where all files live withn the same folder structure and not out on some network drive. 2) How was this translated. Is it possible the translator botched something by translating the MIF files or whatnot? Perhaps the translator deleted cross-reference markers? 3) Could there be issues with conditional text? 4) If the links worked when you sent it out, is the translator responsible for fixing the errors? They might have an easier time with the Japanese. Cheers and g'luck. Sean -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lisa M. Bronson (TCP) Sent: Wednesday, December 13, 2006 12:11 PM To: tcp@techcommpros.com Subject: [TCP] broken cross references Hi everyone, The longer I use FrameMaker (7.0 p579 on Windows XP), the more I realize I don't know about the program. I sent documents out for translation, and they came back with a number of broken cross references (~50). The only thing I know to do is to look at each corresponding cross reference in the English file, figure out what it's referencing, find the corresponding location in the Japanese, and fix the cross reference to go to that location. Since I don't speak or read Japanese, the thought of doing that 50 times is making me rather cross. :( Does anyone know a better way to fix this? If not, please send chocolate. Lisa B. ______________________________________________ Author Help files and create printed documentation with Doc-To-Help. New release adds Team Authoring Support, enhanced Web-based help technology and PDF output. Learn more at www.doctohelp.com/tcp. Are you a Help Authoring Trainer or Consultant? Let clients find you at www.HAT.Matrix.com, the searchable HAT database based on Char James-Tanny's HAT Comparison Matrix. Contact [EMAIL PROTECTED] for details. _______________________________________________ Technical Communication Professionals Post a message to the list: email [EMAIL PROTECTED] Subscribe, unsubscribe, archives, account options, list info: http://techcommpros.com/mailman/listinfo/tcp_techcommpros.com Subscribe (email): send a blank message to [EMAIL PROTECTED] Unsubscribe (email): send a blank message to [EMAIL PROTECTED] Need help? Contact [EMAIL PROTECTED] Get the TCP whole experience! http://www.techcommpros.com
