<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Reference&gt;Editing</title>	<link>http://tc.eserver.org/dir/Reference/Editing</link>
	<description>A listing of the most recently indexed works about Reference and Editing in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Reference&gt;Editing</title>
		<link>http://tc.eserver.org/dir/Reference/Editing</link>
	</image>
	<item>
		<title>Regular Expression</title>
		<link>http://tc.eserver.org/34210.html</link>
		<guid>http://tc.eserver.org/34210.html</guid>
		<description>regular expressions provide a concise and flexible means for identifying strings of text of interest, such as particular characters, words, or patterns of characters. Regular expressions (abbreviated as regex or regexp, with plural forms regexes, regexps, or regexen) are written in a formal language that can be interpreted by a regular expression processor, a program that either serves as a parser generator or examines text and identifies parts that match the provided specification.</description>
	</item>
	<item>
		<title>Regular Expression Tutorial - Learn How to Use Regular Expressions</title>
		<link>http://tc.eserver.org/34208.html</link>
		<guid>http://tc.eserver.org/34208.html</guid>
		<description>Basically, a regular expression is a pattern describing a certain amount of text. Their name comes from the mathematical theory on which they are based. In this tutorial, I will teach you all you need to know to be able to craft powerful time-saving regular expressions. I will start with the most basic concepts, so that you can follow this tutorial even if you know nothing at all about regular expressions yet.</description>
	</item>
	<item>
		<title>Regular Expressions for Client-Side JavaScript</title>
		<link>http://tc.eserver.org/34209.html</link>
		<guid>http://tc.eserver.org/34209.html</guid>
		<description>Here is the syntax for a very powerful and very cryptic string pattern matching scheme in the client-side JavaScript of web browsers. You can use it to validate form entry, parse URLs, and many other things.</description>
	</item>
	<item>
		<title>Punctuation Made Simple</title>
		<link>http://tc.eserver.org/31676.html</link>
		<guid>http://tc.eserver.org/31676.html</guid>
		<description>Some people write well but allow themselves to be disabled by a fear of punctuation and grammar. They know how to prewrite, organize, and revise, but proofreading for punctuation and grammar causes them difficulties. There’s no need to fear these conventions of standard written English. In fact, these conventions can help you become a more effective communicator.</description>
	</item>
	<item>
		<title>Professional Editorial Standards</title>
		<link>http://tc.eserver.org/22632.html</link>
		<guid>http://tc.eserver.org/22632.html</guid>
		<description>The skills listed in this publication are those most commonly required for editing English-language text, whether on paper or on screen. The editor&apos;s functions start when the writer declares the manuscript more or less complete and continue through to the point at which it is ready for publication, regardless of the medium. Editors perform many tasks along the way, including structural editing, stylistic editing, copy editing, markup/coding, and proofreading. The technologies used in editing and in publishing change, but the fundamental tasks and the editorial skills required to work with words remain relatively constant.</description>
	</item>
	<item>
		<title>Proofreader&apos;s and Editor&apos;s Symbols</title>
		<link>http://tc.eserver.org/21581.html</link>
		<guid>http://tc.eserver.org/21581.html</guid>
		<description>The following marks are standard proofreading and editing marks. A professional proofreader puts a mark (usually a line or caret) in the line and writes the correction in the margin. An editor makes corrections within the line rather than in the margin (in part because an editor&apos;s changes are typically more extensive), which is why editors prefer to work with double-spaced copy.</description>
	</item>
	<item>
		<title>Tracking Reviewers&apos; Comments</title>
		<link>http://tc.eserver.org/10873.html</link>
		<guid>http://tc.eserver.org/10873.html</guid>
		<description>I had a manual under review by over 60 people. I posted a question about how to track all of their comments. Here is the summary. Thanks to everyone who responded. You all gave me a lot to think about. I realized as I got the comments that I left out a crucial piece of information...the manual went out to our managers and maintenance specialists in the field (we have offices all over the United States). Thus, we can&apos;t hold traditional meetings.</description>
	</item>
	<item>
		<title>Common Proofreading Symbols</title>
		<link>http://tc.eserver.org/10817.html</link>
		<guid>http://tc.eserver.org/10817.html</guid>
		<description>A list of symbols, their meaning, and an example of usage.</description>
	</item>
	<item>
		<title>Standard Editing Symbols</title>
		<link>http://tc.eserver.org/10716.html</link>
		<guid>http://tc.eserver.org/10716.html</guid>
		<description>Editing and proofreading symbols are used by editors and others for indicating text changes. The symbols are universally understood among most writers, editors, proofreaders, text processors, and printers.  </description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Reference/Editing.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>