Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

April 13, 2016, 9:47 am

≫ Next: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

≪ Previous: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

$

0

0

Forum: SDL Passolo
Topic: Passolo and TM: error when using Trados' TM after Trados update to SR2
Poster: Achim Herrmann
Post title: Explanation

Hello,

SDL Passolo is using SDL Trados Studio components to interface with TMs. The installation path of Studio is searched in the Windows registry using a GUID. Unfortunately this GUID is changing with newer SRs in Studio. So older Passolo licenses will not find newer Studio SRs which can be solved with the described work-around.

Achim Herrmann
SDL Solutions Consultant

---

Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

March 3, 2017, 1:47 am

≫ Next: Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

≪ Previous: Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

$

0

0

Forum: SDL Passolo
Topic: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional
Poster: francoisdebeck
Post title: i have the same problem

Hi

After my trial ran out(where everything worked properly), I reinstalled my recently purchased copy of Passolo 2016 professional on a different computer and now I dont seem to have the .net parser to be able to work with resx files

did you ever figure out how to fix it?

Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

April 13, 2016, 9:47 am

≫ Next: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

≪ Previous: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

$

0

0

Forum: SDL Passolo
Topic: Passolo and TM: error when using Trados' TM after Trados update to SR2
Poster: Achim Herrmann
Post title: Explanation

Hello,

SDL Passolo is using SDL Trados Studio components to interface with TMs. The installation path of Studio is searched in the Windows registry using a GUID. Unfortunately this GUID is changing with newer SRs in Studio. So older Passolo licenses will not find newer Studio SRs which can be solved with the described work-around.

Achim Herrmann
SDL Solutions Consultant

Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

March 3, 2017, 1:47 am

≫ Next: Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

≪ Previous: Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

$

0

0

Forum: SDL Passolo
Topic: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional
Poster: francoisdebeck
Post title: i have the same problem

Hi

After my trial ran out(where everything worked properly), I reinstalled my recently purchased copy of Passolo 2016 professional on a different computer and now I dont seem to have the .net parser to be able to work with resx files

did you ever figure out how to fix it?

Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

April 13, 2016, 9:47 am

≫ Next: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

≪ Previous: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

$

0

0

Forum: SDL Passolo
Topic: Passolo and TM: error when using Trados' TM after Trados update to SR2
Poster: Achim Herrmann
Post title: Explanation

Hello,

SDL Passolo is using SDL Trados Studio components to interface with TMs. The installation path of Studio is searched in the Windows registry using a GUID. Unfortunately this GUID is changing with newer SRs in Studio. So older Passolo licenses will not find newer Studio SRs which can be solved with the described work-around.

Achim Herrmann
SDL Solutions Consultant

Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

March 3, 2017, 1:47 am

≫ Next: Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

≪ Previous: Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

$

0

0

Forum: SDL Passolo
Topic: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional
Poster: francoisdebeck
Post title: i have the same problem

Hi

After my trial ran out(where everything worked properly), I reinstalled my recently purchased copy of Passolo 2016 professional on a different computer and now I dont seem to have the .net parser to be able to work with resx files

did you ever figure out how to fix it?

Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

April 13, 2016, 9:47 am

≫ Next: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

≪ Previous: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

$

0

0

Forum: SDL Passolo
Topic: Passolo and TM: error when using Trados' TM after Trados update to SR2
Poster: Achim Herrmann
Post title: Explanation

Hello,

SDL Passolo is using SDL Trados Studio components to interface with TMs. The installation path of Studio is searched in the Windows registry using a GUID. Unfortunately this GUID is changing with newer SRs in Studio. So older Passolo licenses will not find newer Studio SRs which can be solved with the described work-around.

Achim Herrmann
SDL Solutions Consultant

Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

March 3, 2017, 1:47 am

≫ Next: Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

≪ Previous: Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

$

0

0

Forum: SDL Passolo
Topic: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional
Poster: francoisdebeck
Post title: i have the same problem

Hi

After my trial ran out(where everything worked properly), I reinstalled my recently purchased copy of Passolo 2016 professional on a different computer and now I dont seem to have the .net parser to be able to work with resx files

did you ever figure out how to fix it?

---

Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

April 13, 2016, 9:47 am

≫ Next: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

≪ Previous: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

$

0

0

Forum: SDL Passolo
Topic: Passolo and TM: error when using Trados' TM after Trados update to SR2
Poster: Achim Herrmann
Post title: Explanation

