This is the preferred solution until the cloud connector is implemented.

The source files are maintained in the workspace on the Rigi server.

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

1. Source files in the Rigi cloud.
2. Previews in the Rigi cloud.
   
3. Passolo project synchronizes with Rigi server.
4. Addin contains all Rigi parsers.
   
5. Addin uploads translations to the Rigi server.
   

Detailed instructions including screenshots.

Workflow

1. The developer
   
1. uploads the latest source files to the workspace and assigns the parsers.
2. generates the files with Rigi tokens.
   
3. updates the app with Rigi tokens.
   
4. captures HTML Previews.
2. The project manager (PM)
   
1. first time:
   
1. downloads the rigsln file from the Workspace (source files are not needed yet).
   
2. creates a project in Passolo (.lpu) using the .rigsln as source file.
2. updates the project. This will retrieve the source files from the workspace.
   
1. assigns external translators, or activates the auto-login feature.
3. exports Passolo translation bundles (.tbulic)
   
4. sends the tbulic files and HTML Previews to the translators.
3. The translators
   
1. translate in-context (using the Rigi plugin), where the HTML Previews from the server are shown.
2. return the translated bundles.
4. The PM
   
1. imports the translated bundles.
   
2. uploads the translations to the Rigi server.
5. The developer
   
1. generates the target files.
2. imports the target files in the code-repository.
   

Workflow extensions

1. After the initial project setup, the PM can align the translations with the available translations in the target files (Passolo > Home > Scan Target File)
2. Correct the source texts on the Rigi server.
3. After the translation task, the PM can conduct a language test. When ready, the translators can apply the suggestions directly in their Passolo project.
   

Passolo standalone

Key characteristics

1. No cloud.
2. Previews are stored locally.
   
3. Addin contains all Rigi parsers.
4. Rigi solution editor.
   

Detailed instructions including screenshots.

Workflow

1. The project manager (PM)
   
1. uses the solution editor to define the project (.rigsln)
   
2. creates a project in Passolo (.lpu) using the .rigsln as source file.
   
3. updates the project.
   
4. generates the files with Rigi tokens.
2. The developer and/or PM
   
1. updates the app with the Rigi tokens
   
2. uses Websnap (or another tool) to capture HTML Previews.
   
3. stores the HTML Previews with the project.
   
3. The PM
   
1. exports Passolo translation bundles (.tbulic)
   
2. sends the tbulic files and HTML Previews to the translators.
4. The translators
   
1. store the tbulic and HTML Previews to a local folder
2. translate in-context (using the Rigi plugin)
   
3. return the translated bundles
5. The PM
   
1. imports the translated bundles
   
2. generates the target files.
   
6. The developer
   
1. imports the target files in the code-repository.

Workflow extensions

1. After the initial project setup, the PM can align the translations with the available translations in the target files (Passolo > Home > Scan Target File)
2. After the translation task, the PM can create translation bundles and send them to in-country reviewers who can make changes.
   
3. Before the developer imports the translations in the code repository, the PM updates the project with the latest source files. The generated files will then contain also the new file identifiers.
   
4. It is possible to connect the cloud at a later moment. It is then possible to upload the translations from Passolo to the Rigi server, perform a language test, and let the translators apply the corrections.

Cloud connector

Under development
The .rigi parser for SDL Passolo is under development.
The preferred use case is: Passolo hybrid

The source files are maintained in the workspace on the Rigi server.

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

1. Source files in the Rigi cloud.
2. Previews in the Rigi cloud.
   
3. Parsers in the cloud.
4. Passolo exchanges texts with the Rigi server via API.