1 / 24

Simplified Technical English:

Simplified Technical English:. Why Companies Should Use It And Translators Should Learn It. Patricia María Ferreira Larrieux Technical & Literary Translator Warsaw, 29 /03/14. Agenda. About me Purpose of this presentation The STE Project – Historical background Who uses STE?

Download Presentation

Simplified Technical English:

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. SimplifiedTechnical English: WhyCompaniesShouldUseIt And TranslatorsShouldLearnIt Patricia María Ferreira Larrieux Technical & Literary Translator Warsaw, 29/03/14

  2. Agenda • About me • Purpose of this presentation • The STE Project – Historical background • Who uses STE? • ASD-STE Specification – writing rules & dictionary • Practical examples • My thoughts on STE and technical writing • Where to find training & more information?

  3. About me • Born in Uruguay, living in Italy since 1990 • Degree in English<>Spanish Translation (1989) • Ran my own translation company (1997-2003) • 10 years at Johnson & Johnson (2003-2013) • May 2013: returned to freelancing • Currently freelance technical & literary translator • Member of: CTPU, IATPI, ITI (UK), COM&TEC

  4. Purposeofthispresentation • Raise awareness of the use of STE, a controlled language, and the advantages it may have for: • Readers • Technical Translators

  5. The STE Project – History • Late 70s: AEA asked AECMA to investigate readability of aircraft maintenance documentation • 1983: AECMA Simplified English Project started • 1986: First release of the AECMA Simplified English Guide (predecessor of the STE Specification) • 2004: ASD is founded (AECMA+EDIG+EUROSPACE) • 2005: New issue of specification released as ASD-STE100

  6. The STE Project – History (cont'd) • 2013: • January: Issue number 6 of STE Specification released – First issue ever to be distributed free of charge • November: Memorandum of Understanding signed with UNINETTUNO

  7. Who uses STE? • STE is not just for the aviation industry • 99% of the keywords are applicable to all types of documentation • A strong interest is growing within the Academic World, Faculties of Language and Engineering • STE is used by companies providing language services, technical documentation, localization and translations

  8. Who uses STE? (cont’d) • Information Technology, Software • Telecommunications • Oil and gas • Automotive, Trucks, Transportation, Railways • Agricultural equipment • Buildings • Medical and Healthcare • Fire protection • Nuclear • Urban planning • Gaming • Machinery, Mining, Manufacturing, Automation • Semiconductors • Consulting, Legal • Shipping • Food Industry • Non-profit associations

  9. The ASD-STE100 Specification • Controlled language: a subset of a language, obtained by restricting: • grammar • vocabulary to reduce or eliminate ambiguity and complexity • ASD-STE100 is an international specification for preparation of maintenance documentation using a controlled language

  10. The ASD-STE100 Specification(cont’d) • STE consists of: • a set of writing rules • a dictionary of controlled vocabulary • STE is meant for both native and non-native readers of English • STE is intended to be used for written communication only • STE is maintained by the ASD-STEMG

  11. What’s new in Issue 6? • New general layout and formatting • Review of sections 1 and 3 of writing rules • Review of the categories of technical names • Inclusion of Information Technology and telephony terms • New category of technical verbs (Operational language) • Improvement of the dictionary • Further reduction of aerospace examples • Clarification of the assigned meanings of some important keywords

  12. What's new in Issue 6? (cont'd) • Distribution free of charge by requesting it at: http://www.asd-ste100.org/request.html • 1700 copies have been distributed as of 19/03/14 • About 40% distributed to users outside the AeroSpace and Defence fields

  13. Writingrules The basic philosophy of STE is to keep texts as simple and readable as possible. • Use only approved words from the STE Dictionary • Use approved words only as part of speech given • Use consistent language and spelling • No noun clusters of more than three nouns • Use only approved verb tenses

  14. Writingrules (cont'd) The basic philosophy of STE is to keep texts as simple and readable as possible. • Use the active voice • Keep to one topic per sentence • Procedures: write one instruction per sentence and use imperative verb • Warnings: always start a warning/caution with a simple and clear command • Keep sentences short (20/25 words max)

  15. The Dictionary

  16. The Dictionary

  17. PracticalExamples • Non-STE: Test the system for leaks. • STE: Do a test for leaks in the system or Do the leak test for the system. Reason: “test” is approved for use only as a noun and not as a verb. • Non-STE: Make a sandwich with two washers (25) and the spacer (26). • STE: Install the spacer (26) between the two washers (25). Reason: do not use slang or jargon words.

  18. PracticalExamples (cont'd) • Non-STE:Ensure that the 600 Hz tone is audible when the XY switch is depressed. • STE: (a) Push the XY switch. (b) Make sure that you hear the 600 Hz tone at the same time. Reason: ensure, audible and depressed are not STE approved words. Always use a verb to describe an action (not a noun or other part of speech). Use the active voice.

  19. My thoughts on STE and technical writing • Using STE to write technical documents enhances readability by eliminating ambiguity and promoting consistency • STE minimizes the chances that an operator may misunderstand a technical procedure, warning or caution (increased safety) • STE texts are more CAT-tool-friendly than non‑STE texts

  20. My thoughts on STE and technical writing (cont'd) • Income diversification: Technical Translators can offer STE-related services to clients (e.g. revision, translation, re-translation) • Technical Translators can interact with Technical Writers to support the use of STE • Technical Translators can join their local Technical Communication Association

  21. Where to get training on STE? In November 2013 ASD and the International Virtual University UNINETTUNO signed a Memorandum of Understanding, a key milestone in the history of STE As a result, UNINETTUNO is now the only body accredited by ASD to provide STE trainings and certifications.

  22. Where to get training on STE? (cont’d) Training activities are being organized by UNINETTUNO on a distance-learning basis and delivered worldwide. For more information, you can visit the UNINETTUNO website: http://www.uninettunouniversity.net/en/ASD-STE100.aspx

  23. Where to find more information on STE? • ASD website: www.asd-ste100.org • ASD e-mail: info@asd-ste100.org • STEMG Facebook page • STEMG Twitter account @asd_stemg • Contact STEMG on Linkedin • Contact the STEMG Chairman: orlando.chiarello@secondomona.com

  24. Thankyou!! • Dziękuję!! ¡Gracias!

More Related