• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 65 subscribers
  • Views 673 views
  • Users 0 members are here
Options
Related

Can I open Passolo 2022 LPU in Passolo 2018?

Burckhardt Rueffer

The situation: We used Passolo 2018 until recently. A client (who also uses P'18) sent us an LPU that required the .NET addin which we did not have. After speaking with RWS, we were told that it is not possible to purchase that add-in any longer for the 2018 version and that we would need to upgrade to 2022.
So we did that, including the new add-in, everything worked well until we returned the LPU to the client who is not planning to upgrade.

We now have a fully completed LPU in 2022 format that our client can't open. They are not happy ...

Any suggestions on how to handle this? Is there an export or work-around?
emoji
Rate translation
×
Suggest better translation
×
Parents
  • 0

    The previous answer is correct, but of course you have to have all the source files, otherwise it won't work. However, this is not always the case.

    There is a solution based on the licensing technology. As with Trados Studio, the previous product version of Passolo (here Passolo 2018) can be started with the license of the newer version (here Passolo 2022)

    When a valid Passolo 2022 is installed on the system and you then start Passolo 2018 (latest CU), you will see the following screen.

    SDL Passolo error dialog box displaying 'Cannot find license information' with an option to 'Use 2022 License' highlighted.

    Just activate that Passolo 2018 can use the Passolo 2022 license and the problem is solved.

    Unfortunately, you missed this solution and have already converted the Passolo 2018 project to the new Passolo 2022 project format. There is no way back.

    There are certainly various solutions, but they all involve more or less additional effort. I would export the translations from the Passolo 2022 project as SDLXLIFF and then import them back into the Passolo 2018 project, complete the project in Passolo 2018 and then deliver it to the customer.
    emoji


    Generated Image Alt-Text
    [edited by: RWS Community AI at 5:54 AM (GMT 1) on 23 May 2024]
Reply
  • 0

    The previous answer is correct, but of course you have to have all the source files, otherwise it won't work. However, this is not always the case.

    There is a solution based on the licensing technology. As with Trados Studio, the previous product version of Passolo (here Passolo 2018) can be started with the license of the newer version (here Passolo 2022)

    When a valid Passolo 2022 is installed on the system and you then start Passolo 2018 (latest CU), you will see the following screen.

    SDL Passolo error dialog box displaying 'Cannot find license information' with an option to 'Use 2022 License' highlighted.

    Just activate that Passolo 2018 can use the Passolo 2022 license and the problem is solved.

    Unfortunately, you missed this solution and have already converted the Passolo 2018 project to the new Passolo 2022 project format. There is no way back.

    There are certainly various solutions, but they all involve more or less additional effort. I would export the translations from the Passolo 2022 project as SDLXLIFF and then import them back into the Passolo 2018 project, complete the project in Passolo 2018 and then deliver it to the customer.
    emoji


    Generated Image Alt-Text
    [edited by: RWS Community AI at 5:54 AM (GMT 1) on 23 May 2024]
Children
No Data