Office 2008 mac os x compatibility

To print them on the Mac:. You do it exactly the same way in Windows, or see here for a more extensive pre-built list. With OS X, Apple changed some of the keystrokes reserved for the operating system and added some new ones. On each version of Mac OS, Word follows system convention. Some Mac keyboards do not have a Forward Delete key. You will strike it most often in tables: in a Table, Delete becomes " Clear " which removes the cell contents without removing the cells.

You may also like

Use Cut to delete the cells themselves. Back Delete will remove text within a cell but has no effect if more than one cell is selected. The Mac has an Option Key , Windows does not have an equivalent. Generally what you expect from the Option key will be on the Control Key in Windows. On Mac OS 9 , they are the same. One thing that will catch you out all the time is that on the Mac, Word adopts the Mac convention of having a Preferences command.


  • san andreas map editor mac;
  • pdf mehrere seiten trennen mac;
  • Footer Resource links.

It's the same thing, the tabs are exactly the same inside. Word on the Mac still has a Work menu you can put on your menu bar; this has been replaced by the Task Pane which is nowhere near as convenient in later versions of PC Word. In order to display a document in WYSIWYG mode, Word needs to know a lot about the capabilities of the printer the document will eventually be sent to. In Windows this is very simple: Word reads all the information it needs from the printer driver for the printer set as the Windows default. On the Mac, it attempts to do the same thing, but the mechanism is vastly more complex.

Look here for more detail.

Making software is a depressingly manual activity. Every line of code has to be planned, typed, and checked. There are more than 30 million of them in Microsoft Office. There simply was not enough time and money to bring all the features of PC Word across to the Mac. And some of them we wouldn't want , anyway! Most of the omissions are of interest only to solution developers:. On the PC, you can use characters with impunity: if the PC does not have the font, it will find the closest font that contains the character.

On the Mac, in Word and above, you can use the exact same range of characters because Word is running in Unicode; however, because you cannot embed the font in the document, you need to make sure that each character that you use exists in one or more of the Unicode fonts your recipient has. If in doubt, for PC compatibility, use only the fonts that Microsoft supplies. Microsoft includes a pack of fonts with Mac Office that have been very carefully hinted to display and print the same on the Mac as the same-named fonts do on the PC.

Although the Mac can happily use PC fonts, the rendering of those may be subtly different, particularly on the high-res Mac displays. Jim says "Office for Mac has a very nice feature to make font compatibility a cinch.

[] Microsoft Office for Mac with Service Pack 1 - Macintosh Repository

There is no work-around to the restrictions John mentioned. Fonts embedded by Windows Word are ignored. Code you write on the Mac will run on the PC if you are careful. Expect code you write on the PC in Word or above to generate compile- or run-time errors on the Mac. Active-X controls will not work on Macs. Some of the latest controls from won't work on a Mac. Developers should read George Clark's article for more detail.

ActiveX is not supported on the Mac at all. If you create userforms, use only the controls provided in the Forms Toolbar on the Mac, anything else you bring from the PC will generate an error when the user opens the document. Digital Signatures are not supported on the Mac, and neither is code signing. You will not be able to open a signed project in Mac Word. If the signature prevents you from changing a macro, the code will be execute-only on the Mac. AppleScript is not available on the PC. Word: mac. Every patch Tuesday, something changes.

Due to multiple bugs in the file path resolving and handling mechanism, templates in network directories should not be shared between PC Word and Mac Word. For a long and happy life, copy the templates locally to the user's My Templates folder on the Mac. Ribbon Customizations are not available in Mac Word.

They will be silently ignored, unless done in code, where they will blow up.

Share your voice

Generally Mac Office has a wider gamut, but Mac monitors have a very different gamma. Unless you are prepared to create color profiles and carefully color-match every device in the chain on both the PC and the Mac, just accept that colors are going to look quite different. It is expensive and time-consuming to fix this, and you will never get it perfect. Various commands in Mac Word exist only in the menu bar, which Mac Word still has, or on the toolbars that Mac Word still has.

