Age | Commit message (Collapse) | Author |
|
I hope I’m not breaking this for others who are using it, if I’m, feel
free to revert.
Change-Id: I6d91340d17c9edcd3db6064c9ab9755ffeac4f96
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/139139
Tested-by: Jenkins
Reviewed-by: خالد حسني <khaled@aliftype.com>
|
|
Previously, when measuring caret position, Writer would measure the
width of the substring before the caret (i.e. layout it independent of
the text after the caret and measure its width).
This is incorrect, though. It assumes cutting the string laying it out
would result in the same width as when laid out as part of a bigger
string, which is invalid assumption when e.g. cutting inside a ligature
or between letters that have different shapes when next to each other,
etc.
This appears to work when the width of the substring laid out alone is
close enough to its width when laid out with the full text. But in cases
where is widths are largely different, like the extreme case in the bug
report, the caret will be jumping around as it is positioned based on
the unligated glyphs not the ligated, rendered glyphs.
This change introduces a special mode of measuring text width for caret
positioning, that will layout the whole string that return the width of
the requested substring.
Fields and small caps text are trickier to handle, so old behaviour is
retained for them. Now one will probably notice but if they do, it can
be dealt with then.
This also tries to be conservative and keep other pleases using the
existing behaviour which might be desirable (e.g. when measuring text
width for line breaking, we want the unligated width), but there might
be other places that should use the new behaviour.
To handle caret inside ligatures, the grapheme clusters in the ligature
are counted and the width of the whole ligature is distributed on them
evenly. A further improvement would be using HarfBuzz API to get
ligature caret positions for fonts that provide them, which helps when
the ligature components have different widths.
Change-Id: I02062e2e2e1b1a35c8f84307c0a8f5d743059ab5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/138889
Tested-by: Jenkins
Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
|
|
Insert command in menu Sheet > Navigate
(alongs with To Previous/Next Sheet)
Use .uno:JumpToTable command from Navigator
Use its own Go To Sheet dialog
Add a Search entry to type partial name of sheet
Menu translation missing?
Change-Id: I16b8b56a688c8396159617f04a2a7e034721ce31
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134714
Tested-by: Jenkins
Reviewed-by: Laurent Balland-Poirier <laurent.balland@mailo.fr>
|
|
Change-Id: If54e8ed6c41afcaaeb6b629ffae447de7240a61f
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/129368
Tested-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I2b4cc77d1d7a873c3a3549a8132fd8a1d90525cc
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/129048
Tested-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: If2f1d379e8e8694a3519d20eb3f425c0bbd381e6
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/129032
Tested-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: Ibd537ed709be237e00715057c162dd9197759373
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/127722
Tested-by: Jenkins
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
|
|
Change-Id: I2b86c39610f31260fe8fb5abdbb94e853ec31cec
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/127700
Tested-by: Jenkins
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
|
|
Build target was kept for backward compat in 'rework the default make
target', so lets retire it after 1.5 years.
Use 'make build' instead (which is since the default target anyway).
Change-Id: I93d5237dce2abf2536a4d847d79d33d5b6d6cec9
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126362
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens <thorsten.behrens@allotropia.de>
|
|
Change-Id: I00bafec0f3caef86fa886dc4331e5d38e9fa1766
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/125755
Tested-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I10e84beb550c9e0410c35fe85db407fa1dceb5b1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/123955
Tested-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Previously, all of the README files have been renamed to README.md
and now, the contents of these files were changed to use Markdown
format. Other than format inconsistency, some README.md files lacked
information about modules, or were out of date. By using LibreOffice
/ OpenOffice wiki and other documentation websites, these files were
updated. Now every README.md file has a title, and some description.
The top-level README.md file is changed to add links to the modules.
The result of processing the Markdown format README.md files can be
seen at: https://docs.libreoffice.org/
Change-Id: Ic3b0c3c064a2498d6a435253b041df010cd7797a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/113424
Tested-by: Jenkins
Reviewed-by: Michael Stahl <michael.stahl@allotropia.de>
Reviewed-by: Adolfo Jayme Barrientos <fitojb@ubuntu.com>
|
|
Renaming all README files for all top level modules to README.md,
applying no content change at this stage to be able to track history
of the files. These files should be edited to use correct Markdown
syntax later.
Change-Id: I542fa3f3d32072156f16eaad2211a397cc212665
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/112977
Tested-by: Jenkins
Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
|
|
Change-Id: I130273b7b5e812df1eeb904f652d23a492398636
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/109270
Tested-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: Ie669750404dd9b73881a9e217e3cced0bf21e42b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/109263
Tested-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I5f00e1ef1b606a7b1c19d5c55ed5bdbe1ef194f8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/107433
Tested-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
(Xcode also insists on moving a couple of other lines around, oh
well.)
Change-Id: I7b295f51ca5b38bfcace464f9d06bfe2d93de066
|
|
Note that what osx/README says still holds. This Xcode project is for
making debugging easier only.
Change-Id: I8ebbad2a2de5366616ad7304125bdd05ae001489
|
|
Clang's scan-build tool uses the CLANG_CXX environment variable (setting it up
in the scan-build script to pass it to the ccc-analyzer script), but happens to
erroneously set it to a non-existing path (see <https://reviews.llvm.org/D89481>
"[scan-build] Fix clang++ pathname again"). So wrapping LO's autogen.sh and
make in scan-build picked up that broken CLANG_CXX and caused build
failures like
> [CXX] external/skia/source/SkMemory_malloc.cxx
> /bin/sh: ~/llvm/inst/bin/clang-12++: No such file or directory
(see
<https://lists.freedesktop.org/archives/libreoffice/2020-October/086113.html>
"Re: llvm/clang static analyzer reports").
So rename CLANG_CXX, and for consistency also CLANG_CC and the various
CLANG_CXXFLAGS_INTRINSICS_*, by prefixing each with LO_.
Change-Id: Ib41cabe940f8bfb1997f74e865cca5725f859e07
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/104383
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
|
|
Change-Id: Ie8fa026becb1899e466fb0e7dbb987290788aaf2
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/96207
Tested-by: Jenkins
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
|
|
Change-Id: I7462abcf0e79b4c43c8fd67c755113484e245310
|
|
Change-Id: I173846f9073364ac5573744e9d03cdbef22a8c10
|
|
Change-Id: If5bc137d95dd507fbf748b45c11d6b18094dc0ba
|
|
Change-Id: I3f0555a8a1a83342dd0dfff266f92c47ed5a9f80
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/94063
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I21e0ebb7776f829c1ad97272be4210d7e7dfbb34
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/93949
Tested-by: Jenkins
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I48ed28f8b6ccb125aefb464550bc9fa1238bb086
|
|
Change-Id: I0558fc3190983f5b97f40599c51d074b2bb72ada
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/93160
Tested-by: Tor Lillqvist <tml@collabora.com>
Reviewed-by: Tor Lillqvist <tml@collabora.com>
|
|
Change-Id: I0008393be56341fe7e1f385bd111475b67446240
|
|
(A fairly ad-hoc small subset of the source files are included in the
Xcode project to make it possible to set breakpoints in them in
advance.)
Change-Id: I6c2655337e1d623b299e65aa977650e7519b7bd8
|
|
Change-Id: I651b7f202fa52ff5f5357a11aa72c43eb7dc7f95
Reviewed-on: https://gerrit.libreoffice.org/64102
Tested-by: Jenkins
Reviewed-by: Bartosz Kosiorek <gang65@poczta.onet.pl>
|
|
Change-Id: Ibfc8995c4d35c33fe203b9779b10a182cf5a4294
|
|
Change-Id: Ia9a87f3f9bdf357079c6d259d736504e0109bf57
|
|
Change-Id: I36b42ca16932cab10342894840f57e89d08dac4f
|
|
In order to compile correct this flag is needed and
it is not exported in the json files
Change-Id: Ib8f0b882f2d59ed467a9198c148263e2882c60b3
|
|
First step in removing make as builder.
Change-Id: I445627df5610a7d0b8bfbabddb66f1273e021b1a
|
|
Change-Id: Ic9b44918a27bf185c534b3705f15a2dac29bc642
|
|
Change-Id: I77b30f28ae5a6fad360d7cada9acfaa9c324408b
Reviewed-on: https://gerrit.libreoffice.org/22216
Reviewed-by: Chris Sherlock <chris.sherlock79@gmail.com>
Tested-by: Chris Sherlock <chris.sherlock79@gmail.com>
|
|
Not intended for other use. The Xcode project has references to a
fairly arbitrary bunch of source files from here and there in LO that
I have happened to been debugging in Xcode on OS X.
Change-Id: I9e94c02b2a4b057e35310362c90167f7e8670bb8
|