Hello,

SDL Passolo is using SDL Trados Studio components to interface with TMs. The installation path of Studio is searched in the Windows registry using a GUID. Unfortunately this GUID is changing with newer SRs in Studio. So older Passolo licenses will not find newer Studio SRs which can be solved with the described work-around.

Achim Herrmann
SDL Solutions Consultant

Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

March 3, 2017, 1:47 am

≫ Next: Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

≪ Previous: Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

$

0

0

Forum: SDL Passolo
Topic: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional
Poster: francoisdebeck
Post title: i have the same problem

Hi

After my trial ran out(where everything worked properly), I reinstalled my recently purchased copy of Passolo 2016 professional on a different computer and now I dont seem to have the .net parser to be able to work with resx files

did you ever figure out how to fix it?

Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

April 13, 2016, 9:47 am

≫ Next: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

≪ Previous: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

$

0

0

Forum: SDL Passolo
Topic: Passolo and TM: error when using Trados' TM after Trados update to SR2
Poster: Achim Herrmann
Post title: Explanation

Hello,

SDL Passolo is using SDL Trados Studio components to interface with TMs. The installation path of Studio is searched in the Windows registry using a GUID. Unfortunately this GUID is changing with newer SRs in Studio. So older Passolo licenses will not find newer Studio SRs which can be solved with the described work-around.

Achim Herrmann
SDL Solutions Consultant

Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

March 3, 2017, 1:47 am

≫ Next: Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

≪ Previous: Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

$

0

0

Forum: SDL Passolo
Topic: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional
Poster: francoisdebeck
Post title: i have the same problem

Hi

After my trial ran out(where everything worked properly), I reinstalled my recently purchased copy of Passolo 2016 professional on a different computer and now I dont seem to have the .net parser to be able to work with resx files

did you ever figure out how to fix it?

Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

April 13, 2016, 9:47 am

≫ Next: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

≪ Previous: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

$

0

0

Forum: SDL Passolo
Topic: Passolo and TM: error when using Trados' TM after Trados update to SR2
Poster: Achim Herrmann
Post title: Explanation

Hello,

SDL Passolo is using SDL Trados Studio components to interface with TMs. The installation path of Studio is searched in the Windows registry using a GUID. Unfortunately this GUID is changing with newer SRs in Studio. So older Passolo licenses will not find newer Studio SRs which can be solved with the described work-around.

Achim Herrmann
SDL Solutions Consultant

Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

March 3, 2017, 1:47 am

≫ Next: Problem with Passolo and MS Word 2016 Spell checker

≪ Previous: Passolo and TM: error when using Trados' TM after Trados update to SR2 | Explanation

$

0

0

Forum: SDL Passolo
Topic: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional
Poster: francoisdebeck
Post title: i have the same problem

Hi

After my trial ran out(where everything worked properly), I reinstalled my recently purchased copy of Passolo 2016 professional on a different computer and now I dont seem to have the .net parser to be able to work with resx files

did you ever figure out how to fix it?

Problem with Passolo and MS Word 2016 Spell checker

May 28, 2017, 12:39 am

≫ Next: Passolo 2011 compatibility issues with Windows 10 | Explanation

≪ Previous: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

$

0

0

Forum: SDL Passolo
Topic: Problem with Passolo and MS Word 2016 Spell checker
Poster: Tomi Loruntuomi

Using Passolo 2016 Translator Edition I have been able to use MS Word 2010 Spell checker for spell checking translations in English-Finnish.

However, updating my Office (and Word) to the new 2016 version I get this error message:

ERROR - MS Word Spellchecker: No dictionary for this language.

The Passolo information indicates that even MSWord spell checker old versions (until Office 2000) will be compatible with Passolo. But there is no indication about compatibility with Word 2016. Is there some problem with using the new MSWord 2016 spell checking or something extra to be done? There is no other spell checker available for the Finnish language and the old Word XP versions are no more supported by Microsoft.

---

Passolo 2011 compatibility issues with Windows 10 | Explanation

April 13, 2016, 10:01 am

≫ Next: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

≪ Previous: Problem with Passolo and MS Word 2016 Spell checker

$

0

0

Forum: SDL Passolo
Topic: Passolo 2011 compatibility issues with Windows 10
Poster: Achim Herrmann
Post title: Explanation

Hello Nicolas,

