kb.8dh.de

27Aug/100

KB238810 – A list of features and settings that are affected in Word 2010 and Word 2007 when you change the default editing language in Office 2010 or the primary editing language in Office 2007

SUMMARY

loadTOCNode(1, 'summary');

Note In Microsoft Office 2010, we use the term "default editing language" instead of the term "primary editing language," which we use in Microsoft Office 2007. 

This article contains information about how to change the editing language in Office 2010 and Office 2007. This article also provides a list of the changes that occur in Word when you change the editing language. 

How to change the default editing language in Office 2010

  1. Open a Microsoft Office program. For example, open Word. 
  2. Click the File tab.
  3. Click Word Options.
  4. Click Language.
  5. In the Set the Office Language Preferences dialog box, under Choose Editing Languages, select the editing language that you want to use, click the name of the language that you want to be the default language, and then click Set as Default.
  6. Close all your Office 2010 programs, and then open them again for the change to take effect.

 How to change the primary editing language in Office 2007

  1. Click Start, click All Programs, click Microsoft Office, click Microsoft Office Tools, and then click Microsoft Office 2007 Language Settings.
  2. Click the Editing Languages tab.
  3. In the Primary editing language list, click the language in which you plan to do most of your work.

List of features and settings that are affected when you change the editing language settings

  1. The Normal template: When you will change the default editing language in Office 2010 or the primary editing language in Office 2007, your Normal template is replaced if the Normal template is incompatible with the language that you set as default. Some languages need certain specific settings in Normal template. Because of this, Word has to replace the existing Normal template with new Normal template. If you have customized the Normal template, you will lose these customizations.
  2. Bullets and numbering: In Word 2007, this setting shows native numbers or letters based on primary editing language. In Word 2010, this setting does not display native numbers.
  3. AutoFormat As You Type settings: When you change the default editing language in Office 2010 or the primary editing language in Office 2007, all the settings on the AutoFormat As You Type tab in the AutoCorrect dialog box are reset.
  4. Fonts and the Fonts dialog box: When you change the default editing language in Office 2010 or the primary editing language in Office 2007, the font will be set based on the default or primary language setting.
  5. Show/Hide option: When you change the default editing language in Office 2010 or the primary editing language in Office 2007, this option is affected for some languages in Word 2010 and Word 2007. For example, for the Japanese language, the Show/Hide option is enabled by default.
  6. Japanese Consistency Checker: When you change the default editing language in Office 2010 or the primary editing language in Office 2007, this option is be enabled when you set editing language to Japanese (Japan). This option appears on the Ribbon's Review tab.
  7. Chinese Translation: When you change the default editing language in Office 2010 or the primary editing language in Office 2007 to Simplified Chinese or to Traditional Chinese, you will see the group name "Chinese Translation" if you click the Ribbon's Review tab and then you click the Chinese conversion tab.
  8. Theme gallery: When you change the default editing language in Office 2010 or the primary editing language in Office 2007, your theme gallery is localized to the current editing language. Also, any localized themes are added to the gallery. 
  9. Create New Theme Fonts dialog box and Edit New Theme Fonts dialog box: When you change the default editing language in Office 2010 or the primary editing language in Office 2007 to an East Asian or to a Complex Script language, an East Asian text section or a Complex script section is displayed in the Create New Theme Fonts dialog box and the Edit New Theme Fonts dialog box. The respective default theme fonts are also pre-filled, and the Sample section shows the localized sample text.
  10. English Assistance: This feature is enabled when you change the editing language to Japanese. This provides an English explanation of the Japanese text. 

MORE INFORMATION

loadTOCNode(1, 'moreinformation');

For more information, visit the following Microsoft websites:

