diff options
| author | Andrea Gelmini <andrea.gelmini@gelma.net> | 2019-08-09 17:13:59 +0200 |
|---|---|---|
| committer | Julien Nabet <serval2412@yahoo.fr> | 2019-08-09 18:02:08 +0200 |
| commit | e6c036915b75cd5c81323e337a8604701b869052 (patch) | |
| tree | 75eb436ed26dcffbbc9659206b35436bc13fe6f9 /vcl | |
| parent | b8c87fa294678180191588134b9e9c7993a659fc (diff) | |
Fix typos
Change-Id: Ie63c7b2d8bf9579b7b41d7bae515818c8d5706dc
Reviewed-on: https://gerrit.libreoffice.org/77217
Reviewed-by: Julien Nabet <serval2412@yahoo.fr>
Tested-by: Julien Nabet <serval2412@yahoo.fr>
Diffstat (limited to 'vcl')
| -rw-r--r-- | vcl/README | 4 | ||||
| -rw-r--r-- | vcl/README.lifecycle | 2 | ||||
| -rw-r--r-- | vcl/README.scheduler | 2 | ||||
| -rw-r--r-- | vcl/inc/salframe.hxx | 2 |
4 files changed, 5 insertions, 5 deletions
diff --git a/vcl/README b/vcl/README index 6ee9dad11e80..d37ffe9e8407 100644 --- a/vcl/README +++ b/vcl/README @@ -110,7 +110,7 @@ emf/wmf is translated to GDIMetafile in import filter vcl/source/filter/wmf and so special handling ends here emf+ is encapsulated into GDIMetafile inside comment records and -parsed/rendered later, when it reaches cppcanvas. it is parsed and +parsed/rendered later, when it reaches cppcanvas. It is parsed and rendered in cppcanvas/source/mtfrenderer. also note that there are emf+-only and emf+-dual files. dual files contains both types of records (emf and emf+) for rendering the images. these can used also @@ -196,7 +196,7 @@ compression is disabled (so the PDF file is directly readable) and the MARK function puts comments into the PDF file about which method generated the following PDF content. -The compression can be disabled even using a env. var: +The compression can be disabled even using an env. var: export VCL_DEBUG_DISABLE_PDFCOMPRESSION=1 diff --git a/vcl/README.lifecycle b/vcl/README.lifecycle index d9d186425b64..c7dc05812b03 100644 --- a/vcl/README.lifecycle +++ b/vcl/README.lifecycle @@ -30,7 +30,7 @@ between calls: Update(); Unfortunately use of such protection is/was ad-hoc, and far -from uniform, despite the prevelance of such potential problems. +from uniform, despite the prevalence of such potential problems. When a lifecycle problem was hit, typically it would take the form of accessing memory that had been freed, and contained garbage due diff --git a/vcl/README.scheduler b/vcl/README.scheduler index 23decf3b7ec2..56be76913781 100644 --- a/vcl/README.scheduler +++ b/vcl/README.scheduler @@ -162,7 +162,7 @@ loop. == General: invalidation of elapsed timer event messages == Since the system timer to run the scheduler is single-shot, there should never -be more then one elapsed timer event in system event queue. When stopping or +be more than one elapsed timer event in system event queue. When stopping or restarting the timer, we eventually have to remove the now invalid event from the queue. diff --git a/vcl/inc/salframe.hxx b/vcl/inc/salframe.hxx index 19293b913621..e190d3e758b5 100644 --- a/vcl/inc/salframe.hxx +++ b/vcl/inc/salframe.hxx @@ -282,7 +282,7 @@ public: virtual weld::Window* GetFrameWeld() const; - // Callbacks (indepent part in vcl/source/window/winproc.cxx) + // Callbacks (independent part in vcl/source/window/winproc.cxx) // for default message handling return 0 void SetCallback( vcl::Window* pWindow, SALFRAMEPROC pProc ); |