we are facing some issue with passolo 2016.
this is only for our x64 translation. it's not seen with our x86 translation.
the symptoms look very similar to the ones claimed to be fixed in CRQ-8438 for passolo 2018.
warning when generating the target file:
[x] strings did not use the translation, because the source file has changed text or coordinates
can you share some details, please?
under what exact conditions would one face CRQ-8438? and how exactly was it fixed at passolo end?
There was an issue caused by missing referenced assemblies where Passolo would add Menus items twice in the list and then throw the warning during saving the target that those Menus would not use the translation.
The issue was fixed and Passolo stores only once the Menus and no warning should be present.
Similar warnings could show if the source / target string lists have not been updated before generating the target. Please update first and then try to generate the target or verify if you can replicate the issue by creating a new project just with the strings / dlls affected.
in the meanwhile we have identified the exact conditions under which passolo 2016 shows those error symptoms:
we have an inherited form where the base form is defined in a 64-bit assembly.
there apperently is a bug in passolo 2016 which makes it fail in such a case.
this is very similar to microsoft visual studio - where such forms cannot be displayed in the "designer":
https://support.microsoft.com/en-us/topic/cannot-display-inherited-form-in-form-designer-when-base-form-defined-in-64-bit-assembly-29ca1d78-f6e6-24d3-37e2-f1d918037ebf
the workaround is to change the assembly to AnyCPU.
this is no long-term solution, of course.
we want that assembly to be pure x64. and passolo should be able to cope with it.
now the big question remains:
does passolo 2018 (plus the fix for CRQ-8438) fully support x64?
I've tried to replicate the issue from the Microsoft article but I do not get similar warning in Passolo(both 2016 or 2018).
Can you send me a sample file with the issue at amaniu@sdl.com to check it?
I was able to replicate the issue on Passolo 2018 as well, although with fewer (17) strings affected.
Is reported now to development with ID CRQ-22892 and I hope we have a fix in the near future.
I was able to replicate the issue on Passolo 2018 as well, although with fewer (17) strings affected.
Is reported now to development with ID CRQ-22892 and I hope we have a fix in the near future.
Translate
