review granted: [Bug 49155] Unwanted top distance after insertion of a caption for a graphic : [Attachment 81756] Patch with proposed fix
Oliver-Rainer Wittmann has granted review: Bug 49155: Unwanted top distance after insertion of a caption for a graphic https://issues.apache.org/ooo/show_bug.cgi?id=49155 Attachment 81756: Patch with proposed fix https://issues.apache.org/ooo/attachment.cgi?id=81756&action=edit --- Additional Comments from Oliver-Rainer Wittmann patch looks good - I will integrate it into trunk for the next release. Ariel: Is this ok for you that I initiate the 'svn commit'? Additionally, I will try to enable 'above' option for graphic captions and drawing captions - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: crashes
Hi Cynthia, we are sorry to hear that you have problems on Windows 8 but without getting more info it is hard to explain what happens. Many users can use OpenOffice on Windows 8 without any problems Some questions 1. From where do you have downloaded OpenOffice. Theo official and recommended download is from http://www.openoffice.org/download/ 2. which version of OpenOffice do you have installed 3. Had you installed an older version before Kind regards Juergen On 11/22/13 11:13 AM, Cynthia Taylor wrote: > cant work out with mail lists and forums too complicated for me - > right now i'm ready to uninstall open office and look for another > program that will work for me. > > i installed open office for windows 8. and it keeps crashing. i cant > get one document completed without it keep crashing i need to work > effectively .why does it keep crashing ?? > > Cynthia > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Hello
On 11/21/13 2:37 PM, Daniel Nilsson wrote: > Hi, > > I'm not sure if this mail should be sent to the dev, or user mailing list. > I have been working as a developer for a year now and I'm interesting in > learning more about testing. So i thought I'd look into the open source > scene. From what i have read, triage is a good place to start. > > My experience so far comes from writing automated test cases but I'm > interested in getting a wider knowledge in testing. > Hi Daniel, welcome to OpenOffice and your interest in testing and automated tests is perfect. We still have on our wish list the integration of new unit test framework because cppunit is license incompatible. I personally believe that the googletest framework [1] can be a good choice and I am asking if you are potentially interested to start something new going in this direction. It's an active project and is used in Google internal projects and in some popular projects like Chromium, LLVM. This would be a really cool project and we have to start with it sooner or later. What do you think? As first steps I would recommend to 1. set up your own build environment for AOO 2. integrate the googletest in our build process (compile the source from scratch in our env) 3. start using it by migrating some existing cppunit tests or implement new ones Again welcome at OpenOffice Juergen [1] http://code.google.com/p/googletest/ - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Reporting a problem with the OpenOffice web site
Vous êtes sur une liste internationale. La langue qui doit être utilisée est l'anglais. Outlook est un logiciel payant édité par Microsoft. OpenOffice n'a rien à voir là dedans. Si vous cherchez un courrielleur gratuit, vous pouvez utiliser Thunderbird. Si vous avez d'autres questions et que vous ne parlez que français, vous pouvez utiliser la liste francophone ou le forum pour obtenir de l'aide. http://www.openoffice.org/fr/Support/ - Mail original - De: "Michel de CENAC" À: dev@openoffice.apache.org Envoyé: Jeudi 21 Novembre 2013 09:26:23 Objet: Reporting a problem with the OpenOffice web site Bonjour et un grand merci pour m’avoir permis de charger votre OpenOffice 4.0.1 (gratuitement). Elle fonctionne très bien. Par contre, je suis à la recherche de Outlook ! l’avez-vous dans vote site Web ? Sinon ... Ou puis-je la trouver ? Mr Michel PERES 1, avenue de Lignan 33360 CENAC FRANCE m.per...@sfr.fr tél : 05 56 20 75 82 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
crashes
cant work out with mail lists and forums too complicated for me - right now i'm ready to uninstall open office and look for another program that will work for me. i installed open office for windows 8. and it keeps crashing. i cant get one document completed without it keep crashing i need to work effectively .why does it keep crashing ?? Cynthia - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: many many stlport issues...can anyone help
On 21.11.2013 01:27, Kay Schenk wrote: [...] short update...in building xml2cmp/source/finder the reference to # include BOOST_TR1_STD_HEADER(utility) in ../boost/tr1/detail/config_all.hpp fails for me either from the externally installed boost or my local install. BOOST_TR1_STD_HEADER(utility) should find a C++ header named utility [1]. Since we are using boost/tr1 it should be found from solver/*/*/inc/boost/tr1/tr1/utility [1] http://www.cplusplus.com/reference/utility/ I have no idea why this never happened before the stlport removal but there you have it. I guess to make this work, I will need to define BOOST_TR1_STD_HEADER properly at least. Do you happen to have set a HAVE_STL_INCLUDE_PATH manually? This could interfere with boost finding its own headers. So please undefine it. Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: many many stlport issues...can anyone help
On Thu, Nov 21, 2013 at 8:07 AM, Herbert Duerr wrote: > On 21.11.2013 01:27, Kay Schenk wrote: > >> [...] >> >> short update...in building xml2cmp/source/finder >> >> the reference to >> >> # include BOOST_TR1_STD_HEADER(utility) in >> >> ../boost/tr1/detail/config_all.hpp >> >> fails for me either from the externally installed boost or my local >> install. >> > > BOOST_TR1_STD_HEADER(utility) should find a C++ header named utility [1]. > Since we are using boost/tr1 it should be found from > solver/*/*/inc/boost/tr1/tr1/utility > > [1] http://www.cplusplus.com/reference/utility/ right...I mean I *understood* that was supposed to happen, but somehow the logic in config_all.hpp isn't getting there. I did see some notes from the boost docs on how to set some of these things manually, though. I HAVE the utility header -- but this file can not find it. > > > I have no idea why this never happened before the stlport removal >> but there you have it. I guess to make this work, I will need to define >> BOOST_TR1_STD_HEADER properly at least. >> > > Do you happen to have set a HAVE_STL_INCLUDE_PATH manually? um...not that I know of -- I didn't do it, but maybe one of these other headers did it -- accidentally. Yeah, I saw a bunch of logic dealing with STLPORT here, but, well, I am not a C++ expert. I will try to track this down. I dumped the "supplied" boost and did a local install -- that went fine -- thinking there were referencing problems somehow, but, alas, the same problem in the same place. > This could interfere with boost finding its own headers. So please > undefine it. > > > Herbert > Thanks for all your help. I may not be able to get back to this for a few days...but I will let you know what happens. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- - MzK “Unless someone like you cares a whole awful lot, Nothing is going to get better. It's not.” -- Dr. Seuss, The Lorax
Re: Hello
Please also check the q...@openoffice.apache.org we are actively looking for testers and also write testcases for OpenOffice. First step should be review the introductory module for QA and read the testing area: http://openoffice.apache.org/orientation/intro-qa.html On Thu, Nov 21, 2013 at 7:37 AM, Daniel Nilsson wrote: > Hi, > > I'm not sure if this mail should be sent to the dev, or user mailing list. > I have been working as a developer for a year now and I'm interesting in > learning more about testing. So i thought I'd look into the open source > scene. From what i have read, triage is a good place to start. > > My experience so far comes from writing automated test cases but I'm > interested in getting a wider knowledge in testing. > > Regards > Daniel > -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614
Re: Reporting a problem with the OpenOffice web site
Hi Michel... Apologies for the response in English. By "Outlook", do you mean email? Apache OpenOffice does not currently have an email client. Don 2013/11/21 Michel de CENAC > Bonjour et un grand merci pour m’avoir permis de charger votre OpenOffice > 4.0.1 (gratuitement). > Elle fonctionne très bien. > > Par contre, je suis à la recherche de Outlook ! > l’avez-vous dans vote site Web ? > Sinon ... Ou puis-je la trouver ? > > Mr Michel PERES > 1, avenue de Lignan > 33360 CENAC > FRANCE > > m.per...@sfr.fr > tél : 05 56 20 75 82
RE: EXTERNAL: Re: Building comphelper
-Original Message- From: Steele, Raymond Sent: Wednesday, November 20, 2013 4:57 PM To: 'Herbert Duerr' Cc: Meffe, David K Subject: RE: EXTERNAL: Re: Building comphelper Thanks, We've run into some errors with dmake and are trying to understand it. First, the startup.mk and makefile.mk could not find settings.mk and some others that are located in solenv/inc even though dmake -v seems to be looking there. We created a link of all the files in solenv/inc to solenv where makefile.mk is to overcome the problem. Although this does not seem to be a good solution. Then dmake could not find seem to find minor.mk. For example, on line 1665 in target.mk we have the following: ALLTAR: \ "$(SOLARVERSION)/$(INPATH)/inc$/$(UPDMINOREXT)/$(UPD)minor.mk" This would be interpreted by dmake as '//inc/minor.mk' as if the variables were not expanded. If I hardcode the full path to minor.mk , then dmake is fine. I eventually got past building solenv by performing the above hacks. I have a feeling I should not have to do that stuff. Now, building 'afms', dmake complains that "SHELL could not find macro" on line 64. I think it has to do with the function macro 'find', but I am not sure. Any help would be great!! Thanks, Raymond -Original Message- From: Herbert Duerr [mailto:h...@apache.org] Sent: Wednesday, November 20, 2013 1:02 AM To: Steele, Raymond Subject: Re: EXTERNAL: Re: Building comphelper Hi Raymond, > I just wanted to give you a heads up that I am beginning to start work on > compiling for Solaris 11 x86. Hopefully, you will be able to assist if needed. Thanks for the heads up! I'm looking forward to this and will try to help. Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Hello
Hi, I'm not sure if this mail should be sent to the dev, or user mailing list. I have been working as a developer for a year now and I'm interesting in learning more about testing. So i thought I'd look into the open source scene. From what i have read, triage is a good place to start. My experience so far comes from writing automated test cases but I'm interested in getting a wider knowledge in testing. Regards Daniel
Re: Hello
Thanks for the replies. Alexandro: Great I'll go through the intro for QA when im off from work. Jürgen: It sounds interesting and i have had a glance at googletest before. However I think it might be a bit overwhelming to start with. Anyway I'll check it out and see if it is something for me. Regards Daniel On Thu, Nov 21, 2013 at 2:54 PM, Jürgen Schmidt wrote: > On 11/21/13 2:37 PM, Daniel Nilsson wrote: > > Hi, > > > > I'm not sure if this mail should be sent to the dev, or user mailing > list. > > I have been working as a developer for a year now and I'm interesting in > > learning more about testing. So i thought I'd look into the open source > > scene. From what i have read, triage is a good place to start. > > > > My experience so far comes from writing automated test cases but I'm > > interested in getting a wider knowledge in testing. > > > > Hi Daniel, > > welcome to OpenOffice and your interest in testing and automated tests > is perfect. We still have on our wish list the integration of new unit > test framework because cppunit is license incompatible. > > I personally believe that the googletest framework [1] can be a good > choice and I am asking if you are potentially interested to start > something new going in this direction. It's an active project and is > used in Google internal projects and in some popular projects like > Chromium, LLVM. > > This would be a really cool project and we have to start with it sooner > or later. What do you think? > > As first steps I would recommend to > 1. set up your own build environment for AOO > 2. integrate the googletest in our build process (compile the source > from scratch in our env) > 3. start using it by migrating some existing cppunit tests or implement > new ones > > Again welcome at OpenOffice > > Juergen > > [1] http://code.google.com/p/googletest/ > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: trunk build failure: ld: library not found for -lc++ in comphelper
On 11/20/13 10:58 AM, Pavel Janík wrote: > Hi, > >> Please update your trunk checkout (r1543407 or newer) and restart doing a >> clean build. > > the same. I already had up-to-date tree. > Hi Pavel, I have made a non pro build on my Mac and it worked. I built with SDK and had to make minor changes in autodoc (already in svn now) and it built completely. I recommend to use a new clean shell and configure again, do a clean build from scratch. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Reporting a problem with the OpenOffice web site
Bonjour et un grand merci pour m’avoir permis de charger votre OpenOffice 4.0.1 (gratuitement). Elle fonctionne très bien. Par contre, je suis à la recherche de Outlook ! l’avez-vous dans vote site Web ? Sinon ... Ou puis-je la trouver ? Mr Michel PERES 1, avenue de Lignan 33360 CENAC FRANCE m.per...@sfr.fr tél : 05 56 20 75 82
Re: Hello
On 11/21/13 3:21 PM, Daniel Nilsson wrote: > Thanks for the replies. > > Alexandro: Great I'll go through the intro for QA when im off from work. > > Jürgen: It sounds interesting and i have had a glance at googletest before. > However I think it might be a bit overwhelming to start with. Anyway I'll > check it out and see if it is something for me. don't be shy, you can ask here on the list and it should be independent of many other things. The first step is to integrate the framework and make it available for general usage. You don't have to write complex unit test, that can evolve later on. The goal would be to make it usable in our buildenv which can be of course a challenge as well. The test framework is good documented which is good and will help to get started. Everything else can we figure our later Juergen > > Regards > Daniel > > > On Thu, Nov 21, 2013 at 2:54 PM, Jürgen Schmidt wrote: > >> On 11/21/13 2:37 PM, Daniel Nilsson wrote: >>> Hi, >>> >>> I'm not sure if this mail should be sent to the dev, or user mailing >> list. >>> I have been working as a developer for a year now and I'm interesting in >>> learning more about testing. So i thought I'd look into the open source >>> scene. From what i have read, triage is a good place to start. >>> >>> My experience so far comes from writing automated test cases but I'm >>> interested in getting a wider knowledge in testing. >>> >> >> Hi Daniel, >> >> welcome to OpenOffice and your interest in testing and automated tests >> is perfect. We still have on our wish list the integration of new unit >> test framework because cppunit is license incompatible. >> >> I personally believe that the googletest framework [1] can be a good >> choice and I am asking if you are potentially interested to start >> something new going in this direction. It's an active project and is >> used in Google internal projects and in some popular projects like >> Chromium, LLVM. >> >> This would be a really cool project and we have to start with it sooner >> or later. What do you think? >> >> As first steps I would recommend to >> 1. set up your own build environment for AOO >> 2. integrate the googletest in our build process (compile the source >> from scratch in our env) >> 3. start using it by migrating some existing cppunit tests or implement >> new ones >> >> Again welcome at OpenOffice >> >> Juergen >> >> [1] http://code.google.com/p/googletest/ >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Hello
In case no one else responds to you have you checked out the DOC mailing list? d...@openoffice.apache.org On 11/20/2013 05:03 PM, David Virden wrote: My name is David and I'm interested in assisting with technical documentation. I have an English degree from the University of North Texas and am pursuing a technical writing graduate certificate from University of Texas at El Paso. I don't have much experience with technical writing other than what I've done in the classroom, which is why I'm here. , Additionally, I am taking some programming classes and have website development experience. However, I'm mainly interested in writing at this moment. I look forward to helping. Thanks, David -- Andrew Pitonyak My Macro Document: http://www.pitonyak.org/AndrewMacro.odt Info: http://www.pitonyak.org/oo.php - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: EXTERNAL: Re: Building comphelper
Herbert, Forget about my last report. We started over and figured out that an environment variable was causing the dmake issues. Once we cleared the environment of variables related to our other projects, the build took off. We will have to figure out what it was later. -Original Message- From: Steele, Raymond Sent: Thursday, November 21, 2013 9:28 AM To: 'Herbert Duerr' Cc: dev@openoffice.apache.org Subject: RE: EXTERNAL: Re: Building comphelper -Original Message- From: Steele, Raymond Sent: Wednesday, November 20, 2013 4:57 PM To: 'Herbert Duerr' Cc: Meffe, David K Subject: RE: EXTERNAL: Re: Building comphelper Thanks, We've run into some errors with dmake and are trying to understand it. First, the startup.mk and makefile.mk could not find settings.mk and some others that are located in solenv/inc even though dmake -v seems to be looking there. We created a link of all the files in solenv/inc to solenv where makefile.mk is to overcome the problem. Although this does not seem to be a good solution. Then dmake could not find seem to find minor.mk. For example, on line 1665 in target.mk we have the following: ALLTAR: \ "$(SOLARVERSION)/$(INPATH)/inc$/$(UPDMINOREXT)/$(UPD)minor.mk" This would be interpreted by dmake as '//inc/minor.mk' as if the variables were not expanded. If I hardcode the full path to minor.mk , then dmake is fine. I eventually got past building solenv by performing the above hacks. I have a feeling I should not have to do that stuff. Now, building 'afms', dmake complains that "SHELL could not find macro" on line 64. I think it has to do with the function macro 'find', but I am not sure. Any help would be great!! Thanks, Raymond -Original Message- From: Herbert Duerr [mailto:h...@apache.org] Sent: Wednesday, November 20, 2013 1:02 AM To: Steele, Raymond Subject: Re: EXTERNAL: Re: Building comphelper Hi Raymond, > I just wanted to give you a heads up that I am beginning to start work on > compiling for Solaris 11 x86. Hopefully, you will be able to assist if needed. Thanks for the heads up! I'm looking forward to this and will try to help. Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: trunk build failure: ld: library not found for -lc++ in comphelper
Hi, > I have made a non pro build on my Mac and it worked. I built with SDK > and had to make minor changes in autodoc (already in svn now) and it > built completely. > > I recommend to use a new clean shell and configure again, do a clean > build from scratch. I always build from scratch. Even the current tree has the same issue. I "fixed" it by the following: cd comphelper make ... it printed command to run which errors... ... I changed -lc++ to -lstdc++ and it works. From where is -lc++ generated? I forgot to mention that I do not use 4u sdk, but MacOSX10.5.sdk only. -- Pavel Janík - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: trunk build failure: ld: library not found for -lc++ in comphelper
> From where is -lc++ generated? > > I forgot to mention that I do not use 4u sdk, but MacOSX10.5.sdk only. The same issue later in module unoxml. Looks like something somewhere is doing s/-lstdc++/-lc++/ ie. removing the string std from the lib name. Hints? -- Pavel Janík - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: trunk build failure: ld: library not found for -lc++ in comphelper
On 22.11.2013 08:17, Pavel Janík wrote: From where is -lc++ generated? I forgot to mention that I do not use 4u sdk, but MacOSX10.5.sdk only. The same issue later in module unoxml. Looks like something somewhere is doing s/-lstdc++/-lc++/ ie. removing the string std from the lib name. Hints? Ah, now that you mention it: Such a replacement is done if MACOSX_DEPLOYMENT_TARGET!=10.4. The unxmacx.* target is for the 10.4 SDK, but the newer mac targets for more recent SDKs use libc++ as their native STL. So if you adjusted the check in main/RepositoryFixes.mk:50 to your use of the 10.5 SDK instead of the intended 10.4 SDK then everything should work again in your environment. Hope that helps! Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
