lo/core - LibreOffice 核心代码仓库

Age	Commit message (Collapse)	Author
2013-04-30	Move to MPLv2 license headers, with ESC decision and author's permission.	Michael Meeks

2012-07-04	refactor handling of double border widths:	Michael Stahl
	Word uses a completely different definition of "width" of a double border than OOo and ODF: for Word the width is apparently the largest of the 3 component widths, while OOo and ODF define the width as the total with of all 3 components. The new border implementation in LO 3.4 was apparently inspired by Word's double border definition, which resulted in various import filter regressions, see the previous fixes: 36e43b52992735c622833e923faa63774b9e2f76 e2ffb71305c5f085eec6d396651c76d6daee3406 70a6a4d425558340bb49507975343a3e0a1bdde8 These fixes set the ScaleMetrics, which actually seems sub-optimal as there is a ScaleItemSet function somewhere that apparently re-scales all items in an itemset, which could undo the fixes. Also, one of the fixes actually managed to break RTF/DOCX import of double borders, as that ended up in the same code via the API. This commit now reverses the change, so that the width of a border is now always the total with of all components, which is (imho) much more intutitive, and also leads to a consistent UI where selecting say 3pt width has predictable results, no matter what the border style. The border widths are now converted in the Word format import/export filters (writerfilter and sw/source/filter/ww8), and various tests were adapted to the new handling. Change-Id: I50456c49b1a298569607e6c88f19f18441348ac3
2012-07-04	replace enum SvxBorderStyle with css::table::BorderLineSyle	Michael Stahl
	Change-Id: I1dadb53f46b23f92d34061ef78dda872bdbcda67
2012-06-27	targetted re-work of cppunit pieces.	Michael Meeks

2012-06-25	rename SvxBorderLine::SetStyle to something unambiguous	Michael Stahl
	Change-Id: Iec70985319a64cdc3630e15499ac304a7f1aabae
2012-01-27	fdo#38542: SvxBorderLine::GuessLinesWidths:	Michael Stahl
	Importing style:border-line-width="0.002cm 0.088cm 0.141cm" (which older OOo/LO apparently could write) fails, because GuessLinesWidths can't find a matching style (result: standard "double" border, 3 equal width parts). Try to create a custom BorderWidthImpl of type DOUBLE instead, that preserves the individual widths.
2011-10-10	ensure correct export size type in stream operation	Caolán McNamara

2011-09-12	sb140: #i113503# mixing system CppUnit and OOo STLport does not work, backed ↵	Stephan Bergmann
	out a6913c9677c2 For LibO, that just means replacing sal/cppunit.h with sal/precppunit.hxx.
2011-03-28	Moved SvxBorder* into editeng namespace to avoid duplicate DOUBLE on windows	Cédric Bosdonnat

2011-03-21	editeng: Adapted borderline unit test to new build system	Cédric Bosdonnat

2011-03-19	editeng: more reliable test library build	Cédric Bosdonnat

2011-03-19	Fixed lines width guessing: gap are no smaller than 1pt	Cédric Bosdonnat

2011-03-19	Switching the order of the SetLinesWidth arguments	Cédric Bosdonnat

2011-03-19	Fixed units mess in SvxBorderLine and BorderLineImpl	Cédric Bosdonnat

2011-03-19	Documented and Unit-tested the SvxBorderLine::SetLinesWidth	Cédric Bosdonnat