クイック検索で関数の代わりに値が検索されるようになりました (the search dialog offers both options). tdf#102506 (Julien Nabet)
Available since 7.3.1
: Fixed a bug that caused table cells incorrectly placed when pasting a HTML table content. tdf#74577, tdf#92960 (Eike Rathke)
Diagonal borders are now accessible from "Toolbar > Borders" tdf#143919 (Bayram Çiçek)
Diagonal down/up and criss-cross borders are accessible from "Toolbar > Borders"
Header and Footer can now be set independently between the first page and the rest, which improves consistency with Writer and interoperability with Microsoft Office. The setting "Same content on first page" can be found in the respective tabs in Format ▸ Page Style. (Daniel Arato, NISZ) tdf#142763
変更された表計算関数
Option "Search criteria = and <> must apply to whole cells" has been fixed to apply properly in lookup functions when turned off (tdf#139612). For better performance it is recommended to leave the option on unless partial cell matching is required. (Luboš Luňák, Collabora)
IF()関数は、条件のエラー値があった場合、エラー値をそのまま返す様になります。以前は、条件がエラーに対してTRUEではないので、関数内のELSE部が実行されていました。これは、ELSEがIFERROR()やISERROR()などのエラー評価関数やその他のIS...()系の関数でない限り重要ではありませんでした。 この修正により非公式の副作用的動作が変更されるため、この挙動に依存してきた既存の式が期待通りに動作しなくなる可能性があります。 tdf#146377 (Eike Rathke, Red Hat)
同じ種類の図形を挿入する際のプロパティ共有の解除 blog post (Miklos Vajna, Collabora)
tdf#140321 (Regina Henschel)Wire Frame - Matt - Plastic - Metal The dialog "3D-Settings" opens if you toggle a shape to "Extrusion on". The dialog has a drop-down list "Surface" with items "Wire Frame", "Matt", "Plastic" and "Metal". In the old version the items "Matt", "Plastic" and "Metal" did nothing, but the solid was always rendered as "Plastic". Now you get different surfaces. "Matt" is really matte. "Metal" is similar to "Plastic" but has more contrast.
DOCX import: fix user index and index entry support defined by field code \f. This is a reworking of a previously patch. Now the import uses com.sun.star.text.UserIndex and com.sun.star.text.UserIndexMark index and index entry fields, which support the requested user index not only during the DOCX and OpenDocument round-trip, but its run-time functionality, the multiple user-defined indices tdf#77051 (László Németh, NISZ)
XLSX import: decreased a row height for XLSX files created by MS Office tdf#144642 (Attila Szűcs, NISZ)
XLSX export: cell indent doesn't increase on each save now tdf#130104 (Kevin Suo)
XLSX import: fix permission for editing tdf#115933 (Tünde Tóth, NISZ)
XLSX import/export: fix permission for editing. The password for editing wasn't asked, also wasn't exported in XLSX documents. tdf#118938 (Tünde Tóth, NISZ). Now it's exported in Calc using the following steps, also verified before editing:
In File->Save As, choose Excel 2007–365 (.xlsx) format;
enable checkbox "Save with password" and click Save;
in the dialog "Set password", click on "Options" and enable checkbox "Open file read-only", and enter a password for editing (i.e. skip the password for opening).
Calc buttons with macros: better XLSX support blog post (Miklos Vajna, Collabora)
Interslavic Latin {art-Latn-x-interslv} and Interslavic Cyrillic {art-Cyrl-x-interslv}. tdf#145853 (Eike Rathke, Red Hat)
校正ツールと言語サポート
Language entries in language listboxes created by spellchecker or hyphenation dictionaries or extensions that support languages without a predefined language listbox entry are now displayed using a possibly translated language/locale name obtained from the ICU (International Components for Unicode) library. Previously such entries were displayed as language tags in curly brackets, for example {en-SG}. (Eike Rathke, Red Hat)
Old Hungarian has got full-text transliteration support: Tools ▸ AutoCorrect ▸ Apply and Tools ▸ AutoCorrect ▸ Apply and Edit Changes transliterate right-to-left Hungarian text to Old Hungarian (only if the paragraph style of the text is Default Paragraph Style). tdf#143176 (László Németh). More info in Release Notes 7.0
Up to and including LibreOffice 7.2, missing optional procedure arguments would be treated as an object of type Error, with error code '448', which would be coerced to e.g. numerical value '448' or boolean true in expressions depending on expression context. This now raises an error, as expected tdf#144353. In particular, expressions like "if IsMissing(FOO) or FOO" used to work "by accident", but now don't any more.
The C functions rtl_str_toFloat, rtl_str_toDouble, rtl_ustr_toFloat, and rtl_ustr_toDouble, and the C++ member functions rtl::OString::toFloat, rtl::OString::toDouble, rtl::OUString::toFloat, and rtl::OUString::toDouble no longer accept a “+” or “-” sign before “NaN” when parsing the XML Schema–style Not a Number notation. (But they still accept an optional “+” or “-” sign before the legacy “1.#NAN” notation.) 9d27a44e
osl_demultiplexSocketEvents and its support functionality, all of which were deprecated, have been removed from the UNO C/C++ API. db392a8a