tag:blogger.com,1999:blog-20155610.post2498515257262844829..comments2024-03-06T02:46:19.929+00:00Comments on Translation Tribulations: memoQuickie: footnote, cross-reference & index entry segmentation in Microsoft Word filesKevin Lossnerhttp://www.blogger.com/profile/14727800526216764023noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-20155610.post-24393545591179241642012-06-20T09:19:13.396+01:002012-06-20T09:19:13.396+01:00Hi Kevin,
Thanks for the clear overview.
I wasn&...Hi Kevin,<br /><br />Thanks for the clear overview.<br /><br />I wasn't aware that Studio had such a clear way of indicating what the tags actually are. memoQ inline tags would benefit from something like this. Perhaps Kilgray should add a third option to the show tags button:<br /><br />Show Short Inline Tags, Show Medium Inline Tags, Show Filtered Inline Tags, Show Long Inline Tags, Show Human Readable Tags?<br /><br />MichaelMichael Beijerhttp://wordbook.nl/noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-25240922140095252312012-06-18T11:52:17.126+01:002012-06-18T11:52:17.126+01:00Hi Kevin,
Interesting comparisons as always. An ...Hi Kevin,<br /><br />Interesting comparisons as always. An interesting point to note is that with both TagEditor and Studio the tags are just placeholders (which can be autoreplaced as needed – so you will always get 100% matches for the main segment even if the content of the index entry changes) and the content of the index entry will always be in a separate segment after the paragraph they belong to. So you can always go back to the paragraph for context, and you get good reuse as the index entry text is put into an extra (short) segment which then can be leveraged against the TM.<br /><br />Thanks for adding the Studio 2011 images too.<br /><br />Regards<br /><br />PaulPaul Filkinhttp://www.sdl.comnoreply@blogger.com