Toolbars remain customizable in Mac Word. The same physical printer will often produce different results from the same document depending on whether the printer driver is on a Mac or a PC. If the printer driver is running on a Print Server, results will be closer but remember: the fonts are different!

Design for the Difference, Design for Re-Flow. While the unsupported apps are usually old versions of apps that have been updated in recent years, there are still a lot of people running them because they didn't wish to upgrade to the subscription model favoured by many software developers. Luckily we were able to solve the issue in Mojave, but we aren't expecting the same fix to work in Catalina. Find out how we were able to get Photoshop running again here: How to open apps that won't run in Mojave. While it was possible to get some problematic apps to work in Mojave, although they might have been buggy, many apps will be disabled when you upgrade to the new macOS Catalina.

This will apply to any app that contains bit code. You may also find you can't run some drivers that use kernel extensions, due to changes coming with Catalina. You should still be able to run apps that are unsigned, for now, but there will come a time when apps that aren't notarised by Apple will not run at all, for security reasons. For this reason we recommend that before updating you check that your apps will run in the new macOS, so it's a good thing you're here. Apple has a web page explaining why it is halting support for bit apps on the Mac.

Essentially, Apple believes these legacy apps won't offer a good user experience because they slow down your Mac. The company explains that bit apps can access more memory and therefore you can expect faster system performance. This isn't the first time Apple has ended support for bit apps - in the company ended support for bit apps in iOS We have further information for those who would like to read more about Apple's 'Not Optimized for your Mac' warning.

You may be hoping that the developer will update your app to make it compatible. You might want to drop them a line to plead with them to do so. This shouldn't be news to them, though. Apple has been warning developers of the move away from bit apps for a few years now. Similarly, you will have been seeing warnings about apps that are "not optimised for your Mac" or "This app needs to be updated by its developer to improve compatibility" for at least a year. Those developers who don't yet have bit versions of their apps will probably be working on the transition from bit.

If they aren't, it's probably time to consider switching to a more modern app.

Office 2008 Mac versus Office 2007 WIndows

Any developer yet to update their app to work in the new version of macOS is running out of time and we would guess isn't planning to do anything. On the other hand, most bit apps have newer bit versions available. It's likely that the developers would encourage you to update to them. Here are some of the most notable apps that you will need to update before you upgrade to Catalina. We'll go into more detail about each below. Even if an app you use is bit, as some of the apps mentioned above are, that doesn't mean that you won't experience problems with it.

You may also experience issues with bit apps if components that they require are not bit. This is the case with some Adobe apps, for example. It's not only third-party developers whose apps are still stuck in bit. Even Apple has a collection of older apps that will be compromised - so if you are still using them it might be time to update to a newer version, or to switch to something else.

This is because older formats or codecs may have been used to produce those media files. You should be able to convert these files to H. More on this below. If you have Aperture 3 which was released in it is bit, so you might be thinking it will still run. However, Apple ended development and support for Aperture back in and the company's support page indicates that "For technical reasons, Aperture will not run in future versions of macOS after macOS Mojave" and recommends that you update to Photos or Adobe Lightroom.

If you are still using older versions of Apple's iWork apps - that's Pages, Keynote and Numbers - you may need to upgrade. All of the iWork '09 applications from are bit. This could be an issue to those Mac users who prefer these legacy apps to the modern versions. If you have iWork 09 and want to update to the newer versions of Pages, Numbers and Keynote, you'll be pleased to learn that they are free on the Mac App Store and have been free since Read which Macs support Catalina.

Microsoft reveals details of Office 2008 for Mac

The versions are all bit apps and Microsoft dropped support for the suite back in October The Office apps weren't bit when they launched, but they did received bit update in version If you had Office and an Office subscription you would have received the update. If you didn't receive the update you may be able to download it here.

If you are still using the version of Office, perhaps it's time to upgrade to the latest version of Microsoft Office - read about the latest version of Office for Mac here , and buy it here.