Age | Commit message (Collapse) | Author |
|
With several legacy pre-ODF1.2 and ODF1.2-only consumers out there,
folks wanted a more backward-compatible ODF1.2 extended mode, that
uses stuff deprecated in 1.2, and/or is 'bug-compatible' to older
OOo-versions.
Therefore, adding ODFVER_012_EXT_COMPAT, and sticking it to several
attributes that were ODFVER_LATEST before.
|
|
Make "export extended ODF" consistently mean "version > ODF1.2".
Future ODF versions need manual review anyway, of the various
changes/additions we ship.
Change-Id: I0f6c1646b306e18f0abcdd1a1802fece821b2e93
|
|
|
|
Change-Id: Iba2839ec04a79b8fa49968aebb194f9dc6799d4d
|
|
Change-Id: I699c424f536b0096b35d3db3aee371793e9e56c4
|
|
Change-Id: I4c20bf3a2aa5ca908db233e54f50404cc7466d72
|
|
Change-Id: Ia54eaa5cb1aa8bb4a052cea25396b07f048ff74c
|
|
* LIBO_LANGTAG_DATADIR environment variable may point to liblangtag data and
override REGDATADIR define.
* deliver data files to $SOLARVER/$INPATH/share/liblangtag
|
|
Change-Id: I687328d08c89c45fc5d95ee02aea5318b9b5a3ff
|
|
Change-Id: I504d3b0ac6250b88ca3de3cad179a7caec35e2a5
|
|
PrintFontManager::countFontconfigFonts returns an int but it's never used
so let's drop the int returned
Change-Id: Iab00916aec36b899a04555743d698a3fc1d45085
|
|
Change-Id: Ic6814b9a3916493bf0b1c96d5e8c12f3d187f887
|
|
If a word is in sentence case then the auto-completed word should
be in the same case i.e. if the auto-complete list contains the
word "LIBRE" then "Lib" should auto-complete to "Libre" rather
than "LibRE". See OpenOffice bug 22961.
Also implement better i18n handling for calander month and day
names. Previously, if a month or day name was not ASCII then it
would only auto-complete if it exactly matched the names retrieved
from the internal calander i.e. had be a case sensitive match.
Change-Id: I0c4543bd9e912072bce1ceaf4adecd41b55b576b
|
|
Note that the replacement vector stores all strings first and then
sort and "unique" are applied (ASCII treated as case-insensitive).
Previously strings were inserted sequentially and only the first
version of a string would be stored (case-insensitive ASCII
comparision). This should have no material impact as the strings
retreived from SwAutoCompleteWord are already unique (case-
insensitive ASCII comparison) and the capitalization of the string
is generally changed anyway to match the capitalization of the word
to be auto-completed. Also, there appears to be no logical reason
to store the first inserted version of a string over of the first
version post-sort.
Change-Id: I132865bbb9b382d417fb2cff9de351fdb2cbfb13
|
|
Change-Id: I56b5bcd459c79de5be079d0c6563148e17f0bc9b
|
|
... BOOST_STATIC_ASSERT_MSG was added in boost 1.46, while the internal
boost is still at version 1.44, so use BOOST_STATIC_ASSERT instead.
Change-Id: I14f8e48e31956b34a1a907cd2c4e454a5715889b
|
|
Change-Id: If75d2daaac2c629028a76f55941345c1c565a69a
|
|
We do a "SELECT * FROM table" just to fetch the primary key columns;
so reuse the same XResultSet to fetch all columns.
Else, we immediately issue a "SELECT * FROM table WHERE
primary_key=current_value" to read the other columns, which is
wasteful and particularly silly.
Commit 1ae17f5b03cc14844fb600ca3573a96deb37ab3b already tried
to do that, but was essentially reverted piecewise because
it caused fdo#47520, fdo#48345, fdo#50372.
Commit c08067d6da94743d53217cbc26cffae00a22dc3a thought it did that,
but actually reverted commit 1ae17f5b03cc14844fb600ca3573a96deb37ab3b.
This implementation fetches the whole current row and caches it in memory;
only one row is cached: when the current row changes, the cache contains
the new current row.
This could be problematic (wrt to memory consumption) if the current
row is big (e.g. with BLOBs) and nobody is interested in the data
anyway (as would often be the case with BLOBs). Note that because of
our "SELECT *", the driver most probably has it in memory already
anyway, so we don't make the situation that much worse.
This could be incrementally improved with a heuristic of not
preemptively caching binary data (and also not LONGVARCHAR / TEXT /
MEMO / ...); a getFOO on these columns would issue a specific "SELECT
column FROM table WHERE primary_key=current_value" each time.
The *real* complete fix to all these issues would be to not do "SELECT
*" at all. Use "SELECT pkey_col1, pkey_col2, ..." when we are only
interested in the key columns. As to data, somehow figure out which
columns were ar interested in and "SELECT" only these (and maybe only
those with "small datatype"?). Interesting columns could be determined
by our caller (creator) as an argument to our constructor, or some
heuristic (no binary data, no "big" unbound data).
Also be extra smart and use *(m_aKeyIter) when getFOO is called
on a column included in it (and don't include it in any subsequent
SELECT).
However, there are several pitfalls.
One is buggy drivers that give use column names of columns that we
cannot fetch :-| Using "SELECT *" works around that because the driver
there *obviously* gives us only fetchable columns in the result.
Another one is the very restrictive nature of some database access
technologies. Take for example ODBC:
- Data can be fetched only *once* (with the SQLGetData interface;
bound columns offer a way around that, but that's viable only for
constant-length data, not variable-length data).
This could be addressed by an intelligent & lazy cache.
- Data must be fetched in increasing order of column number
(again, this is about SQLGetData).
This is a harder issue. The current solution has the nice advantage
of completely isolating the rest of LibO from these restrictions.
I don't currently see how to cleanly avoid (potentially
unnecessarily) caching column 4 if we are asked for column 3 then
column 5, just in case we are asked for column 4 later on, unless
we issue a specific "SELECT column4" later. But the latter would be
quite expensive in terms of app-to-database roudtripe times :-( and
thus creates another performance issue.
Change-Id: I999b3f8f0b8a215acb390ffefc839235346e8353
|
|
Change-Id: Ia8d12d02829087309e248506a7d3b0f94b5a425e
|
|
Change-Id: I3d7023fcb1857da1ef107a8af0d373b9ca464f03
|
|
Change-Id: I1dbb1990033602d7909ecdee72b8b699cce44cab
|
|
fixup of d4ae29a37873843c20fe7d5f5f071f8fb201fed9
after the call to m_pCacheSet->absolute_checked, the data *is* used,
so we cannot anymore exempt m_pCacheSet from giving correct data.
Change-Id: I7d3644ca08ce43cb030a80984605a1f8a8a64211
|
|
Seems these were dropped in 3c4cd1deaf71d0d800957b3580d426c721bf7844.
Change-Id: Ib929e322719e4a50d8d2d32e3cd9466242e1c034
|
|
revert one hunk from 909cd34b7b0982078a50b9ed46cf57811d9571df
Change-Id: I9eb3f3c1cdab2c0624ab65f540b9c3d6b8f1bfb5
|
|
...if there are actually individual line widths given; fixes the
sw_rtftok test.
Change-Id: If5f6ef54b93c5bfccfd011f25d9d9301637d388e
|
|
don't call UpdateAllRowHeights when IsAdjustHeightEnabled property is set and additionally set manual heights for *all* imported row heights ( same afaics xls import does ) - certainly this improves import ( also see documents attached in i#94028, i#93609 )
Change-Id: Id8aff727587ed4fa19fd0897aaf25b2202737084
|
|
this change manaully reverts c07e9299bb2c8d5477669568b12708bd2ff12684 & 4908c16a73b397f83c327789f113658c1ea4d904
Change-Id: Ia8656631f84709430c8e94e8d9dfa961e81d5746
|
|
Change-Id: I0ea2191a281405a0672fac2f8c1d4dafea224ef4
|
|
Change-Id: I8811ce96cb70429ae458e31cafb8979bb6bb9644
|
|
Change-Id: I2e97af8b0d1d6a6770730aa0bf22556b2ec115c0
|
|
|
|
|
|
Update calls to factories to use new ::create methods
Change-Id: I01d4417820f52718836c92faf3c2fae0dc96b30d
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>, added some tweaks.
|
|
Change-Id: Ib8017f950f414601676b54c36425a0592b4cc395
|
|
INCLUDE is used by MSVC (http://msdn.microsoft.com/en-us/library/kezkeayy.aspx)
and make somehow (not sure why) exports the INCLUDE that gbuild uses,
which (again, not sure why) causes MSVC to report a misleading error about
incorrect argument. There actually does not appear to be any (unreasonably)
low path length limit on Windows.
Change-Id: I9329eb668f7a710ec69c8b5262b855f346ed01d2
|
|
Module lcms2 is now using $GNUMAKE instead of the hardcoded "make" in order to allow compilation under Solaris
Change-Id: If4b3395e2b255f6199971792988c242dc5c13a69
|
|
re-instated lines that were accidentally wiped out in configure.in
Change-Id: I54d3140723e99eae1dda6c7b05c29327a22028a3
|
|
Similarly to Ifb04d4a8e485182c5ef2771025b06832bfd75ae0 (commit
ac25f124858b79e302adcc533d6a658d5c529394), we need to rotate the bounding
box of glyphs on MacOSX too.
Additionally, round the position up, and convert the size more
straight-forward way.
Change-Id: Idf7a077836e65072795c6d98d61925ce62ee35b7
|
|
Change-Id: Ibc600ce33bd59b3fd2d5ff29c5fb19710dc0df8f
|
|
There are 2 problems here:
- the border widths are tripled on import, because that is effectively
what SetWidth does for DOUBLE borders; set a divisor of 3 similar to
e2ffb71305c5f085eec6d396651c76d6daee3406
- the 3 individual line widths are ignored and the 3 lines end up with
the same width, while older versions had numerous pre-defined border
styles with asymmetric line widths; fix this by always guessing the
width from the 3 parts for DOUBLE lines
Change-Id: Ibdde7e034e25433835765330e81db0825efd9eb8
|
|
Presumably that is what Martin wanted to do in the previous patch.
Change-Id: I64f1da88c1802a27cf974aa6abc15b014b56126d
|
|
Change-Id: I974ac27ee17219ce3f8a7e5641dbb0098da18f8e
|
|
Change-Id: I7924da4bff73ca8f82c76eb8cb211401530acdeb
|
|
Current resampling methods for images are FAST and INTERPOLATE.
FAST is used where speed of resampling is required, on the other
hand INTERPOLATE resampling is used when we need quality. For
example INTERPOLATE resampling method is used at PDF export.
INTERPOLATE resampling uses bilinear interpolation which is known
to be lower quality as other modern (and slower) resampling
algorithms such as Lanczos, Mitchell or BiCubic resampling.
This change adds Lanczos resampling to the Bitmap class and
enables Lanczos resampling in PDF export.
Lanczos3 resampling is implmented using separable convolution
with which it is also possible to easily add other resampling
methods like BiCubic just by changing the kernel function.
Change-Id: I8dff5b65753b09dffd5bc34f2343d9818efb3e58
|
|
Change-Id: I17df8114983a06f7a58df30821873ecd4387cec0
|
|
Change-Id: Iabaf8f41e82fb7c2f881057bedb4c7757dcf1bce
|
|
Change-Id: I9ee6283a7f4a0b436ea89c7bd16af756c6aa36e4
|
|
Hierarchical path is assumed in loads of places, changed the URLs to the
following:
* Binding URL is encoded in the authority part, the repository ID is
set as a fragment of the binding URL.
* The hierarchical path reflects one of the path to the document on
the server
:x
Change-Id: I8214daeb1d9c9b0f6ab86bdf60875e7e4e5369f4
|
|
Change-Id: I2c49b95279d90ebb06f38ed83061a5f1a905a555
|
|
Change-Id: I9122de6c04561f72c633b05983590871d9ec3a73
|