Friday, May 23, 2008

Introduction

This blog has the purpose to enable creative, dynamic, and team-minded clients and translation agencies, especially translators, to explore, to share, to discuss, and to collaborate on endorsed ideas created, best-practice approaches, and cutting-edge benchmarks regarding Preventive Quality Management for Translations under the implementation of Web 2.0 and Open Source technologies (meaning non-commercial or Creative Commons License ones for free use). The following is also an attempt to find a foothold in this issue in compliance with the EU Standard for Translations EN15038:2006 and the USA Standard for Translations ASTM F2575-06:

Prior to Contracting/Pre-Production
1. How to organizationally structure Collaborative Translation 2.0 http://www.scribd.com/doc/4069269/How-to-Structure-Collaborative-Translation-20, Schematic Overview of Roles http://www.gliffy.com/publish/1476779/
2.
Quality Best Practice: Virtual Communities http://advice.cio.com/lionbridge/v_commuting_the_next_frontier_in_global_workforce_management
3. The Book of Collaborative Translation - Table of Contents: http://collaborative-translation.ning.com/forum/topic/show?id=2237585%3ATopic%3A739
4.
Endorsement of professional guidelines http://www.proz.com/professional-guidelines
(on-going discussion http://www.proz.com/topic/103558)
5. Reasons for No Sample Translations
http://www.gala-global.org/GALAxy-article-why_sample_translations_break_all_the_rules-8668.html
6. All party use of a web-based or open source Requirements Management tool, under evaluation ReqMan (Rally, OSRMT 1.5, Jama Contour, e-LM.com)
7. All party installation and use of Unified Communications (like Skype.com, Oovoo.com, MeGlobe.com), collaborative applications (Skype in conjunction with InstaColl, Live-Documents), or online conferencing (Yugma)
8. All party establishment and use of a web-based Blog Meeting or Project Wiki for project communication and information (Collaborative Wiki to post messages and comments, to share documents and encourage contributions, to maintain to-do lists, to set project milestones), document organization and archive (to use tags, to increase search capability), the raise of discussion points and their feedback, and participative involvement of project members, including the use of according RSS feeds (Collaborative Wiki Log for Abbreviations/Terms, Style Guide source text/target text, Web 2.0 Information Resources, Network Bookmarking Translation 2.0, Error Log, Help Desk 2.0).
Blog Meeting http://eiconsulting.wordpress.com/about/ , Xwiki & XBlog
http://www.netcipia.com/ , Document Archive
http://www.scribd.com
9. Project manager and Translation service provider use of a web-based or open source CRM tool.
Web 2.0 Customer Relationship Management
http://crm.zoho.com/
10. Project manager and Translation service provider use of a web-based or open source Personnel Management tool.
Web 2.0 People Management & Recruitment Solution http://people.zoho.com/
11. Automatic e-mail project reminders via Google Calendar.
12. Use of a comprehensive check list for translations.
13. Use of a web-based project protocol template.
14. Implement best-practice project management principles.
15. Implement best-practice risk management principles.
16.
Directive 2000/35/EC of the European Parliament and of the Council on combating late payment in commercial transactions
http://ec.europa.eu/enterprise/regulation/late_payments/index.htm

During Production
1. Use of web-based collaborative Web 2.0 or Open Source TM translation applications for translation production (evaluation pending: EbiWrite, Freeway 2.0, Logoport, Wordfast 5.5/6.0 in conjunction with Very Large Translation Memory VLTM, Across v4.0,
Translation Memory Open Source System TMOSS, Polyglota (Opensource Collaborative Translation Management Tool))
2. Synchrone Author < > Translator Processing http://collaborative-translation.ning.com/profiles/blog/show?id=2237585%3ABlogPost%3A326
3. Audio Transcription Technology http://e-i-consulting-translation.blogspot.com/2008/08/audio-transcription-technology.html
4. Asia Online Unveils Revolutionary Web-based Statistical Machine Translation Platform with 203 Language Pairs
http://www.pr-usa.net/index.php?option=com_content&task=view&id=110013&Itemid=30
5. Intermediate delivery with sample review or revision, and feedback of error types (error in the form or error in the meaning?). Translation Quality Index More Translation Quality Index. All party use of a web-based or open source Error Log tool (evaluation pending) or Help Desk 2.0 http://www.zendesk.com/
6.
Client case solution for enhanced quality
Step A: 1/3 translation > US English + 2/3 translation > British English
Step B: Subsequently 3/3 editing, review, revision, proofreading, and final verification > US English


Post-Production
1. MindMap Proofreader Check List 2.0 Overview: Error Type Structure for Error Log Protocol
2. Wiki-based Recommendation & Error Log Protocol (for Review,
Revision, Proofreading, Final Verifying) feedback of error types (error in the form or error in the meaning?)
3. Quality survey http://www.surveymonkey.com/
4. Translation client payment behavior blog http://translation-client-payment-behavior.blogspot.com/

Feel free to put this blog on your watchlist, and to use this blog as Your Suggestion Box. Your contributions are valued.

No comments: