Re: Forward planning for OO 5.0
2) Add the extension LanguageTool to the package so that people have access to grammar checking Not sure that's a good idea. For example, french end-users prefer to install another extension like Grammalecte. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Forward planning for OO 5.0
So? Just disable LanguageTool and install the Grammalecte. LanguageTool supports dozens of languages. On 09/09/2014 08:24, FR web forum wrote: 2) Add the extension LanguageTool to the package so that people have access to grammar checking Not sure that's a good idea. For example, french end-users prefer to install another extension like Grammalecte. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org --
Re: Forward planning for OO 5.0
On Fri, Sep 05, 2014 at 11:54:47PM +0200, Vladislav Stevanovic wrote: - Oracle Report builder should be integrated inside AOO, like in LO The code of the extension (and the related core code, modules reportbuilder and reportdesign, respectively) was included in Oracle's Software Grant, but the extension depends on libraries with Category X license, so it cannot be included within an Apache product, whether in source or binary form see: https://issues.apache.org/ooo/show_bug.cgi?id=118573 https://cwiki.apache.org/confluence/x/HaqoAQ https://cwiki.apache.org/confluence/x/4ZuoAQ http://www.apache.org/legal/3party.html#category-x Regards -- Ariel Constenla-Haile La Plata, Argentina signature.asc Description: Digital signature
Re: Wiki:Step-By-Step Guide for Building on Windows not working
Hi, On 08.09.2014 16:41, Martin Tille wrote: Hello Dev Team, I'm trying to compile OO on Win7 64. I red through the guides here: https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_Windows Thanks to Andrea Pescetti I 'repaired' the CPAN installation part but now I'm stuck with the same problem as described here: https://forum.openoffice.org/en/forum/viewtopic.php?f=47t=57054 The forum post reports a problem when building OOo 3.3. You are also trying to build OOo 3.3? As the mentioned building guides are for building AOO version 3.4.0 and later, may be here is the problem. The mentioned file ../mail/solenv/[PLATFORM OUTPUT DIRECTORY]/inc/myworld.mk is created during the build of solenv. Thus, currently I have no idea, why it should be missing. Note: [PLATFORM OUTPUT DIRECTORY] should be 'wntmsci12.pro' for a product build under Windows and 'wntmsci12' for a non-product build under Windows. I noticed that the a unicode directory is created next to aoo\main\solenv\wntmsci12.pro named: aoo\main\solenv\wntmsci12.pro That sounds strange. I never observed something like this. When changing in aoo\main\solenv\bin\mkout.pl line 88 from $envpath = $ARGV[0] if defined($ARGV[0]); to $envpath = wntmsci12pro; It should not be necessary to change ..\mkout.pl to get a AOO build under Windows. I never made changes to certain build and environment scripts. the solenv is build but deliver fails with: Neither common nor platform tree? at /home/MartinT/aoo/main/solenv/bin/deliver.pl line 1158. deliver: /home/MartinT/aoo/main/solenv/prj/d.lst: ERROR: can't copy build.lst: No such file or directory deliver: /home/MartinT/aoo/main/solenv/prj/d.lst: ERROR: directory '/inc/solenv' does not exist My PATH variable is (launched within cygwin): $ echo $PATH .:/home/MartinT/aoo/main/solenv/bin:/home/MartinT/aoo/main/solenv/wntmsci12.pro/bin:/cygdrive/c/PROGRA~2/Java/JDK17~1.0_6/bin:/cygdrive/c/PROGRA~2/Java/JDK17~1.0_6/jre/bin/client:/cygdrive/c/PROGRA~2/MICROS~1.0/VC/bin:/cygdrive/c/PROGRA~2/MICROS~1.0/Common7/IDE:/cygdrive/c/PROGRA~1/MICROS~4/Windows/v7.0/bin:/cygdrive/c/Windows/MICROS~1.NET/FRAMEW~1/V20~1.507:/cygdrive/c/PROGRA~2/MICROS~1.0/VC/bin:/usr/bin::/usr/local/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows your PATH variable looks ok - I did not check it in detail My configure switches are the same from the wiki guide (without --disable-binfilter because not recognized/used anymore). I tryed the procedure with Win7 32 too and I'm stucked at the same point. Nevertheless, I have got the feeling that something went wrong in the configure step. Could you please send the corresponding log file of your configure step? It is found in .../main/ and is called config.log. May be the mailing list will strip a corresponding mail attachment - I do not have the mailing list's attachment rules at hand. Thus, please send the mail also to my personal mail address (o...@apache.org). I would have a look at the log file. Best regards, Oliver. Any suggestions? Regards - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Student Project
Hello Deborah, On Fri, Aug 29, 2014 at 01:49:35PM +0530, Deborah Digges wrote: Hello, I am a *4th year* Computer Science student. As a part of a course - The Architecture of Open source technologies, I am required to contribute to an open source project. The project is needed to be done by a team of *3 members*.The semester ends by* November*, so that gives me *three months* to work on the project. The course requires us to work *8 hours a week*. Also, the course emphasizes on making code contributions. I am familiar with C,C++ and python, and I am eager to pick up additional skills that are required. Please could you help me in this task, as I am quite new to open source. For this period of time, and due to the complexity of the code base, you might be interested in something more self-contained, like a Content Provider or a data base driver; for example, you can take the idea of a CMIS Content Provider that was part of a Google Summer of Code that wasn't completed; searching the mailing list for the subject CMIS you can find several mails http://markmail.org/search/?q=list%3Aorg.apache.incubator-ooo.dev+subject%3Acmis and the extension skeleton at http://people.apache.org/~arielch/extensions/CMISContentProvider.zip As you'll see, a Content Provider can be developed as an extension, there is no need for you to learn nor modify OpenOffice source code. Regards -- Ariel Constenla-Haile La Plata, Argentina signature.asc Description: Digital signature
Re: Reporting a problem with the OpenOffice website
You are on an international mailing list and attachments are stripped. You must write in english only. Your question seems to be an end-user problem. Please post directly to our support forum: https://forum.openoffice.org/fr Other users like you can be help you. - Mail original - De: Alain Vaisse alain.vai...@sfr.fr À: dev@openoffice.apache.org Envoyé: Lundi 8 Septembre 2014 22:12:21 Objet: Reporting a problem with the OpenOffice website Madame, Monsieur, Impossible de télécharger la version 4.1.1 malgré plusieurs essais. En pièce jointe la réponse à chaque essai. Dans l’attente de votre aide. Sincères salutations alain.vai...@sfr.fr - 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: Statistic data per single country
On Sep 7, Rob Weir wrote: On Sep 7, Tal Daniel wrote: Thanks Rob for the detailed download statistics. The CSV is very useful for the English version, though it's less detailed for localized versions). The detail should be the same for the localized versions as well. Where it gives numbers by platform and by version, this is for all languages together, not just English. Then you have the columns for total downloads per day by language. Exactly, not that important, as I can get statistics from SourceForge too, if I'm that picky with the data. The transition from version to version is interesting, I agree. Where it happens quickly, say in 1 or 2 days, it shows that we coordinated everything well, and had the website, update notifications, 3rd party links to the downloads, etc., all changing over at the same time. But even then we still have many downloads of older versions. This suggests that (maybe) there are some 3rd party links to our website still pointing to old versions. That might explain that, while another reason could be developers installing older versions on VM, for testing. TODO(?) - move current version to an archive folder, upon release of newer version (say AOO 5). That would make previous version links obsolete, and maybe allow users to understand there's a new version, somehow.
Feature porting from LibreOffice
Hi all Obviously there are some features in AOO that do not exist in LO and vice versa. I was wondering what the current possibilities are to get certain features from LO integrated into AOO. Background: I am currently trying to get some devs together to fix a feature (creating digitally signed PDFs) that exists under the experimental features of LO (and does not work at the moment). If that should succeed, I would like to see that feature also in AOO. Would this be possible at all? Or would we need to rewrite the entire code and practically reimplement it in AOO? Just how would we go about it once it is fixed in LO? Thanks for any thoughts and inputs krgds /markus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Feature porting from LibreOffice
Background: I am currently trying to get some devs together to fix a feature (creating digitally signed PDFs) that exists under the experimental features of LO (and does not work at the moment). If that should succeed, I would like to see that feature also in AOO. I am not an expert but, as I can see, the best way is that this code for LO has Apache 2 licence. After that, both projects (AOO and LO) can use this code. So, if you have some influence on the people who want to create this code, you should offer this proposal, because much larger community will have benefit from that code. Regards, Wlada 2014-09-09 15:10 GMT+02:00 Markus Wernig liste...@wernig.net: Hi all Obviously there are some features in AOO that do not exist in LO and vice versa. I was wondering what the current possibilities are to get certain features from LO integrated into AOO. Background: I am currently trying to get some devs together to fix a feature (creating digitally signed PDFs) that exists under the experimental features of LO (and does not work at the moment). If that should succeed, I would like to see that feature also in AOO. Would this be possible at all? Or would we need to rewrite the entire code and practically reimplement it in AOO? Just how would we go about it once it is fixed in LO? Thanks for any thoughts and inputs krgds /markus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Feature porting from LibreOffice
From LibO to AOO, I already posted this question one year ago: http://openoffice.2283327.n4.nabble.com/LibO-code-will-be-integrated-to-AOO-td4649464.html - Mail original - De: Markus Wernig liste...@wernig.net À: dev@openoffice.apache.org Envoyé: Mardi 9 Septembre 2014 15:10:01 Objet: Feature porting from LibreOffice Hi all Obviously there are some features in AOO that do not exist in LO and vice versa. I was wondering what the current possibilities are to get certain features from LO integrated into AOO. Background: I am currently trying to get some devs together to fix a feature (creating digitally signed PDFs) that exists under the experimental features of LO (and does not work at the moment). If that should succeed, I would like to see that feature also in AOO. Would this be possible at all? Or would we need to rewrite the entire code and practically reimplement it in AOO? Just how would we go about it once it is fixed in LO? Thanks for any thoughts and inputs krgds /markus - 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: Forward planning for OO 5.0
Hi Ariel, but the extension depends on libraries with Category X license, so it cannot be included within an Apache product, whether in source or binary form Well, does somebody know who made this libraries? Are this libraries existing separately? I mean, does can help if someone ask this authors to donate this libraries under Apache 2 licence? Is it possible? Regrads, Wlada 2014-09-09 10:05 GMT+02:00 Ariel Constenla-Haile arie...@apache.org: On Fri, Sep 05, 2014 at 11:54:47PM +0200, Vladislav Stevanovic wrote: - Oracle Report builder should be integrated inside AOO, like in LO The code of the extension (and the related core code, modules reportbuilder and reportdesign, respectively) was included in Oracle's Software Grant, but the extension depends on libraries with Category X license, so it cannot be included within an Apache product, whether in source or binary form see: https://issues.apache.org/ooo/show_bug.cgi?id=118573 https://cwiki.apache.org/confluence/x/HaqoAQ https://cwiki.apache.org/confluence/x/4ZuoAQ http://www.apache.org/legal/3party.html#category-x Regards -- Ariel Constenla-Haile La Plata, Argentina
Re: Feature porting from LibreOffice
On 09/09/2014 03:31 PM, Vladislav Stevanovic wrote: Background: I am currently trying to get some devs together to fix a feature (creating digitally signed PDFs) that exists under the experimental features of LO (and does not work at the moment). If that should succeed, I would like to see that feature also in AOO. I am not an expert but, as I can see, the best way is that this code for LO has Apache 2 licence. After that, both projects (AOO and LO) can use this code. So, if you have some influence on the people who want to create this code, you should offer this proposal, because much larger community will have benefit from that code. OK, but apart from the license question: are there technical restrictions? Incompatibilities? thx /markus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Feature porting from LibreOffice
On 09.09.2014 15:10, Markus Wernig wrote: Hi all Obviously there are some features in AOO that do not exist in LO and vice versa. I was wondering what the current possibilities are to get certain features from LO integrated into AOO. Background: I am currently trying to get some devs together to fix a feature (creating digitally signed PDFs) that exists under the experimental features of LO (and does not work at the moment). If that should succeed, I would like to see that feature also in AOO. Would this be possible at all? Or would we need to rewrite the entire code and practically reimplement it in AOO? Just how would we go about it once it is fixed in LO? That's a problem of licenses. The Apache License has no so called copyleft, so LibreOffice can use our code. But LibreOffice uses licences with a (weak) copyleft, so we can't use their code, if the developer doesn't use also the Apache License (v 2.0) for his or hers code. So: if you want to share your code with Apache OpenOffice, use the Apache License version 2.0. But there midht be strong problems, if your patch is a derivative work from code which is under copyleft licenses only. Regards Michael signature.asc Description: OpenPGP digital signature
Re: Feature porting from LibreOffice
Hi Michael, That's a problem of licenses. The Apache License has no so called copyleft, so LibreOffice can use our code. But LibreOffice uses licences with a (weak) copyleft, so we can't use their code, if the developer doesn't use also the Apache License (v 2.0) for his or hers code. So: if you want to share your code with Apache OpenOffice, use the Apache License version 2.0. Not possible for a developer to use a double licence ? ALv2.0 and the license of Libreoffice?. Or maybe the double licence is only possible with a couple of two copyleft licences or not copyleft but not with a mix, as a couple with a copyleft licence and another non copyleft ? Other question : if an original work is produced under a double licence, which is the licence of a derivate work : obligatory the initial double licence of the original work or one or the other of the original work ? Thank you A+ -- gw
Re: Feature porting from LibreOffice
Guy Waterval wrote: Not possible for a developer to use a double licence ? Sure it is possible. And it is also possible for the copyright holder to add the Apache 2 license to work previously released under other, usually more restrictive, licenses. Or maybe the double licence is only possible with a couple of two copyleft licences or not copyleft but not with a mix, as a couple with a copyleft licence and another non copyleft ? This is totally wrong. I'm sure it's a honest question in your case, but a lot of people use this kind of fake questions to deliberately spread uncertainty about licenses. So, in short, these second group of questions is nonsense. Other question : if an original work is produced under a double licence, which is the licence of a derivate work : obligatory the initial double licence of the original work or one or the other of the original work ? For the meaning we give to double, this means take this code under either license A or license B, whichever you prefer. If one of the option is the Apache License version 2, we can take the code and improve it under the Apache License version 2. Then other projects that chose more restrictive licensing terms can obviously use our improved code. There's no need that I always state that I'm not a lawyer and this is not legal advice, right? Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Feature porting from LibreOffice
On Tue, Sep 9, 2014 at 6:40 AM, Markus Wernig liste...@wernig.net wrote: On 09/09/2014 03:31 PM, Vladislav Stevanovic wrote: Background: I am currently trying to get some devs together to fix a feature (creating digitally signed PDFs) that exists under the experimental features of LO (and does not work at the moment). If that should succeed, I would like to see that feature also in AOO. I am not an expert but, as I can see, the best way is that this code for LO has Apache 2 licence. After that, both projects (AOO and LO) can use this code. So, if you have some influence on the people who want to create this code, you should offer this proposal, because much larger community will have benefit from that code. OK, but apart from the license question: are there technical restrictions? Incompatibilities? thx /markus Maybe take a look at the build dependencies for each as a starting point? AOO: https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO See also AOO system requirements: http://www.openoffice.org/dev_docs/source/sys_reqs_aoo41.html vs LO -- - MzK Nothing will work unless you do. -- Maya Angelou
linux desktop integration questions
Currently, we have 4 desktop integration packs for rpm linux package management: * mandriva * suse * freedesktop * redhat and 1 for deb linux packages * deb(ian) menus Some observations about these: In reality, the suse menus are kde3 based in terms of icon locations, etc, so folks using kde4 experience integration problems. Does anyone know -- maybe from user list or forum questions -- how often the mandriva and redhat menus are used/installed? The freedesktop menus work for both KDE4 and Gnome (2 and above?) Some debian-based users are now using Gnome and KDE4 desktop environments and may be experiencing desktop integration problems as well (need more information on this one). In light of this, would it make sense to: * rename the suse-menus to kde3-menus? * perhaps delete the mandriva and redhat menus * provide freedesktop menus for the debian based desktop environments as well as deb * or finally, provide desktop-integrations as a separate pack the way we do language packs, so users could pick and choose -- - MzK Nothing will work unless you do. -- Maya Angelou
Re: Feature porting from LibreOffice
Hi all Sorry, one reply to two posts, but they seem so much related, it would be hard to separate them ... On 09/09/2014 08:58 PM, Andrea Pescetti wrote: Guy Waterval wrote: Not possible for a developer to use a double licence ? Sure it is possible. And it is also possible for the copyright holder to add the Apache 2 license to work previously released under other, usually more restrictive, licenses. OK, this sounds like good news. So if the developers of the original (currently broken) code and those of the (to be developed) fix agree to, eg. license it under both MPL and AL, we could use both code parts in both LO and AOO? On 09/09/2014 03:41 PM, RA Stehmann wrote: So: if you want to share your code with Apache OpenOffice, use the Apache License version 2.0. But there midht be strong problems, if your patch is a derivative work from code which is under copyleft licenses only. That sounds rather straightforward. The prominent question for me now is: how does one determine to which degree one code part is derived from another? In this particular case, from what I have seen, the code that needs to be fixed originally extended the already existing code for PDF generation. The source files in question currently have both, MPLv2 and ALv2, in their header. So, assuming that both, the developer of the original extension and the developers of the new fix to it, at least double-license their work (or put it all under AL), this should be possible, yes? If yes, what are the steps to be taken once development has finished? In what form does that consent (the double-licensing) have to be stated and to whom? And, on a more technical side, how can we make sure that the code developed in the LO tree (the original extension and the new fix) actually gets into the AOO tree? Afaict we would need an AOO committer to do that, as currently none of the devs in question have commit rights to AOO, from what I know. Is there a designated process for that? Thanks again for bearing with me and for any insight ... best /markus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Feature porting from LibreOffice
On 10/09/2014 Markus Wernig wrote: OK, this sounds like good news. So if the developers of the original (currently broken) code and those of the (to be developed) fix agree to, eg. license it under both MPL and AL, we could use both code parts in both LO and AOO? Even Apache License version 2 (in short: ALv2) only would be enough. I haven't become a lawyer in the three hours that separate this mail from my earlier one, but ALv2 is meant to be permissive enough for everybody to reuse code and we see code reuse happening regularly. what are the steps to be taken once development has finished? In what form does that consent (the double-licensing) have to be stated and to whom? Patches can be attached to Bugzilla: https://issues.apache.org/ooo/ and this is enough, in normal cases, for us to consider it contributed. But make the agreements before developing, not when it's finished. And ask to have a result in the form of a patch that can actually be applied to version X of program Y and work, since patches may need to be adapted for different codebases. we would need an AOO committer to do that, as currently none of the devs in question have commit rights to AOO, from what I know. Is there a designated process for that? This isn't really an issue. I integrated three patches from non-committers in the last three days. If something is in Bugzilla and it is very useful and well-documented and works, and the original author wants to contribute it to OpenOffice, finding a solution is easy. Thanks again for bearing with me and for any insight ... Don't ask too far. Please go by steps. If you want to reuse code from another project in OpenOffice, that code has to be made available under ALv2, or any group of licenses that includes ALv2 (there are other possibilities, but since I'm not a lawyer I can spare you those, and anyway they have no practical value). This is the first step. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: working on one of simple coding tasks
On 09/09/2014 Amali Praveena Soban Kumar wrote: Hi Andrea, I've completed the changes for issue 125581 Committed shortly ago, thanks! Now, I'm planning to take this first task from the simple tasks list and work on it - issue 59059. Shall I do it? Looks good. You'll need someone with better knowledge of the ODF internals than me if you have questions, but this is what this list is meant for, so don't hesitate and ask! Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: working on one of simple coding tasks
Hi Andrea, I've completed the changes for issue 125581 Committed shortly ago, thanks! Not a problem at all; I'm ready to do more tasks like this. Looks good. You'll need someone with better knowledge of the ODF internals than me if you have questions, but this is what this list is meant for, so don't hesitate and ask! The issue 59059, as Bugzilla says, is fixed in LO. I went into the BZ link for LO and found out there is a patch for it. Can I take and use the patch directly in AOO code? I checked it and AOO code is exactly the same, but still have to run it to see if the code works. So now working on second issue 64337. i have questions on this for which I'll start a separate mail. thanks, Amali. On Wednesday, 10 September 2014, 8:47, Andrea Pescetti pesce...@apache.org wrote: On 09/09/2014 Amali Praveena Soban Kumar wrote: Hi Andrea, I've completed the changes for issue 125581 Committed shortly ago, thanks! Now, I'm planning to take this first task from the simple tasks list and work on it - issue 59059. Shall I do it? Looks good. You'll need someone with better knowledge of the ODF internals than me if you have questions, but this is what this list is meant for, so don't hesitate and ask! Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
How to view AOO dialogs (GUI) in Ubuntu Linux
Hi dev, Actually, I'm working on issue https://issues.apache.org/ooo/show_bug.cgi?id=64337. There are .src and .hrc Graphical User Interface files for dialogs in AOO. Though this issue doesn't require addition/removal of GUI controls in Customize dialog, when I try to open it in Ubuntu Linux 14.04, it says, WAIS file type not supported. So I did a google search on these files; couldn't get much help; also read a pdf presentation of recent LO meeting; it talks about removing these obsolete/old file types and replacing with new versions? Thanks, Amali.
Re: How to view AOO dialogs (GUI) in Ubuntu Linux
On Tue, Sep 9, 2014 at 4:50 PM, Amali Praveena Soban Kumar samaliprave...@yahoo.com.au wrote: Hi dev, Actually, I'm working on issue https://issues.apache.org/ooo/show_bug.cgi?id=64337. There are .src and .hrc Graphical User Interface files for dialogs in AOO. Though this issue doesn't require addition/removal of GUI controls in Customize dialog, when I try to open it in Ubuntu Linux 14.04, it says, WAIS file type not supported. You should be able to directly open these from a text editor. At leas this works for me. If I just click on them for an automatic open, I get the same error you describe. So I did a google search on these files; couldn't get much help; also read a pdf presentation of recent LO meeting; it talks about removing these obsolete/old file types and replacing with new versions? Thanks, Amali. -- - MzK Nothing will work unless you do. -- Maya Angelou
question about OpenOffice environment variables
In issue 125499 -- https://issues.apache.org/ooo/show_bug.cgi?id=125499 I'm wondering if the environment variables might come into play here. Info at: https://wiki.openoffice.org/wiki/Environment_Variables I can certainly set OOO_FORCE_DESKTOP, but I'm wondering where I can find additional information on SAL_USE_VCLPLUGIN. Anybody? Right now I'm using the freedesktop.org desktop environment. Maybe I need to track down what else comes into play here besides what's in the spec file? -- - MzK Nothing will work unless you do. -- Maya Angelou
RE: working on one of simple coding tasks
Uh, no, you generally can't use a patch from LibreOffice for Apache OpenOffice unless the author of that patch agrees to it. If Zolnai Tamás were to contribute it to i59059, that would be best. Don't do that yourself. Others will have to decide what the policy is in this case and how the patch can be handled. I'm not a regular here and don't know what specific policy will apply. Andreas will know, of course. It is good that you asked. PS: I can confirm the bug. The ODF in the test documents is correct. AOO 4.1.1 loses that information on loading the document (as did older versions of LibreOffice). LibreOffice 4.3.1.2 loads the document correctly. I also replicated the bug by making a similar document of my own in AOO 4.1.1 and confirming that the drop cap style when set is not reloaded correctly even though it is set properly (and opens correctly in LibreOffice 4.3.1.2). -- Dennis E. Hamilton dennis.hamil...@acm.org+1-206-779-9430 https://keybase.io/orcmid PGP F96E 89FF D456 628A X.509 certs used and requested for signed e-mail -Original Message- From: Amali Praveena Soban Kumar [mailto:samaliprave...@yahoo.com.au] Sent: Tuesday, September 9, 2014 16:29 To: dev@openoffice.apache.org Subject: Re: working on one of simple coding tasks [ ... ] The issue 59059, as Bugzilla says, is fixed in LO. I went into the BZ link for LO and found out there is a patch for it. Can I take and use the patch directly in AOO code? I checked it and AOO code is exactly the same, but still have to run it to see if the code works. [ ... ] On 09/09/2014 Amali Praveena Soban Kumar wrote: Hi Andrea, I've completed the changes for issue 125581 Committed shortly ago, thanks! Now, I'm planning to take this first task from the simple tasks list and work on it - issue 59059. Shall I do it? Looks good. You'll need someone with better knowledge of the ODF internals than me if you have questions, but this is what this list is meant for, so don't hesitate and ask! Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
What issue should I work on?
Thanks Guys. I've finally built successfully. Please, I would like to find an issue with lots of mentors to work on. I have some experience with Java and Python. I am just learning C++ and would really like to get my hands dirty with it on AOO. Thanks again.
