This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
Hi, one of my translators had an issue with a FrameMaker book, the Index section.
Apparently FrameMaker Index doesn't get automatically populated when the target language is Japanese, the index needs to be populated automatically.
Is there a fix/patch that can make index creation for JA as automated as with European Languages? Thanks! Laura
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Olaf (X) Local time: 22:45 English to German
You'll need to provide additional information
Mar 28, 2008
Did you use S-Tagger? Did your translators add sort order string tags to index entries that start with Kanji entries? Did your DTP specialist try to create a brand-new index? etc.
Olaf
[Edited at 2008-03-28 16:12]
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Hi Olaf, Stagger was used. No sort order tags were introduced. And the DTP Specialist didn't try to create a new index order.
I am just aware that FM has a problem often times with languages like Japanese because the index markers can only work with 255 characters so I was wondering if there was an obvious solutions or patch to this or if we'' have to manually solve the problem after translating each book.
Thanks for your input!
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Olaf (X) Local time: 22:45 English to German
Several things could have gone wrong
Mar 29, 2008
This could be either a Trados issue or a FrameMaker issue. AFAIK, FM supports only 255 characters for single-byte languages and 127 characters for double-byte languages, and index entries that are too long will cause problems. (S-Tagger usually displays conversion warnings if it finds very long index entries.)
You may want to open some of the translated Japanese FrameMaker chapters in FM and generate a stand-alone index (Special > Standard Index > Set). If you can gener... See more
This could be either a Trados issue or a FrameMaker issue. AFAIK, FM supports only 255 characters for single-byte languages and 127 characters for double-byte languages, and index entries that are too long will cause problems. (S-Tagger usually displays conversion warnings if it finds very long index entries.)
You may want to open some of the translated Japanese FrameMaker chapters in FM and generate a stand-alone index (Special > Standard Index > Set). If you can generate index entries from each chapter file without any problems you'll probably need to re-create the FM index file from scratch using settings appropriate for Japanese documents.
BTW, you mentioned that your translators didn't add <:so> tags and sort order strings. This means that even if you manage to fix the other issues, the index entries will not be sorted correctly, unless the index contains only Kana or Latin characters.
Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.
Exclusive discount for ProZ.com users!
Save over 13% when purchasing Wordfast Pro through ProZ.com. Wordfast is the world's #1 provider of platform-independent Translation Memory software. Consistently ranked the most user-friendly and highest value