Hi,
spriver:
> Hi,
> thanks for starting such thing; I think that something like this is
> overdue.
>
> In my opinion the glossary thing is more a should or even must. We use
> many technical terms and newbies (esp. people who are'nt that "geeky"
> could run into problems there) may do not know all terms. We also
> experienced the numerous discussion about some terms in our German
> translation team. If we could have a place to unify all agreements we
> made about some terms it would make it also easier for new translators
> to start and it would also reduce traffic on the mailing list. (I hope
> you get what I mean)
Yes, I agree with your arguments. So I'll move the glossary to MUST.
> Furthermore we could also add (maybe this idea is too much or obsolete)
> a list of "core pages" to translate. This would be a list of the most
> needed pages in the wiki to start translations on. (This could be
> helpful for new translation teams to have a overview of the "most
> needed" pages)
Such a page exists [1], but we should link to it indeed.
I've created a ticket for that:
https://labs.riseup.net/code/issues/9118
Cheers,
u.
[1]
https://tails.boum.org/contribute/l10n_tricks/core_po_files.txt
> Am 2015-03-20 12:55, schrieb u:
>> Hello,
>>
>> Our (website) translation infrastructure has a pretty high barrier for
>> new translators, especially those who are not familiar with Git and/or
>> the command line.
>>
>> I think it's a bit sad, because we are missing out on many new
>> translators and we miss documentation in non european languages,
>> although it's probably in those regions that Tails is an important tool
>> for secure communication and censorship circumvention.
>>
>> Emmapeel created a ticket here to disucss possible alternatives or
>> add-ons to our current l10n infrastructure:
>> https://labs.riseup.net/code/issues/9049
>> As suggested by intrigeri on that ticket, we should first discuss what
>> we'd expect from our l10n infrastructure, and order those expectations
>> by MUST / SHOULD / MAY.
>>
>> Here is my summary:
>>
>> MUST
>> ====
>> * integrate with Git (push and pull)
>> * provide a usable easy web interface
>>
>> SHOULD
>> ======
>> * provide support for Git branches (we could also agree upon translation
>> only master through this interface)
>> * should provide checks for inconsistent translations
>> * provide user roles (admin, reviewer, translator)
>>
>> MAY
>> ===
>> * provide context of the translation
>> * provide glossary feature
>> * send email notifications
>> * respect authorship (different committers?)
>>
>> It would be great to discuss here and then add the results of the
>> discussion to the ticket.
>>
>> Looking forward to reading your ideas!
>>
