Summary
This article describes the issues that are fixed in the Microsoft Word 2013 hotfix package that is dated February 27, 2013.
INTRODUCTION
Issues that this hotfix package fixes
-
Assume that you use Word 2013 to save a .docx file as an OpenDocument Format (ODF) file. When you open the ODF file, non-left-aligned paragraphs inside textboxes in the file are displayed incorrectly.
-
Assume that you use Word 2013 to open a Word document that contains a macro. When you execute the macro, a shape is added to the document in the location of the cursor. However, the shape should be added in a specific location.
-
Consider the following scenario:
-
You configure an East Asian language input method editor (IME) for Word 2013 on a Windows 8-based touch device.
-
You type some characters in a new Word document.
-
You touch the document to change the location of the cursor.
-
You type a new character or delete the character before the cursor.
In this scenario, the new character is displayed in the previous location of the cursor, or the character that is before the previous location of the cursor is deleted.
-
-
Consider the following scenario:
-
You install a Latin-script language pack such as the Indonesian, Igbo, Yoruba, or Hausa language pack.
-
You change the keyboard layout to the Latin-script language keyboard layout.
-
You use the keyboard to type a nonexistent word in Publisher 2013.
-
You run the spelling checker.
In this scenario, the English language spelling checker starts to run. Additionally, the "replace with" list in the Autocorrect Options dialog box for the nonexistent word is empty.
-
-
Consider the following scenario:
-
You open a word document in Reading mode in Word 2013.
-
You open a second word document, and the second document overlaps the first document.
-
You use the mouse wheel to scroll through the second document.
In this scenario, the screen flickers between the two documents.
-
More Information
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
There are no prerequisites for installing this hotfix package.
Restart requirement
You do not have to restart the computer after you install this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
Registry information
You do not have to make any changes to the registry after you install this hotfix.
File information
This hotfix package may not contain all the files that you must have to fully update a product to the latest build. This hotfix package contains only the files that you must have to resolve the issue that listed in this article.
The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.x86 Download information
File name |
File version |
File size |
Date |
Time |
Wordpia2013-kb2726937-fullfile-x86-glb.exe |
15.0.4481.1004 |
1,544,952 |
19-Feb-13 |
20:29 |
Microsoft Windows Installer .msp file information
File name |
File version |
File size |
Date |
Time |
Wordpia-x-none.msp |
Not Applicable |
315,392 |
19-Feb-13 |
16:25 |
Wordpia-x-none.msp
File name |
File version |
File size |
Date |
Time |
Microsoft.office.interop.word.dll |
15.0.4481.1004 |
940,632 |
17-Feb-13 |
13:55 |
x64
Download information
File name |
File version |
File size |
Date |
Time |
Wordpia2013-kb2726937-fullfile-x64-glb.exe |
15.0.4481.1004 |
1,544,224 |
20-Feb-13 |
2:57 |
Microsoft Windows Installer .msp file information
File name |
File version |
File size |
Date |
Time |
Wordpia-x-none.msp |
Not Applicable |
319,488 |
19-Feb-13 |
16:44 |
Wordpia-x-none.msp
File name |
File version |
File size |
Date |
Time |
Wordpia.dll |
15.0.4481.1004 |
940,632 |
17-Feb-13 |
14:06 |
References
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates