Bug 248785 - eog using wrong units for svg <clipPath>
Summary: eog using wrong units for svg <clipPath>
Alias: None
Product: Fedora
Classification: Fedora
Component: eog (Show other bugs)
(Show other bugs)
Version: 7
Hardware: All Linux
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-07-18 19:17 UTC by John Ellson
Modified: 2008-06-17 01:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-06-17 01:54:36 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
small cairo example that generates a box image in viewtest.svg (846 bytes, text/x-csrc)
2007-07-18 19:17 UTC, John Ellson
no flags Details
the svg output of the cairo viewtest.c example (545 bytes, text/plain)
2007-07-18 19:19 UTC, John Ellson
no flags Details

Description John Ellson 2007-07-18 19:17:50 UTC
Description of problem:
Cairo generates a clipRegion in the default units (pt I think) but
eog is interpreting the coordinates in px such that the clip region is too small
and two edges are lost from the square.

This is a problem of mismatched interpretation of the SVG standard.  I *think*
that it is eog that is wrong, rather than cairo.  

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. gcc `pkg-config --cflags --libs cairo` viewtest.c -o viewtest
2. ./viewtest
3. eog viewtest.svg
Actual results:
Only top and left sides of box are visible.

Expected results:
Clip region should be larger such that all four sides of the box are visible.

Additional info:

Comment 1 John Ellson 2007-07-18 19:17:50 UTC
Created attachment 159546 [details]
small cairo example that generates a box image in viewtest.svg

Comment 2 John Ellson 2007-07-18 19:19:50 UTC
Created attachment 159547 [details]
the svg output of the cairo viewtest.c example

Comment 3 Bug Zapper 2008-05-14 13:35:32 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2008-06-17 01:54:34 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 is no longer maintained, which means that it will not 
receive any further security or bug fix updates. As a result we 
are closing this bug. 

If you can reproduce this bug against a currently maintained version 
of Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.