Re: text with pictures

2012-12-11 Thread Hagar Delest

Quite the same, just copy and paste.
It may take some time until AOO retrieves the pic from the net.
You may have better results to copy and paste as unformatted text and save the pics 
on your HD before inserting them with the InsertPictureFrom file menu.

Hagar


Le 10/12/2012 23:44, Hans van der Ven a écrit :


I hope that I sent this request to the correct location.
In MS Office I can copy a web page that contains both text and pictures and 
paste it into MS Word. How do I capture both text and pictures into Apache Open 
office? Please advise.
Hans

-
To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org
For additional commands, e-mail: users-h...@openoffice.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org
For additional commands, e-mail: users-h...@openoffice.apache.org



Re: A Tale of Two Office Suites

2012-12-11 Thread Girvin R. Herr



Robert Holtzman wrote:

On Tue, Dec 11, 2012 at 10:45:00AM +, Mike Lish wrote:
  

Hi Carol,

You are definitely NOT out of line.

I'm not desk based and use OoO for the basics.  I come from a military and
hands on manufacturing environment (now retired) where there must be
established procedure for every task, as I'm sure is the same for an office
environment.



That's very true for some environments, especially the military. That,
however is spit Microsoft thinking. Choice is *almost* always a good
thing.

Don't be too sure about an office environment. It depends on the size of
the organization and how it's structured. 


In short, in *many* situations choice is preferable.

  ..snip.
  

Choice allowed me to continue updating the office suite!

I was using OpenOffice 3.3.0 when Apache took over.  When Apache 
released 3.4, I discovered Apache made some, IMHO bad,  decisions that 
broke installation on my older Slackware Linux computer.  Those 
decisions made it very painful for me to upgrade to their 3.4 version.  
The deal breaker was the decision to switch glibc versions.  Even 
though the release notes stated that OO 3.4 would work on glibc 2.5 or 
greater, that was incorrect and in actuality, it required glibc 2.11.  
My computer is running glibc 2.7.  I then tried building from source and 
discovered another Apache decision tossed the tried-and-true GNU 
autotools build environment in favor of something called dmake (sounds 
like yet another PHD project looking for a home).  I tried dmake, but I 
still had problems building the source.  I was facing updating my entire 
Linux computer or abandoning OO.  (See my contribution to thread  
Installing Apache OpenOffice over LibreOffice dated 5-15-2012.)


That said, when LibreOffice split off, I tried a couple of their 
releases with little success.  So I continued to use OO 3.3.  When I 
discovered OO 3.4 was broke, I tried LO 3.5 and discovered TDF did not 
make the same bad decisions that Apache had made.  Deciding to stay 
with glibc 2.5+ allowed LO to still run on my older Linux computer.  I 
found LO very stable, well, at least as stable as OO 3.3 and some bugs I 
had with OO 3.3 were fixed in LO 3.5.  That was when I switched to LO.


So, having the choice was a good thing for me.
He, who lives on the cutting edge of technology, gets sliced to bits! 
- Adam Osborne

Girvin Herr


-
To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org
For additional commands, e-mail: users-h...@openoffice.apache.org



Re: A Tale of Two Office Suites

2012-12-11 Thread Girvin R. Herr



Ariel Constenla-Haile wrote:

Hi,

On Tue, Dec 11, 2012 at 01:01:21PM -0800, Girvin R. Herr wrote:
  

Choice allowed me to continue updating the office suite!

I was using OpenOffice 3.3.0 when Apache took over.  When Apache
released 3.4, I discovered Apache made some, IMHO bad,  decisions
that broke installation on my older Slackware Linux computer.  Those
decisions made it very painful for me to upgrade to their 3.4
version.  The deal breaker was the decision to switch glibc
versions.  Even though the release notes stated that OO 3.4 would
work on glibc 2.5 or greater, that was incorrect and in actuality,
it required glibc 2.11. 



This wasn't a decision, it was a bug, see
https://issues.apache.org/ooo/show_bug.cgi?id=119385

Early testing by the user community would have avoided this bug. There
is no need to be a developer to contribute to an open source project
like OpenOffice.
  

Ariel,
Thanks for the update.  I tend to gravitate toward processes that work, 
so I have not been keeping up with this bug since I switched to LO.  
The bug report does not seem to definitely state that this bug has 
been addressed in the current or even future releases.  That does not 
give me a warm fuzzy feeling to return to AOO.  As my time allows, I 
will keep trying the new releases until they start working without 
intervention.  I would hope that the bug report recommendations will be 
acted upon and AOO becomes more friendly to older Linux systems.


snip


The build environment based in dmake comes from Sun Microsystem times
(or may be even before that).
  
I wouldn't know about that.  I have historically re-packaged the 
downloaded binary packages into Slackware installation packages.  After 
the AOO 3.4 binary would not work, my attempt at building the source, 
was to see if a working AOO 3.4 could be built against the libraries I 
already have.  I have found that if I can do that with any program, the 
program will be the most stable.  It was worth a try, but, as I said, it 
failed.  My computer log states that the failure was something to do 
with a Python 5 module error (I have Python 2.5.2).  There are only a 
very few trusted binaries that I allow to run on my system.  Normally, I 
do build from source.  However, the time involved with building a large 
program such as AOO is a good driver to use it's binary.  Besides, until 
AOO 3.4, the binaries always worked well for me.


snip

Try the unofficial tar ball from
http://people.apache.org/~arielch/packages/r1372282-glibc-2.5/#full-archived-sets
you don't even need to install it.


Regards
  
Thanks, but for computer security reasons, I am _very_ reluctant to 
install an unofficial version.  I would prefer to wait until the 
official, trusted, version is released.  It is my impression, from more 
than just this issue, that the AOO Linux effort is still a bit immature 
and needs to settle down a bit before I can return to a stable AOO.

Thanks again.
Girvin Herr


-
To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org
For additional commands, e-mail: users-h...@openoffice.apache.org