AutoSuggest Case Insensitivity, Source Segment Editing and Other SP2 Improvements

One of the first things I did this week after getting back from my summer vacation was that I installed the new SP2 that came out a couple of weeks ago. I was very happy to notice these two improvements that I (and probably everyone else as well) have been wanting to see since the version 2009:

1. The option to make AutoSuggest case-insensitive
With this improvement it doesn’t matter anymore whether your termbase entries start with an upper or lower case. You just need to go to Tools > Options > AutoSuggest and clear the check box next to the Case sensitive option (see the screen shot below).

2. The ability to edit source segments
This feature needs to be turned on first in Project Settings (see the screen shot below). After that you can enable source segment editing for the segment where your cursor is by pressing Alt+F2 (or right-click on the segment and select Edit Source). I’m not really planning to start correcting the numerous typos I see in source texts but I think the best use for this will be combining sentence fragments that are separated by erroneous hard returns (since these cannot be merged using the Merge Segments command). Note that you can’t actually delete the hard return character because it’s not visible in the source segment but you can cut & paste the segment fragments together after enabling the source segment editing.

The new SP2 has also plenty of other improvements. More information can be found in the Online Help and even more details in the SP2 Release Notes.

Advertisements

2 Responses to “AutoSuggest Case Insensitivity, Source Segment Editing and Other SP2 Improvements”

  1. Michael Schubert Says:

    I installed SP2 over a month ago (since I’m American and don’t take six-week summer vacations …), spotted the AutoSuggest case sensitivity option and thought immediately of you, Tuomas!

    Thank you for the tip on cutting and pasting segment content with the new “Edit Source” feature – I hadn’t thought of that. Unfortunately, the “Edit Source” command is enabled only for documents originating in Word, as far as I can tell, so it really only saves you the trouble of editing and re-importing the file yourself. It is not enabled for InDesign files, where I often encounter hard returns used as line wraps. And it does not let you delete the junk tags so common in PowerPoint files. But I suppose it’s better than a poke in the eye with a sharp stick.

    • Tuomas Says:

      You should take longer vacations Michael!

      You are right about the limitations of the source segment editing. The feature is available only for Word and PowerPoint files and it doesn’t let you to delete (or add) tags. As far as the junk tags in PowerPoint files go, there is an option to skip “advanced font formatting” in PPTX files (File types > PowerPoint 2007-2010 > Common). That might help to avoid some of the junk tags.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: