[Libreoffice] Undeliverable mail: Message could not be delivered

Failed to deliver to 'proj...@quake.ru' LOCAL module(account proj...@quake.ru) reports: account is full (quota exceeded) Reporting-MTA: dns; zfrontend2.aha.ru Original-Recipient: rfc822; Final-Recipient: LOCAL; Action: failed Status: 4.0.0 Received: from [62.113.100.76] (HELO izenguard-zmail-2.z

Re: [Libreoffice] Assertions and Logging

On 11/22/2011 11:50 PM, Miklos Vajna wrote: These changes cause that without an export SAL_LOG="+INFO" former OSL_TRACE() messages do not show up on the console, even with dbglevel=2. I like that SAL_LOG can now filter SAL_INFO messages, but are you sure it's a good idea to disable them all by

Re: [Libreoffice] [PATCH] EasyHack 39625 - Make existing cppunittests work

Thanks Stephan This is a big help. I'll revisit my patch with this new information and get some of the tests enabled so that I can see what happens. I'll repost my patch after doing that and making the changes you have suggested. Cheers Justin Hi Justin, > > Thanks a lot for working on this. U

[Libreoffice] {LibreOffice] bug 34425 hints asked

Dear Bjoern, You made bug 34425 an easy hack; I would like to give it a try, but can you give me a hint where I can find the relevant code for these buttons (in scalc and swriter)? I have tried t find them before, but so far no success. Winfried __

[Libreoffice] Windows build breakage

Hi there, So, not having been able to build master on Windows for almost 2 months, I've decided to give it another go. But it fails in scripting this time, and I have no clue. The build log is attached. Hopefully this will ring a bell for someone... Kohei build.log.bz2 Description: BZip2 com

Re: [Libreoffice] Assertions and Logging

On Fri, Nov 18, 2011 at 03:25:16PM +0100, Stephan Bergmann wrote: > #define OSL_DEBUG_ONLY(s) _OSL_DEBUG_ONLY(s) > -#define OSL_TRACE _OSL_TRACE > -#define OSL_ASSERT(c) _OSL_ENSURE(c, OSL_THIS_FILE, __LINE__, 0) > -#define OSL_ENSURE(c, m) _OSL_ENSURE(c, OSL_THIS_FILE, __LIN

[Libreoffice] [Bug 35673] LibreOffice 3.4 most annoying bugs

https://bugs.freedesktop.org/show_bug.cgi?id=35673 Bug 35673 depends on bug 33463, which changed state. Bug 33463 Summary: Comments are lost after FILESAVE as DOCX https://bugs.freedesktop.org/show_bug.cgi?id=33463 What|Old Value |New Value --

Re: [Libreoffice] [PUSHED] Some OSL cleanup

Hello, I think these system requirements for LibreOffice imply to have a valid implementation of getpid() : - Linux kernel version 2.6.18 or higher; -> clone() for NTPL - glibc2 version 2.5 or higher; -> NPTL With these two requirements on Linux, we have NPTL and a good version of getpid,

[Libreoffice] [Bug 37361] LibreOffice 3.5 most annoying bugs

https://bugs.freedesktop.org/show_bug.cgi?id=37361 Bug 37361 depends on bug 43154, which changed state. Bug 43154 Summary: EDTING : Empty string "" equivalent to any number with several functions. https://bugs.freedesktop.org/show_bug.cgi?id=43154 What|Old Value

[Libreoffice] [PATCH] Enable :first-letter CSS pseudo-class for all browsers in HTML export

Previously when drop caps were specified in a paragraph style (not as direct formatting) export to HTML was implemented with :first-letter pseudo-class for "LibreOffice Writer" and through styling individual characters for other browsers. Since all browsers used these days (even obsolete ones like

Re: [Libreoffice] Newbie question: i18n numeric formats

Hi Olivier, On Tuesday, 2011-11-22 16:23:50 -0200, Olivier Hallot wrote: > I found that the number of pre-defined numeric formats could be > improved to handle telephone number, postal codes, social security > numbers, and other locale numeric formats. > > My question is: is it OK that I patch t

Re: [Libreoffice] [Libreoffice-qa] Improving the QA and Release for 3.5

No those days aren't the only way to test. But it is a way to get more people to test the software and to test the software in ways that the developers won't think about. I think there are enough people that want to help but don't know how, and testing is a easy way to step in. At last I also

Re: [Libreoffice] [Libreoffice-qa] Improving the QA and Release for 3.5

Cor Nouws píše v So 19. 11. 2011 v 16:56 +0100: > Cor Nouws wrote (13-11-11 21:20) > > Rainer Bielefeld wrote (11-11-11 20:06) > > https://wiki.documentfoundation.org/QA/Improving_QA-Release-3.5 > > >> I'm afraid "Try to get more testers doing the testing earlier" will be > >> the critical/limiti

[Libreoffice] Newbie question: i18n numeric formats

Hi I was looking into http://cgit.freedesktop.org/libreoffice/core/plain/i18npool/source/localedata/data/pt_BR.xml and I found that the number of pre-defined numeric formats could be improved to handle telephone number, postal codes, social security numbers, and other locale numeric formats.

Re: [Libreoffice] Solving an introduced runtime dependency on unreleased Qt version (KDE4 vcl backend)

Hi Lubos, On Tue, 2011-11-22 at 18:26 +0100, Lubos Lunak wrote: > Since 3.4 at least, when run with KDE4 integration, LO kind of happens to > have a runtime dependency on a yet unreleased Qt version, otherwise LO will > abort during some reasonably commonplace operations Urk. >

Re: [Libreoffice] Assertions and Logging

On Tuesday 22 of November 2011, Stephan Bergmann wrote: > On 11/22/2011 05:17 PM, Lubos Lunak wrote: ... > I did not commit it in order to stop any discussion. Sorry if it looked > that way. Rather, as I did not get any totally disagreeing reactions, I > thought it would be easier to polish this

[Libreoffice] Solving an introduced runtime dependency on unreleased Qt version (KDE4 vcl backend)

This might be also also for packagers, do we have a place where to reach them? Since 3.4 at least, when run with KDE4 integration, LO kind of happens to have a runtime dependency on a yet unreleased Qt version, otherwise LO will abort during some reasonably commonplace operations, such as dr

Re: [Libreoffice] Assertions and Logging

On 11/22/2011 05:17 PM, Lubos Lunak wrote: First of all: I see this has been already committed, after giving people only slightly more than the weekend and the day after it to react, which I consider too short for something with as large scope as this. Some of us don't work on the weekends and

Re: [Libreoffice] help asked/offered for bug 36555

On Tue, Nov 22, 2011 at 11:12:13AM +0100, Winfried Donkers wrote: >>> .autogen.sh succeeded, now make give a strange error: >>> ... >>> configure: creating ./config.status >>> ./configure: line 8411: test: too many arguments >>> ... >>> configure: error: could not make ./config.status > I found o

Re: [Libreoffice] Assertions and Logging

On Tue, Nov 22, 2011 at 1:41 AM, Stephan Bergmann wrote: > On 11/22/2011 06:35 AM, Norbert Thiebaud wrote: >> >> The run tine flexibility is a great feature, but the proposed >> implementation is scary perf-wise > > I kept the implementation simplistic on purpose.  First, remember that > logging (

Re: [Libreoffice] [PATCH] [REVIEW 3-4] fdo#36555 connect to ADO (MS Access, ...)

On Tue, Nov 22, 2011 at 07:23:48AM -0800, julien2412 wrote: > Like I said in the tracker sorry for all this mess :-( > Thank you for having solved this bug. > Do you know if there's a way to detect cases like this one ? Compile with "gcc -std=c++0x" or "gcc -std=gnu++0x" or (since my commit acc65

Re: [Libreoffice] [PATCH] EasyHack 39625 - Make existing cppunittests work

On 11/20/2011 11:32 AM, Justin Harding wrote: Hi - I'm new to LibreOffice development - I've taken a look at EasyHack 39625 - Make existing cppunittests work - and followed the suggestions in the bug report. I'm not completely sure that this is all that is required - I don't know if all the unit

Re: [Libreoffice] Error " GDK_DISPLAY_X11 (display)->xdisplay) > screen_num' failed " WAS Re: [] Error in/at end of make install

On Tue, 2011-11-22 at 15:34 +0100, Cor Nouws wrote: > Caolán McNamara wrote (22-11-11 15:25) > > >> Program received signal SIGSEGV, Segmentation fault. > >> 0xb309b4f3 in X11SalGraphics::GetResolution(long&, long&) () > > > > Hmm, pity it isn't an --enable-symbols build which would give line > >

[Libreoffice] [Bug 35673] LibreOffice 3.4 most annoying bugs

https://bugs.freedesktop.org/show_bug.cgi?id=35673 Bug 35673 depends on bug 36555, which changed state. Bug 36555 Summary: Cannot View Tables of Connected Access Database files https://bugs.freedesktop.org/show_bug.cgi?id=36555 What|Old Value |New Value -

Re: [Libreoffice] [PATCH] i18n corrections for pt-PT

Hello Eike I will provide anothe patch. Please wait. Thank you Olivier Em 22-11-2011 13:44, Eike Rathke escreveu: Hi Olivier, On Tuesday, 2011-11-22 11:29:11 -0200, Olivier Hallot wrote: Patch to correct month names (case) and Era for pt-PT. The patch is broken, it shredded the utf-8 en

Re: [Libreoffice] Assertions and Logging

First of all: I see this has been already committed, after giving people only slightly more than the weekend and the day after it to react, which I consider too short for something with as large scope as this. Some of us don't work on the weekends and have a backlog when they come back on Mond

Re: [Libreoffice] [PUSHED][PATCH] remove NfShCurrencyEntries and NfShCurrencyEntryPtr types

Hi Daniel, On Monday, 2011-11-21 23:20:02 +0100, Daniel Di Marco wrote: > attached is a simple patch to remove 2 obsolete datatypes. Thanks, good one. Pushed to master http://cgit.freedesktop.org/libreoffice/core/commit/?id=33a8ac0750d4ee7800b9faccdee3fffb850a04b1 I didn't find your license sta

Re: [Libreoffice] [PATCH] i18n corrections for pt-PT

Hi Olivier, On Tuesday, 2011-11-22 11:29:11 -0200, Olivier Hallot wrote: > Patch to correct month names (case) and Era for pt-PT. The patch is broken, it shredded the utf-8 encoding and all non-ascii character are question marks. Either your editor didn't save that properly or your mailer softwa

[Libreoffice] [REVIEWED 3-4] fdo#36555 connect to ADO (MS Access, ...)

On Tue, 2011-11-22 at 15:14 +0100, Lionel Elie Mamane wrote: > Attached patch solves (according to user report on master daily build) > fdo#36555, a severity "critical" bug which keeps users from connecting > to ADO / OLE DB datasources. Wow - nice chasing, as you say - obviously correct,

Re: [Libreoffice] [PATCH] [REVIEW 3-4] fdo#36555 connect to ADO (MS Access, ...)

Hello Lionel, Like I said in the tracker sorry for all this mess :-( Thank you for having solved this bug. Do you know if there's a way to detect cases like this one ? Julien. -- View this message in context: http://nabble.documentfoundation.org/PATCH-REVIEW-3-4-fdo-36555-connect-to-ADO-MS-Acce

Re: [Libreoffice] how to print into .ps

On Tue, 2011-11-22 at 15:22 +0100, Lionel Elie Mamane wrote: > Other CUPS-using applications have choice between PS, PDF or SVG when > printing to file. See for example evince, gimp or gedit. IIRC they all render to a cairo canvas though, and cairo spits out the ps/pdf/svg. i.e. its not cups which

Re: [Libreoffice] Assertions and Logging

> if the MSVC debug stuff is indeed too difficult, then just comment it > out, put in a comment that says FIXME, and re-enable the > --enable-dbgutil stuff, that way windows devs at last get some > assertions and internal consistency checks. But you can't build it with --enable-dbgutil ... configu

Re: [Libreoffice] Question about IAccessibility2

On Mon, 2011-11-21 at 23:11 +0100, Regina Henschel wrote: > I see them for some controls but not for all, especially not for > maLBEdgeStyle. > (1) What they are used for? Well, they're probably intended for accessibility support anyway, e.g. screenreaders. Not sure however whether they're gener

Re: [Libreoffice] Assertions and Logging

On 22/11/11 13:54, Tor Lillqvist wrote: >> Agree. The only valid reason for not having all debug tools compiled in is >> runtime performance and binary size. > > Which brings up the question: Should my attempts to use the MSVC > debugging runtime (and debug code in its headers, i.e. -D_DEBUG) when

Re: [Libreoffice] Assertions and Logging

Stephan Bergmann wrote: > based one; given that configure currently rejects --enable-dbgutil for an > MSVC based one I guess nobody cares for > debug output for that configuration at the moment, anyway?) > I think it's more a case of the Windows users struggling to get a basic build going relia

Re: [Libreoffice] Error " GDK_DISPLAY_X11 (display)->xdisplay) > screen_num' failed " WAS Re: [] Error in/at end of make install

Caolán McNamara wrote (22-11-11 15:25) Program received signal SIGSEGV, Segmentation fault. 0xb309b4f3 in X11SalGraphics::GetResolution(long&, long&) () Hmm, pity it isn't an --enable-symbols build which would give line numbers. I could build like that. But won't be soon, prolly. Do I just h

Re: [Libreoffice] Assertions and Logging

On 11/22/2011 03:05 PM, Caolán McNamara wrote: Only thing left unresolved from my perspective is whether warnings on windows works. Maybe somebody using a Windows build could give input here, whether the current state works well enough? (At least for a MinGW based one; given that configure c

Re: [Libreoffice] Error " GDK_DISPLAY_X11 (display)->xdisplay) > screen_num' failed " WAS Re: [] Error in/at end of make install

On Tue, 2011-11-22 at 13:41 +0100, Cor Nouws wrote: > Caolán McNamara wrote (22-11-11 13:32) > > > lets get a backtrace there, i.e. > > > > . ./ooenv > > gdb --args ./soffice.bin > > (gdb) run > > (gdb) bt > > Starting program: > /home/cono/src/git/libo_core/solver/unxlngi6.pro/installation/opt/

Re: [Libreoffice] how to print into .ps

On Tue, Nov 22, 2011 at 01:26:13PM +0100, Christian Lohmaier wrote: > On Tue, Nov 22, 2011 at 1:02 PM, Petr Mladek wrote: >> if you select "Print to File" check box in the "Print" dialog, it >> generates .pdf file. >> IMHO, if you debug printing bugs, it would be great to see the .ps file >> tha

[Libreoffice] [PATCH] [REVIEW 3-4] fdo#36555 connect to ADO (MS Access, ...)

Attached patch solves (according to user report on master daily build) fdo#36555, a severity "critical" bug which keeps users from connecting to ADO / OLE DB datasources. In particular, it keeps user from connecting to MS Access (.mdb) files in the most natural way; that is, by creating a new ODB f

Re: [Libreoffice] Assertions and Logging

On Mon, 2011-11-21 at 17:53 +0100, Stephan Bergmann wrote: > So, from a practical standpoint, failing smoketest on failed SAL_WARNs > would be right. On the other hand, there might be SAL_WARNs that > legitimately fire during smoketest (a trivial example would be if we > purposefully tested illega

Re: [Libreoffice] how to print into .ps

Michael Stahl píše v Út 22. 11. 2011 v 13:35 +0100: > On 22/11/11 13:02, Petr Mladek wrote: > > Hi, > > > > if you select "Print to File" check box in the "Print" dialog, it > > generates .pdf file. > > > > IMHO, if you debug printing bugs, it would be great to see the .ps file > > that is send t

Re: [Libreoffice] how to print into .ps

Hi, Maybe you can change the printer language to Postscript on the Device page of the Printer settings in the Printing dialog (it works for me on Linux). By the way, there is an important difference within PDF printing and PDF exporting. PDF printing supports EPS embedding (fortunately, like the

[Libreoffice] [PATCH] i18n corrections for pt-PT

Hi Patch to correct month names (case) and Era for pt-PT. Valid also fpr pt-BR. -- Olivier Hallot Founder, Board of Directors Member - The Document Foundation LibreOffice translation leader for Brazilian Portuguese +55-21-8822-8812 >From cc7d404efcc9336c809b93058a1a865fa8515805 Mon Sep 17 00:0

Re: [Libreoffice] Assertions and Logging

On 11/22/2011 01:15 PM, Bjoern Michaelsen wrote: hmmm... i wonder if it makes sense to not distinguish between warnings and info at compile-time (given that it is only active on debug builds anyway), so it is not required to recompile a module to get full debug output... Agree. The only valid r

Re: [Libreoffice] Assertions and Logging

On Tue, Nov 22, 2011 at 01:50:24PM +0100, Stephan Bergmann wrote: > Yes, based on com.sun.star.logging UNO interfaces and > comphelper/logging.hxx wrapper. Apparently only sparingly used, in > connectivity and package/source/xstor. ... and the now dormant Usage Tracking. > Needs revisiting, wheth

Re: [Libreoffice] Assertions and Logging

> Agree. The only valid reason for not having all debug tools compiled in is > runtime performance and binary size. Which brings up the question: Should my attempts to use the MSVC debugging runtime (and debug code in its headers, i.e. -D_DEBUG) when using --enable-dbgutil be reverted? It currentl

Re: [Libreoffice] Assertions and Logging

On 11/22/2011 11:55 AM, Bjoern Michaelsen wrote: There is also 3/4 of a log4j reimplementation in extensions/source/logging. Just saying ... Yes, based on com.sun.star.logging UNO interfaces and comphelper/logging.hxx wrapper. Apparently only sparingly used, in connectivity and package/sourc

Re: [Libreoffice] Error " GDK_DISPLAY_X11 (display)->xdisplay) > screen_num' failed " WAS Re: [] Error in/at end of make install

Caolán McNamara wrote (22-11-11 13:32) lets get a backtrace there, i.e. . ./ooenv gdb --args ./soffice.bin (gdb) run (gdb) bt Starting program: /home/cono/src/git/libo_core/solver/unxlngi6.pro/installation/opt/program/soffice.bin [Thread debugging using libthread_db enabled] [New Thread 0

Re: [Libreoffice] how to print into .ps

On 22/11/11 13:02, Petr Mladek wrote: > Hi, > > if you select "Print to File" check box in the "Print" dialog, it > generates .pdf file. > > IMHO, if you debug printing bugs, it would be great to see the .ps file > that is send to the printer. Is there any easy way how to get it? AFAIK on UNIX w

Re: [Libreoffice] Error " GDK_DISPLAY_X11 (display)->xdisplay) > screen_num' failed " WAS Re: [] Error in/at end of make install

On Tue, 2011-11-22 at 13:22 +0100, Cor Nouws wrote: > Stephan Bergmann wrote (22-11-11 09:23) > > > You have a computer terminal in your bathroom? What a nerd you are. ;) > > Well, close to. But I resist giving more detials ;-) > > > Anyway, confusing install vs. dev-install looks like a plausib

Re: [Libreoffice] how to print into .ps

At 13:02 22-11-2011, Petr Mladek wrote: if you select "Print to File" check box in the "Print" dialog, it generates .pdf file. IMHO, if you debug printing bugs, it would be great to see the .ps file that is send to the printer. Is there any easy way how to get it? My Ubuntu installation under

Re: [Libreoffice] how to print into .ps

Hi Petr, *, On Tue, Nov 22, 2011 at 1:02 PM, Petr Mladek wrote: > if you select "Print to File" check box in the "Print" dialog, it > generates .pdf file. > > IMHO, if you debug printing bugs, it would be great to see the .ps file > that is send to the printer. Is there any easy way how to get it

[Libreoffice] Error " GDK_DISPLAY_X11 (display)->xdisplay) > screen_num' failed " WAS Re: [] Error in/at end of make install

Stephan Bergmann wrote (22-11-11 09:23) You have a computer terminal in your bathroom? What a nerd you are. ;) Well, close to. But I resist giving more detials ;-) Anyway, confusing install vs. dev-install looks like a plausible explanation. make dev-install ran fine. But alas the program

Re: [Libreoffice] Assertions and Logging

Hi Michael, Stephan, all, On Tue, Nov 22, 2011 at 12:46:52PM +0100, Michael Stahl wrote: > one requirement i would have on conditional compilation is that, whether > --disable-dbgutil or --enable-dbgutil, objects built with debug=t > (resulting in OSL_DEBUG_LEVEL being set to non-zero) should alwa

[Libreoffice] [Bug 35673] LibreOffice 3.4 most annoying bugs

https://bugs.freedesktop.org/show_bug.cgi?id=35673 Petr Mladek changed: What|Removed |Added Depends on||42772 --- Comment #234 from Petr Mladek 2

Re: [Libreoffice] printing expert wanted

What you want is a way of dumping the PostScript output, so that you can compare the output from a previous version of LibO with a newer version of LibO. (Just stating the question better - I don't know the answer). Petr Mladek wrote: > Hi, > > I wonder who would be interested into printing bu

[Libreoffice] how to print into .ps

Hi, if you select "Print to File" check box in the "Print" dialog, it generates .pdf file. IMHO, if you debug printing bugs, it would be great to see the .ps file that is send to the printer. Is there any easy way how to get it? Best Regards, Petr __

[Libreoffice] printing expert wanted

Hi, I wonder who would be interested into printing bugs, such as https://bugs.freedesktop.org/show_bug.cgi?id=42759 I do not see anyone at http://wiki.documentfoundation.org/FindTheExpert ;-) Best Regards, Petr ___ LibreOffice mailing list LibreOffi

Re: [Libreoffice] Assertions and Logging

On 18/11/11 15:25, Stephan Bergmann wrote: > The downside of that mixture is that the useful debugging technique of > aborting upon detection of a violated invariant is not available.---If > you make OSL_ASSERT (and OSL_ENSURE, OSL_FAIL, etc.) abort, it will > abort far too often for mundane war

[Libreoffice] [Bug 37361] LibreOffice 3.5 most annoying bugs

https://bugs.freedesktop.org/show_bug.cgi?id=37361 Jean-Baptiste Faure changed: What|Removed |Added Depends on||43154 --- Comment #27 from Jean-Ba

Re: [Libreoffice] Assertions and Logging

Hi, On Fri, Nov 18, 2011 at 03:25:16PM +0100, Stephan Bergmann wrote: > For one, there are two sets of functionality that cater for the same > needs. One is osl/diagnose.h, the other is tools/debug.hxx. There is also 3/4 of a log4j reimplementation in extensions/source/logging. Just saying ...

Re: [Libreoffice] help asked/offered for bug 36555

>> .autogen.sh succeeded, now make give a strange error: >> ... >> configure: creating ./config.status >> ./configure: line 8411: test: too many arguments >> ... >> configure: error: could not make ./config.status >> ... >Hmmm, that looks like a quoting problem with the $CPP variable. >What does yo

Re: [Libreoffice] Assertions and Logging

I pushed the proposed changes as and . Any further refinements (where to send the log output

Re: [Libreoffice] [PUSHED] Some OSL cleanup

On Mon, 2011-11-21 at 20:08 +0100, Arnaud Versini wrote: > For getpid, this is my mistake, sorry, I must check before if NPTL > getpid is conform to the posix requirements (one PID for all threads > in one process). It seems to be Posix compliant : Ah - that's no problem :-) the man-page

Re: [Libreoffice] Error in/at end of make install

On 11/22/2011 09:16 AM, Cor Nouws wrote: Hmm, I just looked again. And it looks as if I was confused and should have run 'make dev-install' ( Was late, basically I was in the bathroom rather then on the office ;-) ) You have a computer terminal in your bathroom? What a nerd you are. ;) Anywa

Re: [Libreoffice] Error in/at end of make install

Hi Stephan, Stephan Bergmann wrote (22-11-11 08:54) Do you need to tell "make install" where to install it to (looks like it uses /usr/local/lib as default prefix, maybe we accept a --prefix configure switch?). Hmm, I just looked again. And it looks as if I was confused and should have run '

[Libreoffice] Bug 38811 - [EasyHack] default to SQLite not HSQLDB in Base

I am interested in writing the SQLite driver code for Base. However I have some questions (that a fellow Base driver developer might be able to help me resolve) with regards to what actually needs to be done, and how it needs to be done. Keep in mind that I am completely new to LibreOffice C++ UNO