Project Settings vs. Tools > Options – What’s the Difference?

I think one of the most confusing aspects in Studio is the way the basic settings are selected. Even some of the more experienced users have difficulties with this, not to mention those who are just starting to use Studio. Every time I train new individual users or teach workshops I think that I should write down the rules and exceptions and create a few screenshots not just to help me to explain the differences/similarities between Projects Settings and Tools > Options settings but also to help the students to see how these settings are connected. Believe it or not, there’s actually some “logic” in the settings, and understanding the logic will make it easier to find the right settings.

This ended up being a much longer article than I had planned, so if my explanations below are too much for you, see at least the summary at the end and the screenshots. That would be a good start.

Project settings

You can access Project settings in every Studio view via the Project menu (Project > Project Settings) and also in the Editor view via the Project Settings button which is above the Translation Results window. Project settings apply only to the active (current) project. Whatever you change here, won’t affect any of the future or other existing projects. (Note that “project” here refers to both “standard Studio projects” [= using the New Project command] and “single file projects” [= using the Open Document command] .) That’s quite simple and straightforward. However, there are two additional things to remember about project settings:

1. File Types: Most of the File Type settings control the conversion and extraction of source files to the SDLXLIFF format, for example whether comments, hidden text, worksheet names etc. are translated or how PDF files are converted, or how elements and attributes are handled in html files. In most cases the default settings work fine and you don’t need to worry about changing these settings. However, if any of these need to be changed it has to be done before the source file is converted (i.e. opened in Studio for the first time), otherwise they don’t have any effect. If you are creating a “single file project” you do this in the Open Document dialog box by selecting the Advanced button to access the File Type settings (see Figure 1 below).If you are creating a “standard Studio project” you do this on the Project Files page of the New Project wizard by clicking the File Types button (see Figure 2 below).

Note that when you select the Advanced button to access the File Type settings in the above example, it will take you to the Project Template Settings dialog box (which looks almost exactly like the Project Settings dialog box). Everything you change here will actually stay as part of your default project template and will affect all future projects unless you change the setting later in the Project Template Settings dialog box or in the Options dialog box. I’m not explaining the Project Template concept here but you can find more info about it here. Utilizing the templates can help you to streamline the process of creating projects, particularly if you have similar projects frequently.

OpenDoc_Advanced

Figure 1. Accessing File Type settings via the Open Document dialog box when creating a single file project.

NewProj_FileTypes

Figure 2. Accessing File Type settings via the Project Files page when creating a standard Studio project.

So, what can you do if you have already created a project and then notice that you should have changed File Type settings? If you are working on a “standard Studio project” and need to change the settings, go to the Project Settings (> File Types), change the needed settings, and add the file again to the project (you might need to delete the previous file first or rename your new file in order to be able to add it to the project). Adding files to an existing project is another less than intuitive process but you can find the instructions here.  If you are working on a “single file project” and need to change the settings, you would need to create the project again and remember to change the settings when you are in the Open Document dialog box (Figure 1).

2. Language Pairs: The other source of confusion in Project Settings is the various language pairs listed under Language Pairs (see Figure 3). You should have there “All Language Pairs” and then at least one additional language pair. The settings under All Language Pairs are basically general settings that apply to all the language pairs of a project. If you want to change these settings independently for specific language pairs you would do it under the language pair in question. This way you could, for example, use different minimum match values or translation memory fields for different language pairs. However, since most of us are working with a single language pair per project, it’s simpler if you just make all the changes directly to the settings under your language pair (i.e. not the All Language Pairs option). That way you can be sure that they will take effect. Note, however, that the settings on the Translation Memory and Automated Translation page (i.e. TMs and their usage, such as Lookup, Concordance, etc.) can only be changed under All Language Pairs (they are grayed out under the individual language pairs). In addition, as you can see in Figure 3, Termbase settings are selected under All Language Pairs (because termbases are multilingual), and Auto-substitution and AutoSuggest Dictionaries settings are selected under each specific language pair only (because they are language-specific).

I could throw in a couple of other exceptions here but I’m going to spare you from that, and I’m not going to explain what happens if you have selected the Use different translation providers for this language pair option.

More info about Language Pair settings can be found here.

ProjSettings_LangPairs

Figure 3. Comparison of settings under “All Language Pairs” and an individual language pair in Project Settings.


Tools > Options settings

The Options dialog box looks very much like the Project Settings dialog box which can be confusing but there are some clear differences when you look at them more closely. The Options dialog box navigation tree includes 12 setting categories. Three of them (File Types, Verification and Language Pairs) are the same as in the Project Settings dialog box. These are marked in Figure 4 with a blue frame. However, the difference is that if you change any of the settings under these three items in the Options dialog box, the changes will affect only your future projects – they do not have any effect on your current project. If you want the changes to apply to your current project you need to make the changes via the Project Settings page, as explained earlier. All the other nine items (i.e. Editor, AutoSuggest, Default Task Sequence, Translation Memories View, Colors, Keyboard Shortcuts, Automatic Updates, Home View, and Java Runtime Engine Startup) are NOT on the Project Settings page (as you can see in Figure 4) and will take effect immediately when you click OK, and will stay in effect until you change them. In other words, they will affect your active project as well as all future and past projects.

projsetting_toolsoptions - Copy

Figure 4. Comparison of Project Settings and Options settings. Identical parts are marked with a blue frame.


Summary

Confusing? Yes, but the short version of all this is actually quite simple:

1. Project Settings affect only your active project.
2. The three “shared” items in Tools > Options dialog box (File Types, Verification and Language Pairs) affect only future projects. These are your “global” settings for future projects. See Figure 4.
3. The other nine items in Tools > Options dialog box affect active, past and future projects. They are not really project settings but affect other, more general preferences, such as font sizes, color, spell checker, keyboard shortcuts, etc. that control how Studio functions, regardless of any project-specific settings.

When you add the language pairs to the mixture, it gets a bit more confusing:

1. Memories and their usage (Lookup, Concordance, etc.) are selected under All Language Pairs.
2. If you are working with just one language pair, it’s simpler if you make all the other TM-related changes (i.e. Search, Penalties, Filters and Update) under your language pair (rather than under All Language Pairs).
3. Termbase settings are selected under All Language Pairs (because termbases are multilingual). See Figure 3.
4. Auto-substitution and AutoSuggest Dictionaries settings are selected under each specific language pair (because they are language-specific). See Figure 3.

And some of the File Type settings add their own dimension to this confusion as well:

1. Most of the File Type settings control how source files are extracted and converted to the SDLXLIFF format, so if you want to change the conversion you need to change the settings accordingly beforehand. It’s too late after the file has already been converted (i.e. opened in Studio).


Still unsure about all this?

1. Go to Tools > Options. Review all the settings and change them so that they would be the most useful “global settings” for your work in general.  For example: Editor > Spelling, Font Adaptation, Auto-propagation, Languages; Verification > QA Checker 3.0; Language Pairs > All Language Pairs > Translation Memory and Automated Translation and select the TMs that you usually want to use. All the Editor settings will take effect immediately and the Verification and Language Pairs settings will take effect when you create the next project (single-file or standard).

2. If you need to modify any of the Verification or Language Pairs settings for an individual project, do that via the Project Settings dialog box.

//

Advertisements