Glossary Converterで Excel ファイル(.xlsx)からMultiTerm Termbase (.sdltb)に変換できなくなりました。

起動すると以下のメッセージが表示されます。

 

「Can’t detect MultiTerm, using Xdt/xml as termbase format instead」

 

おそらくらMultiTerm 2017 SR 1にアップデートしたあたりから使えなくなりました。

 

以下、使用しているのソフトウェアのバージョンです。

SDL MultiTerm 2017 SR1 - 14.2.7.43908

SDL Trados Studio 2017 SR1 - 14.1.10015.44945

Glossary Converter version 5.1.6860.15775

Excel 2013



同じような質問をされている方もいらっしゃるようですが解決できません。

どなたか解決策を教えていただければ助かります。

どうぞよろしくお願いいたします。

 

7 Replies Latest Replies: 10 Jan 2019 7:39 AM by Paul < 1   2  >
  • Hello

    The core Studio development team and the Glossary Converter developer are investigating this at the moment because it appears as though the latest updates in SR1 for 2017 and 2019 have broken the Glossary Converter.

    The workaround is to use MultiTerm Convert... the old fashioned way! This video is a little old but gives a quick example of how to use it if you're not familiar:

    https://youtu.be/d96s9o2N3xw
  • In reply to Paul:

    Paul,

    Any progress on this matter? It would be great if Glossary Converter could be integrated into MultiTerm as a standard feature.
    The old fashioned way is just too inefficient.

    Tak
  • In reply to Takayuki Osato:

    Hello  

    Takayuki Osato
    Any progress on this matter?

    Very little I'm afraid.  We have a couple of solutions that works for some but not for others so you can try these and see if it helps:

    1. Copy the file "log4net.dll" from the location C:\Program Files (x86)\SDL\SDL MultiTerm\MultiTerm15 to C:\Program Files (x86)\Common Files\SDL\MultiTerm15
    2. Download a Beta version from here - http://www.cerebus.de/glossaryconverter/downloads/GlossaryConverterProgramOnly.5.2.6947.beta.zip - which is just the zipped files and not a proper installer.  So unzip into your program folder for the converter and run the application.

    We have found that the first one helped a few users; the second one helped a couple of others.  Unfortunately from the several dozen users the developer shared this with only 4 responded so we're very short of feedback and have still not managed to find the real solution for all users.

    So if you try these and one works, please let us know.

    Takayuki Osato
    It would be great if Glossary Converter could be integrated into MultiTerm as a standard feature.

    It doesn't belong to us, and in many ways I like it better as a standalone external application.  Faster turnaround for bug fixing (normally... but this time it's not the developers fault), easier to implement new features.

  • In reply to Paul:

    Hello

    I am just adding my feedback regarding this issue:
    (Feedback has already been given in SDL community and also to the developer Mr. Gerhard Kordmann)


    Step 1.: Copying the log4net.dll file did not help resolve the error.
    Step 2: replacing the original folder with the contents of beta version of glossary converter.
    I am able to use the glossary converter (beta) successfully.

    Please Note:
    All these steps DID NOT help to run the regular version of Glossary converter 5.1.6860.

    Thank you always for your prompt guidance and help in this forum and I am always thankful so much to you!

    Have a nice day!
  • In reply to Paul:

    Hi Paul,

    I have figured out that when you get this error there is a problem with Settings.xml file in c:\ProgramData\SDL\Sdl.MultiTerm.Tools.GlossaryConverter\5.1.6860.15775 folder. When you open it, it's simply empty, so you need to copy and paste this line to Settings.xml file and save it. Command line below:

    <?xml version="1.0"?><settings><key name="MultiTerm\ServerDatabaseInfo"><value name="(default)"></value></key></settings>
< 1   2  >
Related