No matter which termbase I try to open -- even the sample ones included in the SDL software -- I get an error message which translates into "There is an invalid character in the given coding. Row 1, position 25."
This is extremely annoying, since I certainly don't want to go through each and every termbase to correct this (even if I knew what the error is, which of course I do not). Since all these termbases worked fine with MT 2015, the error must be with MT 2017. What should I do?
Mats
I have the exact same problem. Termbase created with MultiTerm 2017 opens fine in MultiTerm. After adding anything to it through Studio (2017), MultiTerm can't open it anymore but gives this error:
Invalid character in the given encoding. Line 1, position 25.
Type System.Xml.XmlException, System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Stacktrace
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
at System.Xml.XmlTextReaderImpl.InvalidCharRecovery(Int32& bytesCount, Int32& charsCount)
at System.Xml.XmlTextReaderImpl.GetChars(Int32 maxCharsCount)
at System.Xml.XmlTextReaderImpl.ReadData()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.Load(String filename)
at Sdl.MultiTerm.Studio.Catalogue.LoadObjectDialog.FillDialog(String location)
at Sdl.MultiTerm.Studio.Catalogue.LoadObjectDialog.cmdBrowse_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
This is super annoying and completely breaks my workflow!
Even the sample termbase from Studio 2015 (...\Documents\Studio 2015\Projects\Samples\SampleProject\Termbase\Printer.sdltb) gives this error, if that is any help for the developers. I never touched that file since installing Studio 015.
Please make a support case for me too by the way.
I have the exact same problem. Termbase created with MultiTerm 2017 opens fine in MultiTerm. After adding anything to it through Studio (2017), MultiTerm can't open it anymore but gives this error:
Invalid character in the given encoding. Line 1, position 25.
Type System.Xml.XmlException, System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Stacktrace
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
at System.Xml.XmlTextReaderImpl.InvalidCharRecovery(Int32& bytesCount, Int32& charsCount)
at System.Xml.XmlTextReaderImpl.GetChars(Int32 maxCharsCount)
at System.Xml.XmlTextReaderImpl.ReadData()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.Load(String filename)
at Sdl.MultiTerm.Studio.Catalogue.LoadObjectDialog.FillDialog(String location)
at Sdl.MultiTerm.Studio.Catalogue.LoadObjectDialog.cmdBrowse_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
This is super annoying and completely breaks my workflow!
Even the sample termbase from Studio 2015 (...\Documents\Studio 2015\Projects\Samples\SampleProject\Termbase\Printer.sdltb) gives this error, if that is any help for the developers. I never touched that file since installing Studio 015.
Please make a support case for me too by the way.
Translate
