1. General - Recent Threads

Source/target language used in the fuzzy search (bug ?)

Philippe Noth — Sat, 18 May 2019 17:19:45 GMT

Hi everyone,

I notice a strange behaviour in Passolo 2016, which is really annoying since it slows me down.

Here the fuzzy search for a string works OK, using the source language as expected:

/resized-image/__size/1411x422/__key/communityserver-discussions-components-files/142/6177.sdl_2D00_passolo_2D00_fuzzy1.jpg

Then, as soon as I hit Ctrl-Down to go to the next segment, the fuzzy search changes to the target language and becomes useless (it searches using the pre-translated French text):

/resized-image/__size/1418x426/__key/communityserver-discussions-components-files/142/5810.sdl_2D00_passolo_2D00_fuzzy2.jpg

Is that a bug ? I can avoid that by grabbing the mouse to select the segments, but is there a solution or a better workaround?

Of course, I cannot "upgrade" to Passolo 2018 since the package is a tbulic16 file.

Philippe

RE: Source/target language used in the fuzzy search (bug ?)

Emil Meinhardt — Mon, 03 Aug 2026 10:44:59 GMT

This faulty behavior is still present in Passolo 2022. If the caret/focus is in the Target section of the Translation Window when moving to the next segment via Ctrl + Down, Passolo erroneously uses the target section's content to perform a fuzzy match. This is fine when translating untranslated (red) strings, since the target for those is populated with the source text anyway. But it makes translating fuzzy matches a chore.

For Ctrl + Down, the workaround I'm using is an AutoHotKey script that changes focus to the source before moving to the next segment, and then changes it back to the target afterward:

; Make Ctrl + Down use the Source text for fuzzy matching when going to next segment.
#IfWinActive, ahk_exe psl.exe
^Down::
#IfWinActive, ahk_exe psl16.exe
^Down::
Send, {Tab 2} ; Changes focus to Source section
Sleep, 75 ; Increase this if Passolo's UI can't keep up with the keystrokes
Send, ^{Down} ; Goes to next segment
Sleep, 75 ; Increase this if Passolo's UI can't keep up with the keystrokes
Send, {Tab}{Left} ; Changes focus back to Target section and moves caret to start of string
#IfWinActive
return

RE: Hungarian ignores 'one' pluralisation when exporting to android - but it shouldn't

Adrian Maniu — Mon, 03 Aug 2026 06:58:58 GMT

Hi Andreas Ebbert-Karroum

We had a similar issue for Warning - Ignored pluralisation form 'zero' which was caused by using the digit 0 instead of the word zero in the file.

Can you check if this is also the case on your side? This might fix the issue.

Or let me know what is the source string in the source file?

Hungarian ignores 'one' pluralisation when exporting to android - but it shouldn't

Andreas Ebbert-Karroum — Fri, 31 Jul 2026 10:21:38 GMT

We're using Passolo Team Edition 2022 to translate an Android app. When exporting the new hungarian language, there are warnings:

Generating "strings:Hungarian"
Warning - Ignored pluralisation form 'one' (line 0) because it is not supported by target language.
Warning - Ignored pluralisation form 'one' (line 0) because it is not supported by target language.
Warning - Ignored pluralisation form 'one' (line 0) because it is not supported by target language.

This is an issue, since Android supports 'one' plurals, and so should Passolo (or the android plugin), too. Also unicode itself, which passolo claims to be based upon, says that 'one' plural form should exist:
www.unicode.org/.../language_plural_rules.html

Any idea, how to handle that?

Unable to re-import translated .txt / .csv file in Passolo

Gregory Desomer — Fri, 19 Jun 2026 12:03:42 GMT

Good morning,

We seem to be having an issue with Passolo 2022:

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

The file was then fully translated and Arabic translations are visible when opening in Excel or text editor.

However, when re-importing the file back to Passolo, the import succeeds, but the translated strings are not displayed in the Translation column, it's still in English.

I have tried converting the file to different formats UTF-8, UTF-16, ... , even used concatenate to produce the exact same format as the exported file, but nothing seems to solve it.
Even replacing just 1 string in the original final, doesn't make it display when re-importing

Also tried the suggestions here, but no luck.

Anyone who can provide some further insights or assistance?

RE: Unable to re-import translated .txt / .csv file in Passolo

Achim Herrmann — Tue, 23 Jun 2026 10:08:56 GMT

The Customizable Text Export feature can be used for many use cases; while it is suitable for communicating with translators, the export settings must be configured correctly for the import to work properly. Before exporting, you need to open the Export settings and preferably use these settings. The most important setting is that the File will be reimported in PASSOLO setting is activated. This creates a header line in the export file with information that controls the import.

Try to re-export with the recommended settings, then manually insert the translations from the existing translation file.

For future translation workflows, try to use the SDXLIFF Export/Import and ask your supply chain translators whether they are able to handle this file format.

RE: ODBC Parser after update not available

Paul Tudoran — Tue, 09 Jun 2026 13:14:37 GMT

Via a remote session we found that the issue was that Passolo was licensed but not with the correct Passolo 2022 Network license.

We managed to solve the issue by resetting the license information from the server, done a reset on those licenses from our end and then activate online the Network Passolo licenses. We then checked and the ODBC Parser was working fine.

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?

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 — Wed, 03 Jun 2026 06:14:16 GMT

Manually updated the value of IsSynchronizedWithCurrentItem, the bug fixed now.

RE: ODBC Parser after update not available

Anca Stoian — Mon, 25 May 2026 06:32:26 GMT

Michael Söhn If an issue is not solved, you need to inform the technical team via email immediately, the won't keep the case open indefinitely. 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 : CS0049776.

RE: ODBC Parser after update not available

Michael Söhn — Sun, 24 May 2026 19:34:25 GMT

Hi, we're still not able to work with the Passolo 2022 . the pronlem is not solved and now a new service pack needsto be delivered, please don't close the ticket again unless it's solved.

RE: Checkbox: "Don't overwrite existing values when leveraging empty values" not working

Adrian Maniu — Mon, 11 May 2026 11:44:38 GMT

Hello,

The issue CRQ-41953 is still with the development team, but we've escalated it, and we hope to have it fixed in the near future.

Checkbox: "Don't overwrite existing values when leveraging empty values" not working

Software Entwicklung — Thu, 03 Apr 2025 15:15:14 GMT

Version: Passolo 2022 Team Unlimited Edition (Network SN)

We got 2 branches of the same software with one lpu project each

branch #1 version1.lpu
branch #2 version2.lpu

version2.lpu has all current translations, alle new features, bugfixes etc.

versio1.lpu has missing translation

e.g. : version1.lpu:

ID1	de.text1new
ID2	de.text2
ID3

ID3 is not yet present in this version1.lpu

version2.lpu

ID1	de.text1
ID2	de.text2
ID3	de.text3

Workflow:

open version2.lpu
leverage from version1 with checked checkbox: "Don't overwrite existing values when leveraging empty values"

expected result:

ID1	de.text1new
ID2	de.text2
ID3	de.text3

"real" result:

ID1	de.text1new
ID2	de.text2
ID3

Is this the right workflow for working with multiple lpu files in branches?

Screenshots:

Thank you!

RE: Checkbox: "Don't overwrite existing values when leveraging empty values" not working

Software Entwicklung — Fri, 08 May 2026 06:51:41 GMT

Are there any plans to solve this issue? We have a lot of trouble because of this!

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.