1. General - Recent Threads

Properti related to .NET forms class is unexpectedly being included in the satellite assemblies.

Kan Matsuda — Tue, 24 Mar 2026 06:33:03 GMT

We are implementing our code using C# and the .NET Framework.
This property has been implemented within the .resx files for a long time, and our forms have been created based on that.

After generating satellite assemblies using Passolo 2022 Update 7, layout issues began to appear in certain language environments—issues that did not occur previously.

During our investigation, we found that satellite assemblies created with an earlier version of Passolo 2022 (unfortunately, we no longer remember the exact version) did not include any information related to the property mentioned above.

However, starting from Passolo 2022 Update 7, the satellite assemblies began to include information related to this property, and this appears to be the direct cause of the layout issues.

We would like to prevent this property from being included in the satellite assemblies.
Is there any solution for this?

We have already tried the following:

Checked Tools → Add‑ins → .NET Parser settings and added the property to Excluded Properties.
Checked File → Options → Leverage.

If there are any other methods, we would appreciate your advice.

Additionally, in the Passolo Update 8 fix list, we found the following item:

“Fixed an issue where a .NET target dialog was too large in an earlier beta build.
Dialog sizes now better match the source file, preventing inconsistencies. (CRQ‑42672)”

Could this issue be related to our problem?

Indentation in json files decreases when generating target file in Passolo 2022, making the build fail

Bernadette Haury — Fri, 13 Mar 2026 09:19:50 GMT

When generating the target files for .json files translated in Passolo, the tool seems to decrease the indentation in the file. Development has strict rules about file formatting, and this indentation change made by Passolo makes the build fail, and development needs to manually reformat the files to match their format.

They expect 4 spaces indentation, and the tool is putting 2. Each time we retranslate the same file, it looks as if the entire file was translated for the first time, and the entire file changes in formatting.

Why does Passolo change the indentation in the target file, where normally, the target file should be generated with the exact formatting as the source file?

For the project management and target file creation, we are using the Passolo 2022 Team Edition Version 22.0.246.0

Creating json target file with utf8 and bom

Rex Turnbull — Mon, 09 Mar 2026 13:41:09 GMT

In a Passolo 2018 project we have some new json files, encoded in utf8 with bom (byte order mark). We are looking for a setting to get this encoding in the translated target files. They currently appear as json in utf8 without a bom.

It must be possible, because we have a different json file (in the project for a few years) for which the target is written as json utf8 with bom. Perhaps there is a way to copy these settings? Have checked the help for project settings, target rules, configuring JSON add-in...

Thankful for any tips.

The translations for the strings have changed after updating the files using Passolo 248

Tina Han — Thu, 12 Feb 2026 08:19:15 GMT

We updated the LPU from version M31_130 to M31_138. Both the source and target files have some changes, including one string translation that changed from “上書き保存” to “保存”.

Translation List - Autodesk.iLogic.UI.dll:Japanese (Japan)
(144) String "SaveMenuItem.Header" in BAML "logger/logwindow.baml" Text Save

Please help investigate the cause.

Thanks.

The M31_138 source file, old LPU, new LPU can be found in uat.community.rws.com/.../M31_5F00_138.zip

Passolo changed values in .NET files that should not have been changed during file generation

Tina Han — Thu, 05 Feb 2026 08:01:29 GMT

source file--InvAIRLookContent.dll

target file--InvAIRLookContent.resources.dll

This file includes a value named `IsSynchronizedWithCurrentItem`, defined as `true` in the source file. We did not process this value in Passolo, only translating the strings within the file. However, during file generation, this value changed to `false`, causing an issue in our product:[INVGEN-81390] WWL:GLOB: Update button doesn't work in Chinese simply build - Autodesk, Inc. JIRA
We processed files in 12 localized languages using Passolo, and only the CHS files have this issue—all others worked fine.
This problem has existed for several years. I'm currently using Passolo version is 22.0.248.0.
I've attached the complete source files, LPU, the CHS file(have issue), and the JPN file(no issue) here: uat.community.rws.com/.../Passolo-issue.zip

Please help check this issue.

Thanks

English Source (Correct):

<inv:InvFlowRibbonSplitButton x:Uid="inv:InvFlowRibbonSplitButton_2"
Id="AppUpdateCmd" Text="Update" IsSplit="True"
IsSynchronizedWithCurrentItem="True"   
ShowText="False" Size="Standard" IsVisible="True" ToolTip="Update">

Chinese Localized DLL (Incorrect):

