Program by Day
Program by Track
Program Titles
“Wiki Roundtripping? Structured Authoring? How Do They Co-Exist?”
24 Ways to Shut Down The Application and Other Apocryphal Stories
A Comparison of Three Visual Help Authoring Tools
Beyond L10N and G11N—Communicating with Everybody
Breathing Life into your Technical Documents using Adobe AIR and the Technical Communication Suite
Bringing the Video Revolution to Technical Communication
Changing the Rules of the Game for the Benefit of the User
Document Engineering in User Experience Design
Documentation Planning and Library Design in a Web 2.0 World
Extending the Value of Content in Enterprise Systems with Web Content Management
How an Author and Editor Used a Wiki to Write a Book
Living Multiple Lives: The New Technical Communicator
Making XML Technology Accessible
Manage Your Messaging with Machine-Assisted Editing and Large Scale Sentence-level Reuse
Mapping the Entire Global Content Supply Chain
On the Road to Modular Training Content
Once Content is in XML. Now what?
Putting Everything Back Together Again
See Dynamic Publishing in Action!
Taking Our Information Assets to the Next Level
The In.vision DITA Enterprise Suite for Microsoft Word and SharePoint
Understanding and Communicating the Financial Impact of XML and DITA
Understanding Component Content Management
Using Collaborative Tools for Virtual Team Management
Using Task Modeler to Streamline DITA Content Development
What Technical Communicators Need to Know about Flash
Wikis Are Wonderful, or Are They? A Real World Story of Using Wikis For User Information
Writing Reusable Content to Support Content Models
[Workshop] Moving from Unstructured Documents to Structured XML
[Workshop] An Overview of RoboHelp 7
[Workshop] Content Engineering
[Workshop] DITA Authoring and Publishing with XMetaL
[Workshop] Introduction to XSL
[Workshop] Making DITA Work For Your Data
[Workshop] Simplified Technical English
[Workshop] Single Sourcing with the Technical Communication Suite
Session Details
[Workshop] Simplified Technical English: How Standardization of Content Will Reduce Costs and Facilitate Quality Assurance
Speaker: Berry BrasterTime: 1:30 PM - 5:00 PM Date: May 6
Track: Pre-Conference Workshops
Experience level: All levels
Room: Point Grey Room
Products and processes are becoming more complex, while companies worldwide increasingly have to deal with different languages.
Although technical documentation is predominantly written in English, it can often be difficult to understand due to its complexity: complex sentence structures, multiple meanings and synonyms easily result in confusion. In addition, many readers command of English can fall below the level of those who created the documentation, which especially applies to non-native English speakers.
In addition, for documentation that has to be translated into other languages, one cannot expect the translation to be of great quality if the source file was ambiguous to begin with.
As a result, these are often the consequences:
- Confused and frustrated readers
- Safety risk
- Damage during operation or maintenance
- Liability claims
- High localization costs
- Unsatisfactory translations
- Higher training support costs
- Ineffective customer service
- Unanticipated costs as a result of miscommunication
In this context, clear and effective writing has become more important than ever before.
Simplified Technical English (also known as Controlled English) is a method of writing that makes technical English easy to understand. The use of Simplified Technical English stimulates (global) acceptance of technical documentation as it improves readability and prevents misunderstandings and misinterpretations.
Benefits of Simplified Technical English
- Standardization of technical writing
- Quality assurance for technical documentation
- Efficient authoring and editing
- Reduction of errors, misunderstandings and safety risks
- Reduced time to market
- Easier to reuse, translate and maintain
- Cost savings due to reduced risk of safety, damage and liability claims
- Lower product lifecycle cost
- Content management: Simplified Technical English facilitates CMS through optimum reusability of content that is clear and concise
How controlled authoring facilitates XML and translations
As today’s authoring environment is changing to structured XML and content management, it would only make sense to also adapt controlled terminology and good writing practice rules to further improve reusability and create additional cost savings.
Doing so will not only standardize the content, it will standardize content management in general, create efficiency, and further increase the many benefits content management already offers. Reusability is the key word here, which applies both to the English content, as well as to the translations, which can decrease the content up to 30% AND save translation cost up to 40% per language! Cheaper translations are one aspect, but avoiding costs as a result of clear and unambiguous communication to our customers can be tremendous, let alone the fact that our customers simply understand what they are reading, which will be a further enhancement to your product.
Simplified Technical English is a long-term and comprehensive initiative designed to standardize the way technical publications are written. It facilitates globalization in a reliable, cost-effective and efficient way.
In addition to bringing clarity and consistency to technical documentation, STE can save you up to 30% in translation cost. Furthermore, STE facilitates industry standards like DITA, S1000D, and SCORM, but also XML and CMS through optimum reusability.
If you are opting to go towards any of these standards, if you have a translation requirement, or in case you are only looking to create clearer and understandable technical documentation, Simplified Technical English is the standard to take into serious consideration.
Berry Braster will explain the principles of STE and its benefits, and will give you practical and real-life examples in the form of case studies.



