summaryrefslogtreecommitdiffstats
path: root/editeng/qa
Commit message (Collapse)AuthorAgeFilesLines
* Rename SectionAttribute to Section.Kohei Yoshida2013-08-281-9/+9
| | | | | | It fits better this way. Change-Id: I139de7858e999a6dd26633a548c47634dfad8a65
* Fix incorrect logic in section attribute array construction.Kohei Yoshida2013-08-281-41/+103
| | | | | | And a new test case to catch it. Change-Id: Ie51ddf185f70c656e7d838fc7016b5726efbdf3f
* Add a means to retrieve all formatting attributes in non-overlapping sections.Kohei Yoshida2013-08-201-0/+93
| | | | Change-Id: Id04dffc135fad6bb66ea157cd280dd481cb80117
* String to OUStringMatteo Casalin2013-07-301-1/+1
| | | | | | | Change-Id: I8d4f62b473ad43807621a9dbb826ed33857b737e Reviewed-on: https://gerrit.libreoffice.org/5189 Reviewed-by: Luboš Luňák <l.lunak@suse.cz> Tested-by: Luboš Luňák <l.lunak@suse.cz>
* fdo#55315 Added simple Trie lookup tree for autocomplete words storageTomaž Vajngerl2013-06-111-4/+91
| | | | | | | | | | | | | Added simple Trie lookup tree which is more tailored to what is needed in autocomplete implementation, but still has the speed of the LatinLookupTree that has been used till now. As the implementation is much simpler it should be more managable and easier fixable. For now two actions: insert (word) and findSuggestions are supported. Acttion findSuggestion returns all words in a list for a searched sub-word, it also fixes fdo#62945. Change-Id: I63b69c30d28b4e1c465c2122ebc537f7f75a033a
* Work around -Werror=strict-aliasingStephan Bergmann2013-06-111-1/+2
| | | | Change-Id: I0184488344bd11c50bddd1bb1726e0d1225aff7e
* sw: fix AutoCorrect bold/underline regressionMichael Stahl2013-06-071-15/+30
| | | | | | | | | | | | | The horrible SvxAutoCorrect::AutoCorrect() inserts the character into the document half-way through, and then _expects_ this inserted character to show up in its rTxt parameter. This broke in Writer when SwTxtNode::m_Text was converted to OUString, because now a temporary String copy is created. Work around this disaster area for now. (regression from 0295c8a34e39326414c1b98cf4da905802f061b0) Change-Id: I1cb11a20cb0c2577036176e605426105631f3311
* Move to MPLv2 license headers, with ESC decision and author's permission.Michael Meeks2013-04-301-24/+4
|
* Move to MPLv2 license headers, with ESC decision and author's permission.Michael Meeks2013-04-221-23/+4
|
* mass removal of rtl:: prefixes for O(U)String*Luboš Luňák2013-04-072-21/+21
| | | | | | | | Modules sal, salhelper, cppu, cppuhelper, codemaker (selectively) and odk have kept them, in order not to break external API (the automatic using declaration is LO-internal). Change-Id: I588fc9e0c45b914f824f91c0376980621d730f09
* Related: fdo#55693 add regression tests for autocorrectionCaolán McNamara2013-03-011-0/+116
| | | | Change-Id: Ie9bbeb38ec9cc2fa0377709e75abb0338b20bab5
* Invalidate current position in LookupTree at remove action.Tomaž Vajngerl2012-07-311-6/+6
| | | | Change-Id: I7a32e8d7c21c1e87e1acab9020f9ecbb7e441f2c
* LookupTree for fast autocompletion lookups (by Nico Weyand).Tomaž Vajngerl2012-07-301-0/+225
| | | | | | | | | | | | | | LookupTree is a tree structure for fast autocompletion lookups. Additionally the tree structure stores word probabilities, so each autocompletion request returns a result with highest probability. LatinLookupTree is an implementation which was designed to be even faster and more efficient latin text, however it works with any kind of unicode strings. The tree structure was coded by Nico Weyand, Unicode strings support and conversion to Libreoffice code structure was done by me. Change-Id: I6549ee45d0952407b8a070f30ed0598fcb420aa7
* refactor handling of double border widths:Michael Stahl2012-07-041-4/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* replace enum SvxBorderStyle with css::table::BorderLineSyleMichael Stahl2012-07-041-8/+10
| | | | Change-Id: I1dadb53f46b23f92d34061ef78dda872bdbcda67
* targetted re-work of cppunit pieces.Michael Meeks2012-06-272-6/+1
|
* rename SvxBorderLine::SetStyle to something unambiguousMichael Stahl2012-06-251-6/+6
| | | | Change-Id: Iec70985319a64cdc3630e15499ac304a7f1aabae
* Renamed FILE to DOCINFO_TITLE, which is more appropriate for this field.Kohei Yoshida2012-05-141-1/+1
| | | | Change-Id: I1267629da8b66fc21c4ae2e78634c2093274aa61
* Unit test for UNO field item implementation.Kohei Yoshida2012-05-111-0/+139
| | | | | | Make sure the type IDs are associated with correct service names. Change-Id: I5ff8ec7fb56f2790f9a3eca8e019c784cb27de43
* setup/teardown default component context once before/after all testsCaolán McNamara2012-04-131-1/+1
| | | | | | | | | | | | | avoids the problems of dangling uno singletons invalidated after the first dispose and the chain of other singletons that don't expect to need to re-initialize, etc. reenable editeng cppunit test inherit i18npool cppunit test from unotest base drop LibreOfficeProtector, do "throwable" work in setUp/tearDown not in ctors/dtors
* partially revert the editeng singleton stuff to get build to completeCaolán McNamara2012-04-121-1/+1
|
* Handle the correct deletion order of EditDLL in the base class.Kohei Yoshida2012-04-121-2/+0
| | | | Turns out that this change affected all cppunit runs.
* Remove the TODO comment that's no longer relevant.Kohei Yoshida2012-04-111-1/+0
|
* We need to delete EditDLL before de-initialize vcl to avoid crash.Kohei Yoshida2012-04-111-2/+3
| | | | | | | | | Without manually releasing the EditDLL singleton instance, it gets deleted *after* the cppunit does its cleanup, which de-initializes VCL. The problem is, when the EditDLL instance is destroyed, its member GlobalEditData instance deletes the OutputDevice instance that it owns, which in turn accesses font caches in VCL. But by the time we reach that point, VCL is already de-initialized, hence the problem.
* Avoid duplicate symbols & use setUp() and tearDown() for the item pool.Kohei Yoshida2012-04-111-4/+26
|
* Just use the internal item pool already written for the edit engine.Kohei Yoshida2012-04-111-69/+4
|
* You *are* fixed.Kohei Yoshida2012-04-111-1/+0
|
* Set default items to the item pool, do this and that, and now the test passes.Kohei Yoshida2012-04-111-2/+8
|
* needs ure and base-class setUp does necessary stuffCaolán McNamara2012-04-111-7/+0
|
* Attempt to add general-purpose unit test for editeng.Kohei Yoshida2012-04-111-0/+141
| | | | | But instantiating EditEngine causes segfault. The line is commented out for now.
* fdo#38542: SvxBorderLine::GuessLinesWidths:Michael Stahl2012-01-271-1/+1
| | | | | | | | 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.
* ensure correct export size type in stream operationCaolán McNamara2011-10-101-0/+19
|
* sb140: #i113503# mixing system CppUnit and OOo STLport does not work, backed ↵Stephan Bergmann2011-09-121-1/+3
| | | | | | out a6913c9677c2 For LibO, that just means replacing sal/cppunit.h with sal/precppunit.hxx.
* Moved SvxBorder* into editeng namespace to avoid duplicate DOUBLE on windowsCédric Bosdonnat2011-03-281-0/+2
|
* editeng: Adapted borderline unit test to new build systemCédric Bosdonnat2011-03-213-128/+1
|
* editeng: more reliable test library buildCédric Bosdonnat2011-03-191-2/+11
|
* Fixed lines width guessing: gap are no smaller than 1ptCédric Bosdonnat2011-03-191-1/+1
|
* Switching the order of the SetLinesWidth argumentsCédric Bosdonnat2011-03-191-5/+28
|
* Fixed units mess in SvxBorderLine and BorderLineImplCédric Bosdonnat2011-03-192-18/+9
|
* Documented and Unit-tested the SvxBorderLine::SetLinesWidthCédric Bosdonnat2011-03-193-0/+238
generated by cgit (git 2.34.1) at 2024-09-03 20:49:58 +0000