Feature #7024

Better documentation for translators

Added by Anonymous 2014-04-05 12:11:27 . Updated 2014-05-06 19:13:01 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Internationalization
Target version:
Start date:
2014-04-05
Due date:
% Done:

20%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

The website lacks some detailed information on how to set up a working environment.


Subtasks


History

#1 Updated by intrigeri 2014-04-05 12:17:57

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

#2 Updated by Anonymous 2014-04-07 08:59:14

I was wondering, shall i create a new page “Translating with Git”?
Or shall i add the documentation to this page: https://tails.boum.org/contribute/how/translate/?
This page seems a bit too specific / too developer oriented.

What is your opinion on this?

#3 Updated by Anonymous 2014-04-07 08:59:43

I was wondering, shall i create a new page “Translating with Git”?
Or shall i add the documentation to this page: https://tails.boum.org/contribute/how/translate/?
This page (https://tails.boum.org/contribute/git/) seems a bit too specific / too developer oriented.

What is your opinion on this?

#4 Updated by intrigeri 2014-04-07 09:11:08

> I was wondering, shall i create a new page “Translating with Git”?

I think so, yes. But perhaps sajolida has better ideas about it.

#5 Updated by sajolida 2014-04-10 10:51:24

If the documentation specific to translating Tails using Git keeps growing, yes, I think it is useful to have all the info in a single page. The current /contribute/how/translate will also gets simplified by factoring everything related to translating with Git into a dedicated page.

Another issue I see on this page is that the “Translate this website into a new language” is not structurally related to translating using Git, even if it is the only possible way at the moment. So why could improve that in the same move maybe.

#6 Updated by Anonymous 2014-04-11 00:56:50

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10

ok, thanks for the input.

I thought i could maybe improve and reorganize the “Workflow” part of the documentation too, but i have some questions:
* is the rest of the documentation up-to-date?
* the files in the po folder, which are also on Transifex, how are they treated? are translations from Transifex used at all and merged into the devel branch? are there files which are pushed from the devel branch to Transifex? I would just like to make that clearer.

Would one of the mailing lists be a better place to ask these questions?

#7 Updated by intrigeri 2014-04-11 08:47:49

> * is the rest of the documentation up-to-date?

I think so.

> * the files in the po folder, which are also on Transifex, how are they treated?
> are translations from Transifex used at all and merged into the devel branch?

For languages that don’t have a translation team that takes care of it
via Git (that is, every language but French, currently), yes.

> are there files which are pushed from the devel branch to Transifex? I would just
> like to make that clearer.

No, translation work happening in Git is not sync’d to Transifex.

#8 Updated by Anonymous 2014-04-16 11:11:00

  • % Done changed from 10 to 20

This needs review, see tails-dev.

#9 Updated by intrigeri 2014-04-16 12:17:47

  • Assignee set to sajolida
  • QA Check set to Ready for QA

u wrote:
> This needs review, see tails-dev.

Marking as such.

#10 Updated by sajolida 2014-05-06 19:13:01

  • Status changed from In Progress to Resolved
  • Assignee deleted (sajolida)
  • QA Check deleted (Ready for QA)