https://bugzilla.gnome.org/show_bug.cgi?id=695553
l10n | other | unspecified
Rajesh Ranjan <rajeshkajha> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rajeshka...@yahoo.com
--- Comment #13 from Rajesh Ranjan <rajeshka...@yahoo.com> 2013-03-13 07:12:19
UTC ---
A good brainstorming is happing here and I would like to share my experience of
working with open source localization field (more than 8 years) and some ways
and means we adopted to deal with this problem.
Context (co-text + rel-text + chron-text + bi-text + non-text) is crucial while
translating. So we should treat this bug as an important one and do whatever is
possible to help translators and finally the language desktop users.
To deal with the issue, FUEL project [1] prepared a list of Frequently Used
Entries for Localization called FUEL desktop list [2] with context from major
user applications. To some extent it solved our problems of context while
dealing with the problem of standardization and inconsistency.
Just now a similar interesting discussion like this bug appeared on FUEL
project's mailing list [3]. Peter Mráz is very right in citing deckard
instance as it can be very much helpful in understanding the context. The
visual comparison and its method is documented under FUEL [4] and released in
Aug '12 to help the localizers and the persons associated with its QA.
I want to reiterate Pavol concern that without context translation can generate
critical errors and it is very much difficult and time consuming to remove
errors which are generated due to unavailability of Context info.
[1]. http://www.fuelproject.org/
[2].
http://git.fedorahosted.org/cgit/fuel.git/tree/language/en/terminology/desktop/fuel-desktop-en.pot
[3].
https://lists.fedorahosted.org/pipermail/fuel-discuss/2013-March/000446.html
[4]. http://svn.fedorahosted.org/svn/fuel/qa/
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n
