Cannot load glossary file. "Invalid character in coding"....

I've switched to MultiTerm 2024 recently. Now i cannot load an existing database file in the administration/management area. Ir get the following error message:

Screenshot showing the MultiTerm 2024 interface with a dialog box titled 'Termbase aus Datei laden' and an error message in German stating 'Ungultiges Zeichen in der angegebenen Codierung. Zeile 1, Position 25.'

"Invalid character in defined coding. Line 1 position 25..."

I can still open the file in the "Terms" view and edit entries there. I tried to open the file in ultraedit or similar to find the character but that doesn't work. 

So where does this error come from and how can I solve it? 

Thanks :) 

yve



Generated Image Alt-Text
[edited by: RWS Community AI at 3:01 PM (GMT 1) on 3 Jul 2025]
emoji
  • Probability score: 0.6  

    Question improvement suggestion: Provide the exact version of MultiTerm you are using and any specific steps you have already taken to troubleshoot the issue.  

    In the meantime, based on the information you have provided, here is a suggested answer to your question:  

    Hello yve,  

    It sounds like you're encountering an issue with loading your glossary file in MultiTerm 2024 due to an "Invalid character in coding" error. Here are some steps you can take to troubleshoot and potentially resolve this issue:  

    **Step 1:** Check for Special Characters  

    - Open the termbase definition file (.xdt) in a text editor like Notepad++. Look for any special characters that may not be allowed in the file. The error message you received should indicate the position of the invalid character.  

    **Step 2:** Rename the Termbase  

    - If your termbase name contains special characters, consider renaming it to remove those characters. You can do this in the MultiTerm Administrator view by right-clicking on the termbase and selecting Edit.  

    **Step 3:** Recreate the Termbase  

    - If the issue persists, you may need to recreate the termbase. Ensure that you avoid using special characters in the name during the creation process.  

    **Step 4:** Import Data Correctly  

    - When importing data, make sure to use a custom import definition and select the "Allow over-complete entries" option. This will help ensure that entries with content in removed sub-fields are still imported.  

    **Step 5:** Check for Updates  

    - Ensure that your version of MultiTerm is up to date. Sometimes, issues are resolved in newer releases.  

    If these steps do not resolve the issue, please provide additional details about the exact version of MultiTerm you are using and any troubleshooting steps you have already taken. This will help in providing a more tailored solution.  

    I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

    RWS Community AI

    emoji
  • If this is still causing you grief, one thing you can try is just re-creating the termbase with the new version of MultiTerm. To do so, do a full export of the termbase from the older Multiterm version and then create a new termbase in Desktop 2024. You can even base the settings on the old one (including catalog items for Export, Import, etc.) during the creation process. Import the export file with all your terms and you're finished. Hope this helps!

    emoji