Re: [1/2OT] soffice and data import
On Sun, 05 Aug 2012 23:49:40 +0800, lina wrote: > I got a temp file which was generated by "paste temp_a temp_b". > > The temp file look like: > > $ paste temp_a temp_b > 3 1.0 3 1.0 > 5 2.0 4 2.0 > 5 3.0 > > When I used the commend "soffice -o temp -calc" (This commend was told > by someone from list long time ago, very helpful) > > the > 5 3.0 > jumped to the left rows. (...) Have you tried to get a dump with a different separator field (e.g., comma ",")? That way you'll get something like: 3,1.0,3,1.0 5,2.0,4,2.0 5,3.0 Which can be processed by "oocalc" more accurately. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jvm66t$kog$1...@dough.gmane.org
[1/2OT] soffice and data import
Hi, I got a temp file which was generated by "paste temp_a temp_b". The temp file look like: $ paste temp_a temp_b 3 1.0 3 1.0 5 2.0 4 2.0 5 3.0 When I used the commend "soffice -o temp -calc" (This commend was told by someone from list long time ago, very helpful) the 5 3.0 jumped to the left rows. Thanks ahead for any suggestions, P.S, the only way I come up is to paste temp_b temp_a ; but I have a series of files, a bit big ones. Best regards, -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAG9cJm=DBAVtimw7wCt39s-b_X7XwSu=9JpPjR=v629rk0y...@mail.gmail.com
Re: soffice and vmware file access trouble
On Saturday 14 April 2001 16:40, Elfert wrote: > Both StarOffice and VMware are failing because they claim to be unable to > access certain files. In VMware's case it's a log file. With soffice it's > sofficerc. The programs suggest a problem with the path or permissions, but > the path is dead-on, the permissions are all set, and the files are > certainly present. As root they run fine. What's going on? Did you run the StarOffice setup with the /net from your regular user account? You have to run setup as root to do the full install, then setup /net as each user who wants to run it. There is a README in the package. -- Bud Rogers <[EMAIL PROTECTED]> http://www.sirinet.net/~budr All things in moderation. And not too much moderation either.
soffice and vmware file access trouble
Both StarOffice and VMware are failing because they claim to be unable to access certain files. In VMware's case it's a log file. With soffice it's sofficerc. The programs suggest a problem with the path or permissions, but the path is dead-on, the permissions are all set, and the files are certainly present. As root they run fine. What's going on? Thanks, Galen
Re: Soffice
* Manoj Srivastava said: > thomas> when opening.. If you please could let me know which package > thomas> i shall downgrad or upgrade to get it work again i would be > thomas> very glad since i use soffice everyday.. > > I am not sure, but quite possibly the issue may be the libc > upgrade? I havfe heard rumors that so broke when upgrading from RH > 5.2 to 6.0, and the major change there too was libc. It's certainly a case of the libc6 upgrade. I didn't see the beginning of this thread, so I don't know which version of SO you are talking about. I will assume that it's 5.1 - the latest release. SO5.1 requires you to have glibc2.0 while the current potato uses v2.1 of the library. You don't have to downgrade anything at all - it's sufficient to do some wizardry with the SO5.1 binaries and the .so loader. Below is a full recipe on how to do that (tested by me yesterday after downloading a fresh copy of SO5.1 :)): 1. Get the libc6_2.0.7.19981211-6.deb and install it to some directory in the /usr/local tree (e.g. /usr/local/glibc2.0) 2. Do ln -sf /usr/local/glibc2.0/ld-2.0.7.so /lib/ld-2.0.7.so 3. Get some comfortable binary editor (hexeditor is a good choice) 4. Unpack the soffice .tar file as usually 5. Unzip the so51inst/office51/setup.zip to a separate directory 6. Copy the so51inst/office51/setup.ins to the same directory where you put the files extracted in the previous step. 7. Change the case of all the files in the directory to lowercase: for x in [A-Z]*; do mv $x `echo $x | tr A-Z a-z` done 8. Open the setup.bin file in the binary editor, find the string /lib/ld-linux.so.2 and replace it with /lib/ld-2.0.7.so *** MAKE SURE YOU PUT TWO NULL CHARACTERS AFTER THE NEW STRING *** 9. Start X-Window and open an xterm window 10. Now execute (while still in the directory the setup.zip was extracted to): LD_LIBRARY_PATH=/usr/local/glibc2.0:/lib:/usr/lib:./ ./setup 11. SO5.1 installation starts. Enter the path where you extracted the original soffice .tar when prompted for the location of the install files. 12. After the setup finishes successfully go back to the shell prompt and then switch to the bin/ subdirectory of the location where you installed the Office. 13. Unpack the attached tar.gz file in this subdirectory (sorry, couldn't make a diff because I haven't saved the originals :(() 14. Repeat the step 8 for every .bin file in the directory. If everything went well (e.g. if I didn't misled you :))) you should now be able to use SO5.1 without problems. marek soscripts.tar.gz Description: Binary data pgpYQ9bKzEsAb.pgp Description: PGP signature
Re: Soffice
Hi, >>"thomas" == thomas <[EMAIL PROTECTED]> writes: thomas> Hi, not sure were this email should go but i give thomas> [EMAIL PROTECTED] a try... The most appropriate list, in this case, would have been debian-user@lists.debian.org, where there is a greater chance of more people listening who havce had similar problems, and know the solution. thomas> I use dselect alot to upgrade my version of Potato.. Im not thomas> sure which package or update who got my Staroffice to fail thomas> when opening.. If you please could let me know which package thomas> i shall downgrad or upgrade to get it work again i would be thomas> very glad since i use soffice everyday.. I am not sure, but quite possibly the issue may be the libc upgrade? I havfe heard rumors that so broke when upgrading from RH 5.2 to 6.0, and the major change there too was libc. Possibly someone on debian-user can answer this definitively. manoj -- "Most of us, when all is said and done, like what we like and make up reasons for it afterwards." Soren F. Petersen Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/> Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