This issue is not related to the operating system and can't be solved by re-installing SDL Passolo. It is also not related to SDL Passolo and is not a software bug.

SDL Passolo itself doesn't use any of these .NET GUI libraries like DevExpress, Infragistics, Telerik or others. Such .NET GUI libraries are used by the software developers of your client. They are used to create a nice a fancy interface but these libraries must be available in the localization process for SDL Passolo to correctly visualize and check the dialogs of the client software.

So these are client files and there are various options to provide you with these referenced assemblies. It is the job of the localization engineer or project manager of your client and there are easy options to automatically embed the necessary files into the bundle.

Please contact your client and ask for all referenced assemblies or ask the localization engineer of the client to change the project settings so that all referenced assemblies will be embedded into the bundle. Then it will work properly.

Achim Herrmann
SDL Solutions Consultant

Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

March 3, 2017, 1:47 am

≫ Next: Passolo 2011 compatibility issues with Windows 10 | Explanation

≪ Previous: Passolo 2011 compatibility issues with Windows 10 | Explanation

$

0

0

Forum: SDL Passolo
Topic: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional
Poster: francoisdebeck
Post title: i have the same problem

Hi

After my trial ran out(where everything worked properly), I reinstalled my recently purchased copy of Passolo 2016 professional on a different computer and now I dont seem to have the .net parser to be able to work with resx files

did you ever figure out how to fix it?

Passolo 2011 compatibility issues with Windows 10 | Explanation

April 13, 2016, 10:01 am

≫ Next: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

≪ Previous: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

$

0

0

Forum: SDL Passolo
Topic: Passolo 2011 compatibility issues with Windows 10
Poster: Achim Herrmann
Post title: Explanation

Hello Nicolas,

This issue is not related to the operating system and can't be solved by re-installing SDL Passolo. It is also not related to SDL Passolo and is not a software bug.

SDL Passolo itself doesn't use any of these .NET GUI libraries like DevExpress, Infragistics, Telerik or others. Such .NET GUI libraries are used by the software developers of your client. They are used to create a nice a fancy interface but these libraries must be available in the localization process for SDL Passolo to correctly visualize and check the dialogs of the client software.

So these are client files and there are various options to provide you with these referenced assemblies. It is the job of the localization engineer or project manager of your client and there are easy options to automatically embed the necessary files into the bundle.

Please contact your client and ask for all referenced assemblies or ask the localization engineer of the client to change the project settings so that all referenced assemblies will be embedded into the bundle. Then it will work properly.

Achim Herrmann
SDL Solutions Consultant

Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

March 3, 2017, 1:47 am

≫ Next: Passolo 2011 compatibility issues with Windows 10 | Explanation

≪ Previous: Passolo 2011 compatibility issues with Windows 10 | Explanation

$

0

0

Forum: SDL Passolo
Topic: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional
Poster: francoisdebeck
Post title: i have the same problem

Hi

After my trial ran out(where everything worked properly), I reinstalled my recently purchased copy of Passolo 2016 professional on a different computer and now I dont seem to have the .net parser to be able to work with resx files

did you ever figure out how to fix it?

Passolo 2011 compatibility issues with Windows 10 | Explanation

April 13, 2016, 10:01 am

≫ Next: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

≪ Previous: Not able to Enable Microsoft .Net Parser, Add-in with Passolo 2015 Professional | i have the same problem

$

0

0

Forum: SDL Passolo
Topic: Passolo 2011 compatibility issues with Windows 10
Poster: Achim Herrmann
Post title: Explanation

Hello Nicolas,

This issue is not related to the operating system and can't be solved by re-installing SDL Passolo. It is also not related to SDL Passolo and is not a software bug.

SDL Passolo itself doesn't use any of these .NET GUI libraries like DevExpress, Infragistics, Telerik or others. Such .NET GUI libraries are used by the software developers of your client. They are used to create a nice a fancy interface but these libraries must be available in the localization process for SDL Passolo to correctly visualize and check the dialogs of the client software.

So these are client files and there are various options to provide you with these referenced assemblies. It is the job of the localization engineer or project manager of your client and there are easy options to automatically embed the necessary files into the bundle.

Please contact your client and ask for all referenced assemblies or ask the localization engineer of the client to change the project settings so that all referenced assemblies will be embedded into the bundle. Then it will work properly.

Achim Herrmann
SDL Solutions Consultant