When you try to open a Word document on Mac document, Word stops opening. If you are faced with this issue and are willing to solve it, then follow the 3 solutions. If you have data loss problem after fixing the Word not opening issue, EaseUS Data Recovery Wizard for Mac can do you a favor.
On this page, we have collected three practical solutions that can help fix the 'Word Not Opening' error on Mac. And if you mistakenly removed a Word file on Mac, let reliable Mac file recovery software as recommended here for help. Check out how to fix the not opening Word file to accessible again:
Workable Solutions | Step-by-step Troubleshooting |
---|---|
Fix 1. Repair Disk | Open Disk Utility > Select the primary hard disk on Mac and select 'First Aid' > Click 'Run'...Full steps |
Fix 2. Remove Word Preference | Open 'Library' > Open 'Preferences' > Copy com.microsoft.Word.plist file to desktop...Full steps |
Fix 3. Open and Repair Word | Start Word > Click 'Open' on the File menu > Click 'Repair' on the Open button...Full steps |
Fix 4. Recover Lost Word | Run EaseUS Mac file recovery software > Scan mac drive > Restore lost Mac word file...Full steps |
'Word 2016 on my Mac won't open. It flashes immediately by double-clicking and then closes unexpectedly. I didn't do anything or any change. How to fix it if Microsoft Word won't open at all?'
Here, for example, in our “Replace With” box we’re using the text “ 2 1” and that tells Word to replace what it finds by placing the second grouping (the name Amelia) in the first position and the first grouping (the name Griggs) in the second position. Use a Backslash ( ) if You Need to Search for a Character That’s Also a Wildcard. Joins three things: the string in cell C2, a string with a comma and a space character, and the value in cell B2. The result is Andreas, Hauser. =CONCATENATE(B3, ' & ', C3) Joins three things: the string in cell B3, a string consisting of a space with ampersand and another space, and the value in cell C3. The result is Fourth & Pine. When Office cannot determine the SIP address for the contact, it calls the IContactManager.Lookup method to find the SIP by using the IM service. Here Office passes in the best data that it can find for the contact (for example, just the email address for the contact). The Lookup method asynchronously returns an AsynchronousOperation object.
In addition to this situation, most users are also faced with these errors:
- The application Microsoft Word quit unexpectedly
- Microsoft Word cannot be opened because of a problem. Check with the developer to make sure Microsoft Word works with this version of Mac OS X
As Microsoft Word is widely used among people, owning some basic Word troubleshooting is recognized as an essential skill. Today you're going to learn three tricks in solving Word not opening on Mac. The given workarounds are applicable to all Word editions such as 2003, 2007, 2010, 2013 2016.
1. Run Repair Disk Permissions
Step 1: On the 'Go' menu, click 'Utilities'. Start the Disk Utility program.
Step 2: Choose the primary hard disk drive for your computer. Then, click the 'First Aid' tab.
Step 3: Click 'Run' to repair the disk volume errors and permissions. When it finishes, click 'Done'.
2. Remove Word Preferences
![Missing Localized Strings Here Office For Mac 2016 Missing Localized Strings Here Office For Mac 2016](/uploads/1/1/9/8/119876815/382699158.jpeg)
Step 1: Open 'Library'. Usually, click 'GO' > 'Go to the folder', then type ~/Library
Step 2: Locate a file named as 'Preferences'.
Step 3: Find a file named com.microsoft.Word.plist. Move the file to the desktop.
Start Word, and check whether the problem still occurs.
If the problem still occurs, exit Microsoft Word, and then restore the 'com.microsoft.word.prefs.plist' file to its original location. Then, go to Step 4.
If the problem seems to be resolved, you can move the file to the trash.
Note: If you do not locate the file, the program is using the default preferences.
Step 4: Exit all Microsoft Office for Mac programs. Then, Click the Word icon. On the left, click 'Preferences'.
Step 5: Click 'File Locations'.
Step 6: Select 'User templates'.
Step 7: Locate the file that is named Normal, and move the file to the desktop.
You can also find the file named as Normal through this way: 'Library' > 'Application Support' > 'Microsoft' > 'Office' > 'User Templates' > 'Normal'
Start Word, and check whether the problem still occurs. If the problem seems to be resolved, you can move the 'Normal' file to the trash.
3. Try to Open and Repair Word
Step 1: Start Word. On the File menu, click 'Open'.
Step 2: In the Open dialog box, select the file that you want to open. Click the down arrow on the Open button, click 'Open' > 'Repair'.
Recover Deleted and Missing Word on Mac
Do not worry if the 'Word not opening' issue causes data loss disaster, you can recover unsaved Word document on Mac from its Temporary folder and AutoRecovery save. While for a deleted Word document on Mac, the easiest way of recovery is using a third-party Mac data recovery software.
EaseUS Data Recovery Wizard for Mac also recovers Word document that is missing, deleted or lost due to formatting, virus infection and other misoperation, and the best part of using the software to recover Word is being able to preview the file entirety.
Step 1. Select the location where your important Word documents were lost and click Scan button.
Step 2. EaseUS Data Recovery Wizard for Mac will start immediately a quick scan as well as a deep scan on your selected disk volume. Meanwhile, the scanning results will be presented in the left pane.
Step 3. By Path and Type, you can quickly filter the Word files you've lost earlier. Select the target files and click Recover Now button to get them back at once.
« Cleaner HTML using CSS |Main| Costs of running a software small business »
November 11, 2004
Localization on Mac OS X
Mac OS X has a fully-fledged and elegant localization infrastructure that enables software to be translated into multiple languages and shipped as a single convenient package to end users. In this article I don't rehash the material on localization that is already available on the web. I am specifically writing about what you would need to do to produce a localization of a Wincent product.
Background
This article assumes some prior knowledge, so if you don't yet know about the following topics you should probably do some background reading and make sure you have the appropriate tools first:
- General reading on internationalization:
- Apple's International Technologies page.
- Apple's Localization on Mac OS X page.
- Apple's Mac OS X System Overview: Internationalizing Your Application.
- StepWise article, Internationalizing Cocoa applications by mmalcolm Crawford.
- Internationalizing Cocoa Applications by Andrew Stone.
- Localization tools and resources (see Apple's Localization tools page to be sure that you get the latest versions; these links below last updated 8 April 2006):
- ADViewer 2.1 disk image: the text editor recommended by Apple for use in localization.
- AppleGlot 3.2 disk image.
- AppleGlot 3.2 User Guide (PDF).
- AppleGlot glossaries (FTP site).
Localization procedure for Wincent software
Whenever I prepare a final build for shipping, as a final step in the build process I use a collection of tools, including Apple's genstrings and nibtool utilities, nibtrans by Manfred Schwind and a modified version of stringsUtil by the OmniGroup, to produce a localization package that is made available for download on the corresponding product's download page.
Before you start work on a localization you should contact me to let me know that you are going to start work on it. Sometimes more than one person steps forward to do a localization, so it's useful to coordinate your efforts with other people and minimize duplication of effort.
By default, every localization pack includes one or more English localizable project folders ('English.lproj' or 'en.lproj') containing the unlocalized, English-language versions of the program resources. Sometimes there is more than one such folder because a given product may actually be comprised of various components, each with its own 'English.lproj' or 'en.lproj' folder. If you are localizing a product into a target language for the first time, make a copy of the English resources, rename the containing folders appropriately (for example, 'Spanish.lproj', 'Japanese.lproj' and so on), and perform the localization. You must localize every file in every component otherwise the localization will be incomplete.
In cases where a localization already exists for a given product, the build process will merge the new, unlocalized portions of the project into the existing localized resources. In this way you don't have to begin the localization process all over again from the beginning. Rather, you can do an incremental localization, translating only the new (unlocalized) additions. Where pre-existing localizations exist, the merged lproj folders awaiting incremental localization will be included in the downloadable localization pack. Look at each and every file and make sure that there are no new strings that need to be translated. When you send back the updated localization you should only send files to which you actually made changes; if you did not make any changes to a file then do not send it back (the easiest way to do this is probably to simply delete those files to which you did not make any changes). Likewise, if you updated the Japanese localization do not send back the other localizations as well.
Office For Mac 2016 Release
As a general rule localization packs contain string files and not nib files; this is to streamline the process and make incremental localization more straightforward. It is also necessary in some cases where the nib files depend on private frameworks which are not included in the standard Mac OS X install and which Interface Builder will refuse to open. It is important that when you provide translations that you pick wordings that are of approximately the same length as their untranslated counterparts. If the translations are too lengthy then they will not fit within the geometry of the user interface. I can make minor adjustments to the interface geometry, but in general it is best for the purposes of consistency if translations can be chosen which obviate the need to do this.
If you do decide to do a localization please make sure that it is complete. Merging localizations is a time-consuming process that takes a lot of work, so it is not very efficient to integrate partial localizations (and then updates to those localizations). This is why I ask that when you do an updated localization that you only send back the files which you have actually modified. If you do not have the time to do a full localization of every localizable file then you should not go ahead with the project. Fully localizing the project also means localizing the InfoPlist.strings files which are often overlooked; for example, the English words for 'copyright' and 'version' should be translated.
Missing Localized Strings Here Office For Mac 2016 Torrent
Summary
- Use a Unicode-aware text editor, such as ADViewer.
- Save '.strings' files with UTF-16 encoding, as per the Apple documentation.
- Save '.plist' files with UTF-8 encoding, as per the encoding attribute at the head of the file.
- Double check the encoding before you send back the localized files.
- Keep your translations roughly the same length as the original text.
- If you can, get a friend to double-check your translations.
- Localize all the files, including InfoPlist.strings files.
- Only submit complete localizations, not partial ones.
- If updating an existing localization, only send back the files which you actually modified.
- Send only the lproj folders for the specific language you are working on; do not send back the lproj folders for the other languages.
Publisher For Mac
Posted by wincent at November 11, 2004 02:08 AM