Age | Commit message (Collapse) | Author |
|
Change-Id: Ia3d1d8dbe100443410b80c3881f10ab51b2d0419
|
|
Change-Id: I4465281396f44f53ba87db0a405586294ea65076
|
|
... to store not Strings but derived SwAutoCompleteStrings with
something far saner: an abstract base class with virtual dtor.
Change-Id: I7d966f385dd41154ee1c4cdb43b56ff1aace9b5e
|
|
Change-Id: Ie1fa9b3cc2aef83ae9a82fbc110a08b2f298daef
|
|
Change-Id: I0799f22685609201dfb524c373d065b6184ed53c
|
|
Change-Id: I41d59d386b8f1fd5dc1fb9744a649085c66143f9
|
|
Change-Id: I6e242de572595fdf39553d76932bc0e953cd3a34
|
|
Change-Id: I31783eecc28cdc6f4d8c40841302d5338a2cd7be
|
|
Change-Id: I998d0f46020d3f5ea6fd387fbed8480e3d57e59a
|
|
Zemberek is a java spellchecker extension. With it installed the collecting of
spellchecker information on first activation of spellchecking is insanely slow
as the cache of spellcheckers is thrown away on each iteration through each
language known to LibreOffice.
So...
move the config updating stuff from editeng down to the linguistic layer. Let
the linguistic layer keep its spellchecker cache and listen to the extension
manager to know if an extension which might be a spellchecker one has been
modified and only throw away the cache on that event or if (existing
implementation) the config data for linguistics changes.
The polling of changed linguistic data in SvxLinguConfigUpdate::IsNeedUpdateAll
can be removed and leave it up to LngSvcMgr to load everything in its ctor and
keep itself up to date with its config and extension listeners.
Change-Id: I9c93d998928e2e7f5128c36771b3e450a8057cd6
|
|
Change-Id: I851c0ac078b57f07e0a58a9fb2119d11cc5048e5
|
|
Change-Id: Ibded6b0a72c9501d35fb884c93c505a2f716f678
|
|
getAvailableServices is very expensive, so halve the amount of calls to it that
we need. This should be logically equivalent
Change-Id: I5627ed539695fd837a497362cf9873debd254013
|
|
Change-Id: I870df7d4af666c1cb087cec6d4daebcba87ff8ab
|
|
Change-Id: Ie69b30094da25df23a36baca2c7723d6a41f48c3
|
|
This should do the inverse of ConvertBorderWidthFromWord.
Change-Id: If0b2a8a83a7faa6600a07ecfcb13a124d7cdeab6
|
|
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
|
|
Change-Id: I1dadb53f46b23f92d34061ef78dda872bdbcda67
|
|
Change-Id: I0d6aad17c471b6edd584c668dc7ff054090c185c
|
|
Change-Id: I2b482bd323ac510629c5ee31868010b7cd6ce691
|
|
Change-Id: Ia1c31cc8122c99a7e37bc285f61f8c5d2779b577
|
|
Some of them were commented out for documentation purpose.
Change-Id: I29a6b2cbe774b527f0c3a0be5675160817a7f3ce
|
|
|
|
Change-Id: I45e1618dcff920b63b7e21ba9e842eed684114d7
|
|
Change-Id: I96f76ed6b33f5c786d1e3ab3981a535037a9c1b5
|
|
Change-Id: Ib4095dee416cab6d954e1612d2e3f6e2d4464f48
|
|
Change-Id: Iafca82ac728feba97fb68523dcb032b0e17e5a3c
|
|
|
|
Change-Id: Ifd82dbc35d2f03ee9a9a40f498c8fde3f5a1d5c6
|
|
Change-Id: I494ceee07d6825f9466cab810742d7f85291fe14
|
|
|
|
Change-Id: Iec70985319a64cdc3630e15499ac304a7f1aabae
|
|
Change-Id: Ibb55fcedecaf66f0817d24d8f408ef69d273ffa2
|
|
Change-Id: Ib06d88890007fd27d6838a5c8829230733d3df97
|
|
Change-Id: I5fae2ec81b50203e9d6100f8c938fb3643ff651f
|
|
Change-Id: I8018d9b5fa01d1720c0392dc5fdc4a0656f25a35
|
|
Change-Id: I15e94f112144549692d0c2babeb48c77adcb93a9
|
|
Change-Id: I8c375e3bfbcd3d7046a8bdb1968934b7d7ca96f8
|
|
Change-Id: I6c145e984c885c7e06caa1c27bfb354ea49ad9ce
|
|
Change-Id: Ice06e639213aeb6f7f23cbf4634947dd25613db1
|
|
All of those defines (should) not be used at any point in the code.
False positives may exist, because some macro names are getting
generated by some template/macro foo. This is the version which
compiled fine for me.
Also there are many commented out lines removed.
Change-Id: I6394024682e4ab3691eb72707a9363d41ba31df8
|
|
Change-Id: If58683331c50f2a95204e8e2dea11edbef3ccb63
|
|
merge together a gadzillion hand-crafted
isSimpleChinese/isTraditionalChinese/isKoreanVariants/isCJK
implementations which should fix a goodly amount of them
add a MsLangId::isFamilyNameFirst for locales where
family name appears first while I'm at it.
Change-Id: I65377793be037d16fe7250cd7450b28aec689e83
|
|
Change-Id: I3abcd97b15d9a8500435fab795a7834fa5745dc9
|
|
Change-Id: I0fa0c60e12c418d25f8bd96cc04c6abd74b1a608
|
|
Change-Id: Icb5f5adf9139d1c0f0e86d8128ea6742ce20b138
|
|
These RID definitions aren't used at any other point. So remove
them. Unused START and END definitions were commented out for
documentation purpose.
All definitions in basctl/source/basicide/tbxctl.hrc were unused,
so I removed this file.
Change-Id: I4713188a12b9da912b2a91b85ea4e54ca1aeb994
|
|
...it is done in UniString(rtl::OUString const&) ctor anyway
Change-Id: I890ab21a6c04fe0ddc0a9b2c9a356359984e516e
|
|
...that are not intended to be short after all; just the length
calculation turned out to be wrong.
Change-Id: Ic3a81c935161564f980ddd0241575fff2f76b467
|
|
SvxUnoTextRangeBase::SetPropertyValueHelper throws a
css::lang::IllegalArgumentException but its delaration did not mention
that. This caused a crash in sd_filters_test with Apple's Clang which
does not have -fno-enforce-eh-specs. So drop the whole throw clause.
Change-Id: Ib9bbbc885f657aeb8d671c75a41b60a6544ea421
|