Improving Compatibility with Microsoft Office

From NeoWiki

Revision as of 11:33, 10 February 2006 (edit) Sardisson (Talk | contribs) m (er, link that whole page) ← Previous diff		Revision as of 06:31, 24 May 2006 (edit) (undo) ( | contribs) m (Copyedits) Next diff →
Line 1:		Line 1:
-	As much as we would all like th pretend Microsoft Office didn't exist, it is a fact of life that, at some point, everyone will have to exchange documents with Microsoft Office users. While NeoOffice is quite good at reading and writing Microsoft Office documents, it's not perfect (in large part because, unlike the native file formats of NeoOffice, the Office file formats are not publicly or freely available nor stable, so import and export has of the formats has to be reverse-engineered over and over again). This page presents a number of tips or "best practices" to use to ensure better compatibility with Microsoft Office formats.	+	As much as we would all like to pretend Microsoft Office doesn’t exist, it is a fact of life that at some point, everyone will have to exchange documents with Microsoft Office users. While NeoOffice is quite good at reading and writing Microsoft Office documents, it's not perfect (in large part because, unlike the native file formats of NeoOffice, the Office file formats are not publicly or freely available nor stable, so import and export has of the formats has to be reverse-engineered over and over again). This page presents a number of tips or "best practices" to use to ensure better compatibility with Microsoft Office formats.
	* As a first step, always ask your collaborator(s) or recipient(s) if they can handle the "OpenOffice.org" (or, when NeoOffice 2 arrives, OpenDocument) formats. It's not unheard of for two people using NeoOffice or OpenOffice.org to exchange documents using the imperfect MS Office formats because neither bothered to ask what formats the other could handle!		* As a first step, always ask your collaborator(s) or recipient(s) if they can handle the "OpenOffice.org" (or, when NeoOffice 2 arrives, OpenDocument) formats. It's not unheard of for two people using NeoOffice or OpenOffice.org to exchange documents using the imperfect MS Office formats because neither bothered to ask what formats the other could handle!
Line 10:		Line 10:
	* Set up defaults using [[Editing Default Styles|styles and templates]], e.g. a "Word Collaboration" template that contains all the font settings, styles, and so forth so you don't forget some setting in any particular document.		* Set up defaults using [[Editing Default Styles|styles and templates]], e.g. a "Word Collaboration" template that contains all the font settings, styles, and so forth so you don't forget some setting in any particular document.
-	* Remember to actually save the docment in the relevant MS Office format and to use the correct extension.	+	* Remember to actually save the document in the relevant MS Office format and to use the correct extension.
-	*: If you're exchaning documents with collaborators using Word 2001 or older on the classic Mac OS or in Classic under Mac OS X, you'll need to ensure the documents have the correct type and creator code in order for those applications to open the files. [http://www.geocities.com/sardisson/mac/index.html Add Microsoft HFS Codes] is one way of solving this problem.	+	*: If you're exchanging documents with collaborators using Word 2001 or older on the classic Mac OS or in Classic under Mac OS X, you'll need to ensure the documents have the correct type and creator code in order for those applications to open the files. [http://www.geocities.com/sardisson/mac/index.html Add Microsoft HFS Codes] is one way of solving this problem.
	* When writing Greek text, follow the instructions [[Problems_with_the_Symbol_font%2C_Greek_text%2C_or_bullets_in_Word_documents#Typing Greek text for Word 2004 compatibility|here]] if you exchange with Word 2004 users.		* When writing Greek text, follow the instructions [[Problems_with_the_Symbol_font%2C_Greek_text%2C_or_bullets_in_Word_documents#Typing Greek text for Word 2004 compatibility|here]] if you exchange with Word 2004 users.

---

Revision as of 06:31, 24 May 2006

As much as we would all like to pretend Microsoft Office doesn’t exist, it is a fact of life that at some point, everyone will have to exchange documents with Microsoft Office users. While NeoOffice is quite good at reading and writing Microsoft Office documents, it's not perfect (in large part because, unlike the native file formats of NeoOffice, the Office file formats are not publicly or freely available nor stable, so import and export has of the formats has to be reverse-engineered over and over again). This page presents a number of tips or "best practices" to use to ensure better compatibility with Microsoft Office formats.

• As a first step, always ask your collaborator(s) or recipient(s) if they can handle the "OpenOffice.org" (or, when NeoOffice 2 arrives, OpenDocument) formats. It's not unheard of for two people using NeoOffice or OpenOffice.org to exchange documents using the imperfect MS Office formats because neither bothered to ask what formats the other could handle!

• If the recipient doesn't need to edit the document, saving as a PDF (via either supported NeoOffice method or even extendedPDF) will preserve formatting, fonts, and layout and be compatible with nearly every computer on the planet.

• Use common (MS Office) fonts.

  Note, however, that the versions of the MS Office fonts that ship with Mac OS X are approaching 10 years old and do not support Unicode or most non-Roman, non-CJK scripts, unlike the versions of these fonts shipped with Windows or the most recent version of Office:Mac. If you work in non-Roman or non-CJK scripts, choose an appropriate free and open font set from our Alternative Fonts list and suggest your collaborator(s) do the same.

• Set up defaults using styles and templates, e.g. a "Word Collaboration" template that contains all the font settings, styles, and so forth so you don't forget some setting in any particular document.

• Remember to actually save the document in the relevant MS Office format and to use the correct extension.

  If you're exchanging documents with collaborators using Word 2001 or older on the classic Mac OS or in Classic under Mac OS X, you'll need to ensure the documents have the correct type and creator code in order for those applications to open the files. Add Microsoft HFS Codes is one way of solving this problem.

• When writing Greek text, follow the instructions here if you exchange with Word 2004 users.

Add other tips, and we'll eventually organize this a little more logically

See also

• Problems with the Symbol font, Greek text, or bullets in Word documents