How to translate user-guide content.
-
Install VSCode: https://code.visualstudio.com/
-
Create target folder for GIT content
c:\git -
Run VSCode.
-
Clone GIT Repository
https://github.com/SuperOfficeDocs/superoffice-docs.git
- Choose target folder to contain superoffice-docs folder.
c:\git - Files and branches are now cloned locally.
When you open the target folder
c:\git\superoffice-docsin VSCode, it will automatically connect to Github. It remembers where it came from.
-
Someone at SuperOffice runs the Create-translations-branch flow on Github.
-
This creates a new branch called
Translate-Xxx-dateand a ZIP file containing the changed english files. -
Go to Actions tab on GitHub to find artifact
https://github.com/SuperOfficeDocs/superoffice-docs/actions/workflows/build-translations.yml
-
Click on the run to access the artifacts
- Download the changes zip:
- Unzip the changes and send them in for translations.
Translations happen.
Time passes...
French, Swedish, etc translations come back.
- Open VSCode
- Open the target folder
C:\git\superoffice-docs
- Click the SYNC button in the footer. This ensures that the list of branches is up to date, and contains the translation branch that was created when the ZIP file was generated.
- Click the MAIN branch in the footer to switch to the translate_xxx branch.
- Choose the
origin/Translate_xxxbranch from the list of branches
- Wait for the new branch to be copied.
- Click the SYNC button just to make sure everything is up to date.
- Drag/Drop to copy the translated files to the corresponding language folders in the target folder:
- Go back to VSCode - should now show changed files
- Double check you are on the right branch - check the footer
-
Enter a commit message
Oversettelser -
Click COMMIT button.
-
Click SYNC button
-
Open Github
-
Pick the translate branch on GitHub:
- Click the CREATE PR button (should appear automatically):
- Finished!
The changes committed to the branch can now be reviewed and merged back to main.
You can continue to make changes to the branch and push them to Github after you have created the PR.














