3.1.0 (build OOO310_m11) - Release Notes

These notes contain changes between DEV300_m29 and DEV300_m40 +
OOO310_m1 and OOO310_m11. References to former Release
Notes are still available
(example: http://development.openoffice.org/releases/3.0.m28_snapshot.html).
This release will install as OpenOffice.org 3.1.0.
Sources can be received from SVN by tag OOO310_m11.

What's
new ?

feature-info:
The key combination Ctrl+F11 doesn't call the Style Catalog anymore.
Now it puts the focus into the style ListBox in the toolbox of text,
frames, OLE-objects and pictures. It makes it easier to apply a
paragraph or frame style without using a mouse.

feature-info:
Added locale data for Maltese (Malta) [mt-MT].
The locale is selectable for character attribution and spell-checking,
as default locale, default document language and available for number
formats and outline numbering.

feature-info:
Added locale data for Myanmar (Myanmar) [my-MM].
The locale is selectable for character attribution and spell-checking,
as default locale, default document language and available for number
formats and outline numbering.

feature-info:
Added locale data for Shuswap (Canada) [shs-CA].
The locale is selectable for character attribution and spell-checking,
as default locale, default document language and available for number
formats and outline numbering.

feature-info:
The language table and list box now have an "Arabic" entry (without
region/country) that does not correspond to a locale. It is not
offered for language attribution et al, but is selectable if an Arabic
language pack is installed, instead of the previous "Arabic (Egypt)".

feature-info:
Added locale data for Tok Pisin (Papua New Guinea) [tpi-PG].
The locale is selectable for character attribution and spell-checking,
as default locale, default document language and available for number
formats and outline numbering.

In regions where people uses right-to-left directed
text like
Arabia or Israel (Hebrew) forms will look strange if they need to use
left-to-right layout control forms.This specification will enhance
OpenOffice.org 2.0 with control forms that can have both text
directions/layout - left-to-right and right-to-left.

feature-info:
The Function Autopilot which is used in the
spreadsheet can now be
used inside the Sun Report Builder.
The Autopilot can be started from:
- the data field ( formatted field and image control)
- the conditional print expression
http://wiki.services.openoffice.org/wiki/SUN_Report_Builder/Documentation#Report_Navigator_-.3E_Report_-.3E_Functions_-.3E_Function_-.3E_Properties_of_General_Tab
- the formula
- the initial value
The Autopilot shows all functions which are supported by the report
engine.
The documentation for the SRB can be found here
http://wiki.services.openoffice.org/wiki/SUN_Report_Builder/Documentation
The function description can be found here
http://wiki.services.openoffice.org/wiki/Base/Reports/Functions

feature-info:
The property browser now shows the selected output format for a report
on teh data page when it is selected in the SRB. Currently available
formats are - Text document
- Spreadsheet document

feature-info:
The Add Field dialog now has a toolbar above the listbox for the
fields. The toolbar allows to sort the fields ascending and descending
as well to remove the sort order and restore origin order from the
source (table,query). Additional the toolbar contains an "Insert"
entry which allows to insert the selected fields into a report
section. Multiselection of fields is also supported.

This Specification describes three single tasks which
are so
closely related, that i will describe them in a single specification.
The following definitions of the three tasks will be used throughout
the document:

Target of the extensible help project is to support
help content
inside OpenOffice.org extensions. The extensions' help content is
provided together with the OpenOffice.org installed help content. The
help index can be extended by extensions. The implementation supports
extended tool tips and accessing extension help content by pressing F1
in UNO dialogs and menus.

File locking is needed to control access to a document.
If a
file/document is locked, nobody else could change/delete the document.
A file locking mechanism is offered by the operating system, but in
some cases this mechanism does not/could not work. Therefore OOo
implements an own mechanism beside the one provided by the operating
system. System and OOo file locking are combined. This allows OOo to
have a reliable locking also when the locking from the operating
systems fails in some cases. Furthermore it allows to OOo see who has
already opened the document.

This Specification describes three single tasks which
are so
closely related, that i will describe them in a single specification.
The following definitions of the three tasks will be used throughout
the document:

feature-info:
Sorting has been improved:
- Sorting preserves the original order of entries with equal sort keys.
- If there are no previous sort settings, the sort dialog defaults to
the column of the cursor position. The toolbar buttons always use the
cursor position.
- The toolbar buttons use the same logic as the sort dialog to
determine if a range has column headers.

feature-info:
Sorting has been improved:
- Sorting preserves the original order of entries with equal sort keys.
- If there are no previous sort settings, the sort dialog defaults to
the column of the cursor position. The toolbar buttons always use the
cursor position.
- The toolbar buttons use the same logic as the sort dialog to
determine if a range has column headers.

feature-info:
For MS-Excel interoperability the INDIRECT function now supports the
'!'
exclamation mark as sheet name separator when interpreting cell address
strings, additionally to the '.' dot separator Calc uses.
This change aligns with the behavior of other spreadsheet applications
and
the definition given in the OASIS ODFF/OpenFormula specification
available at
http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula

feature-info:
A column or row vector is now replicated if used in an array formula
such that a 2D matrix is required by an operation but only a vector was
given. For example, the formula
={1;2;3}
entered as a matrix formula in a range selection of 3 columns by 2 rows
results in two rows with values 1 2 3 each.
This works also in not so trivial cases,
http://qa.openoffice.org/issues/show_bug.cgi?id=46681 mentions a few
use
cases.
This change aligns with the behavior of other spreadsheet applications
and
the definition given in the OASIS ODFF/OpenFormula specification
available at
http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula

feature-info:
Sorting has been improved:
- Sorting preserves the original order of entries with equal sort keys.
- If there are no previous sort settings, the sort dialog defaults to
the column of the cursor position. The toolbar buttons always use the
cursor position.
- The toolbar buttons use the same logic as the sort dialog to
determine if a range has column headers.

feature-info:
The BETADIST spreadsheet function now has an additional optional
'cumulative' parameter to specify whether to calculate the probability
density function or the cumulative distribution function, defaulted to
TRUE for compatibility.
This change aligns with the behavior of other spreadsheet applications
and
the definition given in the OASIS ODFF/OpenFormula specification
available at
http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula
A new implementation of BETADIST now yields results with a much better
precision than in earlier releases.

feature-info:
The implementation of how data pulled in by references to external
documents in formulas is stored internally was changed. Previously, all
data of a referred external sheet was stored in a hidden sheet. Now
only
the data referred is stored in a separate structure, hidden sheets are
not created anymore. This has the advantages that
- By not creating hidden sheets the amount of available 255 sheets is
not decremented.
- It should be possible to refer more than 254 external sheets, given
enough memory for the amount of data of course.
- Less data needs to be stored when saving the document to file.
- No unintended data leakage may occur because data not referred is not
saved to files.
Note that the external sheets will not show up anymore in the
Navigator.
For ODF file storage the data is still saved as external sheets,
previous versions will be able to read the document. Re-saving an
already existing document with the new version may result in
a significantly decreased size of the file's storage, depending on the
previous amount of data in the entire sheet and the amount of data
actually used in formulas.

feature-info:
The EUROCONVERT spreadsheet function to convert
between former currencies of the Eurozone is implemented, including
import from and export (binary) to Excel file formats.
This change aligns with the behavior of other spreadsheet applications
and
the definition given in the OASIS ODFF/OpenFormula specification
available at
http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula

feature-info:
Several changes according to ODFF.
(1) Introduce the GAMMA function.
(2) Introduce CHISQDIST.
In contrast to CHIDIST it gives the left tail probability, same as
other
distributions do. In addition it has an optional parameter to calculate
the density function.
(3) Introduce CHISQINV.
(4) Adapt the "cumulative" parameter of the GAMMADIST function to be
optional. If omitted, the default value 1 is stored in ODF documents
and
export to Excel for compatibility.
(5) Adapt the domain of CHIDIST to allow negative x, see ODFF 6.17.10.
(6) Remove the constraint "degrees of freedom < 1.0E5" from
CHIDIST and
CHIINV because they are no longer needed with the new implementation.
Unfortunately the identifier GAMMAINV is already used for the inverse
of
the Gamma-distribution. It can likely be confused to be the inverse of
the Gamma function. A comment in the application help is necessary.
These changes align with the definition given in the OASIS
ODFF/OpenFormula
specification available at
http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula
Note: for GAMMADIST and GAMMAINV, the third parameter 'beta' is used in
the way that mean=alpha•beta, but ODFF draft spec uses the
third
parameter 'lambda' in the way that mean=alpha/lambda. This needs to be
changed in ODFF spec. The application help must explain, which use of
the parameter OOo has, because the common usage of the parameter
differs
between countries.
Note: The domain of the GAMMA function contains negative values. The
ODFF draft spec is not adapted yet.

feature-info:
The DATEVALUE and TIMEVALUE spreadsheet functions now return the
numeric value for date repectively time only. In the case of DATEVALUE
only the integer part of the date serial is returned, in the case of
TIMEVALUE only the fractional part is returned. Previously, both
functions returned the combined integer and fractional value.
This change aligns with the behavior of other spreadsheet applications
and
the definition given in the OASIS ODFF/OpenFormula specification
available at
http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula

feature-info:
The 'base' parameter of the LOG spreadsheet function is now optional,
defaulted to base 10. The implementation already handled this, but it
was not reflected in the UI of the formula wizard.
This change aligns with the behavior of other spreadsheet applications
and
the definition given in the OASIS ODFF/OpenFormula specification
available at
http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula

feature-info:
The 'cumulative' parameter of the POISSON spreadsheet function is now
optional.
If omitted, storing the function in ODF files adds the default value
for backwards compatibility. Also during export to Excel the parameter
is added, as Excel expects all 4 parameters to be present.
This change aligns with the definition given in the OASIS
ODFF/OpenFormula specification available at
http://www.oasis-open.org/committees/documents.php?wg_abbrev=office-formula

Digits used in Arabic text (“Hindi
digits”) are
different from digits
in Western text (“Arabic digits”). Since some of
the IMEs (Input Method
Editor) do not deliver the correct Hindi digits but the common Arabic
digits, a configuration setting has been implemented for OpenOffice.org
1.2 that allows the user to switch the digits that are shown in the
document. This setting used to have three different states:
“all digits
Hindi”, “all digits Arabic”, and
“all digits depending on the system
locale”. This feature was lacking a mode that chooses the
correct
digits based on the context of the digits: Hindi digits in an Arabic
context, Arabic digits in any other context.

Introduce a new font effect that draws a line above a
selected
character or group of characters. The line style and colour may be
selected by the user, with the same options available as for the
underline font effect.

Introduction of an outline level attribute for
paragraphs and paragraph
styles

Introduce a new paragraph and paragraph style
attribute, named
“outline level”, to transform a normal paragraph
directly and
independently from any certain list style or paragraph style into a
heading.

Hyperlinks in Writer documents can be modified with the
hyperlink
dialog and in the Format/character dialog. It should also be possible
to easily remove a hyperlink and to copy the URL of the hyperlink to
the clipboard.

Grammar checking is now available in OpenOffice.org
Writer.
Therefore the former dialog gets extended to handle grammar checking
too. The dialog is now also able to show a vendor logo as a bitmap and
name in the dialog title.

feature-info:
Image controls can now be bound to images which are embedded in the
document where the control lives in.
More precise, when you select an image to be displayed at an image
control, the "Link" option in the file picker is not disabled anymore.
When you uncheck the option (the default is "checked", to mimic the
legacy behavior), then the image is displayed in the control, and upon
saving the document, it's embedded in the document itself.
This way, you can create documents with image controls which are
exchangeable with other people/installations/platforms, which formerly
was much more difficult due to the need to also copy the images, and
place them in exactly the same location as on the originating machine
(which often is simply impossible).
Thanks for Noel Power for providing the patch for this.

feature-info:
At the moment, when you create a file-based database (such as dBase or
Spreadsheet), the URL to the files (let's call it the "data URL") is
stored in
an absolute manner - that is, something like "file:///c:/foo/bar".
As a result, when you move the database document (the .odb file),
together with
the underlying data, to another machine, you need to either duplicate
the file
structure on this target machine, or to adjust the settings for the
database.
Now it is possible that the path is stored relatively when the option
"Save URLs relative to file system" setting in the
"Tools->Options->Load/Save" dialog is checked.

feature-info:
When you open an table view for editing its constituting SQL command
(which is a feature currently supported for embedded HSQLDB only),
then the query editor is automatically put into the "Run SQL command
directly" mode.

feature-info:
In the course of fixing issue 90403 and issue 92471, the behavior of
form controls whose "Empty string is NULL" property is set to "Yes"
has been refined. This change might make existing forms behave
slightly different than before, but certainly more
expectation-conformant now.
First, the property is now also respected when you never touched the
respective control before saving the record. That is, imagine a
control which has this property set to "Yes", this way declaring that
if the control contains an empty string, then this should be
propagated to the database as (the dedicated) NULL value.
Formerly, when you moved to the insertion row of the form, so the
control was initially empty, entered some data into other controls of
the current record, and saved the record without actually touching the
first control, then it actually updated an empty string. Now, with the
change, it updates NULL, as this is what "Empty String is NULL" =
"Yes" requests.
Second, when a control was bound to a database column which was
declared as NOT NULL, then the control *always* updated an empty
string instead of NULL, no matter what its "Empty string is NULL"
property requested. Effectively, this killed server-side defaults of
database fields, as such defaults are only applied when the field is
NULL. Now, with the change, controls always update NULL in such a
setup, this way enabling server-side defaults.

feature-info:
Image controls in database forms can now be bound to text columns.
Formerly, you could only bind them to columns whose content could
reasonably be interpreted as binary (BLOB etc.). Now, when you select
a text database column as source for the image control, then it will
interpret the content of the respective column's content as URL, and
load and display the image pointed to by this URL. Also, the URL might
be relative to the document which the image control is embedded into.

feature-info:
All form controls which can be bound to a database column (i.e. have
the "Data field" property) now have a new property called "Input
required".
Description
=========
This property controls whether or not the input of this field is
checked against being empty (NULL). It is evaluated for controls which
are bound to a database field which is defined as required (i.e. which
is not allowed to contain the special NULL value), immediately before
the current record of the form is to be written into the database.
If the property is set to "Yes", and the field contains no input when
the current record is to be written to the database, then an error
message will be shown to the user, and the respective control will be
focused afterwards. Note that this is the known behaviour so far - the
property defaults to "Yes" so that newly created controls behave as
they would do in previous OOo versions.
If the property is set to "No", and the field contains no input when
the current record is to be written to the database, then this is
ignored. It's up to the underlying database to either reject the
update, or fill the respective column with a server-side default value.
Functional Constraints
=================
If the "Form data input checks for required fields" option in the
advanced settings of the database document (Edit / Database / Advanced
Settings ...) is *not* checked, then the "Input required" property for
all controls in all forms in this database document does not have any
effect, since the document-wide setting overrules the per-control
settings.
UI
==
In the property browser, the "Input required" is located immediately
below the "Empty string is NULL" property, if it is present, otherwise
immediately below the "Data field" property.
If the "Data field" is not set (i.e. empty), then "Input required" is
disabled, since it would be evaluated for bound controls only, anyway.
If the "Empty string is NULL" is set to "No", then "Input required" is
also disabled, since "Empty string is NULL" being "no" implies that
when the user does not enter any value in the control, then an empty
string, instead of the dedicated value NULL, is written, so there's
always a non-NULL value no matter the user's action.

feature-info:
Image form controls in documents got an additional mode for scaling
the image they display.
Previously, you could control the scaling by setting the "Scale"
property to "Yes" or "No" only, where "Yes" implied an anisotropic
scaling, i.e. one which distorted the image's dimensions.
Now, the "Scale" property allows the values "No" (same as before),
"Keep Ratio" and "Fit to Size" (equivalent to the old "Yes"). When
"Keep Ratio" is selected, the image is still scaled up or down to
match the control dimensions, but it's ratio is aspect kept constant.
This is especially useful for controls where the designer of the
document does not know, at time of designing the document/control, the
dimensions of the to-be-displayed images. In particular, this is
useful for image controls in database forms, displaying images
obtained from the database.

feature-info:
Check box columns in grid controls now have the "Tristate" property,
which controls whether or not the "indetermined" state is allowed for
the check box, as known from ordinary check box form controls.

As practice has shown, it is a quite common case that
OOo is used to
edit documents of alien formats on network.
Unfortunately it looks to be impossible to let the file be locked
using file system locking, since it does not work in heterogeneous
file systems as expected, and the mentioned scenario has been
recognized as very important one. Thus the locking mechanics of OOo is
not recognizable for third-party applications, except they implement
support for OOo locking mechanics.
The implementation in childworkspace fwk94 let the alien files be
locked using the OOo file locking mechanics as well. That solves at
least the cases when a file of alien format is edited only by OOo3.x
in network.

Add stemming and morphological generation capabilities toOpenOffice.org Mythes thesaurus by the latest Hunspell spell checkerand morphological analyzer. Without any dictionary modification,OpenOffice.org will be able to stem the selected words for synonym search.With an annotated affix file, OpenOffice.org will generate the right wordforms of the synonyms based on the morphological category of affix of the selected word(documentation: http://sourceforge.net/docman/display_doc.php?docid=29374&group_id=143754)

Fixes for oversights during code review of iniinfo.inc.This is a fix with low risk but should be done because the code behind it does not make sense otherwise.Second attempt on getting the test extensions for minor minimal required office versions into CVS asbinary files.

"The program maps a file with MAP_PRIVATE and both PROT_WRITE and PROT_EXEC

If the program really needs this behavior there is no really easy way out. Onepossibility is to createan anonymous file (just unlink it after creation), size the file using ftrunctate, and then map thefile in two places. In one place map it with MAP_SHARED and write permission but without execution.For the second mapping use execution permissions but no write permissions. This might be a bit confusingat first but can be handled. The program must be adjusted to write to one location and expect to executecode in another one. This is reasonably safe in case the two mappings are allowed to be randomied."

Separate the doc and rtf import/export filters out of the (large) libsw; this way we save compilation time when doing changes in the filters to allow further refactoring, and also we save memory during runtime in case OOo operates only on ODF.

Introduce
a new paragraph and paragraph style attribute, named “outline
level”,
to transform a normal paragraph directly and independently from any
certain list style or paragraph style into a heading.

The OpenOffice.org Usage Feedback Extension is an extension that collects anonymously dataabout how OpenOffice.org is used. This information is used to better understandhow people use OpenOffice.org. Especially with regards to the user interface. http://wiki.services.openoffice.org/wiki/User_Experience/OpenOffice.org_User_Feedback_ExtensionThis cws only contains fixes to the core in OpenOffice itself, not the extension.

All automated tests currently load the UI filters which creates some overhead.Do not load the filter names during test initialization but only on an as needed basis.This CWS has impact on all TestAutomation modules.

Continue rework of the global file-I/O and filter functions within the testautomation moduleThis CWS is used for evaluation purposes as well (default filter handling)Provide replacements for automated tests that had to be removed due to last minute changes in the product

Done automation, the test results are as expected - a lot of errors and warnlogs which are present on the MWS as well.Done issue verification.The CWS still needs to be set to RfQA so i can nominate it.

* Enable compiling of layout engine by default.* Old .src dialogs initially replaced by .xml layout dialogs: svx/source/dialog/zoom.src, sw/source/ui/dialog/wordcountdialog.src [WIP: svx/source/dialog/docrecovery.src]* Note: i18n translation strings, compile-time translation and testing can be found in toolkit/workben/layout. See also toolkit/doc/layout/README* Note: the layout engine is still a work in progress, not all widgets have been implemented yet.

Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
OpenOffice, OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
Other names appearing on the site may be trademarks of their respective owners.