office-gobmx/editeng
Stephan Bergmann 9e0de138a5 Use sal_Int64 to printf tools::Long values
(The "%l" format specifiers had now caused -Werror,-Wformat with clang-cl for a
Windows 64-bit build.)

Change-Id: I86b9617310f7348d72172cc7a29f0976c7030dd5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/106576
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2020-11-25 14:07:07 +01:00
..
inc tdf#123936 Formatting files in module editeng with clang-format 2020-11-13 15:15:59 +01:00
qa loplugin:stringviewparam extend to comparison operators 2020-11-24 09:45:04 +01:00
source Use sal_Int64 to printf tools::Long values 2020-11-25 14:07:07 +01:00
uiconfig/ui
AllLangMoTarget_editeng.mk
CppunitTest_editeng_borderline.mk
CppunitTest_editeng_core.mk
CppunitTest_editeng_lookuptree.mk
CustomTarget_generated.mk
IwyuFilter_editeng.yaml tdf#42949 Fix new IWYU warnings in directories [e-f]* 2020-11-12 10:53:07 +01:00
Library_editeng.mk
Makefile
Module_editeng.mk
README
UIConfig_editeng.mk

Edit engine.

In OO.o build DEV300m72 this module was split off from svx but it
has no dependencies on [[svx]] (nor on [[sfx2]]) while in turn svx depends on editeng
Read more in the mailing list post:
[http://www.mail-archive.com/dev@openoffice.org/msg13237.html]

If you build LibreOffice with dbgutil, you have some extended debug keys:
Ctrl+Alt+F1 - draws the paragraph rectangles in different colors
Ctrl+Alt+F11 - toggles dumping the edit engine state to the
               "editenginedump.log" on draw
Ctrl+Alt+F12 - dumps the current edit engine state to "editenginedump.log"