<inv:InvFlowRibbonSplitButton x:Uid="inv:InvFlowRibbonSplitButton_2"
    adw:RibbonItem.Id="AppUpdateCmd" adw:RibbonItem.Text="更新"
    adw:RibbonListButton.IsSplit="True"
    adw:RibbonListButton.IsSynchronizedWithCurrentItem="False"   < !{}(WRONG){} >
    adw:RibbonItem.ShowText="False" adw:RibbonItem.Size="Standard"
    adw:RibbonItem.IsVisible="True" adw:RibbonItem.ToolTip="更新">

ODBC Parser after update not available

Michael Söhn — Sun, 25 Jan 2026 20:40:23 GMT

I just updated from Passolo 2018 to Passolo 2022. We're translating projects using the odbc database parser. After converting a project to 2022, The odbc Parser.has an error status."Function not available"
In Passolo 2018 it is still available. Anyone an idea how to activate the odbc parser?

How to create a translator-compatible package (tublic22 )?

Mandar Inamdar — Thu, 22 Jan 2026 11:04:20 GMT

Hello,

We are currently using SDL Passolo 2022 – Professional Edition and have created a localization package that we need to share with a translator.

In older Passolo versions, we were able to create translator bundles using formats like .tbulc11 via the Export Manager. However, in Passolo 2022, we are unable to find an option to generate a translator-compatible package in a similar format (for example, .tublic22,).

Could you please clarify:

What is the correct translator-compatible package format in Passolo 2022?
Is there an equivalent to the old Export Manager / tbulc bundles in Passolo 2022?
What format should be shared with a translator using Passolo Translator Edition 2022?

Any guidance or best practices for sharing Passolo 2022 projects with translators would be highly appreciated.

Passolo 2022 does not recognize USB dongle license

Christian Heinz — Thu, 08 Jan 2026 12:04:04 GMT

Hello,

I am trying to use Passolo 2022 with a USB dongle license. It was working without any issues until yesterday, but as of today Passolo no longer recognizes the USB dongle.

When I start Passolo, it searches for a license but cannot find one. The USB dongle is visible in the Device Manager and is correctly recognized by Windows.

I have already tried using other clients and reinstalling Passolo. I also downloaded and installed the latest version of Passolo as well as the latest USB dongle drivers. In my account, I can see the license, and it does not have an expiration date. The last activation date was 05/01/2023.

Does the dongle need to be reactivated? How can I check the license stored on the dongle? Is there anything else I can try?

Thank you.

Passolo yml parser cannot generate empty line with right Indentation

rene cui — Wed, 07 Jan 2026 03:40:50 GMT

Hi team,
When I use passolo to generate yml file, passolo add some spaces to empty line 1037(left side is source, right side is target). Please check image blow.

Passolo version I used:

Attached lpu and source/target files.Could you help to check it? Thanks a lot.
1-6-26-passolo-parser.zip

When will Passolo 2022 support .NET 10.0 source assemblies

Tom Pascouche — Tue, 18 Nov 2025 14:12:22 GMT

.NET 10.0 was released on November 11, 2025. It is critical for us that Passolo support .NET 10.0 for translation.

I was previously in some Passolo Beta forums which mentioned .NET 10.0 support upcoming, but I have mysteriously lost access.

When will Passolo 2022 support .NET 10.0 source assemblies for translation?

I am currently using Passolo 2022 Team Edition 22.0.246.0

Transfer Passolo settings from one computer to next

Rex Turnbull — Wed, 22 Oct 2025 13:00:58 GMT

We recently transferred our Passolo 2018 (and license) from an older to a Windows 11 computer. Unfortunately, we did not transfer the application settings at the same time (a note in the lisence migration guide would be helpful docs.rws.com/.../moving-single-user-license-to-another-computer-via-internet-587365 ) and have run into some issues getting the new installation to work. In the File>Options dialog there is a possibility to export/import these settings.

Is there any way to get these settings from the old computer without transferring the license back and forth?

Thank you!

Android Parser adds CDATA to export and breaks our builds

Christian Becker — Mon, 20 Oct 2025 07:37:14 GMT

Hi There,

while using Passolo 2022 for our Android App translation, it destroys our workflow as it adds CDATA annotations to the output.

