![[TEST] Document Foundation Community](https://communitytest.documentfoundation.org/images/discourse-logo-sketch.png){kind=logo}
Very well written, Tom!
Yup, with the help of the community we can improve LibreOffice so that in the future people are more happy with the PPT import/export filter. For this to happen we need good information and simple test-cases showing the ill-behavior.
IMO that's a better response than the original:
Your are wasting your time. Make a cost-benefit analysis and decide
whether to use either LO or m$; do not bother trying to use both.
There's no guarantee that Roger will take the time to do this, and there is not guarantee that someone will pick up the bug reports.
But it is guaranteed that if we tell people they are wasting their time using LibreOffice in a certain way, no progress is made on that front.
Which would be a true shame.
Well, having had your little spat I see we have got back to suggestions as to
what I might do about my problem.
Bear in mind I am new to this game. There is a suggestion of reporting a
"bug". I realise there is a link for that, but what is the best way? Should
I include a sample of a Ppt conversion (and vice versa) with examples of the
problems, or just list them.
Incidentally, there has been some comment about the 'different fonts on
different machines'. I am using Times New Roman (plain and bold) and as far
as I know that is available on any Windows machine, so presumably that is
not causing the problem.
Roger
Am 02.03.2012 23:17, Dag Wieers wrote:
So what do you reply to Roger Sawkins? That he can file a bug report
hoping that some day in future LibreOffice will fully support the
extinct ppt format?Yup, with the help of the community we can improve LibreOffice so that
in the future people are more happy with the PPT import/export filter.
For this to happen we need good information and simple test-cases
showing the ill-behavior.IMO that's a better response than the original:
Your are wasting your time. Make a cost-benefit analysis and decide
whether to use either LO or m$; do not bother trying to use both.There's no guarantee that Roger will take the time to do this, and there
is not guarantee that someone will pick up the bug reports.But it is guaranteed that if we tell people they are wasting their time
using LibreOffice in a certain way, no progress is made on that front.Which would be a true shame.
I did not write the above quote. My answer was a completely different one, trying to help based on the OP's current setup with both office suites LibO and MSO. Installing the same software on both machines is a solid and viable solution rather than a question of partisanship.
This is a massive waste of developers time. After all those years of co-evolution of Star/Open/LibreOffice with MSOffice, open source experts still struggle with very subtile details of their legacy file formats plus the massive load of problems imposed by their "Office Open XML" type of thing.
At the same time ODF goes down the drain because many commercial and non-commercial software projects do not get any support in supporting ODF.
For MSOffice users another option is still available, despite the efforts that have been taken by Oracle to remove it from the scene: http://sun-odf-plugin.soft-ware.net/download.asp
Am 02.03.2012 23:41, Roger Sawkins wrote:
Well, having had your little spat I see we have got back to suggestions as to
what I might do about my problem.Bear in mind I am new to this game. There is a suggestion of reporting a
"bug". I realise there is a link for that, but what is the best way? Should
I include a sample of a Ppt conversion (and vice versa) with examples of the
problems, or just list them.Incidentally, there has been some comment about the 'different fonts on
different machines'. I am using Times New Roman (plain and bold) and as far
as I know that is available on any Windows machine, so presumably that is
not causing the problem.Roger
--
View this message in context: http://nabble.documentfoundation.org/Presentation-conversion-to-from-Powerpoint-layout-tp3782543p3794938.html
Sent from the Users mailing list archive at Nabble.com.
Thank you for the feedback.
First register, then log-in and give a short description of your problem. Submit the report and finally attach the .ppt in question.
Don't hold your breath. This type of conversion flaws is a never ending story because of the special ways how MS software interacts with their own specific file formats. This is supposed to be incompatible with anything else. That's how they run their big business.
Greetings,
Andreas
P.S.: I forgot to mention another solution which adds full ODF compatibility to MS Office: http://sun-odf-plugin.soft-ware.net/download.asp
Am 02.03.2012 19:25, Dag Wieers wrote:
I didn't reply to your post in this thread. I was replying to e-letter's
post. Maybe you got lost and assumed I was replying to your post, I
don't know.
I wonder who got lost in this thread actually.
This is the only answer to e-letter:
There is nothing sensible in spelling Microsoft as 'm$', being condescending to users and force your opinions on others.
It is not followed by any other posting.
Hi 
The link i gave was the old one
http://wiki.documentfoundation.org/BugReport
it's still useful but this is the newer one
https://www.libreoffice.org/get-help/bug/
which is carefully "dumbed down" to make it easier but less flexible.
You could start a bug-report with nothing more than a subject-line and a quick comment, just like a normal email. The triagers would probably be a little more specific about the reports that they would find useful for that particular bug. The guides are a bit generic and try to cover a wide range of different cases. Logs, reports and attachments can be added later. It just helps to try to get as much together as reasonably possible to start with so that the triagers don't get bogged down.
I agree about the fonts. On Gnu&Linux i usually install a single package called something like "MS Core Fonts" which includes Arial and Times New Roman. As an aside I think it's also got Comic Sans, Verdana and Trebuchet and a couple of others but that is not the issue. I have to agree to an MS EULA to be allowed to install the package. All Windows machines i have known of have Times New Roman and Arial.
Regards from
Tom
Hi
[1] The way i see it going is much the same as the newsletter at my work. People will probably start by using MS formats, then they may find the older MS ones work better and then find the ODF are a vast improvement.
Our original newsletter was made in Word 2003 as a Doc. Sadly, with all the logos and even just a couple of photos it would crash plus occasionally error messages would appear. Buying Word 2007 and moving it to DocX stopped the error messages but it still crashed and the older machines couldn't handle it at all and it looked different on different machines. Moving to LibreOffice made it easier to move pictures around into more interesting layouts. Starting afresh with a new Odt took it to the next plateau. Now the images in the headers and footers line-up. The Table of Contents is clickable as are all the logos and photos. Plus all the usual improvements such as greater consistency throughout, bullet points that line-up and don't change size randomly, number lists that manage to keep count without skipping or duplicating numbers yada yada yada. The older machines handle it happily and it looks the same on every machine whether booted
into Ubuntu or Windows despite them both using different versions of LibreOffice.
[2] Can we copy that plugin to our own Extensions pae so that we don't lose track of it?
Regards from
Tom
Well, having had your little spat I see we have got back to suggestions as
to
what I might do about my problem.
What you choose to call a "spat" reveals your ignorance of the
historical context of gnu/linux and consequent inability to comprehend
the connection with your "problem".
Bear in mind I am new to this game. There is a suggestion of reporting a
"bug". I realise there is a link for that, but what is the best way? Should
There is no shame in being "new": everyone starts ignorant; it is now
up to you to acquire the necessary knowledge to understand the fallacy
of your "problem".
I include a sample of a Ppt conversion (and vice versa) with examples of the
problems, or just list them.
The former, not via a mailing list!
Your original post does not explain nor justify why LO should be used
to create m$ formats.
As indicated by previous reply, if "consistent conversion" is so
important to you and similar m$ fans, have you contacted m$ and asked
an equivalent question: "I want to be able to edit and save odf
presentations ((f)odp) in m$o and LO, but formatting is lost. Please
improve m$o. By the way, how do I submit a bug report to m$???"?
Please read the part of the "Posting guidelines" as is appended to every post:
TDF/LibreOffice Mailing List Netiquette
http://wiki.documentfoundation.org/Netiquette#Avoid_Advocacy
It states:
Am 04.03.2012 21:59, Dag Wieers wrote:
Yet, the link you carefully removed from my mail was *your* answer to my
mail to e-letter's mail:http://www.mail-archive.com/users@global.libreoffice.org/msg17560.html
So we are not discussing whatever mail you initially send to Roger, we
are discussing the tone and content of e-letter's mail and how the
LibreOffice project is representing itself to users.And e-letter is doing it again, Roger is offering to report a bug and is
discouraged from the very start. Way to go !
I can't see anything wrong with e-letters statements. If you don't like his style ignore him.
Well, having had your little spat I see we have got back to suggestions as to
what I might do about my problem.Bear in mind I am new to this game. There is a suggestion of reporting a
"bug". I realise there is a link for that, but what is the best way? Should
I include a sample of a Ppt conversion (and vice versa) with examples of the
problems, or just list them.
Including simple sample files would certainly be useful. Also a description of the various steps, as well as software versions and system environment (that can affect the issue, like the fonts installed etc...)
Bugs that are attractive (i.e. are well-documented and look easy to verify without the need to have more interaction) tend to get more support than vague claims or complicated descriptions that require more work by bug triage people or developers.
Make sure that what you contribute will be public and cannot contain content that is copyrighted or illegal to share.
Incidentally, there has been some comment about the 'different fonts on
different machines'. I am using Times New Roman (plain and bold) and as far
as I know that is available on any Windows machine, so presumably that is
not causing the problem.
Even when the fonts appear to be installed on the system, software bugs in the filters might be causing such issues. I don't expect them to, but bugs tend to be unexpected...
Thanks for the bug suggestions. I will try to get around to it in the near
future.
Roger