[cairo] [PATCH] doc: fix some broken references

Maarten Bosmans mkbosmans at gmail.com
Mon Jan 10 04:20:30 PST 2011

2010/12/30 Andrea Canciani <ranma42 at gmail.com>:
> On Thu, Dec 30, 2010 at 11:01 AM, Maarten Bosmans <mkbosmans at gmail.com> wrote:
>> 2010/12/29 Andrea Canciani <ranma42 at gmail.com>:
>>>> Am 28.12.2010 13:50, Maarten Bosmans wrote:
>>>>> This fixes some obvious mistakes in the docs.
>>> The attachment is a patch that should probably be merged with yours.
>> Attached is a new version of my patch and a modified version of yours,
>> with duplicate changes removed
>>> Cairo docs would use some more love and I have a couple of items in my
>>> TODO list, but I haven't fixed them yet.
>> Any suggestions? I was thinking of adding some more cross references
>> ('see also' links) between relevant functions.
> Straight from my TODO list:
>  - document filtering, gradients, get_data/flush/mark_dirty
> We should document the definition of the gradients (or at least give a
> reference to the PDF specification aka ISO32000, where their definition
> is mathematically sound and detailed enough).
> cairo_image_surface_get_data() should reference cairo_surface_flush(), which
> must be called before reading/writing data, and cairo_surface_mark_dirty(),
> which must be called if the content of the data has been modified.
> Similar functions in other backends (cairo_win32_surface_get_dc,
> cairo_win32_surface_get_image, ...) should receive a similar treatment.
> cairo_filter_t and cairo_extend_t would use a more complete definition
> (what does each extend mode mean for gradients, expecially when the
> stops don't cover the whole 0..1 range? etc etc)

Can my patches be applied by someone then? You can then work on top of that.


More information about the cairo mailing list