Hi,
Please find attached a patch that adds experimental PDF/PS export
support via cairo renderer (if cairo is compiled with PDF/PS backends,
of course, which should be the default for next stable release...).
In the process, I've moved some image format related code from gnumeric
to goffice.
Ok
On 11/28/05, Nicholas Lamb [EMAIL PROTECTED] wrote:
Is there any documentation on how to write function docs with the new
format? Compared to what I've seen so far it needs at least:
The test case for the new docs has so far been fn-R. We haven't sorted
about the example issues yet.
Just
On Tue, 2005-29-11 at 16:36 +0100, Emmanuel Pacaud wrote:
Hi,
Please find attached a patch that adds experimental PDF/PS export
support via cairo renderer (if cairo is compiled with PDF/PS backends,
of course, which should be the default for next stable release...).
Why would one consider
Hi,
Le mardi 29 novembre 2005 à 10:55 -0700, Andreas J. Guelzow a écrit :
On Tue, 2005-29-11 at 16:36 +0100, Emmanuel Pacaud wrote:
Please find attached a patch that adds experimental PDF/PS export
support via cairo renderer (if cairo is compiled with PDF/PS backends,
of course, which
On Wed, 2005-30-11 at 00:11 +0100, Pere Pujal i Carabantes wrote:
Hello all!
After some trys I've find the origin of my gnumeric printing problems:
The fact is printing in gnumeric assumes a font resolution of
aproximately 100dpi without looking if the screen is using other
resolution.
AND fails because Gnumeric considers strings to be TRUE
Fixed. Gnumeric converted strings to truth values, not always
to TRUE, though. 0 would be FALSE, for example. Also
fixed the same issue for OR and XOR.
ATAN2 fails because Excel defines ATAN2(0,0) as #DIV/0! while Gnumeric
On Wed, Nov 30, 2005 at 12:51:31AM +, Nicholas Lamb wrote:
ADDRESS failed because Gnumeric always quotes sheet names
Interesting. I just did some work on ADDRESS to handle the special
case of
ADDRESS(-1,-1,,FALSE) // R[-1]C[-1]
being ok but
ADDRESS(-1,-1,,TRUE)
not being ok.
