summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* [mac] Correctly handle endianness in multi-architecture compiles on MacOS X1.4Jeremy Huddleston2008-03-131-0/+18
|
* Fix for a memory leak in pixman.Jan Slupski2008-02-141-0/+9
| | | | | Port of a 1.6 fix for a memory leak in pixman_region_init_rects/pixman_rect_alloc when the count of boxes is 0.
* PDF: Add missing struct member when writing the pattern idAdrian Johnson2008-01-181-2/+2
| | | | | | The bug did not occur on x86 due to 'id' being the first member of the struct. However on some architectures this would result in an invalid pattern id.
* Increment cairo version to 1.4.15 after the 1.4.14 releaseCarl Worth2008-01-141-1/+1
|
* Add miter-precision-ref.png to list of files to include in release.1.4.14Carl Worth2008-01-141-0/+1
|
* Update cairo version to 1.4.14 and library versioning to 13:7:11Carl Worth2008-01-141-2/+2
|
* NEWS: Mention the mixed-format-glyphs fix and update the date.Carl Worth2008-01-141-1/+6
|
* [scaled-font] Upgrade glyph mask as needed in case of mixed-format glyphsBehdad Esfahbod2008-01-143-24/+52
| | | | | | | | | In ecb895803b9d2a3fd142f4a2c694ca08c5581f0e Carl made fallback show_glyphs always use a A8 mask in case of mixed-format glyphs. That's suboptimal if there are ARGB32 glyphs. Using masks smartly we can implement the desired behavior. Done now. Cherry picked from commit 22d7f311f7733a57ece5d91708b2b5da9b71de86
* Migrate glyph mask to A8 in case of mixed-format glyphs.Carl Worth2008-01-111-3/+48
| | | | | | | | | | | | | | | | | | | | | This fixes the remaining image-backend problems with bug 13479: Ugly Courier New font with cairo 1.4.12 https://bugs.freedesktop.org/show_bug.cgi?id=13479 although the xlib-backend had been fixed previously. Specifically, if an A1 glyph is first encountered, then subsequent glyphs will still be rendered with antialiasing, (previously they would be rendered very poorly without antialiasing). Similarly, if the first glyph encountered has component-alpha sub-pixel antialiasing and then an A1 or A8 glyph is encountered then all glyphs will rendered in A8 (grayscale antialiasing). Previously, the non-subpixel-antialiased glyphs would not appear at all. Cherry picked from commit ecb895803b9d2a3fd142f4a2c694ca08c5581f0e
* [cairo-xlib] Support scale fonts with glyphs of multiple formats (#13479)Behdad Esfahbod2008-01-091-43/+136
| | | | | | | We maintain three Xrender glyphsets per scaled font, one for each of A1, A8, and ARGB32. This is required to correctly support fonts with bitmaps for some glyphs but not all. (cherry picked from commit 805b668260c47e6d3d854361fcc53f12bd2a57e1)
* [cairo-ft] Revert "Force non-AA text when using a bitmap strike with only ↵Behdad Esfahbod2008-01-091-24/+0
| | | | | | | | | | | | | | | | | scaling transform." (#13479) The reasoning for that commit was that fonts with bitmap strikes should be rendered with antialiasing off for those (hopefully) few glyphs that don't have a bitmap. However, it turns out, there are fonts that have some, but very few, bitmaps, and this changed forces non-AA rendering on them. We now support multiple glyph formats per font in the Xlib backend, so backing this out to let every glyph render as is. Fontconfig rules can be used to force AA off on a per-font basis. This reverts commit 06af5c2891b89da28581c30afcde06c5442884db. (cherry picked from commit 83963d2a9ec445e23cfbe692b877177a9d9d135e)
* NEWS: Add notes for 1.4.14Carl Worth2008-01-081-0/+21
|
* Directly check the miter corner to detect wild miters.Keith Packard2008-01-041-82/+57
| | | | | | | | The original test for wild miters would only work with a square transform (and, in fact, the original code required an identity transform). Instead of fixing that, I replaced it with a more obvious test which makes sure the miter corner lies between the two faces and not out in space somewhere. (cherry picked from commit 7cf9a6e4e39b18f4967afdb7c3c71eca5f4ba8c7)
* Add new miter-precision test. Checks miter joins at many scales.Keith Packard2008-01-044-0/+82
| | | | | | | | This demonstrates an error in cairo where miter joins are replaced with bevels at high scale factors due to a test added to eliminate wild miters drawn when the line faces are nearly parallel. Cherry picked from commit 81e029edda8c0404c6f0bd1b618e77fb55777c64
* PS: fix compiler warning introduced by previous commitAdrian Johnson2007-12-121-1/+2
|
* PS: Use the correct bounding box in Type 3 fontsAdrian Johnson2007-12-121-7/+36
| | | | Previously this was a fixed size.
* Fix regression in Type1 FallbackAdrian Johnson2007-12-121-2/+4
| | | | | | | | | | | | As a result of the changes to improve the status checking, _cairo_type2_charstrings_init() was failing due to the failure status returned when the font->output stream is destroyed. This is because _cairo_type2_charstrings_init() does not create an output stream. Fix this by initializing font->output to NULL and only destroy it if not NULL. (cherry picked from commit 1441e165f2338bc6a8e2945baca77611ff417b2f)
* PS: Use correct glyphs widths for Type 3 fontsAdrian Johnson2007-12-121-1/+7
| | | | | Previously the widths were set to 0. (cherry picked from commit f4b93cceb7fb83de558ed058915f92d4f75c1a6a)
* PS: Fix the bounding boxes of Type 3 glyphsAdrian Johnson2007-12-121-2/+2
| | | | | When viewing with ghostscript the glyphs were clipped (cherry picked from commit 78e8d3d9bd2d4652f636a668a3fa53ef9edfd9ae)
* PS: Fix typecheck error with Type 3 and recent versions of gsAdrian Johnson2007-12-121-16/+24
| | | | Ghostscipt requires the encoding vector to be filled in.
* PS: Ensure that xyshow operator has a pair of offsets for each glyphAdrian Johnson2007-12-121-1/+1
| | | | | The last entry should have been "0 0" instead of "0". (cherry picked from commit 5e8f60531a09f357db38c4b646b1bbd29b97a891)
* Fix version check for buggy_repeat on modular Xserver 1.xBernardo Innocenti2007-12-051-1/+1
| | | | | | | | The versioning of the X server has restarted from 1.0 in the modular build. So we adjust the text to avoid considering the new servers buggy. Cherry picked from commit d4138d1161c6b683fd0ef62a8d49ccf4ec4674bc
* Increment cairo version to 1.4.13 after the 1.4.12 releaseCarl Worth2007-11-271-1/+1
|
* Increment version to 1.4.12 and 13:6:111.4.12Carl Worth2007-11-261-2/+2
|
* NEWS: Add notes for cairo 1.4.12Carl Worth2007-11-261-0/+55
|
* Mark bitmap-font as XFAILCarl Worth2007-11-262-1/+3
| | | | | | | | I don't know where the PDF failure is coming from, (it appears to be using a too-small font in the rotate cairo_show_text case), but I'm seeing the same behavior in 1.4.10 so this is not a regression compared to that for the purpose of the 1.4.12 release.
* Update two PS reference images for mysterious single-pixel changeCarl Worth2007-11-262-0/+0
| | | | | | It seems ft-vertical-layout-type1 and ft-vertical-layout-type3 change rasterization slightly from time to time, (may be due to changes in the system installation of ghostscript).
* [atsui] Use ascent+descent+leading to get the distance between baselinesRichard Hult2007-11-261-1/+1
| | | | | | | | | | | The height is currently mapped to the atsui metrics property capHeight, which is documented as "The height of a capital letter in the font from the baseline to the top of the letter". That doesn't match what height is in cairo, it should be the disctance between baselines. This patch that fixes that (and makes webkit on GTK+ OS X layout nicely). (cherry picked from commit 4270cd3358fabf0d3e6ac4e866099b172082b592)
* [configure.in] fix atsui experimental warningBrian Ewins2007-11-261-1/+1
| | | | | | The 'experimental' warning for atsui was appearing for --enable-quartz not --enable-atsui as it should. (cherry picked from commit 3141b21c0c581dabc09a6ec9cdf0a071701b0e42)
* Force non-AA text when using a bitmap strike with only scaling transform.Keith Packard2007-11-261-0/+24
| | | | | | | | | When the current font size matches one of the available fixed sizes, and the overall transform has only scaling components, FreeType will use the fixed size bitmaps by default. For glyphs which do not have bitmaps, force them to be rendered in monochrome instead of anti-aliased so that they all match nicely. (cherry picked from commit 06af5c2891b89da28581c30afcde06c5442884db)
* Fix degenerate-pen test case by removing the triggering assertionCarl Worth2007-11-261-1/+15
| | | | | | | | | | | Instead we choose either the first or last pen vertex as appropriate. This makes the degenerate-pen pass stop failing on an assertion, and passes for most backends. It's still failing for the PDF backend, but that looks like a new, PDF-specific bug. (cherry picked from commit 448c9314252bba779194d2b01950b8738b26fd13)
* Limit miters for small anglesCarl Worth2007-11-261-1/+75
| | | | | | | | | | | | This fixes the current failure get-path-extents, which is a demonstration of the following bug: cairo_stroke_extents() gives wrong result for arcs in some cases https://bugs.freedesktop.org/show_bug.cgi?id=7245 Many thanks to Michael Urman whose review of early versions of this work found a fatal mistake in my algebra. (cherry picked from commit 00d701ff7de68609aa8cec7871d93b27a108fd14)
* [cairo-surface] Fix typo in doc.Chris Wilson2007-11-261-1/+1
| | | | | s/INVALUE_FORMAT/INVALID_FORMAT/ (cherry picked from commit 0d42af2427d1de27845cb8a6b3d290a562c28fc6)
* Fix typo in _cairo_gstate_finiCarl Worth2007-11-261-1/+1
| | | | | Obrigado a Luiz Americo Pereira Camara <luizmed@oi.com.br> (cherry picked from commit a69d4731300b430b802222d317698c313c75a31a)
* [quartz] return status instead of CGPatternRefBrian Ewins2007-11-261-9/+11
| | | | | | | Returning status improves error handling, since returning NULL doesn't let us distinguish different types of error. (cherry picked from commit 8f6abdbc26ee15451b5a386610f7d5a7a9114d63)
* [quartz] return status instead of cairo_quartz_surface_tBrian Ewins2007-11-261-12/+14
| | | | | | | Returning status improves error handling, since returning NULL doesn't let us distinguish different types of error. (cherry picked from commit cfb26fdf0f490b4902106b50d02628cffd53a0eb)
* [quartz] return status instead of CGShadingRefBrian Ewins2007-11-261-14/+16
| | | | | | | Returning status improves error handling, since returning NULL doesn't let us distinguish different types of error. Suggested by Chris Wilson. (cherry picked from commit dec3099585eeb184ed51b5c720eb891314d7ea51)
* fix dash-zero-length testBrian Ewins2007-11-261-5/+11
| | | | | | | | Quartz was failing the dash-zero-length test for odd numbers of dashes; it seems cairo wants 3 dashes to be on-off-on, off-on-off, wheras quartz uses on-off-on, on-off-on. Fixed by doubling the number of dashes used. (cherry picked from commit b9c065df74027b06e15e105fee5e4a4d350e0abf)
* Implement EXTEND_NONE for gradients.Brian Ewins2007-11-261-2/+4
| | | | | | | Fixes linear and radial gradients, which were displaying with extend_pad when extend_none was requested. Makes the radial-gradient test pass. (cherry picked from commit f334ee0397963e12c9efcb2690792aac83734661)
* call _cairo_error on failureBrian Ewins2007-11-261-0/+1
| | | | | Call _cairo_error to enable setting a breakpoint on quartz errors. (cherry picked from commit 0eeec372c0e7849d81bde8c8c5bf491919f51a6e)
* do not return a cairo_status_t of UNSUPPORTEDBrian Ewins2007-11-261-3/+12
| | | | | | | We had a bug which converted cairo_int_status_t to cairo_status_t, causing an assertion; reported at http://developer.imendio.com/node/128. Return the generic out of memory error instead. (cherry picked from commit 8c8ec63903f8ad67a88394eff1359607bb93cf88)
* do not ignore errors, return NULL instead (moz#874315)Brian Ewins2007-11-261-9/+28
| | | | | | | | In the quartz backend there are occasional errors where returning NULL can be used to signal that an error has occured. Mozilla bug #874315. (cherry picked from commit 6fec51990e90901ebafbb872a9e618cb70d17911)
* do not ignore errors in setup_sourceBrian Ewins2007-11-261-1/+5
| | | | | | | In setup_source we were ignoring a return value, but we can't relay it to the caller. This patch treats the error as an unsupported operation. (cherry picked from commit 07fd091e3e6b925c588b9a16f6f10efcd46615c2)
* do not ignore errors when creating styles.Brian Ewins2007-11-261-11/+26
| | | | | | | | | This fixes statuses being ignored when calling CreateSizedCopyOfStyle. As a side effect, it cleans up two other bugs - the font object was sometimes not freed, and a the scaled font mutex was aquired recursively, causing a hang in the invalid-matrix test. (cherry picked from commit b6b9cef7136453f97543173bcb2ade46b1c46b77)
* do not ignore ATSUI errors.Brian Ewins2007-11-261-7/+76
| | | | | | | This fixes multiple instances where the return value of an ATSUI call was ignored and converts them into CAIRO_STATUS_NO_MEMORY. As a side effect it fixes a utf8 array not being freed. (cherry picked from commit 4885a12c6863321a566e7103bf6dccdd5d13a986)
* do not ignore errors in glyph pathsBrian Ewins2007-11-261-6/+24
| | | | | | | | When interpreting glyph paths in ATSUI callbacks we were ignoring the cairo status. We need to return this to the caller. In order to do this we introduce a custom OSStatus code in the range that Apple reccommend. (cherry picked from commit b498c928be73635614596243d17a922e9d5ff008)
* [cairo-xlib] Check source for XRender support.Chris Wilson2007-11-261-8/+9
| | | | | | | | | | Do not rely on the assumption that if the destination has render support then the source has it as well - breaks when the boilerplate disables render support for a surface. Similarly do not set the XRender attributes on the source surface unless it actually has a xrender_format. (cherry picked from commit 3211d810d31a6607c8d78a50f577a8ca8eb705e6)
* [cairo-xlib] Release glyph surfaces if we made them to be generatedBehdad Esfahbod2007-11-261-20/+63
| | | | | | | | | | | | | The reasoning is that right now, applications render glyphs to images, upload it to the X server, and keep a local copy in the cache. The X server works hard to reuse glyph renderings, by hashing glyph images and reusing them. So we are wasting memory in cairo apps that don't use the glyph surface after uploading to the server, which is the case if you don't use the glyph in an image surface. The patch does not release the glyph surface if it already existed in the cache, so, worst case scenario is that we render the glyph twice, if you first use it with xlib, then with image surface. That effect should be negligible. (cherry picked from commit 76e3b3cdc3dda986d420637cfc2445aca481a863)
* [cairo-xlib-surface] Match content to xrender_format using the channel masks.Chris Wilson2007-11-261-4/+4
| | | | | | | | | | | | | | _xrender_format_to_content() was using the channel offset to determine whether the format supported a content type. For example, the XRenderPictFormat for the A8 format looks like: direct.alpha = 0; direct.alphaMask = 0xff; direct.red = 0; direct.redMask = 0x00; direct.green = 0; direct.greenMask = 0x00; direct.blue = 0; direct.blueMask = 0x00; which _xrender_format_to_content() matched as CAIRO_CONTENT_COLOR. Switch to using the channel masks for deducing content type. (cherry picked from commit 8ae778273799ee9f6d3c13e9c41730daeda2c743)
* [autogen.sh] Tolerate tput failure (#12757)Chris Heath2007-11-261-2/+2
| | | | (cherry picked from commit 189feaf352f59b0a049202552024578715ef8cc7)
View Lorry Controller Status