NOTE: To prepare a Weblate translation. Once a project has been created, under users, "review" must be set to enabled. Once that is done, all translations marked in XLIFF as approved will be imported as "approved". "Approved" status seems to be part of the function of the database in Weblate and selected behaviors as much as it is a part of the XLIFF model.
-
Go to: https://translations.artefactual.com/projects/atom/25/#repository
-
Commit and push remaining commits to atom/translations.
-
Permissions or ownership seem to affect when we can commit to, and push a Weblate translation. An instinct is that this is related to the way Docker is configured based on my interaction with Docker-compose in the Archivematica project where what is written to a mounted directory from the container will have different ownership than one might expect, especially. as Docker needs to be in a
su -
group to run.-
NOTE: Folder permissions: 0755 [ubuntu:ubuntu]
-
NOTE: File permissions: 0664 [ubuntu:ubuntu]
-
-
-
Update atom branches
-
Update atom-translations branches
-
from
.../.../atom-translations
-->cp -R i18n/ .../.../atom/apps/qubit
- NOTE: Could this be made a submodule of the AtoM project to reduce the hoops?
-
Commit 2.5.x final translations.
- NOTE: we should lock translations at this point. Or soon after, relative to when we do this for real.
-
Run phing i18n-translations
- NOTE: does this recipe need updating to only look at apps/qubit?
-
Commit
apps/quibit/i18n directory/
-
Switch to atom-translations 2.6.x branch.
-
from
.../.../atom/apps/qubit
-->cp -R .../.../atom-translations
-
Commit translations.
-
Approve translations:
../weblate-migration-scripts/scripts/approve i18n
-
NOTE: Approval output:
Attempting to approve XLIFF files in directories in i18n... Cycled through 47 XLIFF files. Done: approved 1174 XLIFF translation units.
-
-
Import new components into AtoM project in Weblate.
- NB. not yet done. Have imported as a secondary project for review: https://translations.artefactual.com/projects/atom-26-test/
And we should be good to go! If the test branch looks okay, we can import this as a new component to AtoM and lock down the 2.5 branch.