Issue 42959 - svg:stroke-opacity had a opposite value
Summary: svg:stroke-opacity had a opposite value
Alias: None
Product: Draw
Classification: Application
Component: formatting (show other issues)
Version: 680m79
Hardware: All All
: P3 Trivial with 1 vote (vote)
Target Milestone: OOo 2.0
Assignee: wolframgarten
QA Contact: issues@graphics
: 62233 (view as issue list)
Depends on:
Blocks: 2497 37210
  Show dependency tree
Reported: 2005-02-17 04:54 UTC by
Modified: 2006-02-20 13:35 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description 2005-02-17 04:54:41 UTC
For example, when you set a line's transparency to 10% then the
svg:stroke-opacity should be set to 90%. But currently we set it to 10%.
Comment 1 wolframgarten 2005-02-17 07:52:21 UTC
Why should this be prio 1 ? Changed it back to 3.
Comment 2 2005-02-17 08:12:46 UTC
>Why should this be prio 1
If we to fix this, we have to modify all our sample files which use
svg:stroke-opacity too. Otherwise we use svg:stroke-opacity but its value is
Comment 3 wolframgarten 2005-02-17 09:13:18 UTC
We seem to have problems with the regard of transparence...
Comment 4 wolframgarten 2005-02-17 09:13:44 UTC
Comment 5 haui 2005-05-22 10:06:41 UTC
I think, this problem has first priority. OOo 1.9x currently produces draw
documents that are simply wrong according to the OpenDocument specification. 

Section "15.13.12 Opacity" states: The attribute svg:stroke-opacity specifies
the opacity of a stroke. The value of this attribute can be a number between 0
(fully transparent) and 1 (fully opaque) or a percentage.

When I currently produce a drawing with strokes that are nearly transparent,
this is saved e.g. in a document with a style attribute like
svg:stroke-opacity="90%". If you fix this problem all drawings created so far
become damaged. Therefore, the milestone mentioned above "OOo Later" seems
careless to me, maximum is 2.0.

> If we to fix this, we have to modify all our sample files which 
> use svg:stroke-opacity too.

You should care about your "customer's" documents at least as much as about your
sample files :-)

Was this problem introduced with this e-mail -- forgetting a (1.0 - x) computation?

Ah, before I forgett, when currently correctly converting SVG documents into
valid OpenDocument documents, OOo renders them wrong (see issue 2497).
Comment 6 ooo 2005-05-24 15:34:43 UTC
CL, please handle this issue after discusing further actions with MIB, seems
that we lost this task during the development of the last months.
Comment 7 Martin Hollmichel 2005-08-24 15:46:05 UTC
set target
Comment 8 clippka 2005-08-29 08:39:22 UTC
Fixed in cws impress67,

I added a Property "BuildId" to the import property sets. It is filled with the
build id from the meta:generator string in meta.xml (xmlmetai.cxx). Its value
can be checked with getBuildIds() from SvXMLImport. It returns the major and
minor version.

I switched the opacity value in propimp0.cxx and also convert old files with
major 680 and minor less than m125, so import of old documents should work fine

I also added conversion for OOo 6 and 7 file format.
Comment 9 clippka 2005-08-29 12:32:02 UTC
verified on cws, back to qa

re-open issue and reassign to
Comment 10 clippka 2005-08-29 12:32:52 UTC
reassign to
Comment 11 clippka 2005-08-29 12:33:09 UTC
reset resolution to FIXED
Comment 12 wolframgarten 2005-09-01 08:30:23 UTC
Verified in CWS.
Comment 13 wolframgarten 2005-11-14 11:44:19 UTC
Tested in m139. Closed.
Comment 14 kla 2006-02-20 13:35:20 UTC
*** Issue 62233 has been marked as a duplicate of this issue. ***