Difference between revisions of "Documentation/FAQ/Writer/DocumentManagement/Files created in other applications do not always display in OOo exactly as they did when they were created. What can be done about it?"

From Apache OpenOffice Wiki
Jump to: navigation, search
(New page: {{DISPLAYTITLE: Files created in other applications do not always display in OpenOffice.org exactly as they did when they were created. Why is this, and what can be done about it?}} <sect...)
 
 
(One intermediate revision by one other user not shown)
Line 6: Line 6:
  
 
<section begin=answer/>
 
<section begin=answer/>
OpenOffice.org provides the best file filters currently on the market, allowing users to read and edit files from other applications. However, the OpenOffice.org filters do not support some features such as macros.
+
OpenOffice.org provides the best file filters currently on the market, allowing users to read and edit files from other applications. The OpenOffice.org filters support macros from [[Python as a macro language|Python]], [http://user.services.openoffice.org/en/forum/viewtopic.php?f=45&t=1829 BeanShell], and [[Documentation/DevGuide/Scripting/JavaScript Editor|JavaScript]].
  
 
One of the main goals of OpenOffice.org is to encourage the adoption of open and fully documented file formats and APIs so that in the future, users will never have a problem opening any file. However, until the OpenOffice.org file formats are fully adopted, users should keep in mind the following when opening, reading and editing files from other applications:
 
One of the main goals of OpenOffice.org is to encourage the adoption of open and fully documented file formats and APIs so that in the future, users will never have a problem opening any file. However, until the OpenOffice.org file formats are fully adopted, users should keep in mind the following when opening, reading and editing files from other applications:
* Hard formatting. Files which rely on hard formatting such as hard returns, hard page breaks, etc. rather than soft spaces, carriage returns, soft page breaks, or tab characters will yield better results.
+
* Hard formatting. Files which rely on hard formatting such as [http://en.wikipedia.org/wiki/Hard_return hard returns], [http://www.typographyforlawyers.com/?page_id=1734 hard page breaks], etc. rather than soft spaces, [http://www.typographyforlawyers.com/?page_id=1732 carriage returns], soft page breaks, or tab characters will yield better results.
 
* Fonts. Opening files from different applications which use uncommon fonts with few metric equivalents can give the impression that the file formatting is jumbled in OpenOffice.org. Formatting will be best maintained when importing documents using common fonts such as, Arial, Book Antiqua, Bookman Old Style, Century, Century Schoolbook, Courier New, Lucida, MS Mincho, Monotype Sorts, Symbol, and Times New Roman.
 
* Fonts. Opening files from different applications which use uncommon fonts with few metric equivalents can give the impression that the file formatting is jumbled in OpenOffice.org. Formatting will be best maintained when importing documents using common fonts such as, Arial, Book Antiqua, Bookman Old Style, Century, Century Schoolbook, Courier New, Lucida, MS Mincho, Monotype Sorts, Symbol, and Times New Roman.
* Unsupported features. Not all features are supported by the file filters, for example, macros, some Table of Contents functionality, some fields, and some footnotes functionality.
+
* Unsupported features. Not all features are supported by the file filters, for example, some Table of Contents functionality, some fields, and some footnotes functionality.
 
<section end=answer/>
 
<section end=answer/>
  
 
[[Category:Documentation/FAQ/Writer/DocumentManagement]]
 
[[Category:Documentation/FAQ/Writer/DocumentManagement]]

Latest revision as of 13:21, 1 July 2018


Files created in other applications do not always display in OpenOffice.org exactly as they did when they were created. Why is this, and what can be done about it?


OpenOffice.org provides the best file filters currently on the market, allowing users to read and edit files from other applications. The OpenOffice.org filters support macros from Python, BeanShell, and JavaScript.

One of the main goals of OpenOffice.org is to encourage the adoption of open and fully documented file formats and APIs so that in the future, users will never have a problem opening any file. However, until the OpenOffice.org file formats are fully adopted, users should keep in mind the following when opening, reading and editing files from other applications:

  • Hard formatting. Files which rely on hard formatting such as hard returns, hard page breaks, etc. rather than soft spaces, carriage returns, soft page breaks, or tab characters will yield better results.
  • Fonts. Opening files from different applications which use uncommon fonts with few metric equivalents can give the impression that the file formatting is jumbled in OpenOffice.org. Formatting will be best maintained when importing documents using common fonts such as, Arial, Book Antiqua, Bookman Old Style, Century, Century Schoolbook, Courier New, Lucida, MS Mincho, Monotype Sorts, Symbol, and Times New Roman.
  • Unsupported features. Not all features are supported by the file filters, for example, some Table of Contents functionality, some fields, and some footnotes functionality.
Personal tools