1 / 3
Caption Text
2 / 3
Caption Two
3 / 3
Caption Three margin testing

Monday, May 14, 2012

10 Spelling Checker Secrets for Microsoft Word

http://www.computerworld.com/s/article/9225180/10_Spelling_Checker_Secrets_for_Microsoft_Word?source=rss_latest_content&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+computerworld%2Fnews%2Ffeed+%28Latest+from+Computerworld%29&utm_content=Google+Feedfetcher
 - Computerworld

10 Spelling Checker Secrets for Microsoft Word

These tips can prevent you from confusing 'advice' with 'advise,' stop Word from flagging acronyms, and make you look more literate.

Helen Bradley

March 14, 2012 (PC World)
You use Word's spelling checker every day, and probably just as often encounter some of the tool's puzzling behavior. Do you know how to get rid of a word that you mistakenly added to its dictionary, for instance, or how to hide the red wiggly lines that appear all over your document?
The following ten tricks will help you to work more efficiently in Word 2010, and they will even make you and your documents look smarter.
1. Control the 'Check Spelling as You Type' Feature
This default feature reviews spelling within your document as you work, indicating with a red wiggly line any words that are missing from the spelling checker's dictionary. The feature can be distracting, but it's easy to disable. To do so, choose File, Options, Proofing, click the Check spelling as you type checkbox to clear it and reverse the current setting, and then click OK.
2. Check Foreign-Language Spelling
Word isn't naturally bilingual, but you can train it to process more than one language at a time. Ordinarily, when you're working on a document that includes text in, say, French, Word likely won't recognize the other language if you've set your primary language to U.S. English; in this case, Word will add wiggly lines under the assorted foreign words, suggesting that they are all misspellings.
You can avoid that situation by setting Word to check the French text using a French word list. To arrange this, select the text in French (or whatever foreign language you're using), and click the Review tab on the Ribbon toolbar. Then click Language and choose Set Language in the Proofing group of buttons. The Language dialog box will appear. Here you should click the language to use for the selected text; the listed languages displaying checkmark icons are available for use in checking spelling. Click OK to finish.
3. Add Unusual Words to the Dictionary
If you know ahead of time that you will be using some unusual words, and if you do not want Word to report them as possible misspellings, you can add them to the dictionary.
Choose File, Options, Proofing, and click Custom Dictionaries. Click the custom.dic file--or the name of the dictionary to add the words to, if you are using a special dictionary--and click Edit Word List. Type a word, and click Add. When you're done, click OK to exit the dictionary.
Adding words one at a time is sensible if you have only a few. But if you have a long list of words to add, it's best to do so by editing the dictionary file itself.
First, from the Custom Dictionaries dialog box, make a note of the file-path entry that shows where the custom.dic file is located. Then launch a plain-text editor such as Notepad or WordPad, and use it to open the custom.dic file. Type or paste your words, one word per line, into the document and then save it. Word will automatically sort the items into alphabetical order when it next uses the file.
4. Remove Misspellings in the Spelling Checker
If you add a misspelled word to the dictionary by accident, Word won't identify it as misspelled until you remove it.
Choose File, Options, Proofing, and click Custom Dictionaries. Select the default dictionary in the list; typically this is the custom.dic file. Click Edit Word List to open the custom.dic dialog box, which contains a list of words you have added to Word's custom dictionary. Scroll down the list, click the errant word, and then click Delete and Close. In the future, if you use this misspelling in a document, Word will properly flag it as a mistake.
5. Determine What the Spelling Checker Checks
Depending on the type of work you do, you may discover that Word either finds errors where none exist, or fails to catch the embarrassing errors you do make. For some terms, such as email addresses, URLs, or items containing numbers, you can decide whether Word checks their spelling or leaves them alone.
To see the preferences that Word is currently configured to use, choose File, Options, Proofing. Here you can set preferences, such as 'Ignore words in UPPERCASE' and 'Ignore words that contain numbers'. If you don't want Word to report email addresses and URLs as misspellings, for example, click to enable the Ignore Internet and file addresses checkbox.
You can also disable Flag repeated words if you find Word's highlighting of repeated words annoying. When you are done, click OK to return to editing the document. These changes apply instantly, and will remain in place even after you shut down and restart Word.
6. Hide the Wiggly Underlines, Just This Once
If you like to work with 'Check spelling as you type' enabled, but wish to hide the wiggly underlines for one document only to reduce distractions, you can do so. This feature lets you control the visibility of the wiggly lines on a document-by-document basis, without disabling the spelling checker itself.
Choose File, Options, Proofing. Within the 'Exceptions for:' group of options, make sure the current document name appears in the box, and click Hide spelling errors in this document only. Click OK, and the document will stop showing wiggly underlines. You can still spelling-check the document, of course, by clicking the Review tab on the Ribbon toolbar and selecting Spelling & Grammar, or by pressing the shortcut key, F7.
7. Configure Text So That Word Doesn't Check It
Computer programming code, scientific data, and other specialized text often includes words that don't live in Word's dictionary, so the spelling checker frequently flags them. To disable spelling checks for such situations, first select the text in question. Then click the Review tab on the Ribbon toolbar, and choose Language, Set Proofing Language. Click the Do not check spelling or grammar checkbox, and click OK. Word will no longer proof the selected text, now or at any time in the future.
8. Use Multiple Dictionaries for Different Projects
Many businesses have their own language. For example, a doctor's office uses medical terminology, and a mining office uses mining jargon. If your business uses certain industry terms, it's convenient to have a dictionary of those terms on hand, to prevent Word from flagging them as misspellings.
You can either add the special terminology to your own custom.dic file or create a second dictionary file of the specialized terms. Maintaining a second file can be beneficial, as you can share it with other users without sharing your own personal custom.dic or needing to overwrite the other user's custom.dic file with your version.
To create a second dictionary, choose File, Options, Proofing, and click Custom Dictionaries. Click New, type a name for your dictionary file, and click Save. Now you can add words to the dictionary as detailed in Tip 3 above.
If you are using two dictionaries--both custom.dic and a second one of specialized words--you'll want Word to use words from both files when it makes suggestions for correcting the items it has flagged as spelling errors. To make sure that Word is configured to do this, click File, Options, Proofing, and confirm that the option Suggest from main dictionary only is disabled. If not, disable it and click OK.
9. Share a Custom Dictionary With Other Users
Once you've created a dictionary file, you can share it with other users so that they can employ it in their version of Word. To do so, in Windows Explorer, locate the .dic file you created, and then send the recipient a copy. The other person, on their computer, will need to place the file in the same folder as their own custom.dic file.
Then, to add the file to Word, the recipient should launch Word and choose File, Options, Proofing, Custom Dictionaries and click Add. The user should then locate and select the new .dic file, which will be in the folder that the dialog box points to, and click Open to add it to Word's Dictionary list.
10. Flag Words Misspelled in Context Only
In some situations you may find yourself using a word that's correctly spelled but incorrect in the context. Homophones, such as stationary and stationery, or advice and advise, can be confusing--all the more so because the spelling checker won't always flag their misuse. In addition, if you tend to overuse a word, you may want Word to alert you so that you can change it on certain occasions. A solution to both issues is to exclude the problematic words so that the tool will flag them.
To exclude one or more words, you must add them to the Word exclusion file, which is already created for you and installed with Word 2007 and 2010.
Start by searching for ExcludeDictionaryEN*.lex using Windows Search. In the search results, you will find multiple files, one for each English variant. The four-digit code in each filename tells you which .lex file belongs to which language variant. For example, 0409 is for the United States, and 0809 is for the United Kingdom. See Microsoft's site for the IDs for each locale; look for the number in the LCID Hex column to identify the files for the language variants you use.
In Windows Explorer, open the folder containing the exclusion files, right-click the ExcludeDictionaryEN*.lex file for the first language variant you use, and choose Open With, then WordPad. Type the words to exclude, one per line, and click Save. Repeat for any other language variants that you use. Close and reopen Word.
In the future, when you type any word that's in the exclude dictionary file, Word will flag it as a spelling error. Take care to click only 'Ignore Once'--not 'Ignore All' or 'Add To Dictionary'--to move past the word when you're using the 'Spelling and Grammar' dialog box. Otherwise, the spelling checker won't flag the word as a misspelling in the future.

10 essential performance tips for MySQL



http://www.computerworld.com/s/article/9227128/10_essential_performance_tips_for_MySQL?source=rss_latest_content&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+computerworld%2Fnews%2Ffeed+%28Latest+from+Computerworld%29&utm_content=Google+Feedfetcher
 - Computerworld

From workload profiling to the three rules of indexing, these expert insights are sure to make your MySQL servers scream

Baron Schwartz
May 14, 2012 (Infoworld)
As with all relational databases, MySQL can prove to be a complicated beast, one that can crawl to a halt at a moment's notice, leaving your applications in the lurch and your business on the line.
The truth is, common mistakes underlie most MySQL performance problems. To ensure your MySQL server hums along at top speed, providing stable and consistent performance, it is important to eliminate these mistakes, which are often obscured by some subtlety in your workload or a configuration trap.
[ To enhance the performance and health of your MySQL systems, check out our 10 essential MySQL tools for admins. | Learn how to master MySQL in the Amazon cloud. | Keep up to date on the key business tech news and insights with the InfoWorld Daily newsletter. Subscribe today! ]
Luckily, many MySQL performance issues turn out to have similar solutions, making troubleshooting and tuning MySQL a manageable task.
Here are 10 tips for getting great performance out of MySQL.
MySQL performance tip No. 1: Profile your workloadThe best way to understand how your server spends its time is to profile the server's workload. By profiling your workload, you can expose the most expensive queries for further tuning. Here, time is the most important metric because when you issue a query against the server, you care very little about anything except how quickly it completes.
The best way to profile your workload is with a tool such as MySQL Enterprise Monitor's query analyzer or the pt-query-digest from the Percona Toolkit. These tools capture queries the server executes and return a table of tasks sorted by decreasing order of response time, instantly bubbling up the most expensive and time-consuming tasks to the top so that you can see where to focus your efforts.
Workload-profiling tools group similar queries together into one row, allowing you to see the queries that are slow, as well as the queries that are fast but executed many times.
MySQL performance tip No. 2: Understand the four fundamental resourcesTo function, a database server needs four fundamental resources: CPU, memory, disk, and network. If any of these is weak, erratic, or overloaded, then the database server is very likely to perform poorly.
Understanding the fundamental resources is important in two particular areas: choosing hardware and troubleshooting problems.
When choosing hardware for MySQL, ensure good-performing components all around. Just as important, balance them reasonably well against each other. Often, organizations will select servers with fast CPUs and disks but that are starved for memory. In some cases, adding memory is cheap way of increasing performance by orders of magnitude, especially on workloads that are disk-bound. This might seem counterintuitive, but in many cases disks are overutilized because there isn't enough memory to hold the server's working set of data.
Another good example of this balance pertains to CPUs. In most cases, MySQL will perform well with fast CPUs because each query runs in a single thread and can't be parallelized across CPUs.
When it comes to troubleshooting, check the performance and utilization of all four resources, with a careful eye toward determining whether they are performing poorly or are simply being asked to do too much work. This knowledge can help solve problems quickly.
MySQL performance tip No. 3: Don't use MySQL as a queueQueues and queue-like access patterns can sneak into your application without your knowing it. For example, if you set the status of an item so that a particular worker process can claim it before acting on it, then you're unwittingly creating a queue. Marking emails as unsent, sending them, then marking them as sent is a common example.
Queues cause problems for two major reasons: They serialize your workload, preventing tasks from being done in parallel, and they often result in a table that contains work in process as well as historical data from jobs that were processed long ago. Both add latency to the application and load to MySQL.
MySQL performance tip No. 4: Filter results by cheapest firstA great way to optimize MySQL is to do cheap, imprecise work first, then the hard, precise work on the smaller, resulting set of data.
For example, suppose you're looking for something within a given radius of a geographical point. The first tool in many programmers' toolbox is the great-circle (Haversine) formula for computing distance along the surface of a sphere. The problem with this technique is that the formula requires a lot of trigonometric operations, which are very CPU-intensive. Great-circle calculations tend to run slowly and make the machine's CPU utilization skyrocket.
Before applying the great-circle formula, pare down your records to a small subset of the total, and trim the resulting set to a precise circle. A square that contains the circle (precisely or imprecisely) is an easy way to do this. That way, the world outside the square never gets hit with all those costly trig functions.
MySQL performance tip No. 5: Know the two scalability death trapsScalability is not as vague as you may believe. In fact, there are precise mathematical definitions of scalability that are expressed as equations. These equations highlight why systems don't scale as well as they should.
Take the Universal Scalability Law, a definition that is handy in expressing and quantifying a system's scalability characteristics. It explains scaling problems in terms of two fundamental costs: serialization and crosstalk.
Parallel processes that must halt for something serialized to take place are inherently limited in their scalability. Likewise, if the parallel processes need to chat with each other all the time to coordinate their work, they limit each other.
Avoid serialization and crosstalk, and your application will scale much better. What does this translate into inside of MySQL? It varies, but some examples would be avoiding exclusive locks on rows. Queues, point No. 3 above, tend to scale poorly for this reason.
MySQL performance tip No. 6: Don't focus too much on configurationDBAs tend to spend a huge amount of time tweaking configurations. The result is usually not a big improvement and can sometimes even be very damaging. I've seen a lot of "optimized" servers that crashed constantly, ran out of memory, and performed poorly when the workload got a little more intense.
The defaults that ship with MySQL are one-size-fits-none and badly outdated, but you don't need to configure everything. It's better to get the fundamentals right and change other settings only if needed. In most cases, you can get 95 percent of the server's peak performance by setting about 10 options correctly. The few situations where this doesn't apply are going to be edge cases unique to your circumstances.
In most cases, server "tuning" tools aren't recommended because they tend to give guidelines that don't make sense for specific cases. Some even have dangerous, inaccurate advice coded into them -- such as cache hit ratios and memory consumption formulas. These were never right, and they've gotten even less correct as time has passed.
MySQL performance tip No. 7: Watch out for pagination queriesApplications that paginate tend to bring the server to its knees. In showing you a page of results, with a link to go to the next page, these applications typically group and sort in ways that can't use indexes, and they employ a LIMIT and offset that causes the server to do a lot of work generating, then discarding rows.
Optimizations can often be found in the user interface itself. Instead of showing the exact number of pages in the results and links to each page individually, you can just show a link to the next page. You can also prevent people from going to pages too far from the first page.
On the query side, instead of using LIMIT with offset, you can select one more row than you need, and when the user clicks the "next page" link, you can designate that final row as the starting point for the next set of results. For example, if the user viewed a page with rows 101 through 120, you would select row 121 as well; to render the next page, you'd query the server for rows greater than or equal to 121, limit 21.
MySQL performance tip No. 8: Save statistics eagerly, alert reluctantlyMonitoring and alerting are essential, but what happens to the typical monitoring system? It starts sending false positives, and system administrators set up email filtering rules to stop the noise. Soon your monitoring system is completely useless.
I like to think about monitoring in two ways: capturing metrics and alerting. It's very important to capture and save all the metrics you possibly can because you'll be glad to have them when you're trying to figure out what changed in the system. Someday, a strange problem will crop up, and you'll love the ability to point to a graph and show a change in the server's workload.
By contrast, there's a tendency to alert way too much. People often alert on things like the buffer hit ratio or the number of temporary tables created per second. The problem is that there is no good threshold for such a ratio. The right threshold is not only different from server to server, but from hour to hour as your workload changes.
As a result, alert sparingly and only on conditions that indicate a definite, actionable problem. A low buffer hit ratio isn't actionable, nor does it indicate a real issue, but a server that doesn't respond to a connection attempt is an actual problem that needs to be solved.
MySQL performance tip No. 9: Learn the three rules of indexingIndexing is probably the most misunderstood topic in databases because there are so many ways to get confused about how indexes work and how the server uses them. It takes a lot of effort to really understand what's going on.
Indexes, when properly designed, serve three important purposes in a database server:
If you can design your indexes and queries to exploit these three opportunities, you can make your queries several orders of magnitude faster.
MySQL performance tip No. 10: Leverage the expertise of your peersDon't try to go it alone. If you're puzzling over a problem and doing what seems logical and sensible to you, that's great. This will work about 19 times out of 20. The other time, you'll go down a rabbit hole that will be very costly and time-consuming, precisely because the solution you're trying seems to make a lot of sense.
Build a network of MySQL-related resources -- and this goes beyond toolsets and troubleshooting guides. There are some extremely knowledgeable people lurking on mailing lists, forums, Q&A websites, and so on. Conferences, trade shows, and local user group events provide valuable opportunities for gaining insights and building relationships with peers who can help you in a pinch.
For those looking for tools to complement these tips, you can check out my MySQL configuration toolQuery Advisor tool, and Percona Monitoring Plugins. The configuration tool can help you generate a baseline my.cnf file for a new server that's superior to the sample files that ship with the server. The Query Advisor analyzes your SQL to help detect potentially bad patterns such as pagination queries (No. 7). Percona Monitoring is a set of monitoring and graphing plugins to help you save statistics eagerly and alert reluctantly (No. 8). All three are freely available.
Related articles
This story, "10 essential performance tips for MySQL," was originally published at InfoWorld.com. Follow the latest developments in data management at InfoWorld.com. For the latest developments in business technology news, follow InfoWorld.com on Twitter.
Read more about data management in InfoWorld's Data Management Channel.

Featured Post

Windows和Ubuntu双系统完全独立的安装方法

http://www.ubuntuhome.com/windows-and-ubuntu-install.html  | Ubuntu Home Posted by Snow on 2012/06/25 安装Windows和Ubuntu双系统时,很多人喜欢先安装windows,然...