Bug 65228 - : Chart export function has SVG as an option but it is not implemented, results in 0-bit file
Summary: : Chart export function has SVG as an option but it is not implemented, resul...
Status: VERIFIED DUPLICATE of bug 60137
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
Version:
(earliest affected)
4.0.3.3 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-01 07:49 UTC by stragu
Modified: 2013-06-01 17:05 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description stragu 2013-06-01 07:49:23 UTC
Problem description: 
Export for single graph has been implemented in LO 4.0, but SVG format appears as a function and it is not implemented in this branch.

Steps to reproduce:
1. Create a chart
2. Right-click on it and select "Export..."
3. Choose SVG format from list and save

Current behavior:
It creates a file that does not contain anything.

Expected behavior:
This option should not appear in the list as it is known it does not work. It makes the user think something is broken.

Note that this might be the case with other formats (I have not tried every single one).

              
Operating System: All
Version: 4.0.3.3 release
Comment 1 Jorendc 2013-06-01 10:04:46 UTC
Hi,

Thanks for reporting!
But exactly the same behavior is already reported in Bug 59083 , which is marked as duplicate of bug 60137.

Especially see this comment: https://bugs.freedesktop.org/show_bug.cgi?id=60137#c7

and this one: https://bugs.freedesktop.org/show_bug.cgi?id=60137#c13

So, big chance the fix can't be backported to 4.0, so only fixed in 4.1 and following versions.

Kind regards,
Joren

*** This bug has been marked as a duplicate of bug 60137 ***
Comment 2 stragu 2013-06-01 15:50:32 UTC
Sorry, Joren. I can understand when this kind of bug is closed when at the end of a bugfix cycle, but this is a real problem, and the 4.0 cycle still has a few releases ahead.
This is a real problem as the user has an option available that is known to be unusable by the developers. 
This can not be marked as fixed at the moment. I understand that bug 60137 has been fixed in the 4.1 branch, but as the 4.0 branch won't reach its end of life until the 21st of November 2013, the best would be to fix bugs that present the user with options that are actually unusable.
Comment 3 Jorendc 2013-06-01 16:09:52 UTC
(In reply to comment #2)
> Sorry, Joren. I can understand when this kind of bug is closed when at the
> end of a bugfix cycle, but this is a real problem, and the 4.0 cycle still
> has a few releases ahead.
> This is a real problem as the user has an option available that is known to
> be unusable by the developers. 
> This can not be marked as fixed at the moment. I understand that bug 60137
> has been fixed in the 4.1 branch, but as the 4.0 branch won't reach its end
> of life until the 21st of November 2013, the best would be to fix bugs that
> present the user with options that are actually unusable.

True :-)... I can't deny that :-). But please reread bug 60137 and particularly comment 13 (https://bugs.freedesktop.org/show_bug.cgi?id=60137#c13). This is a comment by the developer who fixed it:

"To remove the option out is not trivial. I will try to do something about this."

We are aware of the fact we _should_ port the fix, but we have to deal also with the fact that 4.0 is now declared 'stable' for _all_ users. And I think the problem is the fact Tomaz need to apply some other patches to 4.0 as well, to fix this issue.... which can lead to other unstable behavior. Otherwise there is a a code-difference between 4.1 and 4.0, so backporting the fixes might be result in other strange behavior too.

As I quoted Tomaz above ... please be patient. Tomaz is doing great job, and he's trying to backport it *IF POSSIBLE*.

I'll remark this bug as duplicate, because all info is in there too (as well as users asking to backport it to 4.0 (see comment 12).

With all my respect,
Joren

*** This bug has been marked as a duplicate of bug 60137 ***
Comment 4 stragu 2013-06-01 16:30:42 UTC
Thanks for your feedback, Joren.

I definitely agree with everything you are saying, but I guess my issue is we are marking this bug as a duplicate of a bug which is marked as fixed, which basically means: "there is no problem here any more".

I personally think that the best way to make everyone "happy", or, better said, sort the issue out realistically, would probably be to mark this bug as "Won't fix" as the fix would be too likely to break something else.

Bug 60137 relates to a fairly different issue, I believe (implementing the vector export function altogether). The "see also" option is here to link the other bug for more info too, isn't it?

Would you agree wit this, Joren?

Cheers
Comment 5 Joel Madero 2013-06-01 16:57:56 UTC
This is almost surely a duplicate and you will see the fix in 4.1 - where it will be confirmed that it's no longer a problem. Both identify an exact same problem (svg export borked which results in 0 byte files). 

If you test this on a daily build or the RC build of 4.1 it *should* be solved, so WONTFIX seems inaccurate?
Comment 6 Jorendc 2013-06-01 17:05:06 UTC
(In reply to comment #4)
> Thanks for your feedback, Joren.
> 
> I definitely agree with everything you are saying, but I guess my issue is
> we are marking this bug as a duplicate of a bug which is marked as fixed,
> which basically means: "there is no problem here any more".
> 
> I personally think that the best way to make everyone "happy", or, better
> said, sort the issue out realistically, would probably be to mark this bug
> as "Won't fix" as the fix would be too likely to break something else.
> 
> Bug 60137 relates to a fairly different issue, I believe (implementing the
> vector export function altogether). The "see also" option is here to link
> the other bug for more info too, isn't it?
> 
> Would you agree wit this, Joren?

Mmmh. Interesting point of view :-)! But ... I agree with what Joel says. On top of that I think we are reporting bugs related to a bad behavior of LibreOffice in general, not for particular versions. I.e: chart export function <bla bla> doesn't work in versions 4.0.X

Glad to hear someone with another point of view :-). Makes things interesting!

Kind regards,
Joren