Hi :)
Educational institutions and students can sometimes get discounts as do some charitable
organisations.
I think my route would be to try to set-up the template in LibreOffice but use the .otp (native
ODF template format) for the main original, then use that to Save As a .pot rather than a .potX
to create one that MS Office can open and then use MS Office to tweak the .pot to fix any
problems. Scott has more experience with doing presentations tho but that is what i would do for
spreadsheets or word-processor files.
Regards from
Tom :)
--- On Wed, 13/6/12, Scott <sbicknel@gmail.com> wrote:
From: Scott <sbicknel@gmail.com>
Subject: Re: [libreoffice-users] PowerPoint templates and choice of .pot vs .potx?
To: users@global.libreoffice.org
Date: Wednesday, 13 June, 2012, 23:14
On Wednesday June 13, 2012 1:27 pm avamk wrote:
Hello,
My group is in the process of setting up a slideshow template, and
unfortunately for practical reasons need to save it as a PowerPoint
template.
My question is twofold:
(1) What are some of your experiences in opening and using PowerPoint
templates in LibreOffice? I prefer saving in the template in a format that I
can reasonably expect good support for in LibreOffice.
Templates created in PowerPoint, regardless of the file format, often have
issues in LibreOffice. The most common issues I have encountered are elements
that are misplaced on the slide and font effects that do not transfer to
LibreOffice from PowerPoint. But the most faithful reproduction seems to occur
when using ppt files, regardless of whether they were created from a pot or a
potx. pptx files are not as well-supported under LibreOffice as .ppt files are.
But that's just my experience using a couple of templates I created in
PowerPoint 2010.
(2) We prefer a format that is as future proof as possible (in terms of
consistent look and format using it between different software, Micro$oft or
otherwise). With that in mind, which of the following would be a better
choice? Microsoft PowerPoint 97/Xp/2000/2003 Template (*.pot), Microsoft
PowerPoint 2007/2010 XML Template (*.potx), or Office Open XML Presentation
Template (*.potm; *.potx)?
That's a difficult question to give a blanket answer for. It will depend on what
features you include in your template. You will need to ensure that the fonts
you use are available on all systems where the templates will be used, for
instance. Your templates will need to be tested on all the software where it
will be used to ensure that formatting is consistent. This could be an ongoing
process.
One thing you might consider is whether you need the presentation in any of
those formats. PowerPoint and Libreoffice can export presentations to PDF, which
can be presented with some limited transition effects in many PDF viewers. Not
many viewers offer a presentation mode with suitable features, though. Okular
seems to have the best presentation mode among the PDF viewers I have tested,
and there is a Windows version of that available from kde.org.
Our work environment consists mainly of computers running Micro$oft
PowerPoint 2010, a couple with PowerPoint 2007, and only one with
LibreOffice 3.5. (Unfortunately switching all to LibreOffice is not
practical for numerous reasons that I wish weren't true, but beyond the
scope of this email.)
You will have far fewer headaches by obtaining an Office license for the one
machine that doesn't have it than to try to make all presentation programs
happy with whatever format is the least common denominator, unfortunately.
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.