[Libreoffice-bugs] [Bug 39256] Deficiencies in WMF importer implementation
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Jul 24 10:53:07 PDT 2011
--- Comment #11 from Valek Filippov <frob at gnome.org> 2011-07-24 10:53:07 PDT ---
2 Rainer Bielefeld
Thank you for your valuable comment.
I guess you are the person who would fix those issues if bugs were submitted as
Unfortunately I had a wrong assumption, that the only person who _probably_
will work on that is Radek Doulik. That's why I discussed with him on IRC how
he prefers this to be reported: one bug per visual discrepancy, one per WMF
record, one per test file or all in one. Anyway, I shouldn't make it as he
told, right? "Ask and ignore the answer!", sounds as a good idea!
You are also absolutely right about LibO version...
I should NOT assume that
- if those issues were here 4 years ago (when I filed a bug for OO.o
- if it's still here in 3.3.something,
- and there was no changes in WMF code recently,
when it's "ANY" version.
How could I know and claim that it's not fixed automagically in the git HEAD...
And you know what... I agree with you about "an other application". How could
one guess, what is the application for compatibility with which LibO needs
improvements in WMF support? It could be Borland Paradox, Apache or OpenVMS...
Sorry by mistake I put something misleading in the comment #7 and (oh. sh...)
in description to issue #5 ...
Now for other lines in "Then please:"
> - Attach a sample document (not only screenshot) demonstrating the problem
Oh... LibO saves screenshots in WMF format, I didn't know that.
Great feature by the way... Does it vectorize content by tracing it?
Is it good enough to vectorize photos of my friends to cut stamps on plotter
as xmas presents?
>- Attachscreenshots with comments (you can add information using LibO DRAW
You are mostly right. I described which WMF records have what types of issues.
Attachments were not needed at all. They actually distract attention from the
problem. Of course you know what WMF records are and what they do, so instead
of puzzling with images to figure out what is different and why, you can go
directly to fix mentioned record's implementations!
Will take it into account.
>- Contribute a step by step instruction containing every key press and every
> mouse click how to reproduce your problem
Err.. I thought that whoever (ah, now I know it will be you) is going to fix it
have some basic idea about opening files in application he or she makes fixes
for. That was a wrong assumption again, sorry about that.
What do you think about screencasts?
Should I cover application installation, how to run it, folder navigation,
basics of saving attachments from bugzilla by using web browser?
Just in case developers need that...
> -- what exactly is unexpected (The visible effect and the expected root
Probably you lost me here. "Hatches are ignored in CreateBrushIndirect record".
Doesn't it sound like "what exactly is unexpected"?
May be some of my expectations are wrong though (same as assumptions).
> -- and why do you believe it's unexpected
Ah... up to wrong expectations (see above), I assume basic MF records should be
implemented for MF importer to be useful.
Yeah.. very arguable position... 'Usefulness' is not quantitative metric...
Let's say you win this one too.
> -- concerning your PC (especially: video card)
> –- Libo settings that might be related to your problems
> (video hardware acceleration ...)
That's sooo creative... 'SetPolyfillMode is ignored because of VideoCard'...
I have to think about it...
> -- concerning your OS
WMF importer code seems to be the same on all platforms.
Anyway, you are right. It's not fair to leave any place for doubts.
With all that history of my mis-assumptions and mis-expectations, I worry to
assume that it could be just one bug for any OS, or identical bugs one per OS
(I deduce that 'one per' wins over 'all in one' based on your comment! See? I'm
learning new things today! =) Thank you very much!)
> concerning your LibO version and localization (UI language)
Yes, yes... Fully agree with you. Wrong assumption again, commented at the
start. Just a question... one bug per localisation, right? For each and every
of them, just in case.
> how you launch LibO and how you opened the sample document
Now I'm not even sure I did launch it.
One bug per method of launching for each way to open for each LibO application,
no matter results are always the same, correct?
We are not going to confuse developers with qualificators like "all" and "any".
English is not a native language for some of them, so they probably from the
group of people who don't understand what's funny about "any key" anecdote.
> If you can contribute an OOo Issue that might be useful
Who cares about 4 years old one?
Oh... that's was wrong assumption, right?
Two actually: do not assume ppl don't care and do not assume rodo remembers old
> everything else crossing your mind after you read a.m. URL
Yeah... There is one thing I should take into account first of all:
I'm NOT an OO.o/LibO user, hence there is no reason to report bugs.
> Can you please file Bug reports with status UNCONFIRMED if your are not
Please, please, don't involve me into discussion about "default status for bugs
opened for LibreOffice". I'm not interested to participate and/or be counted
for, against or instead.
I'm working on the set of EMF testing files to make a review of EMF/EMF+
support in different applications. I had plans to file a bug for LibO related
to EMF implementation, but it looks like I'm completely out of the skills to
So, do it yourself and/or ask tester8 for help. I know you can easily generate
original content, make comprehensive review and properly file bugs based on it.
So do it! That would save time for everybody.
And to be honest, I don't care if anybody will fix issues listed in that bug or
not. Feel free to close or remove it.
I will not comment here any more, want to discuss -- join #libreoffice-dev.
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Libreoffice-bugs