Best Programmers

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Friday, 8 August 2003

Posted on 06:05 by Unknown

AECMA Simplified English



What Is Simplified English?



AECMA Simplified English is a writing standard for aerospace maintenance documentation. This type of writing standard is also known as a controlled language because it restricts grammar, style and vocabulary to a subset of the English language. The main characteristics of the Simplified English standard are

Simplified grammar and style rules.





  • A limited set of approved vocabulary with restricted meanings.

  • A thesaurus of frequently used terms and suggested alternatives.

  • Guidelines for adding new technical words to the approved vocabulary.

  • The objective of Simplified English is clear, unambiguous writing.
  • Developed primarily for non-native English speakers, it is also known to improve the readability of maintenance text for native speakers.

  • AECMA Simplified English does not attempt to define English grammar or prescribe correct English. It does attempt to limit the range of English; many of its rules are recommendations found in technical writing textbooks. For example, SE requires writers to:



    • Use the active voice.

    • Use articles wherever possible.

    • Use simple verb tenses.

    • Use language consistently.

    • Avoid lengthy compound words.

    • Use relatively short sentences.


Other Controlled Languages



While AECMA Simplified English is designed for use in aerospace maintenance documentation, controlled languages can be created for other writing domains. Companies in several industries -- manufacturing, mining, oil exploration and software development, for example -- have modified AECMA Simplified English or produced their own controlled-language writing standards. The Boeing Simplified English Checker can be modified to support more general technical writing.

Related Sites:



AECMA (European Association of Aerospace industries)


simplified English




write to me: Suman@sumankumar.com
Email ThisBlogThis!Share to XShare to Facebook
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Finding the voice
    Excerpt from LOUIS MENAND's review of Eats, Shoots & Leaves: The Zero Tolerance Approach to Punctuation” (Gotham; $17.50), by Lynne ...
  • Context Sensitive 'Sticky Notes': Stick a Sticky Note to your Blog!
    Conceptworld's Quick Notes Plus might appear like any other Sticky Notes Plus (QNP) program, but its context-sensitive notes feature is...
  • Use it before you write it.
    From the Nikkor ED 80-400mm f/4.5-5.6D VR Review (emphasis is mine): [quote] Here's the warning in the manual : "When the camera is...
  • Style guides: Sacrosanct?
    How many times have you paused and reflected, ‘man, I know I am right, but the style guide does not agree…’? For example, some style guides ...
  • (no title)
    Next STC Chennai Meeting On March 7 : This will be the second knowledge sharing session. The first meeting was a wonderful success and we h...
  • Wanted: Sr Technical Writer for Informatica Corporation
    Location : Bangalore Corporate Headquarters : Redwood City, CA Contact : Thao Diep, tdiep@informatica.com Job Description Responsibl...
  • The Personable Manual
    Why do product manuals sound formal and stiff-upper-lipped? Why don’t users read manuals? These questions have haunted the hallowed precinct...
  • Comments System: Anyone Can Post Comments Now!
    Folks, I know some of you were irritated by the fact that you had to login (if you're a Blogger user) or post as Anonymous while posting...
  • A brand name gone wrong
    "Did you know that Heroin was originally a brand name for cough syrup? In 1874, German scientists developed a formula for a painkiller ...
  • Promoting Document Usage: Taking a leaf out of Business Directories
    You can argue all day that you know a customer that reads your manuals but my point is that most don't. It is a blessing in disguise fo...

Categories

  • conferences
  • contigency design
  • culture
  • design
  • error messages
  • google
  • hall of shame
  • ideas
  • management
  • manual
  • standards
  • stc
  • strategy
  • tools
  • usability
  • writing

Blog Archive

  • ►  2009 (1)
    • ►  February (1)
  • ►  2008 (5)
    • ►  November (1)
    • ►  September (1)
    • ►  May (2)
    • ►  April (1)
  • ►  2007 (7)
    • ►  October (1)
    • ►  August (2)
    • ►  June (1)
    • ►  March (1)
    • ►  January (2)
  • ►  2006 (10)
    • ►  November (2)
    • ►  October (3)
    • ►  September (1)
    • ►  August (3)
    • ►  June (1)
  • ►  2005 (17)
    • ►  December (2)
    • ►  November (1)
    • ►  October (3)
    • ►  September (2)
    • ►  August (3)
    • ►  June (2)
    • ►  May (1)
    • ►  April (2)
    • ►  February (1)
  • ►  2004 (32)
    • ►  December (4)
    • ►  November (1)
    • ►  October (3)
    • ►  September (3)
    • ►  August (2)
    • ►  July (5)
    • ►  June (3)
    • ►  May (1)
    • ►  April (5)
    • ►  March (2)
    • ►  February (1)
    • ►  January (2)
  • ▼  2003 (42)
    • ►  December (2)
    • ►  November (3)
    • ►  October (1)
    • ►  September (3)
    • ▼  August (7)
      • Re: [twin] Course Content for Technical Writing
      • Latin Words Used in The English LanguageTrust me,...
      • Importing Word2000 Documents to RoboHelp HTMLArtic...
      • How to hire a 'Future-Proof' Technical WriterI cam...
      • AECMA Simplified EnglishWhat Is Simplified English...
      • And now, 'Technical Writer': The Movie
      • A Tale of a Technical Writer who did Programming f...
    • ►  July (2)
    • ►  June (1)
    • ►  April (4)
    • ►  February (4)
    • ►  January (15)
Powered by Blogger.

About Me

Unknown
View my complete profile