Re: [AOO 4.0]: migration of AOO 3.4.x/OOo 3.x user profile data - help needed
Rory O'Farrell wrote: On Tue, 18 Jun 2013 21:54:52 +0200 Andrea Pescetti wrote: Ariel Constenla-Haile wrote: On Tue, Jun 18, 2013 at 5:21 AM, Oliver-Rainer Wittmann wrote: Do you have one or two C++ extension at hand (except former Presenter Screen and former Presenation Minizer) for testing? The PDF Import extension: http://extensions.openoffice.org/en/project/pdfimport MySQL Connector: http://extensions.openoffice.org/en/project/mysql_connector My version of this last one: http://code.google.com/a/apache-extras.org/p/aoo-my-sdbc/ This deserves some discussion: these two extensions are very popular so it would be better to find a solution to this before users ask for support in scores. For me, the absence of the Presenter Console would be a major barrier The two extensions I was referring to are: PDF Import and MySQL Connector. Presenter Console and Presentation Minimizer, as Oliver wrote, are staying: they won't be packaged as extensions since they will be directly integrated in OpenOffice. So their functionality will be available in 4.0 with no changes and no need to update any extensions. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: proposal for an update of the AOO 4.0 release schedule
On 19 June 2013 10:14, Jürgen Schmidt jogischm...@gmail.com wrote: Hi, I tried to get an overview where we are with our AOO 4.0 release and I have thought about an updated release plan. I hope you share my view on this updated plan and you will continue to help that we can achieve it. First of all I am still thinking that we should release the 4.0 as soon as possible and before the majority will take a break and go in summer holidays. And with a potential second release later this year in mind I believe July is the best time. We are a little bit behind my proposed schedule that we can't hold under the current circumstances. It's ok, we worked hard, did a lot of testing, work on translation and things moved forward. But when I take a look on the list of proposed show stoppers and the not yet integrated help for the sidebar and the translation, I believe we should adapt our release plan to take the current situation and status into account. I see the following work items that we have to complete before or in parallel to the vote of an RC: - sidebar help merge the English help file on Pootle and give the translation volunteers at least the chance to provide a translation. This is not yet done because the lack of time (I am the bottle neck here and maybe other volunteers can jin me in the future to work on this). The sidebar is the most visible improvement in 4.0 and now where we have a help file, it should be translated if possible - finish general translation update, means update Pootle with offline translated strings on demand, merge the localized strings back from Pootle, run gsi consistency check to find potential problems like mismatched xml tags. I would like to see some further languages complete that are very popular, this includes Danish, Sweidish, German. I asked on the list sometime ago, if anybody was working on Danish and did not get any answer, so I am afraid the will not make 4.0 rgds jan I. - continue to review, identify the real show stopper issues. We expect to come up in the end with a list of 15-20 real show stopper issues - prepare the update service - prepare release notes (attractive marketing material that can be used), with screenshots as many as possible to highlight the features and bug fixes - logo integration as first step of an ongoing brand refresh - depends on the availability of the logo files - RAT scan - have to be checked - document migration path for incompatible API changes, not migrated extensions Some of these points have to be finished until the first official release candidate (RC). Taking all this into account I would like to propose the following update: - Wednesday June 19th, update Pootle with sidebar help and provide Po files for all current languages available on Pootle. - Monday July 1th, deadline for the localization, it always takes more time to merge it back and fix potential problems - Monday July 1th, deadline for logo integration - Wednesday/Thursday July 3/4th, provide last snapshot build with all available translations, logo if finished etc. - create new AOO release branch on Wednesday July 4th after the last snapshot - continue fixing show stopper issues until Friday July 5th on the new created release branch - start RC build on Monday July 8th, on new created release branch - July 9th, provide RC to the community and start voting on July 11th continue to work and improve build independent work items, like release notes etc. - vote should be finished July 4th final preparation, signing, uploading etc. for the release - July 16th public release and announcement Sorry for the longer email but I hope this make sense and we can all agree on this to achieve our goal and make AOO 4.0 available to the public. Opinions and discussion should take place on the dev list only please. thx for your good work. jan I Regards Juergen PS: I will start to work on the Pootle update. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.0.0_release_blocker granted: [Bug 122331] first installation dialog OpenOffice 4.0.0 Installation Preparation misses application image
j...@apache.org has granted Oliver-Rainer Wittmann o...@apache.org's request for 4.0.0_release_blocker: Bug 122331: first installation dialog OpenOffice 4.0.0 Installation Preparation misses application image https://issues.apache.org/ooo/show_bug.cgi?id=122331 --- Additional Comments from j...@apache.org set showstopper flag - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[RELEASE][REMINDER]: showstopper issues have to be proposed and discussed here on the list
Hi, we have a list of showstopper issues where the showstopper flag is already requested and we are working on reviewing this list. If there are new critical issues that come up during further testing or whatever please report an discuss them here on the list. We have to prioritize and can't fix all. There always issues that are critical for certain users but we can't fix all in time. Critieria for real showstopper issues - data loss - crashes - regressions compared to AOO 3.4.1 We can and will discuss the issues on demand but again we have to prioritize and will focus on the most critical issues that affect most users. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
herunterladen Ihre program
Hallo Ich wollte Ihre Programm herunterladen auf der Deutsche Sprache . ich habe es aber auf Holländisch bekomme, ich habe versucht nochmal aber es geht nicht können sie mir bitte helfen mfg H.Averbuch
Starting Introduction to Contributing to Apache OpenOffice Module
Hi I would like to contribute as projects like this only work when there are willing helpers. Unfortunately I'm a silver surfer with virtually no knowledge of how programs work, I can generally work out how to use them, sometimes in unusual ways. I wrote a book on lacemaking full of diagrams and photos using Word 2000 and my publisher had no idea how I did it, 'All about making- Geomtrical Bucks Point Lace' www.alexstillwell.wordpress.com I have others also listed on the website and I have given one to the Arizona University Library for free download because the demand is too small for a reprint but there are those who wish to have access to the material. If I can be of any help please let me know. I have just finished a book and as I do not have another in mind I have time available. Best wishes to all Alex
RE: [RELEASE]: proposal for an update of the AOO 4.0 release schedule
Date: Wed, 19 Jun 2013 10:14:46 +0200 From: jogischm...@gmail.com To: dev@openoffice.apache.org; l...@openoffice.apache.org; q...@openoffice.apache.org Subject: [RELEASE]: proposal for an update of the AOO 4.0 release schedule Hi, I tried to get an overview where we are with our AOO 4.0 release and I have thought about an updated release plan. I hope you share my view on this updated plan and you will continue to help that we can achieve it. First of all I am still thinking that we should release the 4.0 as soon as possible and before the majority will take a break and go in summer holidays. And with a potential second release later this year in mind I believe July is the best time. We are a little bit behind my proposed schedule that we can't hold under the current circumstances. It's ok, we worked hard, did a lot of testing, work on translation and things moved forward. But when I take a look on the list of proposed show stoppers and the not yet integrated help for the sidebar and the translation, I believe we should adapt our release plan to take the current situation and status into account. I see the following work items that we have to complete before or in parallel to the vote of an RC: - sidebar help merge the English help file on Pootle and give the translation volunteers at least the chance to provide a translation. This is not yet done because the lack of time (I am the bottle neck here and maybe other volunteers can jin me in the future to work on this). The sidebar is the most visible improvement in 4.0 and now where we have a help file, it should be translated if possible - finish general translation update, means update Pootle with offline translated strings on demand, merge the localized strings back from Pootle, run gsi consistency check to find potential problems like mismatched xml tags. I would like to see some further languages complete that are very popular, this includes Danish, Sweidish, German. - continue to review, identify the real show stopper issues. We expect to come up in the end with a list of 15-20 real show stopper issues - prepare the update service - prepare release notes (attractive marketing material that can be used), with screenshots as many as possible to highlight the features and bug fixes - logo integration as first step of an ongoing brand refresh - depends on the availability of the logo files - RAT scan - have to be checked - document migration path for incompatible API changes, not migrated extensions Some of these points have to be finished until the first official release candidate (RC). Taking all this into account I would like to propose the following update: - Wednesday June 19th, update Pootle with sidebar help and provide Po files for all current languages available on Pootle. - Monday July 1th, deadline for the localization, it always takes more time to merge it back and fix potential problems - Monday July 1th, deadline for logo integration - Wednesday/Thursday July 3/4th, provide last snapshot build with all available translations, logo if finished etc. - create new AOO release branch on Wednesday July 4th after the last snapshot - continue fixing show stopper issues until Friday July 5th on the new created release branch - start RC build on Monday July 8th, on new created release branch - July 9th, provide RC to the community and start voting on July 11th continue to work and improve build independent work items, like release notes etc. - vote should be finished July 4th final preparation, signing, uploading etc. for the release - July 16th public release and announcement Sorry for the longer email but I hope this make sense and we can all agree on this to achieve our goal and make AOO 4.0 available to the public. Opinions and discussion should take place on the dev list only please. Regards Juergen PS: I will start to work on the Pootle update. Me too, I want to thank you for your hard and good work. As for the the voting on your proposals, I am not going to be able to complete the UI translation for the first release; so for me it is O.K. whatever seems adequate to you. Regards Jonpeli - To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org For additional commands, e-mail: l10n-h...@openoffice.apache.org
OpenCommandArgument2 Data Sink
Hello, I'm working on the XActiveDataSink. I'm slightly confused about how to handle OpenCommandArgument2.Sink . The object is the one which is filled with the XActiveDataSink object for which I have to set the InputStream by calling setInputStream() and pass the XInputStream implementation. This is what I have understood. But, the confusing thing is why is the datatype for Sink - Object? Shoudnt it be XActiveDataSink? I'm not understanding how to handle this Sink. -- Rajath S, M.Sc(Hons.) Physics, Birla Institute of Technology and Science - Pilani, Pilani
Re: OpenCommandArgument2 Data Sink
Hello, with reference to my previous mail. From webdav ucp, this is the statement I'm not understanding: uno::Reference io::XActiveDataSink xSink( rArg.Sink, uno::UNO_QUERY ); Where is this constructor coming from? On Wed, Jun 19, 2013 at 9:55 PM, Rajath Shashidhara rajaths.raja...@gmail.com wrote: Hello, I'm working on the XActiveDataSink. I'm slightly confused about how to handle OpenCommandArgument2.Sink . The object is the one which is filled with the XActiveDataSink object for which I have to set the InputStream by calling setInputStream() and pass the XInputStream implementation. This is what I have understood. But, the confusing thing is why is the datatype for Sink - Object? Shoudnt it be XActiveDataSink? I'm not understanding how to handle this Sink. -- Rajath S, M.Sc(Hons.) Physics, Birla Institute of Technology and Science - Pilani, Pilani -- Rajath S, M.Sc(Hons.) Physics, Birla Institute of Technology and Science - Pilani, Pilani
Re: [DISCUSS] a new web area for Apache OpenOffice third party products
On Mon, Jun 17, 2013 at 6:31 PM, Kay Schenk kay.sch...@gmail.com wrote: On Sun, Jun 16, 2013 at 5:40 PM, Rob Weir robw...@apache.org wrote: On Sun, Jun 16, 2013 at 5:38 PM, Kay Schenk kay.sch...@gmail.com wrote: On Fri, Jun 14, 2013 at 4:11 PM, Kay Schenk kay.sch...@gmail.com wrote: On Fri, Jun 14, 2013 at 10:31 AM, Rob Weir robw...@apache.org wrote: On Fri, Jun 14, 2013 at 12:14 PM, Kay Schenk kay.sch...@gmail.com wrote: . . . Levels in which we might do things: Level 1 -- Do nothing but watch for abuses. If someone wants to sell a CD, then they are free to do it, per the license. They can advertise on eBay, their website, etc., but they have no permission to use the trademarks. Nothing special on our website. Level 2 -- We allow a listing on our website (or wiki) of those who offer CDs. But we make no attempt to verify anything. It is all caveat emptor. We put in disclaimers on the page so users know that we have not vetted anything. Level 3 -- We review requests for listing and approve them only if they meet our qualifications, which might include proper use of trademarks, a link back to our website, etc. This is similar to what we did with consultants. Level 4 -- Like Level 3, but for those distributors who meet our qualifications we offer a special logo they can use, something like a Community Distributor. . . . It seems there is at least some consensus of moving ahead with a CD vendor page similar to the consultants page: http://www.openoffice.org/bizdev/consultants.html so, Rob, if you feel inclined to work on #1 and #2 from your suggestions above, please feel free to draft up something for us to review. Then move on to #3? We might be able to jump directly to #3. We don't need to do #1 or #2 first. I've started to draft the Distributor Best Practices page here: http://www.openoffice.org/distribution/best-practices.html ok, this looks pretty good... I think in the end we need three pages: 1) The main page, which is the listings page. 2) The Distributor Best Practices page 3) An instructions page for would-be distributors, of how to get listed. It might grow over time to include links to ISO's, CD labels, etc., in the future. These pages would be cross-linked. So, we don't have to un-reroute what we've already done with the old distribution area, I'm inclined to put this new CD page(s) in bizdev also. I'm hoping we can just implement this with xml and xslt. I'll do some testing in a day or so. That could be done now or later on. It is OK to start with a static HTML page (not MDText) and prototype the design and even go live with it, and then add the XSLT automation to generate it later. Depending on the number of listings automation might not be needed. Do you want to mock up a distributor listings page? Yes, I can do this over the next day or so I think. I just do up a static HTML as you suggest. Maybe like the old listing but without the region info -- to start. I started looking at some XML, and XSL just now, and well, not sure how this could be handled with the CMS vis a vis standard page headers etc. We could probaly define a new page type. For now, static HTML it is. OK, start here (revision of /distribution/index.html) http://www.openoffice.org/distribution/index_new.html This is a good start. I wonder if the main page (index.html) should the end-user facing page, e.g., the distributor listings? And then have the FAQ be in distributor-faqs.html or something like that? This might be a good idea. The main facing page IS a bit preachy I guess. The legacy Distribution project's main index page was more like a combination of the FAQ and best practices with links to CDs, etc. But if we're only going to be dealing with CDs, no reason to keep that organization, and it would probably be more friendly for users. (I have an archive of the old /distribution/index.html). Not a big deal, just an idea. Do we know what existing incoming links from 3rd party websites point to? I can't answer this one. I did some research and found: http://www.openoffice.org/distribution/ (1183 links from 76 domains) http://www.openoffice.org/distribution/cdrom/sellers.html (273 links from 78 domains) http://www.openoffice.org/distribution/cdrom/ (3728 links from 242 domains) (or even OO websites?) Because distribution used to be a separate project, there are many links to distribution.openoffice.org and a fair number JUST the cdrom area. Whatever URL was used for the distributor list before should probably stay as the listing page. That way the existing links will still be accurate.
Re: [RELEASE]: proposal for an update of the AOO 4.0 release schedule
Hello list, - Wednesday June 19th, update Pootle with sidebar help and provide Po files for all current languages available on Pootle. Is it possible to build AOO 4 with french language? Merci beaucoup - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wrong OS detection on download page
On Wed, Jun 19, 2013 at 1:58 PM, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 06/19/2013 12:46 AM, schrieb Kay Schenk: On Tue, Jun 18, 2013 at 3:39 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 06/18/2013 11:53 PM, schrieb Rob Weir: On Tue, Jun 18, 2013 at 4:45 PM, Marcus (OOo)marcus.m...@wtnet.de wrote: Thanks for the data. Here you can see for yourself that nothing points to Ubuntu or at least to a Debian based Linux distro. Unfortunatelly there is no way to make a correct download suggestion. So, I don't know how to fix this problem. Does it indicate RPMs? Or is it just ambiguous? If we are unable to No indication. If there is no clear point to recognize the package system then RPM is the default. decide maybe just give a link to another page that explains what version is appropriate for what distro? That would prevent the user from getting confused and downloading the wrong package. OK, instead of building a download link the script could offer the URL to the other.html webpage. A task for tomorrow. Marcus I think this is what's been done in the past and would probably work well now. AFAIR there was no redirection to the other.html webpage. We have a redirection for whole languages to their native lang webpages when some are not available. But not for single install files. Truthfully, I haven't investigated all the details of the changes of late . I thought other.html was a fall-thru at one time if no language, or none of our supported OSes, or other odd mismatches occurred. It seems it was handled by the JS on the main download page via hasMirrorLinK. Anyway, I can try to build this up in the test area. With the new release schedule there is now a bit more time. ;-) That would be super! The scripting is really outstanding now but it's nearly impossible to account for every conceivable detail when there are only so many ways to gather information. Thanks for all your work! Marcus Am 06/14/2013 09:54 PM, schrieb Hagar Delest: Le 14/06/2013 17:58, Kay Schenk a écrit : On Fri, Jun 14, 2013 at 6:07 AM, Hagar Delest hagar.del...@laposte.netwrote: I was checking the download process for MD5checksum verification and I noticed that the download page proposes a 64bit RPM file whereas my system is Ubuntu and should give a 64bit DEB. Hence when clicking the MD5checksum link, the wrong version is given. This should be fixed asap if we want users be able to check their download. Hagar Please try: http://www.openoffice.org/download/test/analyze.htmlhttp://www.openoffice.org/**download/test/analyze.html htt**p://www.openoffice.org/**download/test/analyze.htmlhttp://www.openoffice.org/download/test/analyze.html so we can see more about your system. Thanks. Here it is: Variables from the browser Values navigator.appCodeName Mozilla navigator.appName Netscape navigator.appVersion 5.0 (X11) navigator.platform Linux x86_64 navigator.oscpu Linux x86_64 navigator.product Gecko navigator.productSub 20100101 navigator.vendor navigator.vendorSub navigator.language fr navigator.browserLanguage undefined navigator.userLanguage undefined navigator.systemLanguage undefined navigator.userAgent Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 JavaScript functions and variables Values Native language name Français ISO code fr Language array data fr,French,Français,y,http://** www.openoffice.org/fr/http://**www.openoffice.org/fr/http://www.openoffice.org/fr/ Native platform name Linux 64-bit (RPM) Mirror platform name Linux_x86-64_install-rpm Native file name Apache_OpenOffice_4.0.0_Linux_x86-64_install-rpm_fr.tar.gz Native file extension .tar.gz Return value of getLink() http://people.apache.org/~marcus/aoo/4.0.0/binaries/fr/http://people.apache.org/~**marcus/aoo/4.0.0/binaries/fr/** Apache_OpenOffice_4.0.0_Linux_x86-64_install-rpm_fr.tar.**gz http://people.apache.org/~**marcus/aoo/4.0.0/binaries/fr/** Apache_OpenOffice_4.0.0_Linux_**x86-64_install-rpm_fr.tar.gzhttp://people.apache.org/~marcus/aoo/4.0.0/binaries/fr/Apache_OpenOffice_4.0.0_Linux_x86-64_install-rpm_fr.tar.gz Checksum file (here for MD5) http://people.apache.org/~marcus/aoo/4.0.0/binaries/fr/http://people.apache.org/~**marcus/aoo/4.0.0/binaries/fr/** Apache_OpenOffice_4.0.0_Linux_x86-64_install-rpm_fr.tar.** gz.**md5http://people.apache.**org/~marcus/aoo/4.0.0/** binaries/fr/Apache_OpenOffice_**4.0.0_Linux_x86-64_install-** rpm_fr.tar.gz.md5http://people.apache.org/~marcus/aoo/4.0.0/binaries/fr/Apache_OpenOffice_4.0.0_Linux_x86-64_install-rpm_fr.tar.gz.md5 hasMirrorLink() true My system is Xubuntu 13.04 64bit and I use the beta version of FF. Hagar Opinions expressed in this communication reflect the author's individual personal view, not necessarily that of an amorphous collective. The above statements do not reflect an
