[cairo-commit] NEWS

Carl Worth cworth at kemper.freedesktop.org
Tue Aug 8 16:51:58 PDT 2006

 NEWS |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

New commits:
diff-tree 27842ff06f0f4cb764516e91ad51c8a92078e0fa (from c96e1b6d8ff06eba7b09b5ff3c60fe09d56eb80c)
Author: Carl Worth <cworth at cworth.org>
Date:   Tue Aug 8 16:51:48 2006 -0700

    NEWS: Fix some misspellings

diff --git a/NEWS b/NEWS
index eb71938..570aee1 100644
--- a/NEWS
+++ b/NEWS
@@ -42,7 +42,7 @@ The various "print" backends, (pdf, ps, 
 to using image-based rendering for some operations. In cairo 1.2.0
 these image fallbacks were scaled improperly. Applications using cairo
 can influence the resolution of the image fallbacks with
-cairo_surface_set_fallback_resolution. With the bug, any calue other
+cairo_surface_set_fallback_resolution. With the bug, any value other
 than 72.0 would lead to incorrect results, (larger values would lead
 to increasingly shrunken output).
@@ -56,7 +56,7 @@ translation components of a font matrix 
 series, font matrix translation could be used to offset the glyph
 origin, (though glyph metrics were reported incorrectly in
 1.0). However in 1.2.0, the translation was applied to the advance
-values betwen each glyph. The 1.2.0 behavior is fairly useless in
+values between each glyph. The 1.2.0 behavior is fairly useless in
 practice, and it was not intentional to introduce a semantic
 change. With 1.2.2 we return to the 1.0 semantics, with a much better
 implementation that provides correct glyph metrics.
@@ -69,7 +69,7 @@ There has been a long-standing issue wit
 such that font options and other settings from the original
 destination surface would not be preserved to the intermediate
 "similar" surface. This could result in incorrect rendering
-(particulary with respect to text hinting/antialiasing) with
+(particularly with respect to text hinting/antialiasing) with
 fallbacks, for example.
 report:	https://bugs.freedesktop.org/show_bug.cgi?id=4106
@@ -79,7 +79,7 @@ fixes:	http://gitweb.freedesktop.org/?p=
 xlib: Fix text performance regression from 1.0 to 1.2.0 (Vladimir Vukicevic)
 Several people noticed that upgrading from cairo 1.0 to cairo 1.2.0
-caused a significant peformance regression when using the xlib
+caused a significant performance regression when using the xlib
 backend. This performance regression was particularly noticeable when
 doing lots of text rendering and when using a high-latency connection
 to the X server, (such as a remote X server over an ssh

More information about the cairo-commit mailing list