On 9.3.2011 12:20, Dimitris Glezos wrote:
> On Wed, Mar 9, 2011 at 12:11 PM, Vladimir Macek <ma...@sandbox.cz> wrote:
>> Hi, does anyone use an easy way to review translation changes for his/her
>> language?
>>
>> Consider the situation that you developed some i18n rules for your language
>> and want to check whether the changes done by team members or anyone else
>> still abide those. You certainly don't want to read all everytime you check.
>>
>> I hoped Transifex offers some change history browsing but it does not seem
>> to be true.
> This has been mentioned in some meetings with the fellow Tx
> developers, ie. to store the history of a translation, and probably
> under development in a branch. The UI to interact with "Latest changes
> by your team" is still unclear though. Mockups/ideas are welcome!
>
> -d

My compliments to the devs, the site seems straighforward and easy to use,
hence it had to cost boatloads of work.

Some rough ideas for discussion:

Every msgid has a few distinct events. Every event can carry the following
information for later reference:

timestamp, resource name, language, event type, initiating user, msgid

Event types:

    * added to resource (po file)
    * changed, additional values to carry:
          o previous msgstr
          o new msgstr
    * marked/unmarked as fuzzy, as error, as ... ?
    * removed from resource
    * (You may name more.)

UI:

   1. On the bottom of the page "Home?Projects?<project>?Teams?<language>"
      or linked from there:

      The "when DESC" ordered static list of events, at least past 6
      months. There is a (global team) History section already.

   2. The same information in daily/weekly/monthly/off (personal setting)
      digest e-mail everyone could subscribe to. Would be nice if I could
      process the mail by UNIX text tools (tab delimited file attachment?).


Super comfort feature:

Anyone could immediately edit the suboptimal translation as soon as he/she
sees it in the log on the web. The "Edit" button could be shown with every
event whose:

    * event_type = "changed" or "added to resource"

for "changed": new msgstr = current msgstr for that msgid (to avoid editing
old values)

Sorry for being so verbose. :)

-- 
\//\/\ : Vladimir Macek : http://macek.sandbox.cz : +420 608 978 164

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To post to this group, send email to django-i18n@googlegroups.com.
To unsubscribe from this group, send email to 
django-i18n+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-i18n?hl=en.

<<attachment: macek.vcf>>

Reply via email to