[tdf-discuss] Re: Help with telling the story Re: Accessibility: What's the story?
Le 16/02/11 18:59, drew a écrit : I also have some vague recollection that the state of Massachusetts migration to OOo was rejected because of the lack of accessibility tools at the time, a requirement under that state's procurement laws. So the topic is an important one, especially if LibreOffice wants to get a foothold in US government institutions. Alex -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
[tdf-discuss] Re: FOSDEM LibreOffice talk now available as video
Le 2011-02-16 15:11, Michael a écrit : Hi, I have not seen any notice about it on this list, so just in case you are not already aware of it: The great talk Liberating Open Office Development from Michael Meeks presented at this years FOSDEM is available as a video on http://video.fosdem.org/2011/maintracks/ Regards, Michael Hi Michael: Thanks for the notice. I have added this to our newly minted LibreOffice Videos wiki page[1]. In fact, this is our first video to make it into this page. A must see for any serious member in our membership. Inspiring. Thanks to Michael Meeks for the great presentation. Cheers Marc [1] http://wiki.documentfoundation.org/Marketing/Videos -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
Re: Help with telling the story Re: [tdf-discuss] Accessibility: What's the story?
At 18:59 16/02/2011, drew wrote: On Wed, 2011-02-16 at 17:30 +, Michael Meeks wrote: Hi Joanie, On Wed, 2011-02-16 at 16:24 +0100, Cor Nouws wrote: * Is there an active a11y team and/or developers focused on a11y issues in LibreOffice? Sure there are people with a focus on this. I am not sure if we actually can speak of 'a team'. Quite - whether there is a team at OO.o is a similar question ;-) there are people who can help fix problems. From ORCA's perspective, I created the design, prototype, and ~50% of the existing atk bridge in vcl; so I wouldn't fret that we are skill-less in this area :-) Furthermore, it is far easier to work on LibreOffice process-wise to get fixes in, so I anticipate (over time) a better accessibility experience; and of course we welcome patches (on the dev list). Hi, If I may change the subject here for a moment. When lasted I noted any comment on the OO.o lists with regard to the IAccessibilty code coming from IBM, IIRC, the comment was that it was 'not yet integrated' - I don't know if that is still true. As far as I know, the IAccessible2 code is in the OOo repository but not in the main trunk. At FOSDEM (two week ago), Malte Timmermann could not give a date when the integration (and testing) would be finished: It will be done when it's done. (See my summary at http://listarchives.libreoffice.org/www/accessibility/msg00034.html.) Best regards, Christophe From LibreOffice stand point, I am not sure I have heard what the plan is, would that integration be merged here? (if the answer is still don't know till we see it - that's a valid answer) I remember watching the session on accessibility at the last OOoConn and I know there was a MS rep there, as I remember you had some small interaction. I'm don't know then if your (the dev teams) thoughts are to look for the integration coming via OO.o/IBM or if you are looking at going a different route. Please don't feel you need to respond directly - if there are some references already (other emails, blogs) it would be great if anyone could point in the direction of those. This next period there are number of shows in the US and the question of accessibility is treated quite directly in this area. I was thinking of trying to create a small reference piece for the booth staff at the shows with some information on this subject (within this next 2 weeks - to make the first show): LIbreOffice support for accessibility technologies (current and future) [or something similar] I'm starting with the assumption that anything relating to OO.o 3.3 would be correct also for Libo 3.3 - correct assumption? Beyond that - I'm not asking for a direct response here to this email, but if that assumption is not correct, or there are actual plans for a different direction for integration it would be much appreciated if anyone could direct some links my way, I will read and assemble a smaller flyer type piece, then ask folks to review it. Thanks for your time, Drew -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Better products and services through end-user empowerment www.usem-net.eu - www.stand4all.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
Re: [tdf-discuss] Re: Help with telling the story Re: Accessibility: What's the story?
At 09:28 17/02/2011, Alexander Thurgood wrote: Le 16/02/11 18:59, drew a écrit : I also have some vague recollection that the state of Massachusetts migration to OOo was rejected because of the lack of accessibility tools at the time, a requirement under that state's procurement laws. So the topic is an important one, especially if LibreOffice wants to get a foothold in US government institutions. The ODF format itself also needed better accessibility. So the ODF committee at OASIS created an Accessibility subcommittee to tackle the issue: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office-accessibility. There are a number OpenOffice.org/LibreOffice bugs related to ODF accessibility features, for example: * Image title and description that disappear after adding a caption in Writer: https://bugs.freedesktop.org/show_bug.cgi?id=32137 * Image title and description that disappear when you modify the image anchor in Writer * Image title and description are not exported when exporting PDF from Impress: https://bugs.freedesktop.org/show_bug.cgi?id=34135 Best regards, Christophe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Better products and services through end-user empowerment www.usem-net.eu - www.stand4all.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
[tdf-discuss] Re: LibreOffice Community starts 50, 000 Euro challenge for setting-up its foundation
Le 16/02/11 13:18, Florian Effenberger a écrit : Hi Florian, I see that this page exists translated into German and Spanish. If I wanted to provide a translation into French, how would I go about doing that ? At present, I have no access as author to the TDF website, and don't see any real need to have one. Couldn't I just send someone the translation ? Alex -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
Re: [tdf-discuss] Re: LibreOffice Community starts 50, 000 Euro challenge for setting-up its foundation
Hi Alex, :-) On Thu, Feb 17, 2011 at 19:27, Alexander Thurgood alex.thurg...@gmail.com wrote: Le 16/02/11 13:18, Florian Effenberger a écrit : Hi Florian, I see that this page exists translated into German and Spanish. If I wanted to provide a translation into French, how would I go about doing that ? At present, I have no access as author to the TDF website, and don't see any real need to have one. Couldn't I just send someone the translation ? If you like, you can send it to me and I'll post it Monday or Tuesday. David Nelson -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
Re: [tdf-discuss] Re: LibreOffice Community starts 50, 000 Euro challenge for setting-up its foundation
Hi Alex, On 17/02/2011 14:27, Alexander Thurgood wrote: Le 16/02/11 13:18, Florian Effenberger a écrit : Hi Florian, I see that this page exists translated into German and Spanish. If I wanted to provide a translation into French, how would I go about doing that ? At present, I have no access as author to the TDF website, and don't see any real need to have one. Couldn't I just send someone the translation ? I was just working on the pages when I see your mail. Would you mind that we coordinate this with Jean-Baptiste on the fr@discuss list? Did you translate the PR too? Kind regards Sophie -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
[tdf-discuss] bug in libreoffice no update formulas
libo the stable 3.3.0 on windowsXP professional SP2 on intel P4 3.4 GHz 2GB of ram and the same happen in suse linux 11.3 with libo' 3.3.0 by suse on dell latitude intel i7 4GB of ram I suppose this dipend if the file is big and with many formulas, becouse with little files doesn' happen If I make changes the calc doesnt update the values in formulas, I must press ctrlshiftF9 to update. Is possible here to attach a 1MB odt file for test?? thanks -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
Re: [tdf-discuss] FOSDEM LibreOffice talk now available as video
On Thu, Feb 17, 2011 at 3:11 AM, Michael mich...@codingmicha.de wrote:
Hi,
I have not seen any notice about it on this list, so just in case you are not
already aware of it:
The great talk Liberating Open Office Development from Michael Meeks presented
at this years FOSDEM is available as a video on
http://video.fosdem.org/2011/maintracks/
Great!
Just a question:
Why not MSO vs LibO?
--
Best Regards,
Nguyen Hung Vu [aka: NVH] ( in Vietnamese: Nguyễn Vũ Hưng )
vuhung16plus{remove}@gmail.dot.com , YIM: vuhung16 , Skype: vuhung16plus
--
Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***
[tdf-discuss] Re: LibreOffice Community starts 50, 000 Euro challenge for setting-up its foundation
Le 17/02/11 13:25, sophie a écrit : Hi Sophie, I see that this page exists translated into German and Spanish. If I wanted to provide a translation into French, how would I go about doing that ? At present, I have no access as author to the TDF website, and don't see any real need to have one. Couldn't I just send someone the translation ? I was just working on the pages when I see your mail. Would you mind that we coordinate this with Jean-Baptiste on the fr@discuss list? Did you translate the PR too? I haven't translated anything yet, but I've already seen a couple of proposals after I posted a piqure de rappel on the French discussion list. I am easy about it either way, I just jumped on it because it seemed a glaring lack to me, and I know that the French NL group is prety active ;-) I can leave you to it, or you can check out the proposals put forward on the French list. Alex -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
Re: [tdf-discuss] Re: LibreOffice Community starts 50, 000 Euro challenge for setting-up its foundation
Hi Alex, Alexander Thurgood wrote on 2011-02-17 16.06: I haven't translated anything yet, but I've already seen a couple of proposals after I posted a piqure de rappel on the French discussion list. I am easy about it either way, I just jumped on it because it seemed a glaring lack to me, and I know that the French NL group is prety active;-) I can leave you to it, or you can check out the proposals put forward on the French list. thanks for your contribution, much appreciated! David or Christian can give you editor rights -- the more localizations we have for the page, the better it is :) Florian -- Florian Effenberger flo...@documentfoundation.org Steering Committee and Founding Member of The Document Foundation Tel: +49 8341 99660880 | Mobile: +49 151 14424108 Skype: floeff | Twitter/Identi.ca: @floeff -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
[tdf-discuss] Re: LibreOffice Community starts 50, 000 Euro challenge for setting-up its foundation
Le 17/02/11 16:46, Florian Effenberger a écrit : Hi Florian, thanks for your contribution, much appreciated! David or Christian can give you editor rights -- the more localizations we have for the page, the better it is :) Its OK, I don't actually need them, I think Sophie is going to pick up the translation off the French discussion list. Alex -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
[tdf-discuss] Re: bug in libreoffice no update formulas
yahoo-pier_andreit wrote: libo the stable 3.3.0 on windowsXP professional SP2 on intel P4 3.4 GHz 2GB of ram and the same happen in suse linux 11.3 with libo' 3.3.0 by suse on dell latitude intel i7 4GB of ram I suppose this dipend if the file is big and with many formulas, becouse with little files doesn' happen If I make changes the calc doesnt update the values in formulas, I must press ctrlshiftF9 to update. Is possible here to attach a 1MB odt file for test?? thanks -- Use Tools Cell Contents Auto Recalculate Tink. Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity *** -- View this message in context: http://nabble.documentfoundation.org/bug-in-libreoffice-no-update-formulas-tp2519521p2520584.html Sent from the Discuss mailing list archive at Nabble.com. -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
Re: [tdf-discuss] Oracle Contributor Agreement and LibreOffice contributions
Hi Michael, *, Michael Meeks wrote (16-02-11 18:36) This question prolly belongs best on the dev list. On Wed, 2011-02-16 at 15:28 +0100, Christophe Strobbe wrote: 1. Now imagine that I contribute code to LibreOffice and the contribution is accepted. Is it then still acceptable (from a copyright point of view) to sign the Oracle Contributor Agreement and submit the same code to OpenOffice.org? Yes - on the other hand, this creates more work for LibreOffice, and (of course) lots of work for you submitting code to OO.o - signing and faxing a form, CWS creation, etc. etc. That's fine of course by me, but when it comes to merging (the inevitably different) changes from OO.o it just makes even more work when we merge that stuff in. So this practise is essentially not recommended. :-) I know that you are very careful preventing that precious developer time is spoiled, which of course is very just. Reading Christophes question though, I see the route that people contribute code both to LibreOffice and OpenOffice.org. It is right that this (which indeed is perfect possible) will give extra work for the people contributing, but I do not see why that should create extra work for LibreOffice, since the code already has been contributed here. Kind regards, Cor 2.b. Can I contribute the code to LibreOffice while the acceptance of my patch to OpenOffice.org is still pending? So - if it is licensed under LGPLv3+/MPL we are happy to accept it - please post it to the dev list, we're eager to see it :-) if Oracle owns the copyright[1], but you can license it to us under LGPLv3+/MPL, I (for one) don't much mind who owns it :-) But again, you consume LibreOffice engineering resource doing merging changes, and our life is easier if you don't do that in most cases :-) ATB, Michael. [1] - and their assignment-cum-license is a pretty thorough way of giving away your rights. -- - giving openoffice.org its foundation :: The Document Foundation - -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
Re: [tdf-discuss] Oracle Contributor Agreement and LibreOffice contributions
Hi, Christophe Strobbe wrote (16-02-11 15:28) I have a question about licences and copyright. [...] These are important questions for developers who don't want to take sides for or against OpenOffice.org or LibreOffice. If this has already been clarified in a wiki somewhere, please let me know. (I have searched the web but I haven't found any info on this.) I think the questions have been answered in detail clear enough and show there is no problem. I want to add that the question also is an interesting one, since some people simply might prefer to contribute to both OpenOffice.org and LibreOffice, since there is still quite some overlap, and code coming from Open to Libre. Of course I know of the other sides of copy right assignments and that therefore people prefer not to share contributions, but it is not something we, IMHO, would want to imply on all developers :-) Kind regards, Cor -- - giving openoffice.org its foundation :: The Document Foundation - -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
Re: [tdf-discuss] REVIEW ARTICLE: VITAL reading for LibreOffice developers, users, supporters
Thanks for getting in touch, Joe, and I'll try to answer where I can. On 16/02/2011 16:45, Joe Rotello wrote: Almost VITAL reading for LibreOffice developers, users, and supporters: [snip] The reasoning is that these weakness areas MUST be addressed and SOON, ...[snip] These include compatibility with MS Office XML and 2010 files, As has been mentioned here before, LibO will both read and write MS Office OOXML files. The matter of changing specifications for those files by Microsoft in the future is under their control and all we can do is catch up later since the openness of their file structure details is less than perfect. Presentation having limited PowerPoint features, and a few others that the article mentions. The only significant missing feature was the use of free-motion paths which was addressed in a previous version of OpenOffice and is now available. It is true that some of the effects and transitions are not available, as the article notes, but also as it notes wherever possible these degrade gracefully to the best available common form. Hope that this reading of the article brings many fruits to LibreOffice, perhaps in 3.3.1 or the next release and Update. The other significant points the article raises are the lack of full compatibility for macros and programming languages and the lack of a connector to Microsoft Sharepoint. While both are true, I can only point out macros are conversions from Microsoft macros, not implementations of Microsoft coding languages and programming of course also does not implement Microsoft coding languages. Similarly there are no links to Microsft Sharepoint and for the same reasons. Remember that LibO is provided as Open Source Software and operates on systems with very different OSs, not just Windows. We cannot commit to Windows-only versions or to providing proprietary code owned by Microsoft. Simply put, these issues are outside our control. Joe Rotello WindowGroup / Knoxville, TN / USA -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
Re: [tdf-discuss] Oracle Contributor Agreement and LibreOffice contributions
On Thu, 2011-02-17 at 23:44 +0100, Cor Nouws wrote: Hi Michael, *, Michael Meeks wrote (16-02-11 18:36) This question prolly belongs best on the dev list. On Wed, 2011-02-16 at 15:28 +0100, Christophe Strobbe wrote: 1. Now imagine that I contribute code to LibreOffice and the contribution is accepted. Is it then still acceptable (from a copyright point of view) to sign the Oracle Contributor Agreement and submit the same code to OpenOffice.org? Yes - on the other hand, this creates more work for LibreOffice, and (of course) lots of work for you submitting code to OO.o - signing and faxing a form, CWS creation, etc. etc. That's fine of course by me, but when it comes to merging (the inevitably different) changes from OO.o it just makes even more work when we merge that stuff in. So this practise is essentially not recommended. :-) I know that you are very careful preventing that precious developer time is spoiled, which of course is very just. Reading Christophes question though, I see the route that people contribute code both to LibreOffice and OpenOffice.org. It is right that this (which indeed is perfect possible) will give extra work for the people contributing, but I do not see why that should create extra work for LibreOffice, since the code already has been contributed here. It does create extra work for us. Case in point, there was a fix for the filter performance issue that the reporter reported both to us and to OOo http://www.openoffice.org/issues/show_bug.cgi?id=116164 They decided to fix it for 3.3, and I was already working on the same fix right after the reporter reported here. Naturally we ended up solving this differently, merging theirs into ours causes all sorts of conflicts, and resolving that was not trivial. I ended up removing my changes, pull their changes in, removing their changes again (since it caused regression), and re-worked it from scratch. Now, that was slightly different case since it didn't involve a patch. And you might think that, if someone submitted a patch both to our project and OOo project, it shouldn't cause any merging conflict. That's in fact how I interpreted your above statement. But in reality when a patch is being integrated, in most cases the patch does not get integrated as-is; they may do some follow-up changes to cover more cases, and we may do the same. They may make a small follow-up change, or they may entirely re-work the patch and do completely different. Worse, they may make changes in areas that are far removed from the areas where we make changes, in which case merging their changes into ours will not cause conflict, but it will cause issues in run-time behaviors. Discovering that may take months, or sometimes years. So, as Michael says, I'm not a big fan of people submitting patches to both projects. And yes, it will create extra work for us but not necessarily for them since we pull their changes but they don't pull ours. Having said all this, we can't stop people contributing to both projects. It's their choice and it's their basic freedom. But it does create extra work for us, that much is for sure, speaking from experience. Kohei -- Kohei Yoshida, LibreOffice hacker, Calc kyosh...@novell.com -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
Re: [tdf-discuss] REVIEW ARTICLE: VITAL reading for LibreOffice developers, users, supporters
The OOo Extensin site offers sharepoint connector for OOo but it is not free. 2011/2/18, Mark Preston m...@mpreston.demon.co.uk: Thanks for getting in touch, Joe, and I'll try to answer where I can. On 16/02/2011 16:45, Joe Rotello wrote: Almost VITAL reading for LibreOffice developers, users, and supporters: [snip] The reasoning is that these weakness areas MUST be addressed and SOON, ...[snip] These include compatibility with MS Office XML and 2010 files, As has been mentioned here before, LibO will both read and write MS Office OOXML files. The matter of changing specifications for those files by Microsoft in the future is under their control and all we can do is catch up later since the openness of their file structure details is less than perfect. Presentation having limited PowerPoint features, and a few others that the article mentions. The only significant missing feature was the use of free-motion paths which was addressed in a previous version of OpenOffice and is now available. It is true that some of the effects and transitions are not available, as the article notes, but also as it notes wherever possible these degrade gracefully to the best available common form. Hope that this reading of the article brings many fruits to LibreOffice, perhaps in 3.3.1 or the next release and Update. The other significant points the article raises are the lack of full compatibility for macros and programming languages and the lack of a connector to Microsoft Sharepoint. While both are true, I can only point out macros are conversions from Microsoft macros, not implementations of Microsoft coding languages and programming of course also does not implement Microsoft coding languages. Similarly there are no links to Microsft Sharepoint and for the same reasons. Remember that LibO is provided as Open Source Software and operates on systems with very different OSs, not just Windows. We cannot commit to Windows-only versions or to providing proprietary code owned by Microsoft. Simply put, these issues are outside our control. Joe Rotello WindowGroup / Knoxville, TN / USA -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity *** -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
[tdf-discuss] No more desktop Linux systems in the German Foreign Office - The H Open Source: News and Features
They're moving back from Linux to Windows+Office! What's happening there? http://www.h-online.com/open/news/item/No-more-desktop-Linux-systems-in-the-German-Foreign-Office-1191122.html The Foreign Office launched a modernisation process in 2010, one component of which was the pursuit of a new IT strategy moving away from open source software and towards standardised proprietary client solutions as used in other ministries. Specifically, this means a return to Windows XP, to be upgraded at some point to Windows 7, *Office 2010* and Outlook. According to the government, this will not give rise to any immediate costs, indeed, they expect introduction of these standardised software products to produce efficiency gains. -- _/|\_ /Samphan Raruenrom./ Osdev - Open Source Development Co., Ltd. / ??./ ? - ?? ?? ? tel: +66 2 269 9889 web: osdev.co.th http://www.osdev.co.th/ twitter: @osdev http://twitter.com/osdev facebook: facebook.com/osdev http://www.facebook.com/osdev -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
Re: [tdf-discuss] REVIEW ARTICLE: VITAL reading for LibreOffice developers, users, supporters
The OOo Extensin site offers sharepoint connector for OOo but it is not free. 2011/2/18, Mark Preston m...@mpreston.demon.co.uk: Thanks for getting in touch, Joe, and I'll try to answer where I can. On 16/02/2011 16:45, Joe Rotello wrote: Almost VITAL reading for LibreOffice developers, users, and supporters: [snip] The reasoning is that these weakness areas MUST be addressed and SOON, ...[snip] These include compatibility with MS Office XML and 2010 files, As has been mentioned here before, LibO will both read and write MS Office OOXML files. The matter of changing specifications for those files by Microsoft in the future is under their control and all we can do is catch up later since the openness of their file structure details is less than perfect. Presentation having limited PowerPoint features, and a few others that the article mentions. The only significant missing feature was the use of free-motion paths which was addressed in a previous version of OpenOffice and is now available. It is true that some of the effects and transitions are not available, as the article notes, but also as it notes wherever possible these degrade gracefully to the best available common form. Hope that this reading of the article brings many fruits to LibreOffice, perhaps in 3.3.1 or the next release and Update. The other significant points the article raises are the lack of full compatibility for macros and programming languages and the lack of a connector to Microsoft Sharepoint. While both are true, I can only point out macros are conversions from Microsoft macros, not implementations of Microsoft coding languages and programming of course also does not implement Microsoft coding languages. Similarly there are no links to Microsft Sharepoint and for the same reasons. Remember that LibO is provided as Open Source Software and operates on systems with very different OSs, not just Windows. We cannot commit to Windows-only versions or to providing proprietary code owned by Microsoft. Simply put, these issues are outside our control. Joe Rotello WindowGroup / Knoxville, TN / USA -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity *** -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
Re: [tdf-discuss] Oracle Contributor Agreement and LibreOffice contributions
Hi Kohei, Kohei Yoshida wrote (18-02-11 02:07) On Thu, 2011-02-17 at 23:44 +0100, Cor Nouws wrote: Reading Christophes question though, I see the route that people contribute code both to LibreOffice and OpenOffice.org. It is right that this (which indeed is perfect possible) will give extra work for the people contributing, but I do not see why that should create extra work for LibreOffice, since the code already has been contributed here. It does create extra work for us. Case in point, there was a fix for the filter performance issue that the reporter reported both to us and to OOo http://www.openoffice.org/issues/show_bug.cgi?id=116164 They decided to fix it for 3.3, and I was already working on the same fix right after the reporter reported here. Naturally we ended up solving this differently, merging theirs into ours causes all sorts of conflicts, and resolving that was not trivial. I ended up removing my changes, pull their changes in, removing their changes again (since it caused regression), and re-worked it from scratch. Now, that was slightly different case since it didn't involve a patch. And you might think that, if someone submitted a patch both to our project and OOo project, it shouldn't cause any merging conflict. That's in fact how I interpreted your above statement. Correct. But in reality when a patch is being integrated, in most cases the patch does not get integrated as-is; they may do some follow-up changes to cover more cases, and we may do the same. They may make a small follow-up change, or they may entirely re-work the patch and do completely different. Worse, they may make changes in areas that are far removed from the areas where we make changes, in which case merging their changes into ours will not cause conflict, but it will cause issues in run-time behaviors. Discovering that may take months, or sometimes years. So, as Michael says, I'm not a big fan of people submitting patches to both projects. And yes, it will create extra work for us but not necessarily for them since we pull their changes but they don't pull ours. Having said all this, we can't stop people contributing to both projects. It's their choice and it's their basic freedom. But it does create extra work for us, that much is for sure, speaking from experience. Thanks for this extensive answer. Indeed I know the example from i#116164, but did not have the idea that there is a more general considerable risk with patches and changes, apart from the fact that of course pulling from another code base always involves work. But you made the point more clear. Thanks for that. Cor -- - giving openoffice.org its foundation :: The Document Foundation - -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
