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


Am 25.06.2011 15:07, schrieb lee:
Frieder<delorfr@googlemail.com>  writes:

Am 25.06.2011 00:53, schrieb lee:

Yes I also did it with the macro recorder, but I can translate it to
better code if you want (the dispatcher is not reliable ).
Exporting to PDF has turned out to be unreliable in LO, too.
do you men the Macro you produced with the macro recorder ?
The macro recorder uses the dispatcher, and the dispatcher is not reliable as I already mentioned.
It strikes me odd that I shall have to learn another programming
language to do something this simple ...
The Problem is how to use the Uno API no mater programming language
you prefer.
True --- is there a good documentation about it?
Yes there is:
http://wiki.services.openoffice.org/wiki/Category:Tutorial
and specially the export to pdf:
http://wiki.services.openoffice.org/wiki/API/Tutorials/PDF_export
Hm. I have created a database to use instead of a spreadsheet. When I'm
trying to mail the document to myself as PDF, I can specify "Properties"
in the mailmerge wizard. There I could apparently add a text message so
that the PDF is sent as an attachment to it. I could use that to mail
the PDF documents to myself with the reference number in the text part
for easy further processing, or I might even be able to send them
without any further processing.

Unfortunately, LO crashes when I try to send the message:
Have you tried it with a stable  Version????
No, I only tried the version that is in Debian testing. Libreoffice is
not in Debian stable. LO 3.3.3 is in unstable. I could try to install
it, only it probably has so many dependencies that it isn't advisable.
maybe you should try another distribution like Suse, Fedora or Ubuntu (but don't try the Unity desktop its terrible. Use the XFCE desktop(Xubuntu) instead, it is similar to Gnome2 but much lighter and faster) . The problem with Debian is, that the stable version is to old, and the testing and unstable is to unstable.
| # Problematic frame:
| # C  [libuno_sal.so.3+0x43751]  rtl_uString_release+0x1
| #
| # An error report file with more information is saved as:
| # /home/lee/hs_err_pid21389.log
| #
| # If you would like to submit a bug report, please include
| # instructions how to reproduce the bug and visit:
| #   http://icedtea.classpath.org/bugzilla
| #
|
| [error occurred during error reporting , id 0xb]
`----

This seems to be Java problem, and not a LO bug.
There seem to be two bugs, one with using the mailmerge tool and another
one with reporting the bug. Anyway, they shouldn't use java for LO.
but there is still a lot of Java code in LO. They are working hard to translate it into C++ code, but it will take a while.
It doesn't really matter what the problem is, it's just not working, and
one bug after another turns up. After having learned a little about LO,
it seems to be still in a beta stage, and I need something that does
work. It's sad that there has been only very little progress in the
reliability of WYSIWYG word processors over the last 15--20 years.
The LO code contains about 6000000 lines of code. it is not easy to think of all the functions, if you ad some new code.
 So some bugs are unavoidable.

Regards
Frieder



--
Unsubscribe instructions: E-mail to users+help@global.libreoffice.org
In case of problems unsubscribing, write to postmaster@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.