Apache OpenOffice Wiki - User contributions [en]

Documentation/UserGuide/Migration Guide/Sharing Files

2016-03-14T16:02:28Z

Orcmid: Corrected table layout

{{Documentation/MigrationTOC|Migration=block|PrevNext=block|Prev=Documentation/OOoAuthors User Manual/Migration Guide/Introduction|Next=Documentation/OOoAuthors User Manual/Migration Guide/Importing Files}}
{{DISPLAYTITLE:Sharing Files with Microsoft Office Users }}
==Sharing in a Mixed application Environment==
{{Documentation/Note| Migration is people issue, not a software issue}}
Most migration difficulties occur because of incompatibility issues. No two document production applications will always have 100% fidelity, not even if those two applications are just different versions of the same programme. So one of the essential tasks in a successful migration is to identify infidelity risks and thus reduce user frustration. Often the problems that occur are not actually caused by the migration but are areas that have always been problematic but it was easier for users to work around than complain. Migration support desks will inevitably end up fielding calls that have nothing to do with the migration but has been a point of frustration for some time.

Many of these can be minimised by the adoption of some simple policies:
#Ensure all computers in the organisation have the same font set. This is especially important where there is a variation in Operating systems
#Put in place policies for document collaboration, for instance establish standard fonts for use in documents
#Make available a set of templates on the network that covers all document instances that there needs to be collaboration.
#Ensure that all machines use the same default template

== File formats ==
This section gives a simplified overview of Apache OpenOffice’s file format.

By default {{OOo}} stores its files in Open Document Format ([http://en.wikipedia.org/wiki/OpenDocument ODF]), ISO/IEC 26300. For details about ODF, see [http://books.evc-cit.info/book.php here].

Older versions of Microsoft Office files are stored in a proprietary format which is not human readable and not publicly documented. Newer versions of MS Office can now edit and save in ODF.

{| border=1 style="border-collapse:collapse;" cellpadding=3
|+File extensions for {{OOo}} 4.0.
! Document type
! Application
! Extension
! MS Office equiv

|-
| Text
| Writer
| odt
| doc, docx

|-
| Text Template
| Writer
| ott
| dot

|-
| Master Document
| Writer
| odm
| doc, docx

|-
| HTML document
| Writer
| html
| html

|-
| Spreadsheet
| Calc
| ods
| xls, xlsx

|-
| Spreadsheet Template
| Calc
| ots
| xst

|-
| Drawing
| Draw
| odg
| N/A

|-
| Drawing Template
| Draw
| otg
| N/A

|-
| Presentation
| Impress
| odp
| ppt, pptx

|-
| Presentation Template
| Impress
| otp
| pot

|-
| Formula
| Math
| odf
| N/A

|-
| Chart
| Chart
| odc
| N/A

|-
| Database
| Base
| odb
| mdb

|}

Although {{OOo}} can open Microsoft Office files. The reverse is ''not always'' true. Microsoft Office has various degrees of support for ODF, starting in Office 2007, but earlier versions: MSO '97, Office XP etc, are not able to open, read or write ODF documents. For this reason, it is essential, during Migration setup, to identify your document users and their needs to ensure the minimisation of compatibility issues. For example:

*Internal usage -- Use Native file format (OD*)
*External User Non AOO user - Editable -- Save as *.doc (2000, XP)
*External User AOO user - Editable -- Use Native file format (OD*)
*External User - Editable not needed -- Use PDF.
*Archive -- Always use ODF

Identifying these User needs and getting staff to work within those parameters should be part of a pre Migration training programme.

OpenOffice can not open or convert Microsoft Access files (.mdb) files directly, however it can access the data in the tables using DAO and ODBC. See the [[Documentation/OOoAuthors_User_Manual/Base_Guide|Database Guide]] for more information.}}

== Bulk conversion ==
To use {{OOo}} to convert a lot of files, click '''File''' '''> Wizards > Document Converter'''.

Before doing a bulk conversion of files, think about whether it is really necessary. Read this document right through to get an appreciation of the limitations of the conversion process.

== Opening files ==
=== Opening text documents ===
In addition to the native OpenDocument formats (.odt and .ott), {{OOo}} Writer can import the following text document formats:

{|border=1 style="border-collapse:collapse;" cellpadding=3
| Microsoft Word 6.0/95/97/2000/XP)
|(.doc, .dot)
|-
| Microsoft Word 2003
|XML
|-
| Microsoft Office XML
|docx
|-
| Microsoft Winword 5
|.doc
|-
| WordPerfect Document
|.wpd
|-
| WPS 2000/Office 1.0
|.wps
|-
| AportisDoc (Palm)
|.pdb
|-
| Pocket Word
| .psw
|-
|Rich Text format
| .rtf,
|-
|Text
|.txt, .csv

|}

When opening .HTM or .HTML files, OpenOffice.org customizes Writer for working with these files.

=== Opening spreadsheets ===
In addition to the native OpenDocument formats (.ods and .ots), OpenOffice.org Calc 2.0 can open the following spreadsheet formats:

{|border=1 style="border-collapse:collapse;" cellpadding=3
| Microsoft Excel 97/2000/XP (.xls, .xlw, .xlt)
| Rich Text Format (.rtf)

|-
| Microsoft Excel 4.x–5/95 (.xls and .xlw, .xlt)
| Text CSV (.csv and .txt)

|-
| Microsoft Excel 2003 XML (.xml)
| Lotus 1-2-3 (.wk1 and .wk1)

|-
| Data Interchange Format (.dif)
| StarCalc formats (.sdc, .vor)

|-
| dBase (.dbf)
| SYLK (.slk)

|-
| .htm and .html files including Web page queries
| Pocket Excel (pxl)

|-
| Quattro Pro 6.0 (.wb2)
|

|}

=== Opening presentations ===
In addition to the native OpenDocument formats (.odp and .otp), OpenOffice.org Impress 2.0 can open the following presentation formats:

{|border=1 style="border-collapse:collapse;" cellpadding=3
| Microsoft PowerPoint 97/2000/XP (.ppt, .pps)
| Computer Graphics Metafile (.cgm)

|-
| Microsoft PowerPoint 97/2000/XP Template (.pot)
| StarDraw, StarImpress (.sda, .sdd, .sdp, .vor)

|}
=== Opening graphics files ===
In addition to the native OpenDocument formats (.odg, and .otg), OpenOffice.org Draw 2.0 can open the following graphic formats:

BMP, JPEG/JPG, PCX, PSD, SGV, WMF, DXF, MET, PGM, RAS, SVM, XBM, EMF, PBM, PLT, SDA, TGA, XPM, EPS, PCD, PNG, SDD, TIF/TIFF, GIF, PCT, PPM, SGF, VOR

=== Opening formula files ===
In addition to OpenDocument Formula files, OpenOffice.org Math 2.0 can open the StarMath (.smf) and MathML (.mml) files.

<nowiki>When opening a Word document that contains an embedded equation editor object, select the [L] checkbox for </nowiki>''MathType to OpenOffice.org Math/OpenOffice.org Math to MathType'' in '''Tools''' > '''Options''' > '''Load/Save''' > '''Microsoft Office''' and the object will be automatically converted to an OpenOffice.org Math object.

== Saving files ==
=== Default file format ===

OpenOffice.org saves files in the OpenDocument format by default unless told otherwise. This default can be changed, for example if you always want to save as Microsoft Office files. To change the default file formats:

# Go to '''Tools > Options > Load/Save > General'''.<br>[[Image:doc_mig_options_loadsave_general.png|frameless|500px|'''Figure 1''':Choosing default formats for saving files]]
# In the Standard File Format section of this page, choose a document type (for example, “Text document”) and a file format from the '''Always save as''' list.
# Repeat for each document type as necessary.
# Click '''OK''' to save your changes.

{{Documentation/Note|If the option “Warn when not saving in OpenDocument or default format” is checked on the '''Options - Load/Save - General dialog''', a warning dialog about potential loss of formatting may be displayed. In most cases, no loss of formatting will occur, so you may find this warning annoying and choose to disable it.

The Java Runtime Environment is required to use the mobile device filters for AportisDoc (Palm), Pocket Word and Pocket Excel.}}

=== Export to PDF and XHTML ===
Each application has the ability to directly export to PDF (Portable Document Format). This industry-standard format for universal file compression and viewing is ideal for sending the file to anyone else to view using Acrobat Reader or any other PDF display program on any operating system.

You can export directly to PDF using the button on the toolbar next to the Printer icon, or by choosing '''File > Export as PDF''', which allows you to select some detailed options.

To export as XHTML, use '''File > Export''' and for File format choose '''XHTML''' In the dropdown box.

=== Saving files in other formats ===
To save files in different formats, use '''File > Save As '''and select a format from the '''File Type''' dropdown box.

[[Image:doc_mig_saveas.png|500px|'''Figure 2''': The OpenOffice.org Save As dialog, showing some of the Save formats]]

=== Writer can save to these file formats ===
In addition to its native formats, Writer can save in these formats:

OpenOffice.org Writer 1.x (.sxw, .stw)

Microsoft Word 97/2000/XP (.doc)

Microsoft Word 95 (.doc)

Microsoft Word 6.0 (.doc)

Microsoft Word 2003 XML (.xml)

Microsoft Pocket Word (.psw)

DocBook (.xml)

Aportis Doc (Palm) (.pdb)

Rich Text Format (.rtf)

StarWriter 5.0 (.sdw)

StarWriter Template (.vor)

StarWriter 4.0 (.sdw)

StarWriter 4.0 Template (.vor)

StarWriter 3.0 (.sdw)

StarWriter Template 3.0 (.vor)

Text (.txt)

Text Encoded (.txt)

HTML (.html; .htm)

{{Documentation/Note|The .rtf format is commonly used for transferring text files between applications, but you are likely to experience loss of formatting and images when the file is opened by Microsoft Office. The best way to pass a file in Writer to a Microsoft Word user is to save it as Microsoft Word 97/2000/XP (.doc).}}

=== Calc can save to these file formats ===
In addition to its native formats, Calc can save in these formats:

OpenOffice.org Calc 1.x (.sxc, .stc)

Microsoft Excel 97/2000/XP (.xls; .xlw)

Microsoft Excel 97/2000/XP Template (.xlt)

Microsoft Excel 95 (.xls; .xlw)

Microsoft Pocket Excel (.pxl)

Microsoft Excel 2003 XML (.xml)

Data Interchange Format (.dif)

dBase (.dbf)

SYLK (.slk)

Text CSV (.csv; .txt)

StarCalc formats (.sdc, .vor)

HTM and HTML files

=== Impress can save to these file formats ===
In addition to its native formats, Impress can save in these formats:

Microsoft PowerPoint 97/2000/XP (.ppt; .pps)

Microsoft PowerPoint 97/2000/XP Template (.pot)

StarDraw, StarImpress (.sda, .sdd, .vor)

Impress can also export to MacroMedia Flash (.swf) and any of the graphics formats as listed below for Draw.

=== Draw can save to these file formats ===
Draw can only save in its native and StarDraw formats, but it can export to:

BMP, EMF, EPS, GIF, JPEG, MET, PBM, PCT, PGM, PNG, PPM, RAS, SVG, SVM, TIFF, WMF, XPM

=== The HTML writer can save in these formats ===
HTML Document (.html; .htm)

OpenOffice.org 1.0 HTML Template (.stw)

OpenOffice.org 2.0 HTML Template (.oth)

StarWriter/Web 5.0 and 4.0 (.vor)

Text (OpenOffice.org Writer/Web) (.txt)

Text Encoded (OpenOffice.org Writer/Web) (.txt)

== Object Linking and Embedding (OLE) ==
To change the settings for Microsoft Office OLE objects, use '''Tools''' > '''Options''' > '''Load/Save''' > '''Microsoft Office'''.

Having all of these options checked allows embedded objects to be converted and thus be editable in both office suites.

For other OLE objects, it will depend on the machine where the file is being edited just as it does with Microsoft Office alone. Thus Windows application based OLE objects will not be editable in OpenOffice.org on a Linux machine, although the object will still be displayed correctly and can be resized.

[[Image:doc_mig_options_loadsave_vba.png|500px|'''Figure 3''': Choosing Load/Save VBA Properties]]

== Linked files ==
Cells copied from Excel and pasted special, linked and with RTF format, into Word are imported into Writer as a normal table. This means that when the document is imported, the link to the Excel file is lost.

Similarly when a chart is copied from Excel and pasted special, linked into Word, and then the file imported into Writer, the chart is imported as an embedded OLE object but is not converted into a Calc chart. On saving the file in Word format and then opening the file in Word and trying to edit the chart by double-clicking, it displays an error message.

{{Documentation/Caution|Links in Microsoft Office files between Word and Excel are lost when the Microsoft office files have been edited by OpenOffice.org.}}

== WordArt and Fontwork ==
The equivalent to Microsoft Office’s WordArt in OpenOffice.org is Fontwork. WordArt objects are imported as Fontwork objects; they may look slightly different on import. Fontwork objects are automatically exported to WordArt objects when the document is saved in a Microsoft Office format.

== Vector graphics ==
The basic shapes (lines, arrows, rectangles, ovals) all import and export without any problem. OpenOffice.org provides a greater degree of control over some properties than Microsoft Office does, so sometimes there will be changes when going from OpenOffice.org to Microsoft Office. Examples include the size of arrow heads, and line styles.

The Microsoft Office autoshapes, such as the smiley face, keep their special characteristics, for instance the ability to adjust the degree of the smile or frown on the smiley face.

Microsoft Office provides more shadow options than OpenOffice.org, so sometimes there will be a change in shadow appearance. Microsoft Office shadow styles 1, 2, 4, 6, 14, 17 and 18 are supported in OpenOffice.org. Horizontal and tapered shadows do not get imported and any 3D effect on the bottom left is ignored.

== Frames and text boxes ==
When frames or text boxes from Microsoft Office are imported into OpenOffice.org with linked text, the links are lost.

== Active content controls ==
These are the controls in Microsoft Office available on the Controls toolbar; they all import without a problem. However, as these controls typically require macros to be of use, they will be functionally useless in the absence of macros custom built for use in OpenOffice.org.

== Macros ==
OpenOffice.org cannot run Microsoft Office macros. Although the macro language is very similar, the underlying objects are quite different. To set whether OpenOffice.org keeps attached macros (so that they are still available for use in Microsoft Office) for Word, Excel and PowerPoint files, use '''Tools''' > '''Options''' > '''Load/Save''' > '''VBA Properties'''.

{{Documentation/Note|Opening a Microsoft Office file infected with a macro virus is quite safe in OpenOffice.org.}}

OpenOffice.org has the ability to record macros. It is better practice to use the application program interface (API).

== Import, export and sharing issues in text documents ==
=== Good practice in text documents ===
Some issues can be avoided simply by using good word-processing practice:

* Use character and paragraph styles rather than direct formatting.
* Use paragraph formatting for space before and after rather than hard returns, particularly in numbered or bulleted lists.
* Use paragraph text flow properties (for example, keep with next) rather than using manual page breaks.
* Do not use multiple tabs or spaces to align text – either set specific tab stops or better yet use a table.
* Use only commonly available fonts.

=== Compatibility settings in OpenOffice.org for the current document ===
The following settings change the way OpenOffice.org works with the current document so that it works more like Microsoft Office.

Use '''Tools''' > '''Options''' '''> OpenOffice.org Writer > Compatibility'''.

[[Image:doc_mig_options_writer_compat.png|500px|'''Figure 4''': Choosing compatibility options]]

==== Add paragraph and table spacing at tops of pages (in current document) ====
In Writer, with this setting unchecked, if a paragraph at the top of the page (or column) is formatted with space above then that space is ignored; whereas in Word the space above is included. Checking this option causes Writer to behave in the same way as Word.

==== Use OpenOffice.org 1.1 tabstop formatting ====
This setting specifies whether centered and right-aligned paragraphs containing tabs are formatted as a whole in the center or aligned to the right. If this checkbox is checked, only the text to the right of the last tab is aligned to the right, while the text to the left remains as is.

==== Use OpenOffice.org 1.1 line spacing ====
Writer uses the greater of the two spacings for above and below paragraphs; Word sums the two together. Uncheck this box to have Writer behave in the same way as Word.

=== Font and font spacing ===
Text effect animations are imported by Writer with the character attribute of blinking from Word files. For example “Marching red ants” simply becomes “blinking”.

Typically Word’s character spacing is tighter than Writer’s, so often Word will fit more characters to a line. It is also possible that the spacing between lines could be slightly different. The end result is that the page breaks may be in different places.

=== Tables ===
The author could find no issues with tables.

=== Mail merge documents ===
As OpenOffice.org has a different approach to data sources. On importing a Word document that is the main document for a mail merge, there is no connection with the data source. It is not just a matter of making that connection; each field needs to be reinserted. See the Mail Merge section in the chapter titled “Differences in use between Writer and Word”.

Also in Word you can have another Word document as a data source for a mail merge. There is no way of specifying a Word (or Writer) document as a data source in OpenOffice.org.

Writer does not have the option of suppressing blank lines when data fields are empty, so you need to use conditional fields.

<nowiki>Writer merge fields export as text with the name of the field between angle brackets, for example <Name>.</nowiki>

''Summary'': To work in a shared environment would require a separate file for each “main document”: one in Word format, the other in OpenOffice.org format. If you have a master mail merge document in Word format, it is probably easiest to paste the text into Writer and use the Writer mail merge wizard to recreate the mail merge from scratch.

=== Forms ===
==== Issues with forms created in Microsoft Office ====
A locked file in Microsoft Office imports unlocked into OpenOffice.org; that is, in design mode.

Text form fields import into OpenOffice.org as Input fields and so lose their type. For example, a text form field of type “number” or “date” will accept any text for input. In use a text form field in OpenOffice.org displays a dialog for entering the text. Exporting back to Microsoft Office, text form fields are changed into “Fillin” fields. The current date and time and calculation fields import as simple text.

Checkboxes import and export correctly.

Drop-down form fields import as Input List fields. Like text form fields in operation these display a dialog from which the user can select an option. On export back to Microsoft Office they return to drop-down form fields again.

==== Issues with forms created in OpenOffice.org ====
The controls are exported as active controls when there is a Microsoft Office equivalent. As Word does not have the same database functionality of OpenOffice.org and as the macros are not compatible, it would be very difficult to have one form that works in both environments using standard form controls.

''Summary'': To work in a shared environment with forms is not easy, but one workaround would be to use other fields like Input field and Input List. To insert these fields, use '''Insert''' > '''Fields''' > '''Other''' > '''Functions'''.

=== Footnotes, endnotes, tables of contents and indexes ===
Footnotes, endnotes and indexes all import / export correctly. Some issues have been found:

* The location of the endnotes may change (in Word the endnotes are placed before the index. In Writer they are always at the end of the document).
* Writer bibliographic entries become text in Word.
* A three-column index exported from Writer to Word as three columns but on re-import it was one column.
* On importing a Word file containing index entry fields, the index entry fields are imported but as fields to the left of the text rather than the field containing the text.

''Summary'': Working in a shared environment is possible with some minor issues.

=== Numbered paragraphs, outline numbering, cross-references ===
Numbered paragraphs, outline numbering, and cross-references import / export without a problem, except for references to numbered paragraphs:

* Cross-references to the numbers of numbered paragraphs that are not numbered using outline numbering do not work as Writer does not have this ability.
* Writer also does not have the ability to use relative numbering in its cross-references to numbers.
* Cross-references to chapter numbers do not have the same format as that displayed.

=== Page numbering ===
A quick and dirty approach in Word for having a different first page (like a cover page) and then to have the numbering start on the second page but numbered as page 1 is to have a layout of different first page and setting the starting page to be zero. Unfortunately, on importing such a file into OpenOffice.org the page number on the second page is 2 instead of 1. To fix this problem in Writer:

# Create a page style for how the pages after the first page should look. Name it (for example) Convert1.
# Have the cursor in the first paragraph of the second page.
# '''Format > Paragraph > Text Flow'''.
# In the Breaks portion of the dialog, select the checkbox Insert.
# Check '''With Page Style'''.
# Choose the page style created in step 1.
# Leave the position as '''Before''' and set the page number to 1.

On exporting this document back to Word it will work, the only difference being that the document will have a section break at the end of the first page. Documents created with section breaks like this in Word will work fine importing and exporting with Writer. There is one difference with Word: now there will be a blank page between the cover page and the next page when printed (or print previewed).

In the author’s testing a document with different formats for odd and even page numbering, the odd page numbers were imported as the text of the first odd page rather than as a field.

''Summary'': For some documents a little work maybe required to fix up the page numbering on importing to Writer. Once “fixed” the page numbering of the documents will import / export without a problem.

=== Date and time fields ===
Word’s CreateDate and SaveDate fields do not get imported with the same formats. For example, if the fields in the Word document have a format that includes time, then this information is not displayed by default. To include time in the format:

'''Right-click''' on the field > '''Fields''' > scroll to the bottom of the Formats listbox > '''Additional formats >''' in format code add HH:MM:SS

On export the SaveDate / DocInformation:Modified is exported as text.

Writer’s Time Fixed and Date Fixed fields get exported as text.

=== Importing Word fields ===

{|border=1 style="border-collapse:collapse;" cellpadding=3
|+Imported Word fields conversion
! Word field:
! Writer converts to:

|-
| ASK
| Input field

|-
| AUTHOR
| DocInformation:Created

|-
| AUTONUM
| Number Range AutoNr

|-
| AUTONUMLGL
| Number range AutoNr

|-
| AUTONUMOUT
| Number range AutoNr

|-
| COMMENTS
| DocInfomation:Comments

|-
| CREATEDATE
| DocInformation:Created

|-
| DATE
| Date

|-
| EDITTIME
| DocInformation:Modified

|-
| FILENAME
| File name

|-
| FILLIN
| Input field

|-
| HYPERLINK
| (as a hyperlink)

|-
| INFO xxx
| DocInformation:xxx

|-
| KEYWORDS
| DocInformation:Keywords

|-
| LASTSAVEDBY
| DocInformation:Modified

|-
| MACROBUTTON
| (the name of the macro?)

|-
| MERGEFIELD
| Mail merge fields (displayed as the name of the field)

|-
| MERGEREC
| Record number

|-
| NEXT
| Next record

|-
| NOTEREF
| Show variable

|-
| NUMCHARS
| Statistics (with select = Characters)

|-
| NUMPAGES
| Statistics (with select = Pages)

|-
| PAGE
| Page numbers

|-
| PAGEREF
| Bookmarks (displayed as name of bookmark)

|-
| REVNUM
| DocInformation:Document number

|-
| SAVEDATE
| DocInformation:Modified

|-
| SEQ
| Number range

|-
| SET
| Set variable

|-
| SUBJECT
| DocInformation:Subject

|-
| TEMPLATE
| Templates

|-
| TIME
| Date

|-
| TITLE
| DocInformation:Title

|-
| TOC
| (Displays the table of contents)

|}

The following fields are not imported into OpenOffice.org (only the text that they displayed when last saved): <nowiki>=, IF, DOCPROPERTY, FILESIZE, LINK, LISTNUM, QUOTE, SECTION, SECTIONPAGES, STYLEREF, TOA, USERADDRESS, USERINITIALS, USERNAME.</nowiki>

The following fields are ignored on import: AUTOTEXT, AUTOTEXTLIST, BARCODE, BIDIOUTLINE, DOCVARIABLE, EQ, GOTOBUTTON, INCLUDETEXT, LISTNUM, MERGESEQ, PRINT, RD, SKIPIF, SYMBOL, TA, TC.

The Word field EDITTIME is mapped to Writer field DocInformation:Modified on import but the meaning has changed to the date and time last saved rather than how long the file has been open for editing.

== Import, export and sharing issues in spreadsheets ==
=== Form fields ===
Combo boxes, list boxes and checkboxes with links to spreadsheet cells all import and export properly, although due to font handling the number of rows displayed in list boxes may be slightly different. List boxes in Calc can either have multi-selection or not, whereas Excel has two multi-selection modes: multi and extend. In Excel a link from a multi-selection listbox to a cell is ignored (at least in Excel 2000; the author has not checked Excel XP). In Calc the link works, but if more than one item is selected, the cell’s value is set to #N/A.

Option buttons import into Calc, but the link with cells works differently. In Calc each option button has its own link to a cell, setting its value to true or false depending on whether the option is selected. In Excel the cell link returns the number of the selected option button. On exporting option buttons to Excel, the option buttons lose their radio operation; in other words, they are not grouped so that selecting one “unselects” the others.

Scroll bars and spinners are now implemented in Calc, but are not imported yet.

=== Array constants ===
Array constants are not available in OpenOffice.org. The workaround is to have the constant values in cells on a sheet and refer to them. Array constants used as parameters to a function in Excel are omitted when imported into Calc.

=== Optional parameters in formulas ===
Some formulas have more than one optional parameter at the end of the parameter list. In Excel it is possible to leave an optional parameter blank and specify a later parameter, but this is not possible in Calc. Formulas with optional parameters are not correctly imported into Calc.

=== Functions ===
==== Statistical, engineering and financial functions ====
In Excel some of the financial functions accept string parameters for dates; in OpenOffice.org they require a serial number, and thus they are not correctly imported into Calc.

==== Analysis ToolPak Functions ====
The function EFFECT provided by the Analysis ToolPak for Excel is converted to EFFECT_ADD in Calc and returns the same results.