The following is a valid string resource (according to documentation https://developer.android.com/guide/topics/resources/string-resource):

<string name="ValidFrom"><b>Valid from:</b> %s</string>

But export creates the following:

<string name="ValidFrom"><![CDATA[<b>Valid from:</b> %s]]></string>

How can we disable the CDATA annotation?

Bests
Chris

How to only save translated strings to target files?

Christian Becker — Mon, 13 Oct 2025 07:36:24 GMT

Hello community,

we are building our resources in a way, that only the translated strings are present in the resource files. All non-translated strings are only in an overall resource file.

How can I tell Passolo 2022 to only export the translated strings (Android)?

Bests

Chris

Import existing Android translation resources into Passolo 2022

Christian Becker — Thu, 11 Sep 2025 10:59:16 GMT

Hi There,

I'm new to Passolo 2022. I need to prepare the translation package for our Android App. There are already some strings translated and I wan't to import them.

We have f.e.

values/strings.xml
values-de-rAT/strings.xml
values-de-rDE/strings.xml

When I import all 3 files Passolo does not recognize that they belong together. How can I import existing translations?

Bests
Christian

Imported Arabic translations not displaying in Passolo

Gregory Desomer — Fri, 05 Sep 2025 08:59:48 GMT

Good morning,

We seem to be having a new issue with Passolo:

We have added Arabic as one of our application's supported languages. I have exported the source strings using the export manager in Passolo. I used the 'Customizable text export' to produce a .csv file.

The file was fully translated and Arabic translations are visible when opening in Excel (UTF-8 with BOM):

However, when importing the translated file back into Passolo, the translated strings are displayed as question marks in Passolo:

I have searched through the RWS knowledge center, but did not find any recent related topics (except this one, from 7 years ago... https://sdl.service-now.com/csm?id=kb_article_view&sysparm_article=KB0029493 [sdl.service-now.com]).

Do you have any idea what could be going wrong here? Are there any settings I need to adjust?

Passolo 2016 stopped translating all languages

Ed Hartford — Fri, 15 Aug 2025 17:47:04 GMT

We have be running Passolo 2016 with TFS. It has been running on multiple projects for years. Without changes, we stopped getting fully translated dlls for some languages (11 of 25). Re-running the build did not fix the problem. Could this a known issue with 2016? Someone mentioned clearing the history in the LPU could be the issue. This seems to fix the issue, but we want to confirm this is the issue and not a random problem.

Passolo keeps crashing while localisation

Anita Nagy — Wed, 06 Aug 2025 11:11:27 GMT

I am working on localisation in mulitiple languages, and Passolo is crashing without saving my changes, even though I did save them before. No error message appears, explaining what's the problem.

We are using Passolo 2022.

Usually, we have these problems when working in Homeoffice via VPN because our Passolo projects are not stored locally, they are stored on a server. But this time I am in the office and I even tried working on a local copy of the project I am working on. But the problem remains.

Localization bug of Passolo itself: Filter menu.

nbb1967 nbb1967 — Wed, 09 Jul 2025 14:31:30 GMT

Passolo reads Filter menu strings from user settings file, not from localized program resources.

The user settings file (%UserProfile%\AppData\Roaming\Trados\Passolo 2022\filters.dat) is created once and is not recreated when switching interface languages.

Fig. 1 shows the transition from English Passolo interface to German: the Filter menu items remain in English.
If you manually delete the filters.dat file in the user profile, the settings file is recreated from the localized German template (Fig. 2).
Fig. 3. The result of direct editing of the user settings file, proving that the interface strings are taken from the settings file and not from localized resources.

Passolo does not find translatable strings in XAML file

Susanne Aldridge — Tue, 17 Jun 2025 13:56:57 GMT

We have been asked to translate XAML files, but Passolo cannot find translatable strings and shows: "There are no translatable strings in this resource".

The content of the file looks like this:

I read through a couple of related posts for BAML, and the suggested solution was to make sure the file contains the x:Uid

I believe my file contains x:Uid so I am wondering why it does not work. My translatable strings of this test file should be "Close", "Update Databases" and "Automatic Updates:"

Any ideas what is going wrong here?

Thanks
Susanne

Passolo Machine Translate using LanguageWeaver

Mark Owens — Tue, 27 May 2025 12:25:21 GMT

Hi,

We have a LW licence - TEAM Yearly subscription.

I want to use it to translate a project in Passolo Team 2018.

I downloaded and installed the "Auto Translation" Add-in - v18.0.178.0

I ensured the add-in is loaded.

When I setup the Add-in I login using the same user/password credentials as I use to access my LW account via a browser.

I used "Edit Settings" to ensure the language pairs I want are enabled.

When performing a Pretranslate, I ensure the settings for Pretranslate has the "allow automatic translation" checkbox ticked.

When the PT ends, it has not performed a MT, nor has it reported anything in the messages window.

Can someone show me where I'm going wrong?

Thanks

Mark

Delete a folder from a project

Edoardo Belfiglio — Fri, 16 May 2025 12:07:50 GMT

hello

I want to delete a folder as shown in the picture, how do I do that?

psl.exe gets removed as a result of update to ver. 22.0.239.0

Vassily Buryanau — Thu, 08 May 2025 19:36:03 GMT

The version of Passolo installed on my computer was 22.0.207.0 when I was prompted to update it to ver. 22.0.239.0, so that was what I did. As a result, the psl.exe file got removed from the program folder. I uninstalled Passolo ver. 22.0.239.0 and tried to install version 22.0.207.0 to the same location, but I got an error saying that the files could not be installed to that folder possibly due to a permissions related problem. Personally, I do not think the error message was correct because I ran Passolo2022.exe as an administrator. I started installing version 22.0.207.0 to a new location, and I got a different error saying that the shortcut to the psl.exe file could not be created. Since the file did get installed, I created the shortcut myself. The program seems to be working fine, but I do not risk to install the 22.0.239.0 update any more.

I wonder if anyone has encountered the same or similar problem with the 22.0.239.0 update, and if there is a way to avoid it.

Type initializer error in Passolo Translator 2022

Bernadette Haury — Thu, 08 May 2025 07:32:59 GMT

Last Wednesday, I've installed the latest update for Passolo Translator 2022 and am now on version 22.0.239.0. Since yesterday, I'm getting an error each time trying to validate a string:

ERROR - Error when saving translations in TM UI_1_EN-DE. Info: The type initializer for “Sdl.LanguagePlatform.TranslationMemoryImpl.FGA.StorageBasedAlignableCorpusId” has caused an exception.
ERROR - Error when saving translations in TM UI_2_EN-DE. Info: The type initializer for “Sdl.LanguagePlatform.TranslationMemoryImpl.FGA.StorageBasedAlignableCorpusId” has caused an exception.
Warning - The TM cannot be updated! To save translations, activate the “Update” option in the TM settings.
Warning - The TM is deactivated! To save translations, activate the TM in the add-in settings.

Checking the Translation Memory Setup, the respective TMs are greyed out. I'm enabling the TM again, but when validating a string, I'm getting the same error again.

Any idea how this issue could be resolved? Thanks!

HTML Parser - displaying extra information in the string list

Mark Owens — Tue, 06 May 2025 08:02:37 GMT

Hi,

I have a Passolo 2018 project which contains what I call HTML "big files". Passolo treats these big files as HTML files (using the standard HTML parser) but are in fact a concatenation of thousands of individual HTML files.

This method has served me well over the many years I've been using it.

Here's a sample:

<?xml version="1.0" encoding="UTF-8"?>
<FILES>
<FILE name="P:/help/file1.htm">
<html>
<head>
<title>Panoramica di cronologia saldi</title>
</head>
<body>
<h1 class="ref">Panoramica di cronologia saldi</h1>
</body>
</html>
</FILE>
<FILE name="P:/help/file2.htm">
<html>
<head>
<title>Modifica della visualizzazione di riepilogo conto</title>
</head>
<body>
<h1 class="task">Modifica della visualizzazione di riepilogo conto</h1>
</body>
</html>
</FILE>
</FILES>

I now have a requirement to be able to associate a specific translation with a specific file. E.g. "Modifica della visualizzazione di riepilogo conto" belongs to "P:/help/file2.htm"

Does anyone know of a method whereby the FILE name attribute value could be somehow displayed when the string list is opened for translation?

Regards

Mark

text parser setup for JS files

Tim Roberts — Tue, 29 Apr 2025 15:28:37 GMT

I have a JS file with strings. Here is the format:

const UntranslatedStrings = {

actual_level: "Actual Level",

add: "add",

add_layer: "Add Layer",

add_timer: "Add Timer",

adjust_f1: (what) => `Adjust ${what}`,

admin_configuration: "Admin Configuration",

}

I can create a string rule to get the strings in between "" but it is missing the adjust_f1: (what) => `Adjust ${what}`, line.

Also I can't get to bring in the identifiers. So for add: "add", I get the add, but the ID comes in as 3 for example.

I have tried to use Regular Expressions in setup, but no luck.

Thanks,

Tim