localization/tickets
7
3
Fork 1
Code Issues 11 Projects Wiki Activity Actions

Archive silverblue and kinoite translations #70

New issue
Open
opened 2026-06-20 10:02:05 +00:00 by peartown · 3 comments
peartown commented 2026-06-20 10:02:05 +00:00
Owner
Copy link

localization-docs/silverblue and localization-docs/kinoite repos are not used anymore.
Replaced by localization-docs/atomic-desktops.

They could be archived or read-only in order to retain an access to the translation memory.

localization-docs/silverblue and localization-docs/kinoite repos are not used anymore. Replaced by localization-docs/atomic-desktops. They could be archived or read-only in order to retain an access to the translation memory.
peartown commented 2026-07-02 06:49:34 +00:00
Author
Owner
Copy link

So, my plan is to:

  • create again translation projects for the two repos in Weblate in order to generate their translation memory,
  • store the memory in shared TM (sitewide),
  • download the TM files of the projects and ideally save them to their respective localization-docs repos
  • remove the translation projects from Weblate
  • archive the localization-docs repos.

If their translation memory will be also removed from the shared TM after the projects are removed in Weblate, I can try to upload the TM files in administration.

Do you have better idea/way how to preserve the translation memory? I'd like to know. ;)

So, my plan is to: - create again translation projects for the two repos in Weblate in order to generate their translation memory, - store the memory in shared TM (sitewide), - download the TM files of the projects and ideally save them to their respective localization-docs repos - remove the translation projects from Weblate - archive the localization-docs repos. If their translation memory will be also removed from the shared TM after the projects are removed in Weblate, I can try to upload the TM files in administration. Do you have better idea/way how to preserve the translation memory? I'd like to know. ;)
peartown commented 2026-07-02 19:42:04 +00:00
Author
Owner
Copy link

Fedora-kinoite, translation project created, TM files downloaded and added to localization-docs repo, which is now archived.

I am not sure how to learn if translation memory stays in the shared translation memory in Weblate when the project is removed/deleted (probably it is removed also).

Fedora-kinoite, translation project created, TM files downloaded and added to localization-docs repo, which is now archived. I am not sure how to learn if translation memory stays in the shared translation memory in Weblate when the project is removed/deleted (probably it is removed also).
peartown commented 2026-07-04 20:13:41 +00:00
Author
Owner
Copy link

Fedora-silverblue, translation project created, TM files downloaded and added to localization-docs repo, which is now archived.

And I am now sure deleting a project from Weblate means deleting its translation memory from the instance's shared translation memory (sitewide).

I can think of these options:

  1. Let projects stay in Weblate, probably in 'locked for translations' state.
  2. Remove projects from Weblate, upload the TM file as uploaded shared entries (Administration -> Translation memory -> Import translation memory -> Upload)
  3. Remove project form Weblate - the traslation memory is removed too, save TM file(s) in the localizatin-docs repo (before removal).

Option 1:
There will be a mix of used and unused translation projects in Weblate.
Translation memory is preserved and available for translations.
There is probably a need for developing a way how to easily differentiate (by translators) between used and unused translation projects.

Option 2:
Translation memory is preserved and available for translations.
Translation memories of unused projects are clearly separated from 'live' shared entries in Weblate administration.
There is no need to differentiate between used/unused projects for translators.

Option 3:
Translation memory is preserved only in a (archived) localization-docs repo, not available for translations in Weblate.
Only used projects are in Weblate.

I somewhat disregard another option when a translator can upload TM file in to his/her/its/their list of translation memories, or using the TM files in 'off-line' translation tools.

My order of preference:

  • option 2
  • option 1
  • option 3

Do you have other ideas and/or what is your preference?

Fedora-silverblue, translation project created, TM files downloaded and added to localization-docs repo, which is now archived. And I am now sure deleting a project from Weblate means deleting its translation memory from the instance's shared translation memory (sitewide). I can think of these options: 1. Let projects stay in Weblate, probably in 'locked for translations' state. 2. Remove projects from Weblate, upload the TM file as uploaded shared entries (Administration -> Translation memory -> Import translation memory -> Upload) 3. Remove project form Weblate - the traslation memory is removed too, save TM file(s) in the localizatin-docs repo (before removal). Option 1: There will be a mix of used and unused translation projects in Weblate. Translation memory is preserved and available for translations. There is probably a need for developing a way how to easily differentiate (by translators) between used and unused translation projects. Option 2: Translation memory is preserved and available for translations. Translation memories of unused projects are clearly separated from 'live' shared entries in Weblate administration. There is no need to differentiate between used/unused projects for translators. Option 3: Translation memory is preserved only in a (archived) localization-docs repo, not available for translations in Weblate. Only used projects are in Weblate. I somewhat disregard another option when a translator can upload TM file in to his/her/its/their list of translation memories, or using the TM files in 'off-line' translation tools. My order of preference: - option 2 - option 1 - option 3 Do you have other ideas and/or what is your preference?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
localization/tickets#70
No description provided.