M and E Tech accepts contributed manuscripts for tutorials, user case histories, and technology articles, as well as survey articles. A description of the various article types follows. In particular, we invite design engineers and engineering managers to contribute manuscripts.
If you'd like to write an article for M and E Tech, first submit an abstract and outline. (If you've already written it, send the entire manuscript.) e-mail submission is acceptable. You should state the topic of the article and the importance and appropriateness of the information. The second step, if the abstract and outline are approved, is to write the article to our specifications. An alternative descriptive method is to collect the figures you plan to use and tell how they fit into the article.
Send to: Tets Maniwa
Editor in chief
M and E Tech
Or send via e-mail to: tets AT mandetech DOT com
M and E Tech specifications:
Submit articles in MS Word via email (Alternatives are plain text (ASCII), or HTML files). All graphics should be in separate files in the floppy or as separate attachments in the e-mail.
Articles normally are between1000 to 2500 words in length.
Articles should include two to four illustrations, figures, or tables
Graphics should be submitted in TIFF, BMP, PICT, GIF, or EPS (Macintosh) formats. Photographs should be in .jpeg or .pdf formats. Minimum resolution is 300 dpi or 2400 for bitmaps.
Include a title and caption with each graphic.
Captions must be complete sentences.
Include a brief biography 15 to 25 words in length.
On M and E Tech, published editorial is divided into the following categories:
Case studies: problem-solved section is a description of a solution to a problem facing the hardware or software in creating the media.
Technology in focus: descriptions of a technology or an industry standard.
The categories are intentionally broad and meant to encompass various types of submissions. Please refer to the list below of the types of articles accepted.
Types of Articles: Although contributed articles are typically very technical in nature, some may deal with other issues such as standards and regulations, the implementation of particular design methodologies, or changes in content creation techniques to address changes in technologies.
Tutorials take a "how-to" approach in providing specific information to help people develop and complete their designs. These articles may describe fundamentals of a particular technology or the structure of some underlying protocol and how it applies to a particular implementation.
User Case Histories
User case histories relate actual experiences of designers in a system development project. They include the decision-making phases, the vendor selection process, the design process, the solution, and hints on how to do it better next time, based on these experiences.
Technology articles offer in-depth analysis of specific technologies or technical issues. Their purpose is to inform readers about current technical developments related to semiconductors, network technologies, or design tools. Examples may include design of experiments, new architectures for network equipment, and new ways to process the packets.
Below are some tips to help you develop a successful article.
Articles should have a beginning, a middle, and an end. Develop a strong lead (such as you find in a consumer magazine) to catch the reader's attention. You may begin with an anecdote. If your article is a problem/solution type article, then present the problem in an interesting or anecdotal way. If it is not possible to develop a conclusion, then provide a summary. Give the reader a clear idea of the subject and the direction the article will take within the first few paragraphs. Tell the reader what the article is about and why the topic is important.
Use the United States' standard for punctuation rather than the British standard. That is, place commas and periods before end quotes.
Ex.) Correct..."The British drive on the wrong side of the road."
Incorrect ..."The Americans drive on the wrong side of the road".
Your style should be friendly and informal. It is fine to use "I" or "you" when appropriate.
Use the active rather than the passive voice. For example, rather than "the AC characteristics can be ignored," it is better to write "You can ignore the AC characteristics."
When you use the word "this" to refer to something from a preceding sentence, it should be followed by a noun to which "this" refers.
When referring to a company in the text, on the first reference, spell out the complete company name and include the city and state. Later references only need the company name.
Spell out acronyms, abbreviations, and names the first time you use them.
Err to the side of being too explanatory. What may seem obvious to you will be less so to another user at another company.
Use short words instead of long ones where possible. For example, "use" is preferable to "utilize."
Use short phrases instead of long ones. For example, use "to" rather than "in order to."
From Manuscript to Publication
We are looking for your technical expertise, but we don't expect your manuscript to be letter perfect. Our editorial staff will edit your manuscript for length and grammatical correctness. Then, before publication we will send you the edited version of your story and your figures for your final approval.