Re: I'm sure glad I didn't buy a Mac Mini!

George Graves wrote:
On Mon, 17 Mar 2008 21:49:36 -0700, Steve de Mena wrote
(in article <o_idnf5aLr191ELanZ2dnUVZ_i2dnZ2d@xxxxxxxxxxxx>):

George Graves wrote:
On Mon, 17 Mar 2008 12:32:32 -0700, Steve de Mena wrote
(in article <--6dnX3gkbjMWkPanZ2dnUVZ_rjinZ2d@xxxxxxxxxxxx>):

George Graves wrote:

The current version of Pages can
read documents written by ClarisWorks (which is an outdated,
discontinued app from the early 90s). Why can't new versions of Word
read docs made by old versions of Word?
It can. The problem was George trying to get an OLD VERSION of Word to understand the output of a new version of Word.
Except in that particular case, MS insists that the file formats are the same for the versions of Word in question. Sorry. Also if one writes a document in Word for Mac, and saves it as a current Word for Windows file, All ASCI Characters above 255 will be missing when the file is opened with a current version of Word on Windows (and vice-versa). These incomaptibilities are mostly caused because Windows font sets are incomplete and special characters have to be accessed from a special menu. On the Mac, Characters above ASCI 255 are available in each type face simply by pressing the option key and shift option keys as you type and are consistent through every application and every version of the OS and the applications running on it.
I just saved a document in OS X [Leopard 10.5.2 with Microsoft Office 2008 12.0.1] with extended characters, saved it as a Word for Windows DOC file, and opened it in Word 2003 (SP3) on Windows and it looked fine.

All the extended characters were intact.

No incompatibility detected.

Steve
They must have fixed it cross-platform because Word X (which I was using at the time of this example) doesn't.
Yes, starting with Windows 2004 for the Mac it fully supports Unicode.

Steve

You mean OFFICE 2004 for the Mac, do you not? :->

Yes, of course!

I find the new Office 2008 very slow to load. Bringing up Word takes 1 minute 27 seconds before I can type. After 50 or so seconds most is loaded, but not the menus. Any ideas why it is taking so long?

This is on a freshly booted MacBook Pro, 3 GB RAM, 2.33Ghz, Leopard 10.5.2, WD 320GB 5400rpm hard drive (90GB free). Other apps running: Safari, Mail, Vienna, Thunderbird. Activity monitor shows like 0 activity before I started Word.

Steve


Steve
.

Relevant Pages

  • Re: Im sure glad I didnt buy a Mac Mini!
    ... George Graves wrote: ... Also if one writes a document in Word for Mac, and saves it as a current Word for Windows file, All ASCI ... Characters above 255 will be missing when the file is opened with a current version of Word on Windows. ... These incomaptibilities are mostly caused because Windows font sets are incomplete and special characters have to be accessed from a special menu. ...
    (comp.sys.mac.advocacy)
  • Re: length of char in bits differs on Win/Linux and Mac
    ... You were just lucky on Windows with your algorithm, and you used the wrong encoding for reading on the Mac. ... because Java uses Unicode for all characters. ...
    (comp.lang.java.programmer)
  • Re: Something the Maccies never seem to post
    ... George Graves wrote: ... Oh, I know enough about Windows, ... You group all Mac users ... You just did by labeling me a Wintroll. ...
    (comp.sys.mac.advocacy)
  • Re: The Windows "software advantage"
    ... Josh McKee wrote: ... George Graves wrote: ... Particularly since Windows comes with a firewall and registry ... have over Mac OS X or Linux? ...
    (comp.sys.mac.advocacy)
  • Re: Im sure glad I didnt buy a Mac Mini!
    ... in Word for Mac, and saves it as a current Word for Windows file, All ... Characters above 255 will be missing when the file is opened with a ... I'd call MS and Apple were I you. ...
    (comp.sys.mac.advocacy)