https://community.rws.com/product-groups/trados-portfolio/passolo/Welcome to the Passolo User Forumen-USTelligent Community 12 Non-Productionhttps://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/55922/how-to-make-passolo-create-64-bit-resources-satellite-assemblies/192725Wed, 08 Apr 2026 10:09:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:b52eadc5-fdfe-4647-baac-4113e056a01aMarkus KaußenThank 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.https://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/55922/how-to-make-passolo-create-64-bit-resources-satellite-assemblies/192676Fri, 03 Apr 2026 19:04:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:bf8caae7-e467-4c21-9552-115acfe65394Adrian ManiuHi 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.https://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/55922/how-to-make-passolo-create-64-bit-resources-satellite-assemblies/192617Wed, 01 Apr 2026 14:19:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:2fba9c0c-3475-4455-b4b9-026ec8c8bc43Markus KaußenHi 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?https://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/60685/properti-related-to-net-forms-class-is-unexpectedly-being-included-in-the-satellite-assemblies/192479Fri, 27 Mar 2026 15:24:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:6d662a65-4334-45de-9894-5349bf42c8deAdrian ManiuHi 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).https://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/60685/properti-related-to-net-forms-class-is-unexpectedly-being-included-in-the-satellite-assemblies/192256Tue, 24 Mar 2026 06:44:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:3de8bc67-3c3c-4a98-b8c2-38e88f50fceeKan MatsudaThe 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.https://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/60685/properti-related-to-net-forms-class-is-unexpectedly-being-included-in-the-satellite-assembliesTue, 24 Mar 2026 06:33:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:294225d4-fc4f-4fa7-bfdf-7bf67f8907e4Kan MatsudaWe 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?Passolo 2022https://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/60575/indentation-in-json-files-decreases-when-generating-target-file-in-passolo-2022-making-the-build-fail/192077Wed, 18 Mar 2026 15:56:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:f5c513d5-db13-493a-980c-32d6207db045Adrian ManiuHi 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.https://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/60544/creating-json-target-file-with-utf8-and-bom/191959Mon, 16 Mar 2026 12:04:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:f475eda2-d6f0-4a9c-b553-6d87148efaebRex TurnbullOkay, thank you.https://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/60544/creating-json-target-file-with-utf8-and-bom/191925Fri, 13 Mar 2026 12:44:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:c24836ae-eeab-426d-8f0b-8eb5d0bda182Adrian ManiuHi 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.https://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/60575/indentation-in-json-files-decreases-when-generating-target-file-in-passolo-2022-making-the-build-failFri, 13 Mar 2026 09:19:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:8dc834b3-be4e-426e-b2d9-1d45f2f10771Bernadette HauryWhen 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.0https://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/60544/creating-json-target-file-with-utf8-and-bomMon, 09 Mar 2026 13:41:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:cb46837d-2b46-4742-aba8-014d602dd286Rex TurnbullIn 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.https://community.rws.com/product-groups/trados-portfolio/passolo/f/object-model/60371/how-to-change-the-virtual-folder-path/191592Thu, 26 Feb 2026 13:36:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:4be98ee6-4f64-4881-8a44-dbdc09a7694fAdrian ManiuHi Gavin Lambert , currently the Virtual folder path is read only and cannot be changed. We have a request CRQ-43623 for the dev team to implement a way to change the Virtual Folder Path and I hope it will be included in the near future. Thanks, Adrian Maniuhttps://community.rws.com/product-groups/trados-portfolio/passolo/f/object-model/60371/how-to-change-the-virtual-folder-pathTue, 17 Feb 2026 04:06:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:5d17f83d-b47c-443c-a443-6c67423e43e6Gavin LambertI am currently using Passolo 2022 22.0.254.0. Once I have obtained an IPslSourceList, I can read the current Virtual Folder Path via the VirtualFolderPath property, but attempts to write to this property fail: ERROR: System.Runtime.InteropServices.COMException (0x0000F18D): Unable to write read-only property. at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams) at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Object[] aArgs, Boolean[] aArgsIsByRef, Int32[] aArgsWrapperTypes, Type[] aArgsTypes, Type retType) at PassoloU.IPslSourceList.set_VirtualFolderPath(String) Is this a bug? Writes to other properties succeed. If this is intended, is there an alternative method for moving a source list to a different virtual folder?Passolo 2022AutomationPassolohttps://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/60337/the-translations-for-the-strings-have-changed-after-updating-the-files-using-passolo-248/191269Mon, 16 Feb 2026 13:19:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:213a8f72-b05c-4943-aa76-8eee42b469b2Adrian ManiuHi 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.https://community.rws.com/product-groups/trados-portfolio/passolo/f/object-model/60269/how-to-set-the-filter-settings-for-translation-list-example-untranslated/191243Fri, 13 Feb 2026 17:39:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:2a45aa2b-34c7-44f0-a024-1319d5e260baAchim HerrmannAs Adrian mentioned, switching the filter is a function that can only be done by users from the UI. You can potentionally circumvent the problem by just sending some keys after you opened all the translation lists by macro. This will then look like SendKeys "^L" ,1 SendKeys "%S" ,1 SendKeys "{Tab}{Tab} " ,1 SendKeys "{Enter}"https://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/60276/passolo-changed-values-in-net-files-that-should-not-have-been-changed-during-file-generation/191217Fri, 13 Feb 2026 01:36:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:49fcf355-5dac-41c8-a197-578ff524e722Tina HanThanks Adrian Maniu , we'll try this method on our side.https://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/60276/passolo-changed-values-in-net-files-that-should-not-have-been-changed-during-file-generation/191212Thu, 12 Feb 2026 10:38:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:6fa26c44-50ea-46f2-ae25-a926ee3ad05cAdrian ManiuHi 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 IsSynchronizedWithCurrent Item 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 Maniuhttps://community.rws.com/product-groups/trados-portfolio/passolo/f/object-model/60269/how-to-set-the-filter-settings-for-translation-list-example-untranslated/191211Thu, 12 Feb 2026 10:10:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:5d5a661e-1be5-4ccd-9ff5-4d3815fbd813Adrian ManiuHi Daniel Masson , maybe you can check if the https://docs.rws.com/en-US/passolo-automation-957276/passoloapp-onfiltertransstring-456122 helps you. Also please confirm what is the end goal of this. You can just change the filter from the UI: Automating just the change of the filter seems to not help too much. Thanks, Adrian Maniuhttps://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/60337/the-translations-for-the-strings-have-changed-after-updating-the-files-using-passolo-248Thu, 12 Feb 2026 08:19:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:7715b780-d2fb-44d4-bd4c-1357aa3f84feTina HanWe 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 community.rws.com/.../M31_5F00_138.ziphttps://community.rws.com/product-groups/trados-portfolio/passolo/f/passolo-general/60276/passolo-changed-values-in-net-files-that-should-not-have-been-changed-during-file-generationThu, 05 Feb 2026 08:01:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:2f87df14-2ee4-4e1b-940a-59c00be1c6d0Tina Hansource 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: community.rws.com/.../Passolo-issue.zip Please help check this issue. Thanks English Source (Correct): ShowText="False" Size="Standard" IsVisible="True" ToolTip="Update"> Chinese Localized DLL (Incorrect): adw:RibbonItem.ShowText="False" adw:RibbonItem.Size="Standard" adw:RibbonItem.IsVisible="True" adw:RibbonItem.ToolTip="更新">