When activated this command displays a separate Background Removal contextual tab and places a selection rectangle and magenta color over portions of the selected image. The selection rectangle determines, based on an algorithm, which area of the selected image will be retained once the background removal process is complete, whereas the magenta color indicates the areas that will be removed.
Users can manually adjust the position and size of the selection rectangle and also mark individual areas of an image to keep or remove;  it is also possible to delete a mark after an inadvertent selection or if it produces an undesired result.
After the background has been removed, users can apply various visual effects to the result image or wrap text in a document around it ; users can also crop the image since removing the background does not reduce its original size. The crop selection rectangle now grays out the portions of an image to be removed during a crop process and displays the result area in color, instead of completely removing all portions of an image outside of the selection rectangle from view as in previous versions of Office; images can now be repositioned underneath the selection rectangle while it is active.
By default, Office , like previous versions, automatically resizes images that are inserted into shapes, which can negatively affect their aspect ratio. To address this, images in shapes can now be cropped or resized after being inserted, and individual Fit and Fill options have been incorporated. The former option resizes the selected image so that the entire area of the crop selection rectangle or shape is filled, whereas the latter option resizes the image so that it is displayed within the selection rectangle or within a shape in its entirety; both options maintain the original aspect ratio of the selected image.
Images inserted into SmartArt diagrams can also be cropped, resized, or repositioned. Publisher and Word support OpenType features such as kerning , ligatures , stylistic sets , and text figures with fonts such as Calibri , Cambria , Corbel , and Gabriola.
Excel supports hardware accelerated chart drawing, and PowerPoint supports hardware accelerated animations, transitions, and video playback and effects; slideshow elements are now rendered as sprites, which are then composited with additional effects such as fades and wipes implemented using Pixel Shader 2. The functionality is exposed through a new Screenshot command on the Insert tab of the ribbon that, when clicked, presents individual options to capture either app windows or selections of content.
The former option presents open windows as thumbnails in a gallery on the ribbon that insert a screenshot of the selected window into the active app, while the latter option minimizes the currently active app, dims the screen, and presents a selection rectangle for users to create a screenshot by holding the main mouse button, dragging the selection rectangle to a desired area of the screen, and then releasing the button to automatically insert the selection as an image into the document.
Only windows that have not been minimized to the taskbar can be captured. After a screenshot has been inserted, various adjustments can be made. The SmartArt text pane now allows users to insert, modify, and reorder images and their associated text within a diagram, and new Move Up and Move Down commands on the ribbon facilitate the reordering of content. Images are automatically cropped when inserted into shapes within SmartArt diagrams to preserve their aspect ratio; users can also manually reposition images.
During the crop process, the layout of shapes in SmartArt diagrams is locked to prevent users from inadvertently modifying its position while making adjustments to an image. Of these, a new Picture category dedicated to the presentation of images includes over 30 diagrams, and the Organization Chart category includes 3 new diagrams. The Convert to Shapes command, a feature introduced in Office SP2 as a context menu option that turned SmartArt into a group of customizable shapes, is now featured as on option on the ribbon in both apps.
Additionally, in PowerPoint, it is possible to convert SmartArt diagrams into bulleted lists through a new Convert to Text option. Accessibility Checker can be accessed through the "Check for Issues" button on the Prepare for Sharing group on the Info tab of the Backstage view. Clicking the button opens a task pane with a list of accessibility issues discovered in the document and also provides suggestions to address these issues.
The Backstage view also reports accessibility issues in the Prepare for Sharing group so that they can be addressed before the document is shared with other users.
Translations for phrases or words are displayed within a tooltip, from which users can hear an audio pronunciation of the selected text provided by one of the Microsoft text-to-speech voices installed on a machine, copy the translation to the clipboard so that it can be inserted into another document, or view a definition provided by an online service if the selected text is a word.
Users can download various text-to-speech engines from Microsoft. Microsoft now offers conditional compilation support that differentiates between bit and bit, so sufficiently savvy programmers can write bit and bit ActiveX controls at the same time, but every single line of old code has to be examined and, in many cases, rewritten. If you have Web applications that work with Office, they may fall over and play dead, too. Even Microsoft has had trouble with SharePoint co-existing with bit Access.
Syncing Outlook 64 with Windows mobile phones may not work as expected. OneNote integration isn't working right -- even at this late date, nobody's entirely sure what integration problems bedevil the evil twin. Some of the supposed benefits of bit may be illusory at best. For example, if you create a bit Excel spreadsheet that's bigger than 2GB, anybody who needs to edit it -- or even look at it -- had better be running bit as well. Microsoft knows all about the bit problems, although the 'Softies hardly trumpet the shortcomings in their marketing material.
If you know where to look, you can find the whole story. For example, the official Microsoft Office Engineering blog puts it this way: Few people remember, but Office had a bit version.
It failed so badly Microsoft passed on a bit Office Office bit has all of the hallmarks of a traditional Microsoft "version 2. Wise folks will wait until version 3. This article, " Word to the wise: Avoid bit Office ," was originally published at InfoWorld.
Otherwise, Outlook and will not work on Windows 7. Before you install Exchange Server , we recommend that you review this topic to ensure your network, hardware, software, clients, and other elements meet the requirements for Exchange Also, make sure you understand the coexistence scenarios that are supported for Exchange and earlier versions of Exchange. To actually install Exchange , see Deploy new installations of Exchange. Supported coexistence scenarios for Exchange The following table lists the scenarios in which coexistence between Exchange and earlier versions of Exchange is supported.
Exchange version Exchange and earlier versions Not supported Exchange Supported with Update Rollup 11 for Exchange SP3 or later on all Exchange servers in the organization, including Edge Transport servers. Exchange Supported with Exchange Cumulative Update 10 or later on all Exchange servers in the organization, including Edge Transport servers.
Mixed Exchange and Exchange organization Supported with the following minimum versions of Exchange: Supported hybrid deployment scenarios for Exchange Exchange supports hybrid deployments with Office tenants that have been upgraded to the latest version of Office For more information about specific hybrid deployments, see Hybrid Deployment Prerequisites. Network and directory server requirements for Exchange The following table lists the requirements for the network and the directory servers in your Exchange organization.
Component Requirement Domain controllers All domain controllers in the forest need to be running one of the following versions of Windows Server: If Exchange is deployed in this configuration, and the network supports IPv4 and IPv6, all Exchange servers can send data to and receive data from devices, servers, and clients that use IPv6 addresses.
For more information, see IPv6 Support in Exchange Directory server architecture for Exchange The use of bit Active Directory domain controllers increases directory service performance for Exchange Note In multi-domain environments, on Windows Server domain controllers that have the Active Directory language locale set to Japanese ja-jp , your servers may not receive some attributes that are stored on an object during inbound replication.
For more information, see KB Installing Exchange on directory servers For security and performance reasons, we recommend that you install Exchange only on member servers and not on Active Directory directory servers. To learn about the issues you can face when installing Exchange on a directory server, see Installing Exchange on a domain controller is not recommended [WarningInstallExchangeRolesOnDomainController].
After Exchange is installed, changing its role from a member server to a directory server, or vice versa, isn't supported. Hardware requirements for Exchange For information about deploying Exchange in a virtualized environment, see Exchange Server virtualization.