• Replies 5 replies
  • Subscribers 367 subscribers
  • Views 2882 views
  • Users 0 members are here
Options
Related

MultiTerm Ideas

Paul

Hi,

I just had a chat with Richard Puschmann, also from our Support Team, and he had a couple of interesting ideas... one of which he has a working version of already.

  1. Enhance the editing experience and ensure you are aware you are in Edit mode.  Adaptation of the MultiTerm interface so that when you are editing terms the background colours change slowly until you save the term.  Looks something like this but changes to more colours as you stay in edit mode:


    This actually makes you think about how to skin MT for customers with their branding maybe... could be some useful skinning tools come out of this idea!
  2. Term Translator - Provide a mechanism for using Machine Translation, or TMs (perhaps), to translate the terms added to a MultiTerm termbase.  So you add a new term in the language you are working in and the rest are automatically populated… maybe with draft status.

Two great ideas... keep them coming.!

Regards

Paul

Paul Filkin | RWS Group

________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear? 
Tell us what you need in our Community Solutions Hub

Rate translation
×
Suggest better translation
×
Parents

  • Hi, Paul.

    Perhaps this may be slightly off-topic, but I had submitted an idea to the SDL Ideas site regarding not Multiterm per se, but its integration into Studio (before 2011 was released). When a translator uses multiple termbases and adds a term on the fly, that term is added to the primary termbase (the first in line). But many times this is not what translators need. Translators may want to add the term to another active termbase.

    What happened to that?

    panagiotis
  • in reply to Panagiotis Arkoudeas

    Panagiotis Arkoudeas said:

    Perhaps this may be slightly off-topic, but I had submitted an idea to the SDL Ideas site regarding not Multiterm per se, but its integration into Studio (before 2011 was released). When a translator uses multiple termbases and adds a term on the fly, that term is added to the primary termbase (the first in line). But many times this is not what translators need. Translators may want to add the term to another active termbase.

     
    A nice idea indeed... one I have seen a few users asking for.  Quite useful when you have a couple of termbases, but maybe a little clunky as the number goes up.  This would be core Studio functionality really and not anything for the OpenExchange... I think.
     
    Regards
     
    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Reply
  • in reply to Panagiotis Arkoudeas

    Panagiotis Arkoudeas said:

    Perhaps this may be slightly off-topic, but I had submitted an idea to the SDL Ideas site regarding not Multiterm per se, but its integration into Studio (before 2011 was released). When a translator uses multiple termbases and adds a term on the fly, that term is added to the primary termbase (the first in line). But many times this is not what translators need. Translators may want to add the term to another active termbase.

     
    A nice idea indeed... one I have seen a few users asking for.  Quite useful when you have a couple of termbases, but maybe a little clunky as the number goes up.  This would be core Studio functionality really and not anything for the OpenExchange... I think.
     
    Regards
     
    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Children
  • in reply to Paul

    Hello all,

    My idea is, in general, to enhance editor tools of MT.

    For example, it would be great to see:

    1. Batch delete of duplicates whichever language pair they are encounered in. I use a 6-lingual termbase compiled from 6 different bilingual ones, and I say editing it to wipe out all the duplicates and merge 3-4 bilingual terms into a single 5-lingual one is a real hell, if we use built-in MT tools, provided the total number of entries is about 60K or more (though some of them are not complete with all the 6 languages).
    2. SImplified customization of interface view (fonts, colours and so on). They could obviously be placed onto the main toolbar as buttons but they are in the depths of menus and numerous wizards instead.

    That seems to be all for now.

    Hope more new ideas to come. 
  • in reply to santonov

    Hi,

    All sound very good ideas... but don't forget that this is a forum for OpenExchange Development and not MultiTerm Development per se.  Unless of course you have some ideas here to develop an application yourself to do this?  I think we're all ears if this is the case ;-)

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub