1. General - Recent Threads

RE: How to make Passolo create 64 bit resources (satellite assemblies)

Markus Kaußen — Wed, 08 Apr 2026 10:09:42 GMT

Thank you Adrian Maniu . We are able to create 64 bit DLLs with the provided DLL.

For our automation system, it would be create if the path to the base dll can be set via CLI or per project. Just as a suggestion.

How to make Passolo create 64 bit resources (satellite assemblies)

Carmen Vollmuth — Mon, 16 Dec 2024 14:14:05 GMT

Dear all,

I need to output target resources that are 64-bit compatible. A test run did not go too well. Apparently, putting 64 bit in does not make Passolo put 64 bit out.

After some digging, I unearthed this thread: Creating 64 bit resource DLLs with Passolo dating a few years back. Maybe this why there is no file attachement and the Passolo HMI does not offer the given options.

Maybe somebody can help?

Many thanks to the everybody dedicating their time and knowledge.

Carmen

RE: How to make Passolo create 64 bit resources (satellite assemblies)

Adrian Maniu — Fri, 03 Apr 2026 19:04:38 GMT

Hi Markus Kaußen , I've re-attached the DLL on the KB.

There is no option to create both versions at the same time. Maybe you could use different machines, one for 32 bit and one for 64 bit.

I hope this helps.

RE: How to make Passolo create 64 bit resources (satellite assemblies)

Markus Kaußen — Wed, 01 Apr 2026 14:19:26 GMT

Hi Adrian Maniu

We have the same issue (but could test with a EmptyRsc64.dll cause I do not see any attachment here and at the mentioned KB).

And we do have the same issue as Carmen Vollmuth : We need to provide 32 and 64 Bit dlls with a Passolo installation and cannot switch this setting constantly.

Any way to solve this?

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

Adrian Maniu — Fri, 27 Mar 2026 15:24:30 GMT

Hi Kan Matsuda ,

I'm not sure if you use the option to Write only changed information but this one could help in your case:

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0034416

Enabling this option writes only strings or properties that have been changed into the target file. If you do not change the property mentioned it will not be included in the target file.

If this does not help then further investigation is needed, which can be done if you raise a support case and provide sample files/Passolo project (if you have a support contract).

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?

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

Kan Matsuda — Tue, 24 Mar 2026 06:44:13 GMT

The link I referred to earlier was incorrect. The correct one should have been the link related to AutoScaleDimensions property.

I also checked this link in the Update 8 fix list.

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

Adrian Maniu — Wed, 18 Mar 2026 15:56:56 GMT

Hi Bernadette Haury

The JSON format does not specify a standard number of whitespaces to be used. Any number used it is a valid JSON file, usually two or four.

Passolo uses the two space format but any tool which processed JSON files further should identify the file as a correct one.

I'd recommend checking with your development team to support such files.

Please note that there is a request to preserve such spaces at: JSON parser - Conserving spaces as source

You're welcome to vote for this to be implemented.

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.

RE: Creating json target file with utf8 and bom

Rex Turnbull — Mon, 16 Mar 2026 12:04:25 GMT

Okay, thank you.

RE: Creating json target file with utf8 and bom

Adrian Maniu — Fri, 13 Mar 2026 12:44:42 GMT

Hi Rex Turnbull , this is how the JSON parser used to work in Passolo 2018. BOM was not written in the target file.

We addressed this for Passolo 2022 and the BOM is written in this version.
Please upgrade to Passolo 2022 for such files.

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

Adrian Maniu — Mon, 16 Feb 2026 13:19:30 GMT

Hi Tina,

This is due to the string Save from the same DLL and located in the LoggerResources:

The string Id SaveMenuItem.Header refers to the same value as the Save ID:

These strings should have the same ID, currently if you translate any of these the translation will be replicated to the second string.

But I think this was not the case in older Passolo versions (which was not ok).

Now when you update the string list in the original LPU it will take the translation of the first string.

Let me know if this clears the situation of if you require further assistance.

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 [View:/cfs-file/__key/communityserver-discussions-components-files/142/M31_5F00_138.zip:900:600]

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: [View:/cfs-file/__key/communityserver-discussions-components-files/142/Passolo-issue.zip:900:600]

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="更新">

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

Tina Han — Fri, 13 Feb 2026 01:36:44 GMT

Thanks Adrian Maniu , we'll try this method on our side.

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

Adrian Maniu — Thu, 12 Feb 2026 10:38:56 GMT

Hi Tina,

For such request please use the support system and raise a support case:

https://gateway.rws.com/csm

As for the current issue,

the value for IsSynchronizedWithCurrentItem is set as false in the More tab of the string:

It's normal in this case to write it as False.

I assume this was changed at some point in past and you can revert it back to True if this is the intended value.

Let me know if this helps or if you require further assistance.

Thanks,

Adrian Maniu

RE: ODBC Parser after update not available

Radu Boloveschi — Wed, 28 Jan 2026 07:03:22 GMT

Michael Söhn We will be pleased to help you with this problem so have logged a support case on your behalf. We do prioritise customers who have a support contract so please keep in mind it could take up to 48 hours, especially over a weekend, but rest assured we will contact you as soon as we can. You will be contacted at the email address used for this Community. Support Case Id : CS0038197.

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?

RE: ODBC Parser after update not available

Michael Söhn — Tue, 27 Jan 2026 19:56:18 GMT

Yes, the License shows the database Addin

RE: ODBC Parser after update not available

Adrian Maniu — Tue, 27 Jan 2026 16:37:59 GMT

Hi Michael Söhn , can you check if your Passolo 2022 license has the Database parser activated?

You can check this in Help > About Passolo > License tab.

The Add-in for Databases should be checked.

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

Nils Jörn — Fri, 23 Jan 2026 05:43:55 GMT

Good morning Adrian Maniu ,

thank you very much for clarifying, that either Passolo Team or Collaboration Edition are required in order to create .tbulic22 bundles. I've not been sure about that.

Best regards and have a great day.
Nils

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.

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

Adrian Maniu — Thu, 22 Jan 2026 17:45:36 GMT

Hello,

Passolo Team Edition or the Collaboration one are required in order to create .tbulic22 bundles to send to translators that use Passolo Translator edition.

You would need to upgrade Passolo to one of the above editions for this capability.

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

Nils Jörn — Thu, 22 Jan 2026 11:27:25 GMT

Hi Mandar Inamdar ,

we're using Passolo version 22.0.254.0. As Collaboration Edition. And we're still creating exports, e. g. as .tbulic22 files, for our translators with the "Export" function.
The "Export Manager" is located under the "Project" tab.

Unfortunately, I'm not sure, if and what kind of exports can be created with the Professional Edition, too. My apologies.

It could be helpful, if you'd let would add the exact version number of Passolo, which you're using.
And possibly, a screenshot of the "Project" tab, as shown below, could be helpfuul, too, if you're missing the "Export" and "Export Manager" buttons.

You could also compare the Passolo functions between the Professional and the Collaboration Edition. I'd assume, there should be an information, if and what kind of exports can be created with the Professional Edition, too.

Hopefully, these informations will help you, to solve the issue.

Best regards and have a nice day.
Nils