Marc Laporte, TikiWiki.org, Canada
Classic translation workflow systems are based on several assumptions.
For example, they assume the presence of a master language and that the source document be "final" before translation is started. But what to do for a wiki, which has no master language and, by the wiki's nature, when a document is never "final"? The presentation will address 7 assumptions (including the two mentioned above) of the traditional translation workflows and how these are challenged in the Web & Wiki world. Finally, we will describe a working solution to these issues, implemented in TikiWiki, a full-featured, open source, multilingual Web Content Management System (CMS). This solution is currently used by the Firefox support site at support.mozilla.com. More information on Wiki-Translation.com"
27 November 2008
Should we setup a test wiki so attendees can experiment?
View as slidewshow
2-Synchronizing translations in a Wiki
1- A full-featured, open source, multilingual Web Content Management System
2- The challenges and a working solution, used by the Firefox support site
by Marc Laporte, at ASLIB 2008, London
What I'll talk about
- Collaboration and Wikis
- Translating the Wiki Way
- Mozilla (Firefox) Support
- Staging and approval
- Free source software & business model
- TikiWiki CMS/Groupware
- Over a decade of Web experience
- Expert on wikis, collaboration and groupware
- Project administrator of TikiWiki CMS/Groupware
- Longstanding interest and involvement in multilingual wikis
What are the most important volunteer mass collaboration projects in the history of humankind?
Add picture here
(add new slides)
Where is the "field" going?
Did open source reduce the number of programmers?
Examples of mass collaboration, crowdsourcing in other fields (FOSS, Wikipedia, etc.)
Why engage new people in your projects?
If you do, 7 assumptions of traditional translation workflow, etc and what this means for wikis
examples of various level of openness vs control. Ex.:
SUMO example: not 100% open, but still permits participation
Tools should support that
7 assumptions of traditional translation processes and tools
- Master language
- Edit freeze
- Enforceable timely translation
- Controlled language pairs
- Strong coordination
- Trained translators
- Separation of Authoring and Translation
Often not applicable in a collaborative environment
Wikis: what for?
- Collaboration -> flexible, simple freeform project management
- Corporate Intranet or extranet
- Great for unstructured content, can be structured with categories and tags
- Effective document workflow
Wikis in plain English
Add image of video, with link
Why a wiki?
Give someone a fish and you feed them for a day.
Teach someone to fish and you feed them for a lifetime.
Add that knowledge to a wiki
And countless people will be able to learn on their own
And share their knowledge
And many will feed their families
Because email doesn't scale
(add picture here)
- Powerful revision control: Every single change is tracked. Who/what/when + ability to show the difference
Need some good screenshots
- Use a standard web-browser
- Shared, editable
- Wiki syntax for simple links and formatting
- Email notification of changes (opt-in)
The same page?
(add image here)
Translating the Wiki Way
- What about when… ?
- …minor changes are frequent?
- …translation can’t be expected to be complete everywhere?
- …there is no master language?
- How do you track and propagate changes across languages? (without pulling your hair out
Wiki translation demo
(add image here, with link to play video)
(add image here)
- Louis-Philippe Huberdeau
- École de technologie supérieure
- Alain Désilets
- Conseil de recherches national du Canada
- Sébastien Paquet
- Université du Québec à Montréal
- Nelson Ko
- TikiWiki CMS/Groupware / Carleton Univ. / Citadel Rock
- Marc Laporte
- TikiWiki CMS/Groupware / Avantech.net
- Xavier De Pedro
- Needs accurate & precise documentation for Firefox
- Contributed by volunteers
- Minimum of 8 languages
- For urgent translations changes, messages can be tagged accordingly
- Staging & approval feature
- Starting with Firefox 3, application documentation is online
- Mozilla is both a user and a contributor/participant/partner.
Staging and approval
Free Source Software
- Shared resource
- Collaborative development
- Popular examples
- Open Office
Free software is software which can be used, copied, studied, modified and redistributed with little or no restriction.
It’s really free?
- Free beer?
- Free speech?
- Free kitten?
- What is the business model?
- How are you protected against vendor lock-in?
Open Source Business model
- No license fee to use the software.
- You can choose to pay for services
- Installation, support, training, custom development and hosting.
- But not licenses.
- Tightly Integrated Knowledge Infrastructure
- Combination CMS + wiki + groupware
- Stable & established application
- Very active community
- Free source software (LGPL)
- Consultants if you need paid support
- Used on tens of thousands of sites
- 6 years, hundreds of people.
- A new code commit every two hours
- Translated into 30+ languages
- 960 pages of documentation
- Unlimited number of users
- Unlimited number of groups
- Users can be in any number of groups
- Runs on standard php/mysql making web hosting easy and inexpensive
More TikiWiki features
- Hundreds of built-in features
- Blogs & articles
- File gallery
- Check-in/out, categories, plugin to filter
- Custom database, forms and reports
- Discussion forums
TikiWiki Use Cases
- Online community / association / club / special interest group / NGO (A)
- Personal site / family site (A)
- Simple portal / news site (A)
- Advanced portal / news site (A)
- Corporate web site (A)
- Groupware Wiki / Corporate Wiki / Corporate Intranet / Team project (A)
- Public Wiki (A)
- Group knowledge base / Knowledge Management (KM) / institutional memory (A)
- Product or software documentation and support (A)
- Customer extranet (B)
TikiWiki Use Cases (part 2)
Personal knowledge base / manage my life (B)
Wiki-based Project Management (PM) (B)
Glossary / Dictionary / Encyclopedia (B)
Writing a book (B)
Framework / Activity Workflow / Specialized web Application (B)
Document Workflow (B)
Bug or Issue tracker (B)
Collaborative research (B)
Voice-enabled wiki and mobile applications (B)
Geo CMS (B)
Blog (one author) (C)
Blog (several authors) (C)
Event Management, Conference Management & planning (C)
TikiWiki Use Cases, part 3
Calendar of events (C)
Document Management System (DMS) (C)
SourceForge/Gforge type site (C)
Translation Management System (TMS) (D)
Traditional Project Management (PM) with Gantt charts, etc (E)
E-learning / Learning Management System (LMS) / classroom / course management system (CMS) (D)
Customer/Contact/Constituent relationship management (CRM) (D)
Social networking / Job board / Dating site / hospitality exchange / Car Pooling (E)
E-commerce / Shopping cart (E)
Enterprise resource planning (ERP) / Accounting (E)
Tracker & form generator
- Multilingual form & report generator
The TikiWiki community will be happy to work with any organization to help use:
- The same principles as Wikipedia
- The same technology as Firefox
- Free source software
- …I want you to remember about this talk in 6 months
- There is a wiki-translation.com community
- Wiki energy will affect many sectors, including the World of translation
- Wiki & open source technology is available at a good Total cost of ownership (TCO)
(add image here)