Bitesize STE is written by Mekon’s Simplified Technical English trainer Ciaran Dodd. In the last of this series, we answer the question: Do you need software to write in STE? Do you need software to write in STE? No, is the short answer. Or, as the STE Maintenance Group (STEMG) states: “NO. Software will not think… Read more Bitesize STE – Do you need software?
Bitesize STE is written by Mekon’s Simplified Technical English trainer Ciaran Dodd This month, we examine the STE Maintenance Group’s statement that: “STE training is the first essential step for a technical author to be able to apply STE correctly.” (asd-ste100.org/training) Is STE training essential? Implementing STE goes to the heart of technical communication and focuses… Read more Bitesize STE – Is training essential?
Bitesize STE is written by Mekon’s Simplified Technical English trainer Ciaran Dodd This month, we challenge the perception that STE is too simple, particularly for native English readers. We answer the question: Is STE too simple? Originally, STE was called AECMA Simplified English. The name was amended to Simplified Technical English in 2005 but the… Read more Bitesize STE – is Simplified Technical English (STE) too simple?
This month, we change the perception that STE is only for use in aerospace and defence and show you how adaptable STE really is. We answer the question: Can I use STE in my industry? It is logical to assume that STE is only for use in aerospace and defence because: STE was developed by… Read more Bitesize STE – Can STE work for you?
So, how would you define a noun, verb or adjective? Pronoun? Adverb? For STE you need to know your parts of speech to make sure that one word has one meaning and that you are consistent. So when I’m training delegates in STE, I have to ask the question: When was the last time you… Read more Bitesize STE – Key principles: one word one meaning and be consistent (part 2)
ASD Simplified Technical English ASD-STE100 (STE) seeks “to keep texts as simple and as readable as possible” (ASD-STE100T Specification, 2013:1-6-1) with two key principles: one word one meaning and be consistent. In the next few articles we look at why these principles are necessary and how STE supports them. One way is to avoid synonyms… Read more Bitesize STE – Key principles: one word one meaning and be consistent (part 1)
If your organisation translates its documentation, I’ve no doubt that your three main concerns are managing: quality time and cost Whether your translation needs are small (one document into one language) or large (several documents with several updates into many languages), you need to manage these three factors. How can STE help you? Quality – a… Read more Bitesize Simplified Technical English – Reasons for using ASD-STE100 part 3: the benefits for translation
Simplified Technical English (STE) adds structure to your content When I first started delivering training in ASD Simplified Technical English ASD-STE100 (STE) in 2002, it was known as AECMA Simplified English. My main customers were in the aerospace and defence industries where companies were required to use Simplified English for regulatory (for example ATA 100… Read more Bitesize Simplified Technical English – Reasons for using ASD-STE100 part 2
The writing rules describe good writing practice. Effective writing in business and technical writing is about communicating information clearly, accurately and concisely. Easy…isn’t it? Apparently not. The good news is that there is agreement on how to write effectively. Over the Christmas break, I took the opportunity to read a selection of books and articles… Read more Bitesize Simplified Technical English – Reasons for using ASD-STE100 part 1
Nick Rowlands, Senior Project Lead, Mekon In the last century, a number of linguists, mainly technical writers, occupied themselves with developing a universal, simplified language to make the product documentation easier to understand for the global users. One of those linguists was Charles Kay Ogden (June 1, 1889 – March 21, 1957). Charles was an… Read more What the Industrial Revolution did for Technical Documentation
