Rigi for SDL Passolo
Rigi has developed an add-in for all Passolo editions. It can be used in various configurations.
This is the preferred solution until the cloud connector is implemented.
The source files are maintained in the workspace on the Rigi server. For details, see the Set up a workspace guide.
Passolo can synch with the project on the Rigi server. In this hybrid version, Passolo uses the same parsers as the Rigi server.
Key characteristics:
Source files are in the Rigi cloud.
Previews are in the Rigi cloud.
Passolo project synchronizes with the Rigi server.
The add-in contains all Rigi parsers.
The add-in uploads translations to the Rigi server.
For detailed instructions, see the Passolo hybrid – detailed instructions for PMs guide.
Typical workflow:
The developer:
Uploads the latest source files to the workspace and assigns the parsers.
Generates the files with Rigi tokens.
Updates the app with Rigi tokens.
Captures HTML previews.
The PM:
Downloads the rigsln file from the Workspace (source files are not needed yet).
Creates a project in Passolo (.lpu) using the .rigsln as the source file.
Updates the project. This will retrieve the source files from the workspace.
Assigns external translators, or activates the auto-login feature.
Exports Passolo translation bundles (.tbulic).
Sends the tbulic files and HTML Previews to the translators.
The translators:
Translate in context using the HTML previews from the server (the Rigi plugin is required).
Return the translated bundles.
The PM:
Imports the translated bundles.
Uploads the translations to the Rigi server.
The developer:
Generates the target files.
Imports the target files in the code repository.
Workflow extensions
The provided workflow can have variations and extensions, for example:
After the initial project setup, the PM can align the translations with the available translations in the target files (Passolo > Home > Scan Target File)
Correct the source texts on the Rigi server. For details, see the Manage the correction of source texts guide.
After the translation task, the PM can conduct a language test. When ready, the translators can apply the suggestions directly in their Passolo project.
This version works without the Rigi cloud. It is useful if your company does not allow working with cloud providers.
All files are stored locally, and the add-in comes with all available Rigi parsers.
Key characteristics:
No cloud.
Previews are stored locally.
Addin contains all Rigi parsers.
Uses the Rigi solution editor.
For detailed instructions, see this external guide: Rigi for Passolo for project managers.
Typical workflow:
The source files are available on the local disk in a folder structure.
The PM:
Uses the solution editor to define the project (.rigsln).
Creates a project in Passolo (.lpu) using the .rigsln as source file.
Updates the project.
Generates the files with Rigi tokens.
The developer or PM:
Updates the app with the Rigi tokens.
Uses Websnap (or another tool) to capture HTML Previews.
Stores the HTML Previews with the project.
The PM:
Exports Passolo translation bundles (.tbulic).
Sends the tbulic files and HTML Previews to the translators.
The translators:
Store the tbulic and HTML Previews in a local folder.
Translate in context (using the Rigi plugin)
Return the translated bundles.
The PM:
Imports the translated bundles.
Generates the target files.
The developer imports the target files into the code repository.
Workflow extensions
The provided workflow can have variations and extensions, for example:
After the initial project setup, the PM can align the translations with the available translations in the target files (Passolo > Home > Scan Target File).
After the translation task, the PM can create translation bundles and send them to in-country reviewers who can make changes.
Before the developer imports the translations into the code repository, the PM updates the project with the latest source files. The generated files will then contain also the new file identifiers.
It is possible to connect to the cloud later. Then, the translations from Passolo can be uploaded to the Rigi server, a language test can be performed, and translators can apply the corrections.
Under development
The .rigi parser for SDL Passolo is under development. The preferred use case is: Passolo hybrid described above.
The source files are maintained in the workspace on the Rigi server. For details, see the Set up a workspace guide.
Passolo can synch text files with the project on the Rigi server.
Passolo has a .rigi configuration file with the URL to the Rigi server.
Key characteristics:
Source files are in the Rigi cloud.
Previews are in the Rigi cloud.
Parsers are in the cloud.
Passolo exchanges texts with the Rigi server via API.