Log Message:
-----------
Some important things were finished as:
- the file-lock process works fine! Lots of Tests are required.
- if a translation has got the max score, then that translation
will not be translated again. That's way another user isn't able
to broke it.
- the string translation can be viewed by all users
TODO (some):
- if a string has got the same score, show the last revision
- Check some lines in the code. In deep, when a user want to lock a file
IMO could be some race conditions between users and files. Well, there
is a PK in the table 'es_locking' in id_usuario field. That way, the
user cannot lock two times a file at the same time.
- Tests, Tests....
Modified Files:
--------------
l10n/es:
template_code.html (r1.1.1.1 -> r1.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/webtranslator/l10n/es/template_code.html.diff?r1=1.1.1.1&r2=1.2)
template_show_file.html (r1.4 -> r1.5)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/webtranslator/l10n/es/template_show_file.html.diff?r1=1.4&r2=1.5)
template_status.html (r1.2 -> r1.3)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/webtranslator/l10n/es/template_status.html.diff?r1=1.2&r2=1.3)
views.py (r1.5 -> r1.6)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/webtranslator/l10n/es/views.py.diff?r1=1.5&r2=1.6)
l10n/scripts:
index.sql (r1.2 -> r1.3)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/webtranslator/l10n/scripts/index.sql.diff?r1=1.2&r2=1.3)
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
