1 - Hitlist settings, you can change the fields to be shown here as well as the font in the view

2 - Project Termbase Settings

You can see the TB names in my screenshot, and as far as I remember it is default.

Thanks Jerzy, but … I meant the Termbase Viewer pane, rather than the Termbase Recognition pane.

Regarding point 2: what I mean is, are there two different shortcuts for quickly adding terms to two different termbases on the fly? This is possible in memoQ (and cafeTran), as you can assign a specific shortcut for quickly adding terms to any of your termbases. I usually work with two termbases active, one project-specific, and one general. As I translate, I then send new terms to either of these, depending on what type of term it is. This is very, very handy. However, it doesn't seem possible in Studio to quickly send terms to two different TBs. Only to the TB that is selected as default.

We would need a second shortcut: "Quick Add New Term to second TB" (i.e., the one with priority level 2).

Michael 

Thanks, yes, I just remembered your great post on this (http://noradiaz.blogspot.co.uk/2016/04/adding-terms-to-secondary-studio.html), which I will definitely be borrowing from as soon as I finish my current job.

Michael

Thanks for the extra info!

Hopefully the developers will add both of these features at some point. The thing about the usefulness of being able to quickly add terms to two termbases instead of one, is that you don't know how useful it is until you've tried it. Once you've tried it, it's hard to go back.

I maintain project specific glossaries for most of my clients, but also have one big one for general stuff. As I translate a job for a particular client, I will generally come across two basic kinds of terms that I would like to save for later: 1. Terms that are specific to the project, and 2. Terms that are general and might be useful elsewhere. Being able to quickly send terms to two dedicated TBs as I work means that when I finish the job, and start another one, I can just use the general TB and not attach the previous project-specific one, and instead attach yet another project specific one. I could of course solve this by just saving them all in the default TB like you do, and then at the end of each project opening MultiTerm and manually extracting some of the terms and exporting them to another TB, but this is way too much work (if even possible, because there is no way to quickly add metadata to terms when saving them, like in CafeTran). I also usually don't have time for any of this because the minute I finished one job I usually start another.

Incidentally, is there a specific place for users to propose feature requests or RFEs here at SDL?

Michael