Hi,
u wrote (28 Mar 2015 18:23:42 GMT) :
>>> MAY
>>> ===
>>
>>> * provide context of the translation
>>
>> I don't really understand how this can merely be a MAY when we're
>> talking about translating a website. Maybe I'm just thinking of
>> something else, that's not on the blueprint yet, so I'll elaborate.
>> I would see what follows as a MUST when translating web pages
>> (especially for translators who won't build the website themselves,
>> because they're not using Git): "allow translators to view, in the
>> correct order, all strings that come from the entire page being
>> translated, both in English and in the target language".
> Ack.
Done in dd15601.
>>> * send email notifications
>>
>> It isn't very clear when/what/to whom.
>> Anyway, that's merely a MAY, so it's probably no big deal :)
> Send email notifications to reviewers whenever new strings have been
> translated or updated.
> Send email notifications to translators whenever a resource is updated.
Added in 8f31c53.
>> What do you think?
>>
>> Also, I see that "provide user roles (admin, reviewer, translator)" is
>> only a SHOULD. This raises a few questions (not necessarily urgent
>> ones, just process stuff to keep in mind):
>>
>> * Would we allow translation from unregistered contributors, or only
>> from logged-in users?
> I'd rather not allow translations from non logged-in users, as this
> would make it hard to keep track of modifications. However, we could
> provide a cypherpunk account for users who don't want to provide
> personal details [1]
OK.
>> * If we don't have such roles, how do we ensure that each translated
>> string has been reviewed?
> Hm, I guess we MUST have such roles.
Done in 484bf3a.
Cheers,
--
intrigeri
