Bug #: 746930
Summary: Mozilla Translation Process needs to be revamped
Classification: Other
Product: Mozilla Communities
Version: unspecified
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: --
Component: Contributor Engagement
AssignedTo: nob...@mozilla.org
ReportedBy: rajes...@yahoo.com
QAContact: contributer...@communities.bugs
User Agent: Mozilla/5.0 (X11; U; Linux i686; hi-IN; rv:1.9.2.24) Gecko/20111108
Fedora/3.6.24-1.fc14 Firefox/3.6.24
Build ID: 20111108102749
Steps to reproduce:
Hi,
We do translation for Mozilla from several years. We find Mozilla translation
process not suitable for the purpose of translators and localizors communities.
There are following reasons for the same:
1. Time Consuming: The whole process is very cumbersome and time consuming. The
task that can be done through some machine work, we have to do by comparing
files in source with our locale. This task itself takes 40% time of a
volunteers who give their free time for the Mozilla.
2. Translation Memory and reuse of database: In the whole translation process,
mainly dependent on committing files through hg and svn and editing the files
through an editor, we am unable to use the translation memory and reuse of the
translation we have done earlier. This again takes a volunteers more time than
what it can be actually required.
3. Inconsistency in Translation: Due to no use of memory, translation leads to
the problem of inconsistency and issue of standardization. This problem leads
to poor usability issues. We have conducted review meets and got feedback of
inconsistencies.
4. Glossary: Due to unavailability of any translation tool that can edit the
files in the dtd and properties format, it is difficult for translators to use
approved terminology in the translation of Mozilla product. Again creates
usuability.
Regards,
Rajesh and Aman
--
Configure bugmail: https://bugzilla.mozilla.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You reported the bug.