Project

General

Profile

Feature #11763

Feature #10034: Translation web platform

Feature #15085: Document our translation platform infrastructure

Adjust contributors documentation for translators

Added by u over 2 years ago. Updated 1 day ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Internationalization
Target version:
Start date:
06/11/2018
Due date:
% Done:

100%

QA Check:
Feature Branch:
Type of work:
Contributors documentation
Blueprint:
Starter:
Affected tool:

Description

You'll need to test how everything works and while doing that, document all your steps in our translation documentation. You might want to create a new mdwn file for that.


Subtasks

Feature #15080: Integrate the staging website with the interfaceConfirmeddrebs

Bug #15649: Make sure users / translators know that they are visiting the staging wiki when they doRejecteddrebs


Related issues

Related to Tails - Bug #13286: Review current documentation of the translation platform Resolved 06/30/2017

History

#1 Updated by mercedes508 over 2 years ago

  • Category set to Internationalization
  • Status changed from New to Confirmed

#2 Updated by intrigeri over 2 years ago

  • Category changed from Internationalization to Infrastructure

(i18n is not l10n)

#3 Updated by intrigeri over 2 years ago

  • Assignee set to emmapeel

(Setting the same assignee as the parent ticket. Please set a more adequate one if I guessed wrong :)

#4 Updated by u almost 2 years ago

  • Related to Bug #13286: Review current documentation of the translation platform added

#5 Updated by u over 1 year ago

  • Category changed from Infrastructure to Internationalization
  • Assignee changed from emmapeel to spriver
  • Target version set to Tails_3.8
  • Start date deleted (09/03/2016)

#6 Updated by u over 1 year ago

  • Subject changed from Document how to use the future translation platform for translators to Adjust contributors documentation for translators
  • Parent task changed from #10034 to #15085

#8 Updated by u over 1 year ago

  • Description updated (diff)

#9 Updated by emmapeel over 1 year ago

For 'languages translated with Git', you can add this trick to review new changes in weblate:

Reviewing translation platform output
--------------------------------------

For languages like fr, fa, de, or it, that are part of tails master repo, you can get the files to review and submit to tails-l10n:


git remote add translations https://translate.tails.boum.org/git/tails/index/
git checkout tails/master
find . -name '*.fa.po' -exec git checkout translations/master --  {} \;
git reset *


And you will have all the changes to farsi (*.fa.po) to review. The same goes for the other languages.

#10 Updated by u about 1 year ago

  • Assignee changed from spriver to drebs

spriver is afk it seems. Reassigning to drebs who would be willing to work on this. @spriver: if you want to take back this ticket, please talk to me :)

@drebs: emmapeel will do the review, once you're done, you can reassign this to her and mark as "Ready for QA".

#11 Updated by u 12 months ago

Some notes on this:

- I think we want to create a dedicated page in wiki/src/contribute/how/translate/with_translation_platform.mdwn
- we need info on how to connect, how to get an account
- how to make a suggestion, how to accept or review a translation
- how to ask for a new language to be added (I think we should not add too many languages, because we will carry all PO files around with us, and this will become heavy if people start to translate one single page to a rare language. There should be a real interest in having a new language)
- where can they see their translations (staging wiki)
- how to vote, how to delete a suggestion
- explain to people when their language will be activated on the main site (point to this part of the doc on wiki/src/contribute/how/translate)
- how to get in contact when they experience technical problems
- suggest they work in a team
- suggest they create a glossary
- how to use weblate itself and it's translation memory
- link their questions to tails-l10n
- eventually link to the blueprint for people who want to know more about our setup (although this blueprint needs some love and is currently lagging behind)
- other things?

#12 Updated by intrigeri 11 months ago

  • Target version changed from Tails_3.8 to Tails_3.9

#13 Updated by emmapeel 11 months ago

I suggest to enlist the help of the Italian translator's team, as they are planning to start using weblate now so they could test the docs with a fresh mind.

#14 Updated by intrigeri 9 months ago

  • Target version changed from Tails_3.9 to Tails_3.10.1

#15 Updated by intrigeri 7 months ago

  • Target version changed from Tails_3.10.1 to Tails_3.11

#16 Updated by CyrilBrulebois 5 months ago

  • Target version changed from Tails_3.11 to Tails_3.12

#17 Updated by anonym 4 months ago

  • Target version changed from Tails_3.12 to Tails_3.13

#18 Updated by u 4 months ago

  • Status changed from Confirmed to In Progress

#19 Updated by u 3 months ago

  • Assignee changed from drebs to u
  • QA Check set to Ready for QA

#20 Updated by u 2 months ago

  • Assignee changed from u to drebs
  • QA Check deleted (Ready for QA)

@drebs: thanks for your work! I did an initial review & provided feedback and a branch by email to you today. I'll let you implement the missing bits whenever you see fits. hefee and intrigeri will have a sprint at the end of June, so you can work on it whenever you want. But as there is not much left to be done, I'm also happy if we can close this chapter sooner :)

#21 Updated by CyrilBrulebois 2 months ago

  • Target version changed from Tails_3.13 to Tails_3.14

#22 Updated by CyrilBrulebois 1 day ago

  • Target version changed from Tails_3.14 to Tails_3.15

Also available in: Atom PDF