==== Other functions not implemented / imported ====
Only three other functions are not imported: INFO, GETPIVOTDATA, and HYPERLINK. Hyperlinks are supported but not as a function; use the '''Hyperlink''' button on the Function bar.

=== DataPilot—Pivot Table ===
DataPilots are Calc’s equivalent to Excel’s Pivot Tables. However there are a number of limitations. Pivot tables import from Excel into Calc (although the cells do not have the PivotTable shading) but as soon as they are worked on these limitations become apparent. The limitations are:

* There is no PivotChart facility, but a DataPilot can be used as the data source for a chart.
* The user interface allows a maximum of 8 fields in the data, row or column areas. (An alternative interface which allows more is available from: [http://homepages.paradise.net.nz/hillview/OOo/ http://homepages.paradise.net.nz/hillview/OOo/] in a document called MyDataPilot.sxc.
* There is some ability to group data (for example, a date field grouping by week or quarter but not by month). The workaround is to create a new column with a formula for calculating the grouping, e.g. =Month().
* You can not define different formats for different fields.
* Calc can have formulas based on things like “Difference From” or “% of”, but can not have own custom fields (work around create new columns to calculate the desired values).
* The Application Program Interface specification is incomplete for writing macros that work with DataPilots—for example, the ability to control through another program, such as OpenOffice.org’s own macro language, BASIC, whether the tables have grand totals, or having access to DataPilots created from external data.

=== AutoFilter ===
AutoFilter imports and exports correctly with the required rows being hidden. However, there are a number of differences between Excel and Calc:

* There is only one AutoFilter active for a spreadsheet document at a time. The rows remain hidden but the drop-downs in the first row disappear on applying AutoFilter elsewhere.
* The remaining visible row numbers do not change color to warn that there is a filter in place.
* Error values do not show as an option in the drop down lists when cells in the column have errors.
* In the drop down lists, the equivalent to Excel’s “Custom” is called “Standard”.

=== Charts ===
Chart types that Excel provides but Calc does not:

* Bar of pie converts to a 2D – columns – normal.
* Pie of pie converts to a 2D – columns – normal.
* Radar filled converts to 3D – columns deep.
* Radar with markers – converts to 2D – net – normal but counterclockwise rather than Excel’s clockwise.

Other charting issues include:

* There are fewer axis options, such as no option for having an inverted y axis (negative at top towards positive at bottom).
* The data must be contiguous, with the labels in the first row or column.

=== Number formats ===
There is no “accounting” format (with the currency symbol at the left edge of the cell). A workaround would be to have another column to the left that contains the currency symbol.

<nowiki>There is no predefined option for bracketing negative numbers. Use a custom format such as “$#,##0.00_);[RED]($#,##0.00)”.</nowiki>

=== Grid lines ===
In Excel grid lines are a property of a worksheet; in Calc it is an application-wide option:

'''Tools > Options > OpenOffice.org Calc > View'''

== Import, export and sharing issues in presentations ==
=== Color gradients and borders ===
The author had not noticed the following changes, so this is a direct quote from ''StarOffice 7 Migration Guide'' by Sun.

Unlike Microsoft PowerPoint, StarOffice Impress does not support three-color gradients, double and triple borders, or round-dotted borders. To improve the results of the import, you have to make the necessary adjusts before import. Change three-color presets to similar two-color gradient fills and change double and triple border lines to a single border line with appropriate width. Round-dotted border lines that are mapped to rectangle-border closely resemble the original line style in PowerPoint, so manual editing should not be necessary.

=== Multimedia ===
Voice-over narration is not supported by Impress.

There appear to be no settings for multimedia custom animations, such as the ability to play a sound for the next slides.

=== Chart animations ===
There is no facility in Impress for “chart effects” as there is in PowerPoint, such as presenting a series or category at a time. On import the charts simply appear. A workaround is to have multiple copies of the chart with each one set up to display as desired.

=== Pack and Go ===
The Pack and Go feature in PowerPoint allowed a PowerPoint file to be split over several floppy disks and assured that all related files were included. This facility is not included in Impress, nor can Impress open such files.

=== Fields ===
Date fields are exported as text, so they do not automatically update.

=== Action settings and interaction ===
PowerPoint provides action settings for mouseover, but Impress does not have this option, only on mouse click, so mouseovers get mapped to mouse clicks. PowerPoint has an option for highlighting the object on mouse click or mouse over; Impress does not have this, so it gets ignored on import.

=== PowerPoint custom animations and Impress object effects ===
Table 3 shows how the custom animations and object effects are imported into Impress and exported to PowerPoint.

{|border=1 style="border-collapse:collapse;" cellpadding=3
|+Importing / exporting custom animations between PowerPoint and Impress
! PowerPoint
! Impress

|-
| Appear
| Appear

|-
| Blinds
| Fade Horizontally

|-
| Box
| Fade To Center

|-
| Checkerboard
| Checkerboard

|-
| Diamond
| Appear

|-
| Crawl
| Fly In From bottom

|-
| Dissolve
| Dissolve

|-
| Flash once
| Appear

|-
| Peek
| Short Fly In from Bottom

|-
| Random Bars
| Horizontal lines

|-
| Spiral
| Spiral Outward Clockwise

|-
| Split
| Close Vertical

|-
| Stretch
| Stretch Vertical

|-
| Strips
| Fade From Top Right

|-
| Swivel
| Rotate Horizontally

|-
| Wipe
| Cross-Fade From Top

|-
| Zoom
| Fade From Center

|-
| Random effects
| Vertical Lines

|}

=== PowerPoint—Impress slide transitions ===

{|border=1 style="border-collapse:collapse;" cellpadding=3
|+Table 4 shows how slide transitions are imported into Impress and exported to PowerPoint.
! PowerPoint
! Impress

|-
| Blinds Horizontal
| Venitian Blinds Horizontal

|-
| Blinds Vertical
| Venitian Blinds Vertical

|-
| Box In
| Box In

|-
| Box Out
| Box Out

|-
| Checkerboard Across
| Checkerboard Across

|-
| Checkerboard Down
| Checkerboard Down

|-
| Cover Down
| Cover Down

|-
| Cover Left
| Cover Left

|-
| Cover Right
| Cover Right

|-
| Cover Up
| Cover Up

|-
| Cover Left Down
| Cover Left-Down

|-
| Cover Right Down
| Cover Right-Down

|-
| Cover Left Up
| Cover Left-Up

|-
| Cover Right Up
| Cover Right-Up

|-
| Cut
| No effect

|-
| Cut Through Black
| No effect

|-
| Dissolve
| Dissolve

|-
| Fade Through Black
| Fade Through Black

|-
| Random Bars Horizontally
| Random Bars Horizontal

|-
| Random Bars Vertically
| Random Bars Vertical

|-
| Horizontal In
| Split Horizontal In

|-
| Horizontal Out
| Split Horizontal Out

|-
| Split Vertical In
| Split Vertical In

|-
| Split Vertical Out
| Split Vertical Out

|-
| Strips Left Down
| Fade From Top Right

|-
| Strips Left Up
| Fade From Bottom Right

|-
| Strips Right Down
| Fade From Top Left

|-
| Strips Right Up
| Fade From Bottom Left

|-
| Uncover Down
| Uncover Down

|-
| Uncover Left
| Uncover Left

|-
| Uncover Right
| Uncover Right

|-
| Uncover Up
| Uncover Up

|-
| Uncover Left Down
| Uncover Left-Down

|-
| Uncover Left Up
| Uncover Left-Up

|-
| Uncover Right Down
| Uncover Right-Down

|-
| Uncover Right Up
| Uncover Right-Up

|-
| Wipe Down
| Wipe Down

|-
| Wipe Left
| Wipe Left

|-
| Wipe Right
| Wipe Right

|-
| Wipe Up
| Wipe Up

|-
| Random Transition
| Random Transition

|}

{{CCBY}}

Documentation/UserGuide/Migration Guide/Sharing Files

2016-03-14T16:01:01Z

Orcmid: Removed HWP as a supported format

{{Documentation/MigrationTOC|Migration=block|PrevNext=block|Prev=Documentation/OOoAuthors User Manual/Migration Guide/Introduction|Next=Documentation/OOoAuthors User Manual/Migration Guide/Importing Files}}
{{DISPLAYTITLE:Sharing Files with Microsoft Office Users }}
==Sharing in a Mixed application Environment==
{{Documentation/Note| Migration is people issue, not a software issue}}
Most migration difficulties occur because of incompatibility issues. No two document production applications will always have 100% fidelity, not even if those two applications are just different versions of the same programme. So one of the essential tasks in a successful migration is to identify infidelity risks and thus reduce user frustration. Often the problems that occur are not actually caused by the migration but are areas that have always been problematic but it was easier for users to work around than complain. Migration support desks will inevitably end up fielding calls that have nothing to do with the migration but has been a point of frustration for some time.

Many of these can be minimised by the adoption of some simple policies:
#Ensure all computers in the organisation have the same font set. This is especially important where there is a variation in Operating systems
#Put in place policies for document collaboration, for instance establish standard fonts for use in documents
#Make available a set of templates on the network that covers all document instances that there needs to be collaboration.
#Ensure that all machines use the same default template

== File formats ==
This section gives a simplified overview of Apache OpenOffice’s file format.

By default {{OOo}} stores its files in Open Document Format ([http://en.wikipedia.org/wiki/OpenDocument ODF]), ISO/IEC 26300. For details about ODF, see [http://books.evc-cit.info/book.php here].

Older versions of Microsoft Office files are stored in a proprietary format which is not human readable and not publicly documented. Newer versions of MS Office can now edit and save in ODF.

{| border=1 style="border-collapse:collapse;" cellpadding=3
|+File extensions for {{OOo}} 4.0.
! Document type
! Application
! Extension
! MS Office equiv

|-
| Text
| Writer
| odt
| doc, docx

|-
| Text Template
| Writer
| ott
| dot

|-
| Master Document
| Writer
| odm
| doc, docx

|-
| HTML document
| Writer
| html
| html

|-
| Spreadsheet
| Calc
| ods
| xls, xlsx

|-
| Spreadsheet Template
| Calc
| ots
| xst

|-
| Drawing
| Draw
| odg
| N/A

|-
| Drawing Template
| Draw
| otg
| N/A

|-
| Presentation
| Impress
| odp
| ppt, pptx

|-
| Presentation Template
| Impress
| otp
| pot

|-
| Formula
| Math
| odf
| N/A

|-
| Chart
| Chart
| odc
| N/A

|-
| Database
| Base
| odb
| mdb

|}

Although {{OOo}} can open Microsoft Office files. The reverse is ''not always'' true. Microsoft Office has various degrees of support for ODF, starting in Office 2007, but earlier versions: MSO '97, Office XP etc, are not able to open, read or write ODF documents. For this reason, it is essential, during Migration setup, to identify your document users and their needs to ensure the minimisation of compatibility issues. For example:

*Internal usage -- Use Native file format (OD*)
*External User Non AOO user - Editable -- Save as *.doc (2000, XP)
*External User AOO user - Editable -- Use Native file format (OD*)
*External User - Editable not needed -- Use PDF.
*Archive -- Always use ODF

Identifying these User needs and getting staff to work within those parameters should be part of a pre Migration training programme.

OpenOffice can not open or convert Microsoft Access files (.mdb) files directly, however it can access the data in the tables using DAO and ODBC. See the [[Documentation/OOoAuthors_User_Manual/Base_Guide|Database Guide]] for more information.}}

== Bulk conversion ==
To use {{OOo}} to convert a lot of files, click '''File''' '''> Wizards > Document Converter'''.

Before doing a bulk conversion of files, think about whether it is really necessary. Read this document right through to get an appreciation of the limitations of the conversion process.

== Opening files ==
=== Opening text documents ===
In addition to the native OpenDocument formats (.odt and .ott), {{OOo}} Writer can import the following text document formats:

{|border=1 style="border-collapse:collapse;" cellpadding=3
| Microsoft Word 6.0/95/97/2000/XP)
|(.doc, .dot)
|-
| Microsoft Word 2003
|XML
|-
| Microsoft Office XML
|docx
|-
| Microsoft Winword 5
|.doc
|-
| WordPerfect Document
|.wpd
|-
| WPS 2000/Office 1.0
|.wps
|-
| AportisDoc (Palm)
|.pdb
| Pocket Word
| .psw
|-
|Rich Text format
| .rtf,
|-
|Text
|.txt, .csv

|}

When opening .HTM or .HTML files, OpenOffice.org customizes Writer for working with these files.

=== Opening spreadsheets ===
In addition to the native OpenDocument formats (.ods and .ots), OpenOffice.org Calc 2.0 can open the following spreadsheet formats:

{|border=1 style="border-collapse:collapse;" cellpadding=3
| Microsoft Excel 97/2000/XP (.xls, .xlw, .xlt)
| Rich Text Format (.rtf)

|-
| Microsoft Excel 4.x–5/95 (.xls and .xlw, .xlt)
| Text CSV (.csv and .txt)

|-
| Microsoft Excel 2003 XML (.xml)
| Lotus 1-2-3 (.wk1 and .wk1)

|-
| Data Interchange Format (.dif)
| StarCalc formats (.sdc, .vor)

|-
| dBase (.dbf)
| SYLK (.slk)

|-
| .htm and .html files including Web page queries
| Pocket Excel (pxl)

|-
| Quattro Pro 6.0 (.wb2)
|

|}

=== Opening presentations ===
In addition to the native OpenDocument formats (.odp and .otp), OpenOffice.org Impress 2.0 can open the following presentation formats:

{|border=1 style="border-collapse:collapse;" cellpadding=3
| Microsoft PowerPoint 97/2000/XP (.ppt, .pps)
| Computer Graphics Metafile (.cgm)

|-
| Microsoft PowerPoint 97/2000/XP Template (.pot)
| StarDraw, StarImpress (.sda, .sdd, .sdp, .vor)

|}
=== Opening graphics files ===
In addition to the native OpenDocument formats (.odg, and .otg), OpenOffice.org Draw 2.0 can open the following graphic formats:

BMP, JPEG/JPG, PCX, PSD, SGV, WMF, DXF, MET, PGM, RAS, SVM, XBM, EMF, PBM, PLT, SDA, TGA, XPM, EPS, PCD, PNG, SDD, TIF/TIFF, GIF, PCT, PPM, SGF, VOR

=== Opening formula files ===
In addition to OpenDocument Formula files, OpenOffice.org Math 2.0 can open the StarMath (.smf) and MathML (.mml) files.

<nowiki>When opening a Word document that contains an embedded equation editor object, select the [L] checkbox for </nowiki>''MathType to OpenOffice.org Math/OpenOffice.org Math to MathType'' in '''Tools''' > '''Options''' > '''Load/Save''' > '''Microsoft Office''' and the object will be automatically converted to an OpenOffice.org Math object.

== Saving files ==
=== Default file format ===

OpenOffice.org saves files in the OpenDocument format by default unless told otherwise. This default can be changed, for example if you always want to save as Microsoft Office files. To change the default file formats:

# Go to '''Tools > Options > Load/Save > General'''.<br>[[Image:doc_mig_options_loadsave_general.png|frameless|500px|'''Figure 1''':Choosing default formats for saving files]]
# In the Standard File Format section of this page, choose a document type (for example, “Text document”) and a file format from the '''Always save as''' list.
# Repeat for each document type as necessary.
# Click '''OK''' to save your changes.

{{Documentation/Note|If the option “Warn when not saving in OpenDocument or default format” is checked on the '''Options - Load/Save - General dialog''', a warning dialog about potential loss of formatting may be displayed. In most cases, no loss of formatting will occur, so you may find this warning annoying and choose to disable it.

The Java Runtime Environment is required to use the mobile device filters for AportisDoc (Palm), Pocket Word and Pocket Excel.}}

=== Export to PDF and XHTML ===
Each application has the ability to directly export to PDF (Portable Document Format). This industry-standard format for universal file compression and viewing is ideal for sending the file to anyone else to view using Acrobat Reader or any other PDF display program on any operating system.

You can export directly to PDF using the button on the toolbar next to the Printer icon, or by choosing '''File > Export as PDF''', which allows you to select some detailed options.

To export as XHTML, use '''File > Export''' and for File format choose '''XHTML''' In the dropdown box.

=== Saving files in other formats ===
To save files in different formats, use '''File > Save As '''and select a format from the '''File Type''' dropdown box.

[[Image:doc_mig_saveas.png|500px|'''Figure 2''': The OpenOffice.org Save As dialog, showing some of the Save formats]]

=== Writer can save to these file formats ===
In addition to its native formats, Writer can save in these formats:

OpenOffice.org Writer 1.x (.sxw, .stw)

Microsoft Word 97/2000/XP (.doc)

Microsoft Word 95 (.doc)

Microsoft Word 6.0 (.doc)

Microsoft Word 2003 XML (.xml)

Microsoft Pocket Word (.psw)

DocBook (.xml)

Aportis Doc (Palm) (.pdb)

Rich Text Format (.rtf)

StarWriter 5.0 (.sdw)

StarWriter Template (.vor)

StarWriter 4.0 (.sdw)

StarWriter 4.0 Template (.vor)

StarWriter 3.0 (.sdw)

StarWriter Template 3.0 (.vor)

Text (.txt)

Text Encoded (.txt)

HTML (.html; .htm)

{{Documentation/Note|The .rtf format is commonly used for transferring text files between applications, but you are likely to experience loss of formatting and images when the file is opened by Microsoft Office. The best way to pass a file in Writer to a Microsoft Word user is to save it as Microsoft Word 97/2000/XP (.doc).}}

=== Calc can save to these file formats ===
In addition to its native formats, Calc can save in these formats:

OpenOffice.org Calc 1.x (.sxc, .stc)

Microsoft Excel 97/2000/XP (.xls; .xlw)

Microsoft Excel 97/2000/XP Template (.xlt)

Microsoft Excel 95 (.xls; .xlw)

Microsoft Pocket Excel (.pxl)

Microsoft Excel 2003 XML (.xml)

Data Interchange Format (.dif)

dBase (.dbf)

SYLK (.slk)

Text CSV (.csv; .txt)

StarCalc formats (.sdc, .vor)

HTM and HTML files

=== Impress can save to these file formats ===
In addition to its native formats, Impress can save in these formats:

Microsoft PowerPoint 97/2000/XP (.ppt; .pps)

Microsoft PowerPoint 97/2000/XP Template (.pot)

StarDraw, StarImpress (.sda, .sdd, .vor)

Impress can also export to MacroMedia Flash (.swf) and any of the graphics formats as listed below for Draw.

=== Draw can save to these file formats ===
Draw can only save in its native and StarDraw formats, but it can export to:

BMP, EMF, EPS, GIF, JPEG, MET, PBM, PCT, PGM, PNG, PPM, RAS, SVG, SVM, TIFF, WMF, XPM

=== The HTML writer can save in these formats ===
HTML Document (.html; .htm)

OpenOffice.org 1.0 HTML Template (.stw)

OpenOffice.org 2.0 HTML Template (.oth)

StarWriter/Web 5.0 and 4.0 (.vor)

Text (OpenOffice.org Writer/Web) (.txt)

Text Encoded (OpenOffice.org Writer/Web) (.txt)

== Object Linking and Embedding (OLE) ==
To change the settings for Microsoft Office OLE objects, use '''Tools''' > '''Options''' > '''Load/Save''' > '''Microsoft Office'''.

Having all of these options checked allows embedded objects to be converted and thus be editable in both office suites.

For other OLE objects, it will depend on the machine where the file is being edited just as it does with Microsoft Office alone. Thus Windows application based OLE objects will not be editable in OpenOffice.org on a Linux machine, although the object will still be displayed correctly and can be resized.

[[Image:doc_mig_options_loadsave_vba.png|500px|'''Figure 3''': Choosing Load/Save VBA Properties]]

== Linked files ==
Cells copied from Excel and pasted special, linked and with RTF format, into Word are imported into Writer as a normal table. This means that when the document is imported, the link to the Excel file is lost.

Similarly when a chart is copied from Excel and pasted special, linked into Word, and then the file imported into Writer, the chart is imported as an embedded OLE object but is not converted into a Calc chart. On saving the file in Word format and then opening the file in Word and trying to edit the chart by double-clicking, it displays an error message.

{{Documentation/Caution|Links in Microsoft Office files between Word and Excel are lost when the Microsoft office files have been edited by OpenOffice.org.}}

== WordArt and Fontwork ==
The equivalent to Microsoft Office’s WordArt in OpenOffice.org is Fontwork. WordArt objects are imported as Fontwork objects; they may look slightly different on import. Fontwork objects are automatically exported to WordArt objects when the document is saved in a Microsoft Office format.

== Vector graphics ==
The basic shapes (lines, arrows, rectangles, ovals) all import and export without any problem. OpenOffice.org provides a greater degree of control over some properties than Microsoft Office does, so sometimes there will be changes when going from OpenOffice.org to Microsoft Office. Examples include the size of arrow heads, and line styles.

The Microsoft Office autoshapes, such as the smiley face, keep their special characteristics, for instance the ability to adjust the degree of the smile or frown on the smiley face.

Microsoft Office provides more shadow options than OpenOffice.org, so sometimes there will be a change in shadow appearance. Microsoft Office shadow styles 1, 2, 4, 6, 14, 17 and 18 are supported in OpenOffice.org. Horizontal and tapered shadows do not get imported and any 3D effect on the bottom left is ignored.

== Frames and text boxes ==
When frames or text boxes from Microsoft Office are imported into OpenOffice.org with linked text, the links are lost.

== Active content controls ==
These are the controls in Microsoft Office available on the Controls toolbar; they all import without a problem. However, as these controls typically require macros to be of use, they will be functionally useless in the absence of macros custom built for use in OpenOffice.org.

== Macros ==
OpenOffice.org cannot run Microsoft Office macros. Although the macro language is very similar, the underlying objects are quite different. To set whether OpenOffice.org keeps attached macros (so that they are still available for use in Microsoft Office) for Word, Excel and PowerPoint files, use '''Tools''' > '''Options''' > '''Load/Save''' > '''VBA Properties'''.

{{Documentation/Note|Opening a Microsoft Office file infected with a macro virus is quite safe in OpenOffice.org.}}

OpenOffice.org has the ability to record macros. It is better practice to use the application program interface (API).

== Import, export and sharing issues in text documents ==
=== Good practice in text documents ===
Some issues can be avoided simply by using good word-processing practice:

* Use character and paragraph styles rather than direct formatting.
* Use paragraph formatting for space before and after rather than hard returns, particularly in numbered or bulleted lists.
* Use paragraph text flow properties (for example, keep with next) rather than using manual page breaks.
* Do not use multiple tabs or spaces to align text – either set specific tab stops or better yet use a table.
* Use only commonly available fonts.

=== Compatibility settings in OpenOffice.org for the current document ===
The following settings change the way OpenOffice.org works with the current document so that it works more like Microsoft Office.

Use '''Tools''' > '''Options''' '''> OpenOffice.org Writer > Compatibility'''.

[[Image:doc_mig_options_writer_compat.png|500px|'''Figure 4''': Choosing compatibility options]]

==== Add paragraph and table spacing at tops of pages (in current document) ====
In Writer, with this setting unchecked, if a paragraph at the top of the page (or column) is formatted with space above then that space is ignored; whereas in Word the space above is included. Checking this option causes Writer to behave in the same way as Word.

==== Use OpenOffice.org 1.1 tabstop formatting ====
This setting specifies whether centered and right-aligned paragraphs containing tabs are formatted as a whole in the center or aligned to the right. If this checkbox is checked, only the text to the right of the last tab is aligned to the right, while the text to the left remains as is.

==== Use OpenOffice.org 1.1 line spacing ====
Writer uses the greater of the two spacings for above and below paragraphs; Word sums the two together. Uncheck this box to have Writer behave in the same way as Word.

=== Font and font spacing ===
Text effect animations are imported by Writer with the character attribute of blinking from Word files. For example “Marching red ants” simply becomes “blinking”.

Typically Word’s character spacing is tighter than Writer’s, so often Word will fit more characters to a line. It is also possible that the spacing between lines could be slightly different. The end result is that the page breaks may be in different places.

=== Tables ===
The author could find no issues with tables.

=== Mail merge documents ===
As OpenOffice.org has a different approach to data sources. On importing a Word document that is the main document for a mail merge, there is no connection with the data source. It is not just a matter of making that connection; each field needs to be reinserted. See the Mail Merge section in the chapter titled “Differences in use between Writer and Word”.

Also in Word you can have another Word document as a data source for a mail merge. There is no way of specifying a Word (or Writer) document as a data source in OpenOffice.org.

Writer does not have the option of suppressing blank lines when data fields are empty, so you need to use conditional fields.

<nowiki>Writer merge fields export as text with the name of the field between angle brackets, for example <Name>.</nowiki>

''Summary'': To work in a shared environment would require a separate file for each “main document”: one in Word format, the other in OpenOffice.org format. If you have a master mail merge document in Word format, it is probably easiest to paste the text into Writer and use the Writer mail merge wizard to recreate the mail merge from scratch.

=== Forms ===
==== Issues with forms created in Microsoft Office ====
A locked file in Microsoft Office imports unlocked into OpenOffice.org; that is, in design mode.

Text form fields import into OpenOffice.org as Input fields and so lose their type. For example, a text form field of type “number” or “date” will accept any text for input. In use a text form field in OpenOffice.org displays a dialog for entering the text. Exporting back to Microsoft Office, text form fields are changed into “Fillin” fields. The current date and time and calculation fields import as simple text.

Checkboxes import and export correctly.

Drop-down form fields import as Input List fields. Like text form fields in operation these display a dialog from which the user can select an option. On export back to Microsoft Office they return to drop-down form fields again.

==== Issues with forms created in OpenOffice.org ====
The controls are exported as active controls when there is a Microsoft Office equivalent. As Word does not have the same database functionality of OpenOffice.org and as the macros are not compatible, it would be very difficult to have one form that works in both environments using standard form controls.

''Summary'': To work in a shared environment with forms is not easy, but one workaround would be to use other fields like Input field and Input List. To insert these fields, use '''Insert''' > '''Fields''' > '''Other''' > '''Functions'''.

=== Footnotes, endnotes, tables of contents and indexes ===
Footnotes, endnotes and indexes all import / export correctly. Some issues have been found:

* The location of the endnotes may change (in Word the endnotes are placed before the index. In Writer they are always at the end of the document).
* Writer bibliographic entries become text in Word.
* A three-column index exported from Writer to Word as three columns but on re-import it was one column.
* On importing a Word file containing index entry fields, the index entry fields are imported but as fields to the left of the text rather than the field containing the text.

''Summary'': Working in a shared environment is possible with some minor issues.

=== Numbered paragraphs, outline numbering, cross-references ===
Numbered paragraphs, outline numbering, and cross-references import / export without a problem, except for references to numbered paragraphs:

* Cross-references to the numbers of numbered paragraphs that are not numbered using outline numbering do not work as Writer does not have this ability.
* Writer also does not have the ability to use relative numbering in its cross-references to numbers.
* Cross-references to chapter numbers do not have the same format as that displayed.

=== Page numbering ===
A quick and dirty approach in Word for having a different first page (like a cover page) and then to have the numbering start on the second page but numbered as page 1 is to have a layout of different first page and setting the starting page to be zero. Unfortunately, on importing such a file into OpenOffice.org the page number on the second page is 2 instead of 1. To fix this problem in Writer:

# Create a page style for how the pages after the first page should look. Name it (for example) Convert1.
# Have the cursor in the first paragraph of the second page.
# '''Format > Paragraph > Text Flow'''.
# In the Breaks portion of the dialog, select the checkbox Insert.
# Check '''With Page Style'''.
# Choose the page style created in step 1.
# Leave the position as '''Before''' and set the page number to 1.

On exporting this document back to Word it will work, the only difference being that the document will have a section break at the end of the first page. Documents created with section breaks like this in Word will work fine importing and exporting with Writer. There is one difference with Word: now there will be a blank page between the cover page and the next page when printed (or print previewed).

In the author’s testing a document with different formats for odd and even page numbering, the odd page numbers were imported as the text of the first odd page rather than as a field.

''Summary'': For some documents a little work maybe required to fix up the page numbering on importing to Writer. Once “fixed” the page numbering of the documents will import / export without a problem.

=== Date and time fields ===
Word’s CreateDate and SaveDate fields do not get imported with the same formats. For example, if the fields in the Word document have a format that includes time, then this information is not displayed by default. To include time in the format:

'''Right-click''' on the field > '''Fields''' > scroll to the bottom of the Formats listbox > '''Additional formats >''' in format code add HH:MM:SS

On export the SaveDate / DocInformation:Modified is exported as text.

Writer’s Time Fixed and Date Fixed fields get exported as text.

=== Importing Word fields ===

{|border=1 style="border-collapse:collapse;" cellpadding=3
|+Imported Word fields conversion
! Word field:
! Writer converts to:

|-
| ASK
| Input field

|-
| AUTHOR
| DocInformation:Created

|-
| AUTONUM
| Number Range AutoNr

|-
| AUTONUMLGL
| Number range AutoNr

|-
| AUTONUMOUT
| Number range AutoNr

|-
| COMMENTS
| DocInfomation:Comments

|-
| CREATEDATE
| DocInformation:Created

|-
| DATE
| Date

|-
| EDITTIME
| DocInformation:Modified

|-
| FILENAME
| File name

|-
| FILLIN
| Input field

|-
| HYPERLINK
| (as a hyperlink)

|-
| INFO xxx
| DocInformation:xxx

|-
| KEYWORDS
| DocInformation:Keywords

|-
| LASTSAVEDBY
| DocInformation:Modified

|-
| MACROBUTTON
| (the name of the macro?)

|-
| MERGEFIELD
| Mail merge fields (displayed as the name of the field)

|-
| MERGEREC
| Record number

|-
| NEXT
| Next record

|-
| NOTEREF
| Show variable

|-
| NUMCHARS
| Statistics (with select = Characters)

|-
| NUMPAGES
| Statistics (with select = Pages)

|-
| PAGE
| Page numbers

|-
| PAGEREF
| Bookmarks (displayed as name of bookmark)

|-
| REVNUM
| DocInformation:Document number

|-
| SAVEDATE
| DocInformation:Modified

|-
| SEQ
| Number range

|-
| SET
| Set variable

|-
| SUBJECT
| DocInformation:Subject

|-
| TEMPLATE
| Templates

|-
| TIME
| Date

|-
| TITLE
| DocInformation:Title

|-
| TOC
| (Displays the table of contents)

|}

The following fields are not imported into OpenOffice.org (only the text that they displayed when last saved): <nowiki>=, IF, DOCPROPERTY, FILESIZE, LINK, LISTNUM, QUOTE, SECTION, SECTIONPAGES, STYLEREF, TOA, USERADDRESS, USERINITIALS, USERNAME.</nowiki>

The following fields are ignored on import: AUTOTEXT, AUTOTEXTLIST, BARCODE, BIDIOUTLINE, DOCVARIABLE, EQ, GOTOBUTTON, INCLUDETEXT, LISTNUM, MERGESEQ, PRINT, RD, SKIPIF, SYMBOL, TA, TC.

The Word field EDITTIME is mapped to Writer field DocInformation:Modified on import but the meaning has changed to the date and time last saved rather than how long the file has been open for editing.

== Import, export and sharing issues in spreadsheets ==
=== Form fields ===
Combo boxes, list boxes and checkboxes with links to spreadsheet cells all import and export properly, although due to font handling the number of rows displayed in list boxes may be slightly different. List boxes in Calc can either have multi-selection or not, whereas Excel has two multi-selection modes: multi and extend. In Excel a link from a multi-selection listbox to a cell is ignored (at least in Excel 2000; the author has not checked Excel XP). In Calc the link works, but if more than one item is selected, the cell’s value is set to #N/A.

Option buttons import into Calc, but the link with cells works differently. In Calc each option button has its own link to a cell, setting its value to true or false depending on whether the option is selected. In Excel the cell link returns the number of the selected option button. On exporting option buttons to Excel, the option buttons lose their radio operation; in other words, they are not grouped so that selecting one “unselects” the others.

Scroll bars and spinners are now implemented in Calc, but are not imported yet.

=== Array constants ===
Array constants are not available in OpenOffice.org. The workaround is to have the constant values in cells on a sheet and refer to them. Array constants used as parameters to a function in Excel are omitted when imported into Calc.

=== Optional parameters in formulas ===
Some formulas have more than one optional parameter at the end of the parameter list. In Excel it is possible to leave an optional parameter blank and specify a later parameter, but this is not possible in Calc. Formulas with optional parameters are not correctly imported into Calc.

=== Functions ===
==== Statistical, engineering and financial functions ====
In Excel some of the financial functions accept string parameters for dates; in OpenOffice.org they require a serial number, and thus they are not correctly imported into Calc.

==== Analysis ToolPak Functions ====
The function EFFECT provided by the Analysis ToolPak for Excel is converted to EFFECT_ADD in Calc and returns the same results.

==== Other functions not implemented / imported ====
Only three other functions are not imported: INFO, GETPIVOTDATA, and HYPERLINK. Hyperlinks are supported but not as a function; use the '''Hyperlink''' button on the Function bar.

=== DataPilot—Pivot Table ===
DataPilots are Calc’s equivalent to Excel’s Pivot Tables. However there are a number of limitations. Pivot tables import from Excel into Calc (although the cells do not have the PivotTable shading) but as soon as they are worked on these limitations become apparent. The limitations are:

* There is no PivotChart facility, but a DataPilot can be used as the data source for a chart.
* The user interface allows a maximum of 8 fields in the data, row or column areas. (An alternative interface which allows more is available from: [http://homepages.paradise.net.nz/hillview/OOo/ http://homepages.paradise.net.nz/hillview/OOo/] in a document called MyDataPilot.sxc.
* There is some ability to group data (for example, a date field grouping by week or quarter but not by month). The workaround is to create a new column with a formula for calculating the grouping, e.g. =Month().
* You can not define different formats for different fields.
* Calc can have formulas based on things like “Difference From” or “% of”, but can not have own custom fields (work around create new columns to calculate the desired values).
* The Application Program Interface specification is incomplete for writing macros that work with DataPilots—for example, the ability to control through another program, such as OpenOffice.org’s own macro language, BASIC, whether the tables have grand totals, or having access to DataPilots created from external data.

=== AutoFilter ===
AutoFilter imports and exports correctly with the required rows being hidden. However, there are a number of differences between Excel and Calc:

* There is only one AutoFilter active for a spreadsheet document at a time. The rows remain hidden but the drop-downs in the first row disappear on applying AutoFilter elsewhere.
* The remaining visible row numbers do not change color to warn that there is a filter in place.
* Error values do not show as an option in the drop down lists when cells in the column have errors.
* In the drop down lists, the equivalent to Excel’s “Custom” is called “Standard”.

=== Charts ===
Chart types that Excel provides but Calc does not:

* Bar of pie converts to a 2D – columns – normal.
* Pie of pie converts to a 2D – columns – normal.
* Radar filled converts to 3D – columns deep.
* Radar with markers – converts to 2D – net – normal but counterclockwise rather than Excel’s clockwise.

Other charting issues include:

* There are fewer axis options, such as no option for having an inverted y axis (negative at top towards positive at bottom).
* The data must be contiguous, with the labels in the first row or column.

=== Number formats ===
There is no “accounting” format (with the currency symbol at the left edge of the cell). A workaround would be to have another column to the left that contains the currency symbol.

<nowiki>There is no predefined option for bracketing negative numbers. Use a custom format such as “$#,##0.00_);[RED]($#,##0.00)”.</nowiki>

=== Grid lines ===
In Excel grid lines are a property of a worksheet; in Calc it is an application-wide option:

'''Tools > Options > OpenOffice.org Calc > View'''

== Import, export and sharing issues in presentations ==
=== Color gradients and borders ===
The author had not noticed the following changes, so this is a direct quote from ''StarOffice 7 Migration Guide'' by Sun.

Unlike Microsoft PowerPoint, StarOffice Impress does not support three-color gradients, double and triple borders, or round-dotted borders. To improve the results of the import, you have to make the necessary adjusts before import. Change three-color presets to similar two-color gradient fills and change double and triple border lines to a single border line with appropriate width. Round-dotted border lines that are mapped to rectangle-border closely resemble the original line style in PowerPoint, so manual editing should not be necessary.

=== Multimedia ===
Voice-over narration is not supported by Impress.

There appear to be no settings for multimedia custom animations, such as the ability to play a sound for the next slides.

=== Chart animations ===
There is no facility in Impress for “chart effects” as there is in PowerPoint, such as presenting a series or category at a time. On import the charts simply appear. A workaround is to have multiple copies of the chart with each one set up to display as desired.

=== Pack and Go ===
The Pack and Go feature in PowerPoint allowed a PowerPoint file to be split over several floppy disks and assured that all related files were included. This facility is not included in Impress, nor can Impress open such files.

=== Fields ===
Date fields are exported as text, so they do not automatically update.

=== Action settings and interaction ===
PowerPoint provides action settings for mouseover, but Impress does not have this option, only on mouse click, so mouseovers get mapped to mouse clicks. PowerPoint has an option for highlighting the object on mouse click or mouse over; Impress does not have this, so it gets ignored on import.

=== PowerPoint custom animations and Impress object effects ===
Table 3 shows how the custom animations and object effects are imported into Impress and exported to PowerPoint.

{|border=1 style="border-collapse:collapse;" cellpadding=3
|+Importing / exporting custom animations between PowerPoint and Impress
! PowerPoint
! Impress

|-
| Appear
| Appear

|-
| Blinds
| Fade Horizontally

|-
| Box
| Fade To Center

|-
| Checkerboard
| Checkerboard

|-
| Diamond
| Appear

|-
| Crawl
| Fly In From bottom

|-
| Dissolve
| Dissolve

|-
| Flash once
| Appear

|-
| Peek
| Short Fly In from Bottom

|-
| Random Bars
| Horizontal lines

|-
| Spiral
| Spiral Outward Clockwise

|-
| Split
| Close Vertical

|-
| Stretch
| Stretch Vertical

|-
| Strips
| Fade From Top Right

|-
| Swivel
| Rotate Horizontally

|-
| Wipe
| Cross-Fade From Top

|-
| Zoom
| Fade From Center

|-
| Random effects
| Vertical Lines

|}

=== PowerPoint—Impress slide transitions ===

{|border=1 style="border-collapse:collapse;" cellpadding=3
|+Table 4 shows how slide transitions are imported into Impress and exported to PowerPoint.
! PowerPoint
! Impress

|-
| Blinds Horizontal
| Venitian Blinds Horizontal

|-
| Blinds Vertical
| Venitian Blinds Vertical

|-
| Box In
| Box In

|-
| Box Out
| Box Out

|-
| Checkerboard Across
| Checkerboard Across

|-
| Checkerboard Down
| Checkerboard Down

|-
| Cover Down
| Cover Down

|-
| Cover Left
| Cover Left

|-
| Cover Right
| Cover Right

|-
| Cover Up
| Cover Up

|-
| Cover Left Down
| Cover Left-Down

|-
| Cover Right Down
| Cover Right-Down

|-
| Cover Left Up
| Cover Left-Up

|-
| Cover Right Up
| Cover Right-Up

|-
| Cut
| No effect

|-
| Cut Through Black
| No effect

|-
| Dissolve
| Dissolve

|-
| Fade Through Black
| Fade Through Black

|-
| Random Bars Horizontally
| Random Bars Horizontal

|-
| Random Bars Vertically
| Random Bars Vertical

|-
| Horizontal In
| Split Horizontal In

|-
| Horizontal Out
| Split Horizontal Out

|-
| Split Vertical In
| Split Vertical In

|-
| Split Vertical Out
| Split Vertical Out

|-
| Strips Left Down
| Fade From Top Right

|-
| Strips Left Up
| Fade From Bottom Right

|-
| Strips Right Down
| Fade From Top Left

|-
| Strips Right Up
| Fade From Bottom Left

|-
| Uncover Down
| Uncover Down

|-
| Uncover Left
| Uncover Left

|-
| Uncover Right
| Uncover Right

|-
| Uncover Up
| Uncover Up

|-
| Uncover Left Down
| Uncover Left-Down

|-
| Uncover Left Up
| Uncover Left-Up

|-
| Uncover Right Down
| Uncover Right-Down

|-
| Uncover Right Up
| Uncover Right-Up

|-
| Wipe Down
| Wipe Down

|-
| Wipe Left
| Wipe Left

|-
| Wipe Right
| Wipe Right

|-
| Wipe Up
| Wipe Up

|-
| Random Transition
| Random Transition

|}

{{CCBY}}

Talk:Uno/Effort/Binary/Extend Threading-Model

2016-03-04T03:27:51Z

Orcmid: Add possible correction to the broken link to a commentary by John Ousterhout

The comment by John Ousterhout is a reference to a bad link at pacbell.net. This presentation may be applicable: http://web.stanford.edu/~ouster/cgi-bin/papers/threads.pdf

Talk:Documentation/Building Guide AOO/Step by step

2016-02-22T17:04:29Z

Orcmid: Wondering about CygWin installation location

==Installation of CygWin==

I notice in the instructions for running that it is assumed cygwin is installed at the root of C:\, as recommended on the CygWin site. These days, with SSD drives at C:\ that might lead to too much consumption of space on that drive. I am facing that problem.

I will use a VM, and the guest image will be on D:\ although it appears as C:\ to the guest OS, of course. If it works well, I will attempt the same on my actual D:\ drive. I am hesitant to take that step at the moment because my Visual Studio and Microsoft Tools are all set up for Windows 10 development on the VM host using the Visual Studio 2015 Community Edition. I can't afford conflicts and PATH problems.

That's too much to add or discuss in the instructions. I'm mulling over something to add to have installation be more variable but not too challenging.

-- '[[User:Orcmid|Orcmid]] ([[User talk:Orcmid|talk]]) 17:04, 22 February 2016 (UTC)'

==Identification of Built Code==
<strike>At the very end of the Windows build information, under * Install > 3. Unpack archive without installation > * Start AOO by running:

the illustration is with AOO 4.0.1.

I assume what is meant is whatever the source is for, if building from an SVN tag or a Source release archive.
-- '[[User:Orcmid|Orcmid]] ([[User talk:Orcmid|talk]]) 19:54, 13 February 2016 (UTC)'</strike>
Clarified. Thanks,
-- '[[User:Orcmid|Orcmid]] ([[User talk:Orcmid|talk]]) 16:20, 15 February 2016 (UTC)'

Talk:Documentation/Building Guide AOO/Step by step

2016-02-15T16:20:15Z

Orcmid: /* Identification of Built Code */ Reflect correction made

==Identification of Built Code==
<strike>At the very end of the Windows build information, under * Install > 3. Unpack archive without installation > * Start AOO by running:

the illustration is with AOO 4.0.1.

I assume what is meant is whatever the source is for, if building from an SVN tag or a Source release archive.
-- '[[User:Orcmid|Orcmid]] ([[User talk:Orcmid|talk]]) 19:54, 13 February 2016 (UTC)'</strike>
Clarified. Thanks,
-- '[[User:Orcmid|Orcmid]] ([[User talk:Orcmid|talk]]) 16:20, 15 February 2016 (UTC)'

Talk:Documentation/Building Guide AOO/Step by step

2016-02-13T19:54:17Z

Orcmid: Minor tweak suggested.

==Identification of Built Code==
At the very end of the Windows build information, under * Install > 3. Unpack archive without installation > * Start AOO by running:

the illustration is with AOO 4.0.1.

I assume what is meant is whatever the source is for, if building from an SVN tag or a Source release archive.
-- '[[User:Orcmid|Orcmid]] ([[User talk:Orcmid|talk]]) 19:54, 13 February 2016 (UTC)'

User:TJFrazier

2016-01-23T21:51:11Z

Orcmid: Have the example math formula and the actual formatted formula agree

== Moving Day ==
Latest information: [[Moving Day]]

[[Template:Hurrah]]

{{Hurrah}}

=== Trouble examples (all now working) ===
'''Math trouble''' fixed by imacat (Thanks!)

<nowiki><math>\sum_{k=2}^N k^3</math></nowiki>
<math>\sum_{k=2}^N k^3</math>

magic FULLPAGENAME {{FULLPAGENAME}}

bad magic fullurl {{fullurl:{{FULLPAGENAME}}|action=edit}}

more magic localurl {{localurl:{{FULLPAGENAME}}|action=edit}}

possible fix $wgServer {{SERVER}}

I'm writing these messages, doing anything necessary inside the wiki, and working closely with those doing the external work (dumping, loading, re-addressing). The best place for questions is on the Talk page of [[Moving Day]] so everybody can see it, but feel free to contact me at the <s>ooo-dev -at- incubator</s> dev -at- openoffice.apache.org ML, or [[Special:EmailUser/TJFrazier|directly]] (if the wiki is up).

== T. J. Frazier (TJFrazier ([[User_talk:TJFrazier|Talk]] | [[Special:Contributions/TJFrazier|contribs]]), a.k.a. TJ, at AOO) ==

*Residence: Melbourne, Florida, USA.

*Background: Retired systems programmer (40 years, Control Data, KRONOS o/s). Professional nit-picker :-)

*Goal: become a developer (when I get broadband, Ubuntu, external hard disk, C++ textbook, . . . )
:[[User:TJFrazier|TJ]] 05:38, 29 January 2009 (UTC) Broadband scheduled Feb 2! Ubuntu to follow . . .
:[[User:TJFrazier|TJ]] 20:09, 18 February 2009 (UTC) Broadband is wonderful. Now examining Basic run-time source, for documentation purposes.
:[[User:TJFrazier|TJ]] 02:09, 31 July 2009 (UTC) Halfway thru big thick C++ book.
*Current OO.o activities: proof-reading and light copy-editing, mostly on Basic Guide and DevGuide Basic-related pages. I also file a lot of minor issues (if it's ''there'', it's supposed to ''work'', right?)
** Promoted to sysop, doing my homework re new accounts and wiki databases. 02:09, 31 July 2009 (UTC)
** Promoted to bureaucrat in preparation for the move to Apache. 11:42, 22 October 2011 (UTC)
** Apache committer and PPMC member (tj -at-), 31 October 2011.
** Resigned from PPMC membership, effective with TLP graduation, Fall, 2012.
*Lists: <s>dev, dev-web, dev-doc,</s> ODFAuthors; dev, issues at openoffice.apache.
== My Useful Links ==
[[Run_OOo_versions_parallel#Windows]]

[[:Category:Candidates_for_speedy_deletion]]

[[:Category:Wiki_Templates]]

==New accounts==
At least temporarily, new accounts can only be created by sysops. The instructions for sysops are at [http://www.mediawiki.org/wiki/Manual:Preventing_access#Restrict_account_creation MediaWiki].

User instructions are at [[New accounts]].

== Macros for use in Writer ==
=== Basic code for wikification ===
Basic code (now available as an extension) which may be useful for processing MediaWiki Export Filter output can be found on this subpage: [[User:TJFrazier/WikiBasic]]. Please report any problems or suggestions to me, on any of the above lists, or on a Talk page, or [[Special:EmailUser/TJFrazier|directly]].

See also [[User:Nnino|Nino Novak's]] very useful [[User:Nnino/ODT2Wiki|workflow guide]] for putting a manual on the wiki.
=== Reveal Codes ===
Preliminary design specs for an extension to provide this WordPerfect-like feature are on [[User:TJFrazier/Reveal Codes]]. Feedback welcome.
=== Toggle Case between Upper and Lower ===
04:05, 1 January 2012 (UTC) I've long had a macro to do this, but it had a problem when the target character was the first character of a portion (e.g., an ''italicized'' word). Now that I've fixed it, the source is available at [[User:TJFrazier/ToggleCaseUL]]. The particular virtue of this macro is that you don't have to select the character: just click in front of it. This is the raw version, with debugging notes commented out, but left in. It runs.

Notice that the same problem exists in the Writer GUI interface. Try changing the first character(s) of a portion (formatted word, ''e.g.'') by hand, ''without'' losing the formatting. Changing from <tt>Insert</tt> to <tt>Overtype</tt> mode works, but most of the other solutions don't. The way I did it through the API also works with the GUI (inserting the new character as the second character of the portion, then deleting the first character).

===Encryption Changing in 3.4===
22:43, 19 April 2012 (UTC) The code to provide SHA256 / AES encryption was added to OO.o 3.4 Beta without a GUI. As an alternative to changing the <tt>registrymodifications.xcu</tt> file by hand, a Basic macro to toggle these settings is now available at [[User:TJFrazier/Encryption]].
===Checking Curly Quotes===
20:35, 9 February 2013 (UTC) A macro to check for proper double curly quotes usage is available at [[User:TJFrazier/Quotes]].

== Sandbox ==
<s>for [[Documentation/BASIC_Guide/Other_Instructions]]</s><br />
fits better here: [[Documentation/BASIC_Guide/Strings_%28Runtime_Library%29]]

== '''<tt>Split</tt>''' and '''<tt>Join</tt>''' ==

The <tt>split</tt> and <tt>join</tt> functions are a specialized and convenient way to deal with ''delimited strings'': strings that contain multiple data items, each delimited by a separator character. Common examples are "comma-separated value" (CSV) strings used with spreadsheets, as well as URLs and path-names, which are delimited by slashes. The two functions are complementary: <tt>split</tt> breaks apart a string into an array; <tt>join</tt> builds a string from an array.

===Syntax===

Both <tt>split</tt> and <tt>join</tt> take the same type of operands.

string array = <tt>'''split'''</tt> (delimited string, delimiter character expression, number)
delimited string = <tt>'''join'''</tt> (string array, delimiter character expression)

The string array is usually defined as a <tt>variant</tt> without explicit dimensions (see the example below). <tt>Split</tt> will give the array proper dimensions.

The delimiter character expression is usually one literal character, but may be several characters.

===Example===
<source lang="oobas">
Option Explicit

Sub SplitAndJoin
Dim aAry() as Variant
Dim aFile() as Variant
Dim last as Integer 'last subscript, aAry
dim lf as Integer 'last subscript, aFile
Dim sOut as String
Dim sURL as String

sURL = ThisComponent.URL
Msgbox sURL,,"URL"

aAry() = split(sURL, "/")
REM A lazy way to show string array contents, one line per element.
Msgbox join(aAry(), chr(13)),,"aAry"

REM Change file extension to "zip".
last = Ubound(aAry())
aFile = split(aAry(last), ".")
lf = Ubound(aFile())
aFile(lf) = "zip"
Msgbox join(aFile(), chr(13)),,"aFile"
aAry(last) = join(aFile(), ".")
sOut = join(aAry(), "/") 'rebuild string
Msgbox sOut,,"New URL"

End Sub 'SplitAndJoin
</source>

Talk:Documentation/UserGuide/Writer/Intro/Content

2016-01-20T23:56:26Z

Orcmid: Add observation about the digital signature technique and the symbol

== Progressive Disclosure and Level/Nature of Details ==

I was looking at this page to become more familiar with the procedures here and how the development of content progresses.

Two questions came to mind.

* First, is it important to engage in progressive disclosure better? I was thinking of this because of the discussion of borders and also the introduction of the Web View on this page. I am thinking about newcomers to this documentation that do not have much technology-oriented knowledge. It would be useful for the more experienced to be able to deep dive, and for people who visit looking for more details to find them, without creating a situation where visitors may be unsettled by the terminology and concepts that are unknown to them. Has there been much thought to this?

* Secondly, I am puzzled by the use of "borders" for the framing that happens in the UI presentation of the document material. Since there are actual, drawn borders that can be introduced and shown, it would be good to use a different term for the all of the frames that delimit structural features of the document that are not part of the presentation of the document on a printer, in a PDF, etc. I would also not say too much about frames at the top level, but perhaps a cross-reference would be useful later.

--''[[User:Orcmid|Orcmid]] ([[User talk:Orcmid|talk]]) 23:29, 20 January 2016 (UTC)''

== Digital Signatures ==

* It would be useful to have a status line that shows the digital signature icon in place. I can provide one of those if necessary. It might be useful to indicate what happens when a signature is not verifiable.

* The note about digital signatures seems to be in the wrong place. We don't even know that the reader knows what one is or what is significant about this statement. An alternative explanation might be "The symbol shown indicates that the document was digitally signed when it was created and that signature has been verified for the document now being viewed." I think any further details need to be in a deeper section (and I don't know enough about this material to make a better suggestion just yet, but it should be in a common place about protections, signatures, and encryption for all of the AOO components).

--''[[User:Orcmid|Orcmid]] ([[User talk:Orcmid|talk]]) 23:56, 20 January 2016 (UTC)''

User:Orcmid

2016-01-20T23:41:34Z

Orcmid: Update the profile information a little.

Every time I work on a Wiki, there is always an User page to fill out.

All right. "Orcmid" is a nom de net of Dennis E. Hamilton.

Dennis is an individual member of the OASIS OpenDocument Format (ODF) TC. He is also one of the founding members of the OASIS ODF Interoperability and Conformance (OIC) TC. Oh, and he is an Initial Committer and PPMC Member of the Apache OpenOffice project. In August, 2015, Dennis became the Apache Vice President for Apache OpenOffice and that has him serve as the Chair of the Apache OpenOffice Project Management Committee.

There is more than you ever wanted to know about orcmid at my not-so-current[http://orcmid.com/construction/orcmid.htm What's an Orcmid?] page. Or maybe my [https://www.linkedin.com/in/orcmid LinkedIn] profile will suffice?

Talk:Documentation/UserGuide/Writer/Intro/Content

2016-01-20T23:29:55Z

Orcmid: Two questions on narrative level and terminology

I was looking at this page to become more familiar with the procedures here and how the development of content progresses.

Two questions came to mind.

* First, is it important to engage in progressive disclosure better? I was thinking of this because of the discussion of borders and also the introduction of the Web View on this page. I am thinking about newcomers to this documentation that do not have much technology-oriented knowledge. It would be useful for the more experienced to be able to deep dive, and for people who visit looking for more details to find them, without creating a situation where visitors may be unsettled by the terminology and concepts that are unknown to them. Has there been much thought to this?

* Secondly, I am puzzled by the use of "borders" for the framing that happens in the UI presentation of the document material. Since there are actual, drawn borders that can be introduced and shown, it would be good to use a different term for the all of the frames that delimit structural features of the document that are not part of the presentation of the document on a printer, in a PDF, etc. I would also not say too much about frames at the top level, but perhaps a cross-reference would be useful later.

--''[[User:Orcmid|Orcmid]] ([[User talk:Orcmid|talk]]) 23:29, 20 January 2016 (UTC)''

Writer/ToDo/Layout

2015-02-12T16:25:55Z

Orcmid: /* Draft Layout */ Added link to issue 126098

{{Writer Project|Category=Writer/Effort/Stalled}}
__TOC__
= Intro =
== Terminology ==

'''Layout:'''
* refers to the orientation and positioning of the textual and non-textual content on an output device
* identical to the user's-referred '''View'''!
** What the users refer to "View" in Writer is correctly designated by developers as the '''Layout'''.

== Available Layouts ==

The following layouts are currently implemented in Writer:
* '''Print Layout'''
* '''Online Layout''' (Web Layout) and
* '''Print Preview Layout'''

The latter isn't editable and is therefore left out of this discussion.

The '''Print Layout''' implements '''WYSIWYG''' and tries to come as close as possible to the printed document. However, this layout is not particularly suited for numerous use cases. In many circumstances, more specific layouts fare definitely better. These will be discussed in the following sections.

= Motivation =

Writing a new document involves some specific steps. Particular Layouts should target these steps and improve the specific tasks for that step. To better understand this issue, we need to examine briefly the pathway leading to the creation of a new document.

== Document Creation Path ==

Various specific Layouts are better suited for particular tasks. In common practice, creating a new document involves the following steps:
* plan the document / write a first draft
** needed: mind-mapping features
** organise/reorganise ideas
** easy move text-blocks/paragraphs
* extend draft, write the content
** only some basic style formatting
** ease typing text
** powerful auto-replace: allow extensive abbreviation handling
** powerful spelling corrections
* verify content and make corrections
** even more powerful spelling corrections
** advanced notes functionality: external/internal review
** external review functionality
** more advanced style formatting
* advanced formatting
** most formatting done in this step
** document structure
*** pagination, TOC, ...
* verify targeted output:
** e.g. ''Print Preview Layout''
** or some other specific Layout (e.g. for web publishing) depending on the targeted output
** only limited editing
** only limited formatting

Every step involves some specific actions. There are indeed specific demands for the various steps. Layouts should therefore target individually and specifically these steps. They should ease the work for a single step, while obviously, they will be less suited for the remaining steps.

= '''Layouts''' =

* the layouts '''should be targeted at each of the individual document creation steps'''

== '''Draft Layout''' ==
(comparable to Word's ''Normal View''):

See:
* [http://www.openoffice.org/issues/show_bug.cgi?id=4914 Issue 4914 - Normal View]
* [http://www.openoffice.org/issues/show_bug.cgi?id=3959 Issue 3959 - Outline View]
* [http://www.openoffice.org/issues/show_bug.cgi?id=89311 Issue 89311 - Scene/Ideas View]
* [https://issues.apache.org/ooo/show_bug.cgi?id=126098 Issue 126098 - Content mode]

* early phase of writing: mind-mapping capabilities
* later phase: actual writing
** focus on '''content''', NO formatting
*** layout shall NOT distract from content
*** avoid eating up space by margins and page breaks; ''text editor'' editing style
*** sophisticated formatting is not part of document (content) creation
*** page breaks should still be visible, but in a less disturbing way
*** page and column layout are artificial and have no content related meaning
*** columns are good for reading on paper, but a pain for reading on screen
** avoid ''horizontal scrolling'' even with big fonts on small screens or windows
** headers and footers don't need to be visible while editing and proof reading
** footnotes can be edited and displayed in a separate window area to avoid hopping between footer and body text
** easy and fast text scrolling for better proof reading

== "Online" Layout ==

* documents that are specifically written for presentation and not for printing
* disadvantage: suboptimal for editing (long lines)
* acts as a final preview

Some new layouts are requested with the following motivations:

== "Outline" Layout ==

* see [http://www.openoffice.org/issues/show_bug.cgi?id=3959 issue 3959]
* '''brainstorming''' the structure of a document to create initial hierarchy
* easy tool for developing and changing document structure
* prioritize, arrange and rearrange ideas hierarchical; add details later
* focus on content, no layout should distract from content
* chose level of details visible in any part of the document

== Multi-Page Layout ==

see [http://www.openoffice.org/issues/show_bug.cgi?id=1598 '''issue 1598'''] and [http://wiki.services.openoffice.org/wiki/Writer/ToDo/Layout/Multi_Page_Layout the '''Multi Page Layout''' wiki page]

* more than one page should be stacked horizontally (for H-locales)
* especially useful on large screens and multi-monitor setups
* subtypes:
** 2 pages per row
** n-pages per row
** variable number of pages on the row (as many as will fit)
** all pages displayed on a single row

== Publishing Layout ==

The last step in professional publishing involves advanced layout formatting. This layout should ease working with the document as a whole, as well as with more complex structures like whole paragraphs, sections, columns, frames, and other advanced writer objects. It is NOT intended as an editing mode, BUT rather as a purely layout-formatting mode.
* advanced formatting should be visible
* paragraphs and various objects should be highlighted as a whole
* specific tools / toolbars displayed
* various complex operations:
** compress line
** compress paragraph to ''x''-lines / by ''x''-lines / fit on page
** compress by ''x''-pages
** keep various ''words / lines / titles / objects'' together
** complex multi-column operations
* document structure
** TOC creation
** index
** bibliography

'''!!! TO BE EXTENDED !!!'''

= Discussion =

There are some common motivations but also some differences. It seems that they also have some technical similarities. This is discussed [[Writer/View Concepts|here]].

There is a particular problem in Writer that needs to be solved before it makes sense to implement more views. A Writer documents always has one layout. If the user switches from "Print Layout" to "Online Layout" the old layout is thrown away and the new layout for the complete document is calculated. On switching back the same happens again. This can become quite annoying when new layouts are used that let switching between layouts happen more often. Perhaps it might also be attractive to have two different layouts visible at a time in two different windows, e.g. Outline Layout and Print Layout.

The Draft Layout also needs information about the position of the page breaks in the document. So at least this has to be saved from the Print Layout but from the above it seems to be a better idea to preserve the Print Layout completely and retrieve the page breaks from it.

So we first must change the code in a way that it can handle more than one Layout at a time. This will make the implementation of new layouts better and their usage more attractive. Work on this has been done up to the point where certain elements made problems that couldn't be solved with the current layout implementation. The problems we found are related to grouped objects and form controls that can't be used in several layouts if they are in the same drawing layer. So another preliminary step is necessary, that is part of the [[Refactoring_of_Writer's_usage_of_the_Drawing_layer|Drawing Layer refactoring]].

[[Category:To-Do]]

User:Orcmid

2012-04-01T20:19:21Z

Orcmid: Mention AOO.

User:Orcmid

2012-04-01T20:17:54Z

Orcmid: Provide something to seed this place.

Talk:Documentation/FAQ/Installation/How Can I Install the Security Patch (CVE-2012-0037)

2012-04-01T20:08:20Z

Orcmid: /* TODO: */ Expanded the list a little

=== TODO: ===

# Link to the announcement and description of the patch.
# Start with an image of the final step - copying the DLL from the Zip to the program folder.
# Then follow with two things:
## A list of links for clarifying when that is not what things look like on the user's particular system
## The list of the top level steps for getting to the final point. The idea is that experts already know, but that different degrees of fluency will require consultation of the linked details, not just review of the list.
# Mine the following information for something to be made more user friendly and not have so much tacit-knowledge required:
<blockquote>
Thanks to Matthew McCue for providing a complete report that helped me see where difficulties were coming up.
* INSTRUCTIONS FOR MICROSOFT WINDOWS, INCLUDING WINDOWS XP
** Find the folder where OpenOffice.org is installed (either Program Files\Open Office.org 3\ or Program Files (x86)\Open Office.org 3\) [Note: "Program Files" may have a different wording depending on the language used on your computer.]
** Inside that folder, there is another folder named "programs". If you examine that folder you will see there is a file named unordfmi.dll there. This is the file that you want to replace. As a precaution, you can rename it to something like unordfmi.dll.bak just to be safe.
** Copy the file unordfmi.dll from the patch Zip folder into that programs folder, providing a replacement for the unordfmi.dll that was there.
** Do not copy anything else. Do not remove anything else in OpenOffice.org 3\programs\.
** More Details:
*** If you see just unordfmi without .dll, that is the same file. It just means your folder options are arranged to not show you the file extension of some files. You can change that by using the Tools | Folder Options ... menu selection on the folder view in Windows XP.
*** If you are following the instructions in the README.pdf, you will not see a property-dialog button named "Open File Location." On Windows XP, the name on the button is "Find Target...". This will take you to the correct folder, but soffice.exe will be selected. Clear that selection. You do not want to touch soffice.exe. You are going to replace the unordfmi.dll that is farther down in the same folder.
***One way to remove the selection is to press Ctrl-click. Another way is to move the mouse pointer to an open area at the top of the folder view outside of the file list and click. That should remove the selection on soffice.exe.
*** That or just scroll down to unordfmi.dll beyond soffice.exe and rename it. (Note, it is easy to lose the copy selection on the replacement in the Zip folder. If nothing happens when you try to paste into the target folder, leave the target folder open, go back to the Zip folder, and simply drag unordfmi.dll from the opened Zip folder to the target "program" folder.
</blockquote>

Talk:Documentation/FAQ/Installation/How Can I Install the Security Patch (CVE-2012-0037)

2012-04-01T20:05:08Z

Orcmid: Collecting material for making into a suitable FAQ

=== TODO: ===

# Link to the announcement and description of the patch.
# Mine the following information for something to be made more user friendly and not have so much tacit-knowledge required:
<blockquote>
Thanks to Matthew McCue for providing a complete report that helped me see where difficulties were coming up.
* INSTRUCTIONS FOR MICROSOFT WINDOWS, INCLUDING WINDOWS XP
** Find the folder where OpenOffice.org is installed (either Program Files\Open Office.org 3\ or Program Files (x86)\Open Office.org 3\) [Note: "Program Files" may have a different wording depending on the language used on your computer.]
** Inside that folder, there is another folder named "programs". If you examine that folder you will see there is a file named unordfmi.dll there. This is the file that you want to replace. As a precaution, you can rename it to something like unordfmi.dll.bak just to be safe.
** Copy the file unordfmi.dll from the patch Zip folder into that programs folder, providing a replacement for the unordfmi.dll that was there.
** Do not copy anything else. Do not remove anything else in OpenOffice.org 3\programs\.
** More Details:
*** If you see just unordfmi without .dll, that is the same file. It just means your folder options are arranged to not show you the file extension of some files. You can change that by using the Tools | Folder Options ... menu selection on the folder view in Windows XP.
*** If you are following the instructions in the README.pdf, you will not see a property-dialog button named "Open File Location." On Windows XP, the name on the button is "Find Target...". This will take you to the correct folder, but soffice.exe will be selected. Clear that selection. You do not want to touch soffice.exe. You are going to replace the unordfmi.dll that is farther down in the same folder.
***One way to remove the selection is to press Ctrl-click. Another way is to move the mouse pointer to an open area at the top of the folder view outside of the file list and click. That should remove the selection on soffice.exe.
*** That or just scroll down to unordfmi.dll beyond soffice.exe and rename it. (Note, it is easy to lose the copy selection on the replacement in the Zip folder. If nothing happens when you try to paste into the target folder, leave the target folder open, go back to the Zip folder, and simply drag unordfmi.dll from the opened Zip folder to the target "program" folder.
</blockquote>

Documentation/FAQ/Installation/How Can I Install the Security Patch (CVE-2012-0037)

2012-04-01T19:57:09Z

Orcmid: Create placeholder for more material.

{{DISPLAYTITLE: Installing the Security Patch (for CVE-2012-0037)}}

{{Documentation/NeedsRework}}

<section begin=question/>
'''How Do I Install the Security Patch (CVE-2012-0037)'''
<section end=question/>

<section begin=answer/>
'''This is a place-holder. The page and companion information is being edited.'''

This is information to be replaced with user-friendly material. See the Discussion page for in-progress material and tasks.
<section end=answer/>

[[Category:Documentation/FAQ/Security]]
[[Category:Documentation/FAQ/Installation]]

QA/TestResults

2012-01-09T05:02:21Z

Orcmid: I am making a trivial change to see if this one appears.

== Overview ==
This wiki page is for Apache OpenOffice 3.4 testing results.

Volunteers: Please follow the template below in summarizing your test results. Link to the bug reports and the location of any detailed materials:

*Platform
*Build
*Component you conduct testing
*Feature you conduct testing
*General testing result as:
*How many bugs you reported
*What they are
*Other issues you want to highlight in result

== IP Cleanup Testing Results ==
<b>IP Clearnup Testing Results</b>:
{| class="wikitable"
|-
! Library
! What is changing
! User Impact
! Testing Result
|-
| lp_solve
| lp_solve is being replaced by CoinMP
| This functionality is invoked by the user in Calc via Tools->Solver. It is used for solving linear programming problems, including integer programming.

CoinMP comes from the Coin-OR open source project, an open source project that involves operations research professionals and includes cutting edge algorithms.

According to one research paper CoinMP offers superior performance compared to lp_solve. So the overall user impact from this change should be positive.
| row 1, cell 5
|-
| xpdf
| The xpdf source code was removed
| PDF import can only be built when the poppler library is pre-installed on the system. It will not be part of the binary release.
| No test required
|-
|MySQL Connector/C++
|
|MySQL connector can only be built when the C++ connector is pre-installed on the system. It will not be part of the binary release.
It impact extension MySQL Connector for OpenOffice.org not function in OpenOffice
|
|-
| libwpd
| The libwpd library is being removed from the product.
| The WordPerfect filter ("WordPerfect Document (.wpd)") won't be available anymore. No replacement unless someone creates a filter extension that can be installed separatel|
|-
| 3rd party/external library gentiumbasic-fonts & liberation-fonts
| Remove fonts from product.
| A useful set of high quality fonts, mostly equivalent to those from MS.
|
|}

== AOO 3.4 Code Changes Testing Results ==
Here is the AOO 3.4 code change:http://development.openoffice.org/releases/3.4beta.html

Please vlounteer update below table for the code change related testing results.

{| class="wikitable"
|-
! Feature title
! Task ID
! Description
! Dev. Owner
! Component
! Test Results
|-
| Improve ODF 1.2 encryption supporte in OOo
| i117562
| The ODF1.2 specification allows to use W3C-specified algorithms to encrypt ODF1.2 documents. The new implementation let the following algorithms be used in case ODF1.2 encrypted document is stored: Start key generation: SHA256 Derived key generation: PBKDF2 Encryption algorithm: AES-256 Checksum generation: SAH256_1K It is possible to let start key and checksum generation use SHA1/SHA1_1K algorithms during storing of ODF1.2 encrypted document by setting the configuration entry org.openoffice.Office.Common/Save/ODF/UseSHA1InODF12 to "true". It is also possible to let Blowfish algorithm be used in this case by setting the entry org.openoffice.Office.Common/Save/ODF/UseBlowfishInODF12 to "true". The storing of encrypted ODF1.1/ODF1.0 documents is not affected. Please see http://docs.oasis-open.org/office/v1.2/csprd03/OpenDocument-v1.2-csprd03-part3.html for details.
| mikhail.voytenko@oracle.com ??
| framew
|-
| row 2, cell 1
| row 2, cell 2
| row 2, cell 3
| row 2, cell 4
| row 2, cell 5
| row 2, cell 6
|}

== General Testing Test Results ==
Please volunteer update below table to give your AOO 3.4 General Testing Result.
{| class="wikitable"
|-
! Platform
! Build
! Component
! Feature
! Test Cases
|-
| RedHat Enterprise Linux (RHEL) 6 32 bit
| ooobasis3.4-sdk-3.4.0-1-linux-2.6-x86_64-2011-12-19.deb
| Impress
| Numbering and Bullet
| Test Results:
*How many defects you raised
*What they are
*Other issues your want to highlight in results
|-
| row 2, cell 1
| row 2, cell 2
| row 2, cell 3
| row 2, cell 4
| row 2, cell 5
|}

QA/TestResults

2012-01-09T04:55:32Z

Orcmid: I edited the first Overview paragraph as part of troubleshooting the wiki.

== Overview ==
This wiki page is for Apache OpenOffice 3.4 testing results. Volunteers: Please follow the template below in summarizing your test results. Link to the bug reports and any detailed materials:

*Platform
*Build
*Component you conduct testing
*Feature you conduct testing
*General testing result as:
*How many bugs you reported
*What they are
*Other issues you want to highlight in result

== IP Cleanup Testing Results ==
<b>IP Clearnup Testing Results</b>:
{| class="wikitable"
|-
! Library
! What is changing
! User Impact
! Testing Result
|-
| lp_solve
| lp_solve is being replaced by CoinMP
| This functionality is invoked by the user in Calc via Tools->Solver. It is used for solving linear programming problems, including integer programming.

CoinMP comes from the Coin-OR open source project, an open source project that involves operations research professionals and includes cutting edge algorithms.

According to one research paper CoinMP offers superior performance compared to lp_solve. So the overall user impact from this change should be positive.
| row 1, cell 5
|-
| xpdf
| The xpdf source code was removed
| PDF import can only be built when the poppler library is pre-installed on the system. It will not be part of the binary release.
| No test required
|-
|MySQL Connector/C++
|
|MySQL connector can only be built when the C++ connector is pre-installed on the system. It will not be part of the binary release.
It impact extension MySQL Connector for OpenOffice.org not function in OpenOffice
|
|-
| libwpd
| The libwpd library is being removed from the product.
| The WordPerfect filter ("WordPerfect Document (.wpd)") won't be available anymore. No replacement unless someone creates a filter extension that can be installed separatel|
|-
| 3rd party/external library gentiumbasic-fonts & liberation-fonts
| Remove fonts from product.
| A useful set of high quality fonts, mostly equivalent to those from MS.
|
|}

== AOO 3.4 Code Changes Testing Results ==
Here is the AOO 3.4 code change:http://development.openoffice.org/releases/3.4beta.html

Please vlounteer update below table for the code change related testing results.

{| class="wikitable"
|-
! Feature title
! Task ID
! Description
! Dev. Owner
! Component
! Test Results
|-
| Improve ODF 1.2 encryption supporte in OOo
| i117562
| The ODF1.2 specification allows to use W3C-specified algorithms to encrypt ODF1.2 documents. The new implementation let the following algorithms be used in case ODF1.2 encrypted document is stored: Start key generation: SHA256 Derived key generation: PBKDF2 Encryption algorithm: AES-256 Checksum generation: SAH256_1K It is possible to let start key and checksum generation use SHA1/SHA1_1K algorithms during storing of ODF1.2 encrypted document by setting the configuration entry org.openoffice.Office.Common/Save/ODF/UseSHA1InODF12 to "true". It is also possible to let Blowfish algorithm be used in this case by setting the entry org.openoffice.Office.Common/Save/ODF/UseBlowfishInODF12 to "true". The storing of encrypted ODF1.1/ODF1.0 documents is not affected. Please see http://docs.oasis-open.org/office/v1.2/csprd03/OpenDocument-v1.2-csprd03-part3.html for details.
| mikhail.voytenko@oracle.com ??
| framew
|-
| row 2, cell 1
| row 2, cell 2
| row 2, cell 3
| row 2, cell 4
| row 2, cell 5
| row 2, cell 6
|}

== General Testing Test Results ==
Please volunteer update below table to give your AOO 3.4 General Testing Result.
{| class="wikitable"
|-
! Platform
! Build
! Component
! Feature
! Test Cases
|-
| RedHat Enterprise Linux (RHEL) 6 32 bit
| ooobasis3.4-sdk-3.4.0-1-linux-2.6-x86_64-2011-12-19.deb
| Impress
| Numbering and Bullet
| Test Results:
*How many defects you raised
*What they are
*Other issues your want to highlight in results
|-
| row 2, cell 1
| row 2, cell 2
| row 2, cell 3
| row 2, cell 4
| row 2, cell 5
|}

OpenOffice.org Wiki:Copyrights

2011-12-11T23:34:59Z

Orcmid: Fixed a typo in the 3rd word

== License ==

Portions of the OpenOffice.org Wiki are Copyright 1999, 2010 by contributing authors and Oracle and/or its affiliates.

Sections or single pages of this wiki are covered by certain licenses. If a license notice is displayed at a given wiki page, you may use the content of that page according to that license.

In all other cases, the page is licensed under the Apache License, Version 2.0 [http://www.apache.org/licenses/LICENSE-2.0 (ALv2)].

In posting a new contribution, you are licensing that contribution under the Apache License, Version 2.0 [http://www.apache.org/licenses/LICENSE-2.0 (ALv2)].

OpenOffice.org Wiki:Copyrights

2011-11-28T03:57:35Z

Orcmid: /* License */ Expanded topic

== License ==

Portions of he OpenOffice.org Wiki are Copyright 1999, 2010 by contributing authors and Oracle and/or its affiliates.

Sections or single pages of this wiki are covered by certain licenses. If a license notice is displayed at a given wiki page, you may use the content of that page according to that license.

In all other cases, the page is licensed under the Apache License, Version 2.0 [http://www.apache.org/licenses/LICENSE-2.0 (ALv2)].

In posting a new contribution, you are licensing that contribution under the Apache License, Version 2.0 [http://www.apache.org/licenses/LICENSE-2.0 (ALv2)].

User talk:Orcmid

2011-06-20T21:32:37Z

Orcmid: Created page with 'Here is a placeholder for a profile yet to come.'

Here is a placeholder for a profile yet to come.