Age | Commit message (Collapse) | Author | Files | Lines |
|
Added a preferred extension property to the filter which overwrites
one(s) given by the default file format type associated with it.
Normally this property is not used for the majority of the filters,
but for plain text filters, we need to use .txt when saving from
writer whereas we do .csv from calc.
(cherry picked from commit ba03f2dc817c692fa8709391ec83d8e01a0f8b28)
(cherry picked from commit 84d1ff7be178ec3572710e092e85fe548ce3042b)
(cherry picked from commit 45b03c888042052a47cb79bc5a2837d04e115c5e)
Squashed these 3 commits into 1.
Also needed rtl::OUString("*.") instead of OUString("*.") in
sfx2/source/bastyp/fltfnc.cxx
Change-Id: Ic6d769bc1180f88fd75f40909e5e054d45719178
Signed-off-by: Eike Rathke <erack@redhat.com>
|
|
Signed-off-by: Petr Mladek <pmladek@suse.cz>
|
|
The Lanczos scaling is of very good quality, but it's rather slow,
which can be very noticeable with large images, so it's not a very
good default for everything. And in general, it's not good to refer
to a specific algorithm when all one usually wants is fast/default/best.
Some of these changes are a bit of a guess between default/best,
but the general logic is that best should be used only for images
that won't be large or where the possible waiting does not matter.
Conflicts:
svtools/source/graphic/grfmgr2.cxx
Change-Id: I53765507ecb7ed167890f6dd05e73fe53ffd0231
|
|
Change-Id: I0362d758205e7d12484e9e86ff2dce9608730c57
|
|
Change-Id: I86b31156e1a9221d9cfdc40d5670b324ce056a89
|
|
Change-Id: Ia0bc37f81b7213b20fc5093beb46d7a05b1ac931
Signed-off-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
|
|
Change-Id: Ib30a77808b9f4726e72f57e9d9ea73c71f5cac34
|
|
Change-Id: I2407a2ebc01f39655b30f7eb1e65deb912f2e606
|
|
Where we explicitly ask for better quality, use BMP_SCALE_LANCZOS, instead of
BMP_SCALE_INTERPOLATE.
Change-Id: I28ddf3290204532a8660e09ee9ab0949b6ce1c73
|
|
Change-Id: I2ee4fbb1e166a926b36b100c47e6da4cf39d51b4
|
|
Change-Id: I44518bb1b464bb0b458c0b5f1c249ef160ea3b26
|
|
Change-Id: I96ce39a3982d7d638283c18a5913c1df13979b1f
|
|
|
|
Change-Id: Ic00cdfce4172af0a2f0aa1aa33ef5e386d407976
|
|
More information on this thread:
http://nabble.documentfoundation.org/Advice-needed-about-some-cppcheck-reports-td3986408.html
Change-Id: Ib70532ad72e8418e1036bd52c07dc6452508cd12
|
|
Change-Id: Ic123c081fcf6ddcf5d61c5d5a3eab01db470014c
|
|
Change-Id: I11f7642346ccc1949d5716b32444df86541eabf8
|
|
Change-Id: I64a38e22f776914605fe3903312524d8827e29a2
|
|
MSO uses undocumented properties that seem to map to o:hr and o:hrpct
from .docx (including differences between .docx spec and implementation),
so treat horizontal rule width the same way in .doc too. Also remove
the guesswork for #i17200# that is not quite correct and no longer needed.
Change-Id: Ibec543fa1679ca0b20e86ef6b4f77147b18dff7e
|
|
Change-Id: Ic709bb128a82016b1bbc2c43cf4fe7ad091e7b1a
|
|
Change-Id: Ic535667b3705fc707966e403edc32681a3c315e9
|
|
Change-Id: I550021c693c0971b952a708f51a0196cbe1fc8dc
|
|
Lotus 1.2.3 is a spreadsheet. We don't need this for Writer.
Change-Id: I7fce85a6e211c0bf1ef6e95e758b4dc8cfcae033
|
|
This way we can run detection services in the correct order; from
more complex to less complex, since the more complex structure is
much easier to test and reject.
Change-Id: Iee2d3e2e4f2834f95e6e89975f646e3928114b11
|
|
Change-Id: Ie2fada1c641d2bc313ddb14903083beab08f8a98
|
|
Change-Id: I95c04f954026047e48976451eb755340d005d773
|
|
Change-Id: I41d24c8d14a781e4100813ebce136d563f8c36b8
|
|
Change-Id: Iab2f715b37d9fae816723b84ee1116fd4aff9537
|
|
Change-Id: I0335111dd30850db435d728ddcc6b4554eea6f5b
|
|
Change-Id: Id7d5744af4800ef5ac6bd70b97f79a76299a2e6b
|
|
Change-Id: Ica6aef56733c7c71568e37166a2f78d6aa05a118
|
|
Change-Id: I95edb869b00764464d91e1f396da1bb648b74515
|
|
Change-Id: I50d5cee6302e8d6b4b329e30b7a5ce47b47bc945
|
|
Right now it will always fail.
Change-Id: I50011bbf7ce59c3b299d23e688dd1af87bcafeb6
|
|
Change-Id: Ib401fb6287efda68d07732382fc814961138d8a9
|
|
This unfortunately breaks plain text format detection for writer, but I'll
get to that next.
Change-Id: I70382529596dbc3e3af4935d6e98ad6d58bb4d91
|
|
Change-Id: Ia5f26c13e7bae42685230769fa86b52703eb2f7e
|
|
Change-Id: If4b946ef4407279f3b260a0f8a8d8309522aa594
|
|
This already didn't work in 3.5.
Change-Id: I12afc1bcdc5c20a7846833763080dac02214e01b
|
|
this avoid the root cause of this bug, avoiding creating a
B2DPlygon which contains no points.
It seems the code relies somehow on an null B2DPolyPolygon, hence the
change done here. Better would be to have time to look how to remove
this fact. But currently it seems the code relies on a
rSet.Put( XLineStartItem( aArrowName, aPolyPoly) where aPolyPoly is
not defined in certain cases.
Change-Id: I61b75d925090d1c9a0da96ce1a6eea50a2d60e5a
|
|
This should reflect the fact that this type was already used as a
generic HTML type.
Change-Id: I0a209d51ed229f07aff001075c39bfc82d4c3088
|
|
Change-Id: I35a3efc506bbcc33ea4c3d2466929f8227dae102
|
|
Change-Id: Ie335ee44a347ab588dbf6cdeb38ef19246c1ad47
|
|
Change-Id: I2aeba0342e46c3a4bd50f49b8a43ebb125269dfa
|
|
Change-Id: If02be864f958de96ae1c54fe575b1828410390b1
|
|
Change-Id: Ib2642e19d9148acca27227b0d91de4e8855178aa
|
|
Change-Id: I5a097beaaeb30214ed6071bba1297e551291922b
|
|
Change-Id: I7d98f36037f589ea742de53b2a52e2c5bdf7c48f
|
|
Change-Id: Ib9bea60e05f1dcdd9501a3320f3b1185d5890d17
|
|
- older BorderLine doesn't seem to work in case InnerLineWidth and OuterLineWidth are set to equal positive value and distance is set to 0 (possible regression)
- using the newer API solves the problem for us
Change-Id: I69f10a0e947352d20b78dbdc39b7c9af95f8603b
|