15,041
edits
No edit summary |
|||
| Line 1: | Line 1: | ||
The suggested backup strategy if you are using [http://www.microsoft.com/en/us/default.aspx MS Word]. | The suggested backup strategy if you are using [http://www.microsoft.com/en/us/default.aspx MS Word]. | ||
== Backup strategy == | == Before writing the long article == | ||
=== Backup strategy === | |||
Backup to different location: | Backup to different location: | ||
* {{Gd}} auto-backup solution: | * {{Gd}} auto-backup solution: | ||
| Line 10: | Line 11: | ||
* your friends: Send each revision to your good friends. | * your friends: Send each revision to your good friends. | ||
== | === How to avoid the word file corrupted === | ||
'''Save each revision to another file''' (the file naming rule ex: file_name_date.doc each day)! The larger file size and the more possible the file corrupted. | '''Save each revision to another file''' (the file naming rule ex: file_name_date.doc each day)! The larger file size and the more possible the file corrupted. | ||
* Troubleshooting: [http://errerrors.blogspot.com/2008/06/word-word2003-2002xp.html Word無法讀取此文件,此文件可能已損害。 (Word2003, 2002/XP)] | * Troubleshooting: [http://errerrors.blogspot.com/2008/06/word-word2003-2002xp.html Word無法讀取此文件,此文件可能已損害。 (Word2003, 2002/XP)] | ||
| Line 19: | Line 20: | ||
** Troubleshooting: [http://support.microsoft.com/?scid=kb%3Ben-us%3B827099&x=19&y=12 How to recover a lost file in Word 2007 or in Word 2003] | ** Troubleshooting: [http://support.microsoft.com/?scid=kb%3Ben-us%3B827099&x=19&y=12 How to recover a lost file in Word 2007 or in Word 2003] | ||
== | === How to avoid the word file using too much CPU resource === | ||
* The ''reviewing symbol'' always take many CPU resource. '''Save each revision to another file''' or decrease the amount of the reviewing symbols! | * The ''reviewing symbol'' always take many CPU resource. '''Save each revision to another file''' or decrease the amount of the reviewing symbols! | ||
== Before writing the technology article == | |||
* Search before writing | |||
* The suggested the solution/software has been used by yourself | |||
* OSS alternative? | |||