Office 2010 language options
(http://office.microsoft.com/en-us/language/)

Set the display and editing languages
(http://office.microsoft.com/en-us/access-help/set-the-display-and-editing-languages-HA010243503.aspx)
 

Change the default language for Office programs
(http://office.microsoft.com/en-us/onenote-help/change-the-default-language-for-office-programs-HA010356057.aspx)



APPLIES TO
  • Microsoft Office Word 2007
  • Microsoft Office Word 2007 (Home and Student version)
  • Microsoft Word 2010
27Aug/100

KB983097 – Error message when you try to preview a Word document, an Excel workbook, or a PowerPoint presentation in the Open dialog box: “This file can’t be previewed”

SYMPTOMS

loadTOCNode(1, 'symptoms');

Consider the following scenario:
  • You run one of the versions of Microsoft Word, of Microsoft Excel, or of Microsoft PowerPoint that are mentioned in the "Applies to" section.
  • You click the Microsoft Office Button or the File tab in Word, in Excel, or in PowerPoint and then click Open.
  • In the Open dialog box, you click Show the preview pane.
  • You take one of the following actions:
    • In Word, you select a Word document to preview.
    • In Excel, you select an Excel workbook to preview.
    • In PowerPoint, you select a PowerPoint presentation to preview.

In this scenario, a preview is not displayed. Instead, you receive an error message that resembles one of the following in the Preview pane:

In Microsoft Word:

This file can’t be previewed because of an error in the Microsoft Word previewer.

In Microsoft Excel:

This file can’t be previewed because of an error in the Microsoft Excel previewer.

In Microsoft PowerPoint:

This file can’t be previewed because of an error in the Microsoft PowerPoint previewer.

27Aug/100

KB229424 – WinRM times out and you receive an error message when you try to add a Mailbox server to an existing DAG

SYMPTOMS

loadTOCNode(1, 'symptoms');

When you try to add a new Microsoft Exchange Server 2010 Mailbox server to an existing Database Availability Group (DAG), the operation times out when it tries to install the Failover Clustering component. Additionally, you receive the following status message:
The task is installing the Windows Failover Cluster component on the server <SERVERNAME>.

When the time-out occurs, you receive the following error message:

Processing data for a remote command failed with the following error message: The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. For more information, see the about_Remote_Troubleshooting Help topic.

+ CategoryInfo : OperationStopped: (System.Manageme...pressionSyncJob:PSInvokeExpressionSyncJob) [], PSRemotingTransportException

+ FullyQualifiedErrorId : JobFailure

However, the installation of the Failover Clustering component continues and succeeds after several minutes. If you run the Add-DatabaseAvailabilityGroupServer task again, the task finishes successfully.

26Aug/100

KB237937 – Microsoft SQL Server compatibility with Single Label Domains, Disjointed Namespaces, and Discontiguous Namespaces

SUMMARY

loadTOCNode(1, 'summary');

This article describes the compatibility of Microsoft SQL Server with Single Label Domains, Disjoint Namespaces, and Discontiguous Namespaces.

26Aug/100

KB237938 – Microsoft System Center product compatibility with Single Label Domains, Disjointed Namespaces, and Discontiguous Namespaces

SUMMARY

loadTOCNode(1, 'summary');

This article describes the compatibility of Microsoft System Center products with Single Label Domains, Disjoint Namespaces, and Discontiguous Namespaces.

26Aug/100

KB237906 – Microsoft Biztalk Server compatibility with Single Label Domains, Disjointed Namespaces, and Discontiguous Namespaces

SUMMARY

loadTOCNode(1, 'summary');

This article describes the compatibility of Microsoft Biztalk Server with Single Label Domains, Disjoint Namespaces, and Discontiguous Namespaces.

26Aug/100

KB237936 – Microsoft Office Communications Server compatibility with Single Label Domains, Disjointed Namespaces, and Discontiguous Namespaces

SUMMARY

loadTOCNode(1, 'summary');

This article describes the compatibility of Microsoft Office Communications Server with Single Label Domains, Disjoint Namespaces, and Discontiguous Namespaces.

26Aug/100

KB232824 – Event ID 4107 or 11 is logged in the Application Log in Windows Vista or Windows Server 2008 and later

Symptom

loadTOCNode(1, 'symptoms');

On a computer that is running Windows 7 or Windows Server 2008 R2, an error that resembles the following is logged in the Application log:

Log Name: Application
Source: Microsoft-Windows-CAPI2
Date: Date and time
Event ID: 4107
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Computer name
Description:
Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab
(http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab)
> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

Or, on a computer that is running Windows Vista or Windows Server 2008, an error that resembles the following is logged in the Application log:

Log Name: Application
Source: Microsoft-Windows-CAPI2
Date: Date and time
Event ID: 11
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Computer name
Description:
Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab
(http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab)
> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

26Aug/100

KB223433 – An ODBC application may not run correctly in Windows Server 2003 SP2 if the application allocates a large block of a contiguous memory buffer

SYMPTOMS

loadTOCNode(1, 'symptoms');

Consider the following scenario:
  • You have a computer that is running an x86-based version of Windows Server 2003 Service Pack 2 (SP2).
  • You start an application that does the following:
    • The application allocates a large block of a contiguous memory buffer. For example, the application allocates a memory buffer that is more than 700 MB. 
    • The application uses the Open Database Connectivity (ODBC) driver to connect to a database.

In this scenario, the block of the contiguous memory buffer may not be allocated. Therefore, the application may not start. Or, random application failures occur after the application starts. 

Note When you run this application on a computer that is running Windows Server 2003 Service Pack 1 (SP1), this issue does not occur.

26Aug/100

KB230855 – On Windows 7, a WSD print job may not complete if the Windows client does not have a subscription to the printer

SUMMARY

loadTOCNode(1, 'summary');

If a Windows 7 client does not have a WSD subscription and a WSD print job is sent while the printer is in a "User Intervention Required" state, the job will not complete until the device is powered down or the spooler is restarted.ÂÂ