Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

Hi :)
step 5 (obviously) is to try to be ready to hand in the .doc quite soon after handing in the Pdf 
and Odt, or Od-whatever

Something else i am doing right now is to talk about the imminent release of "MS Office 2013", 
apparently due out at around the end of this month.  I also quite often point out that the only 
real reason for upgrading is when other people start using the new one because when they do 
documents we produce wont look quite right in the new one.   And, of course, that stuff produced in 
the new MS Office won't look right in our old one.  

I'm deliberately calling MS Office 2010 "the old one".  I say things like "yes, the old one is 
better than the 2007 because the ribbon-bar is a bit more logical".  My boss admitted he couldn't 
find his way around the new ribbon-bar so i printed off the Quick Reference sheets from the MS.Com 
website "to help people get used to the old one we just bought".  

Obviously it's not going to be called 2013 this time, at least i'm fairly sure it isn't but it 
helps people get an idea about when MS Office is likely to be released, because otherwise they seem 
to think that i am talking about something that isn't going to happen for another decade or so.  
When i talk about MSO 2013 i try to get 2010 and 2007 versions into the same sentence.  (Yes, its 
happening soon and we are quickly going to be seen as out-of-date boss ;)  )  

The only reason we bought all the new MSO 2010 was because the new finance spreadsheets have macros 
that only work in 2010.  (Aww gee boss, are these going to work in the new one?).  Since finance 
were getting MSO 2010 obviously everyone else 'had' to have it too.  

So i am being a really Pita at work but it's getting some people to actually give LO a go as long 
as i can keep it secret about it being free and just 'sell it' on it's high quality 'Desktop 
Publishing' features such as handling images better.  

Btw "and" should never be used at the start of a sentence, same with "but".  Very, very rarely you 
can get away with it without looking like a complete moron but it's not worth the risk.  
Regards from
Tom :)

--- On Wed, 17/10/12, Tom Davies <> wrote:

From: Tom Davies <>
Subject: Re: [libreoffice-users] Images and *doc export
To:, "rost52" <>
Date: Wednesday, 17 October, 2012, 9:57

Hi :)
Ok, so best tactic might be to 
1.  create a copy
2.  make a Pdf so you have something ready to hand in fast
3.  Meanwhile work on converting the images to pngs (or jpgs depending on whether you want quality 
or smaller file-size)
4. Try to get the Pdf in before your supervisor expects results but keep working at the pngs/jpgs 
so that you can present the editable version fairly soon after.  When you hand it in also give the 
odt version and a link to the LO download page for the version you use.  

At my place my boss eventually started to cave in when i kept on going on about how LO has Desktop 
Publishing (DTP?) "stuff" that Word just doesn't have.  This was borne out by him not being able to 
line-up pictures and logos in Word that i was then able to line up in seconds on LO.  It's still 
uneasy but he
 has started to use LO too sometimes now.  He does have a tendency to still start documents in Word 
and usually that means i have to start afresh in Writer in order to get rid of insane formatting 
but the thread about how to paste as unformatted text helped hugely with that.  

Regards from
Tom :)  

--- On Wed, 17/10/12, rost52 <> wrote:

From: rost52 <>
Subject: Re: [libreoffice-users] Images and *doc export
Date: Wednesday, 17 October, 2012, 2:03

I think the pdf is really the best solution. However, your supervisor might want to put comments 
into the document while reading it. I tested a pdf-document created in writer (LO 
but I could not add

When I wanted to make the "Comment & Mark UP"  toolbar in Adobe Reader (9.5.2) visible, I saw the 
information "Only available when document rights are enabled". I assume that the rights must be 
given when you create the pdf-document. I know that LO you can create various types of 
but I don't know how to set the right for comments & mark ups.

Maybe someone else in this community can explain about such rights and there settings.

On 17.10.2012 09:28, Orlando Figueiredo wrote:
Thank you all for the suggestion. I think that the PDF solution might be the best way, although I 
am not sure if it will be peacefully accepted by my supervisor.
The worst case scenario will be me constructing a nem file with png images and keeping the 
original done with draw in a safe file to edit afterwards.
We will see.
Thx again,

LinkedIn/facebook/skype/twitter: of1967

Em 16-10-2012 20:49, Steve Edmonds escreveu:
Also, a pdf can be marked up/annotated if your supervisor only needs to comment and not actually 
With a PDF you are also assured that your supervisor will see the exact layout that you see and 
not have the layout reflowed due to some slight font or other difference (as has happened with 

On 2012-10-17 08:40, anne-ology wrote:
         sounds like the sensible way to go  :-)

On Tue, Oct 16, 2012 at 10:31 AM, Tom Davies <>wrote:

How about side-stepping the issue and use
File - "Export to Pdf"

Does the supervisor need to edit the document?  If so it's a non-starter
but generally Pdfs are viewed as being more professional. Everyone sees
Pdfs the same, the layout is the same and everything.  Errr, fonts
sometimes not quite identical unless you print to file and then select Pdf
instead of Ps.  I think.  Anyway Pdf generally gets around that sort of
issue.  Also LibreOffice has more options for exporting as Pdf, such as
doing uncompressed ones for better quality.

Word is really bad with graphics and doesn't have the range of "Anchor to
page" and so on that LO has.  Also it kinda falls over if it
 has too many

Jpg can mess up images a little by making them be a bit swirly but usually
it's tolerable.  Png tends to be a better format.  However by creating a
Pdf you might even impress your supervisor.

Regards from
Tom :)

From: Orlando Figueiredo <>
To: Libreoffice Global List <>
Sent: Tuesday, 16 October 2012, 15:19
Subject: [libreoffice-users] Images and *doc

I am writing a long document (my thesis) using LibreOffice and I have a
lot of images (more than 50 on the 200 pages that the document) have). All
images were made with LO Draw. I scanned portions of the documents that I
am analysing and glue them with Draw, usually put a line framing the images
our group of images when it is ready I select all the objects, group them
and copy/past them to writer. Until here everything works smoothly. The
problem comes when I try to export the document to a doc word (which I can
not avoid has it has to be read by my supervisor and she does not use LO
but M$ Office). All the export goes great except for the images that are
not exported and do not appear in the
 *doc document.
Can anyone help me with this? I understand that I can go to LO Draw, save
the images as jpg and insert them in the Writer document, but if it is
possible to solve this in another way that does not give me more stupid
work to do I would appreciate.
Thank you all.
Orlando Figueiredo


For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.