4.1.0_release_blocker requested: [Bug 123480] CRASH when delete contents in particular document with active 'Record Changes'
Oliver-Rainer Wittmann o...@apache.org has asked for 4.1.0_release_blocker: Bug 123480: CRASH when delete contents in particular document with active 'Record Changes' https://issues.apache.org/ooo/show_bug.cgi?id=123480 --- Additional Comments from Oliver-Rainer Wittmann o...@apache.org My observation is the following on recent developer snapshot (rev. 1566593): - Undo does not work, but no freeze. - A further Redo followed by an Undo causes a freeze -- reopening issue to correct the Undo. -- requesting show-stopper status as a fix is needed - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1.0_release_blocker granted: [Bug 123480] CRASH when delete contents in particular document with active 'Record Changes'
j...@apache.org has granted Oliver-Rainer Wittmann o...@apache.org's request for 4.1.0_release_blocker: Bug 123480: CRASH when delete contents in particular document with active 'Record Changes' https://issues.apache.org/ooo/show_bug.cgi?id=123480 --- Additional Comments from j...@apache.org grant showstopper flag - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Does it make sense to raise a showstopper for MacOSX ?
Hi Jürgen, thank you for your information! Will therefore keep on waiting and hoping that sometimes in the (hopefully near!) future this problem can be researched and tackled. [Maybe Java-oxt's are dispatched by default on a different thread (separate JVM instance?) than the built-in AOO Java classes on MacOSX? Maybe a Java class loader issue only present on MacOSX? Maybe ... of course pure speculations, which may lead to nowhere...] ---rony On 26.02.2014 15:38, Jürgen Schmidt wrote: Hi Ronny, the problem is not new as far as I know and not easy to fix. Both the office and the JVM requires to run their event loop in the main thread and this conflicts on MacOS. A solution can be potentially to start the JVM in a separate process and bridge the communication via UNO. But I don't see the chance that it get fixed for AOO 4.1 or in the near future. Any usage of awt in macros or extensions on Mac will cause problems and is not recommended. And again this problem is not new and exists since some time. It is correct that it worked in the past and I don't know when the problem was introduced and which change triggered it. But I know that exists since several years and is not easy to fix. Juergen On 2/26/14 3:12 PM, Rony G. Flatscher (Apache) wrote: Hi there, it seems that dispatching scripts via AOO's Java scripting framework is done using the wrong thread on MacOSX. This reasoning stems from observing the Java runtime error to be caused e.g. when using a JDialog to popup reporting the following error: com.sun.star.uno.RuntimeException[jni_uno_bridge_error] UNO calling Java method invoke: non-UNO exception occurred: java.lang.InternalError: Can't start the AWT because Java was started on the first thread. Make sure StartOnFirstThread is not specified in your application's info.plist or on the command line This problem is also present in Herbert's latest drop. This effectively inhibits dispatching any scripts from within AOO on MacOSX, which works fine on Windows and Linux otherwise (in 32- and the latter in addition in 64-bit). As the code for making ooRexx available was copied from the BeanShell's Java scripting framework implementation and works on all other platforms flawlessly, this seems to be a serious error on MacOSX, and therefore a showstopper, IMHO. [The code gets dispatched by AOO and on its supplied thread.] However and interestingly, there seems to be no problem with BeanShell and JavaScript, which is surprising to me. Not sure why they execute properly on MacOSX, but that observation is also the reason why I prefer to ask first, before setting the showstopper flag on bug 124170 (see below). There are two bug issues that document this problem: * Bug https://issues.apache.org/ooo/show_bug.cgi?id=124170, Comment # 9: explains where to find the (basically a pure Java-) oxt (a debug version using JDialog) and how to get the Java error on MacOSX. * Bug https://issues.apache.org/ooo/show_bug.cgi?id=120359 is probably related to the same reason (in the part describing problems dispatching scripts and some sort of work around that more or less worked on the prior 32-bit version). --- It might be interesting to note, that in OpenOffice.org times (32-bit OOo) it used to work on MacOSX. I am not aware of any changes in the scripting framework that could cause this behaviour. ---rony - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1.0_release_blocker requested: [Bug 46480] Backup before saving new version overwrites wrong backup file
Edwin Sharp el...@apache.org has asked for 4.1.0_release_blocker: Bug 46480: Backup before saving new version overwrites wrong backup file https://issues.apache.org/ooo/show_bug.cgi?id=46480 --- Additional Comments from Edwin Sharp el...@apache.org As given in description. AOO410m1(Build:9750) - Rev. 1569541 Rev.1569541 Win 7 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1.0_release_blocker granted: [Bug 15508] Break link converts bmp, jpg, png and gif to png format
j...@apache.org has granted Armin Le Grand armin.le.gr...@me.com's request for 4.1.0_release_blocker: Bug 15508: Break link converts bmp, jpg, png and gif to png format https://issues.apache.org/ooo/show_bug.cgi?id=15508 --- Additional Comments from j...@apache.org grant showstopper flag - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1.0_release_blocker requested: [Bug 124233] Different text rendering (word/character width) depending on zoom factor
h...@apache.org h...@apache.org has asked for 4.1.0_release_blocker: Bug 124233: Different text rendering (word/character width) depending on zoom factor https://issues.apache.org/ooo/show_bug.cgi?id=124233 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: How could I linked the dependencies of soffice.bin?
Understood. Thanks for your info.
4.1.0_release_blocker granted: [Bug 124233] Different text rendering (word/character width) depending on zoom factor
j...@apache.org has granted h...@apache.org h...@apache.org's request for 4.1.0_release_blocker: Bug 124233: Different text rendering (word/character width) depending on zoom factor https://issues.apache.org/ooo/show_bug.cgi?id=124233 --- Additional Comments from j...@apache.org grant showstopper flag not usable otherwise - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[RELEASE]: refined AOO 4.1 beta schedule
Hi, we are still verifying some fixes to identify the Beta as real beta, means some branding elements, names etc. And we are working on some serious bugfixes that we have identified already. The current plan is to start the build tomorrow and do the upload over the weekend. That means we should have a RC for AOO 4.1 beta available at the beginning of next. The new icons are still not complete and I am not sure how we can or should continue here. Replacing them for the final release is probably not a good idea. Work remaining before beta 1) Defect verification 2) Release Notes check, update and finalize the release notes [1] 3) Communications Clarify the communication/promotion for the beta. For example how many users do we want to reach with the beta. 4) Release vote Based on this a possible schedule can be March 4th: availability of AOO 41. Beta RC + start vote March 10th: public availability of AOO 41. Beta (until March 31th) ...: additional snapshot builds based on the beta including showstopper fixes April 2th: availability of AOO 4.1 RC April 7th: public availability of AOO 4.1 Any opinions or feedback Juergen [1] https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: refined AOO 4.1 beta schedule
Is it too late for update Serbian language? Wlada 2014-02-27 16:50 GMT+01:00 Jürgen Schmidt jogischm...@gmail.com: Hi, we are still verifying some fixes to identify the Beta as real beta, means some branding elements, names etc. And we are working on some serious bugfixes that we have identified already. The current plan is to start the build tomorrow and do the upload over the weekend. That means we should have a RC for AOO 4.1 beta available at the beginning of next. The new icons are still not complete and I am not sure how we can or should continue here. Replacing them for the final release is probably not a good idea. Work remaining before beta 1) Defect verification 2) Release Notes check, update and finalize the release notes [1] 3) Communications Clarify the communication/promotion for the beta. For example how many users do we want to reach with the beta. 4) Release vote Based on this a possible schedule can be March 4th: availability of AOO 41. Beta RC + start vote March 10th: public availability of AOO 41. Beta (until March 31th) ...: additional snapshot builds based on the beta including showstopper fixes April 2th: availability of AOO 4.1 RC April 7th: public availability of AOO 4.1 Any opinions or feedback Juergen [1] https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: refined AOO 4.1 beta schedule
On 2/27/14 4:58 PM, Vladislav Stevanovic wrote: Is it too late for update Serbian language? I have merged the latest translation updates including sr on Monday. The last changes for sr were from Feb. 21th. We should be save here :-) But we can discuss a selective update on demand during the beta phase and for the final release. Especially for the 6 languages where only 2000-5800 words are missing to complete the UI translation. Juergen Wlada 2014-02-27 16:50 GMT+01:00 Jürgen Schmidt jogischm...@gmail.com: Hi, we are still verifying some fixes to identify the Beta as real beta, means some branding elements, names etc. And we are working on some serious bugfixes that we have identified already. The current plan is to start the build tomorrow and do the upload over the weekend. That means we should have a RC for AOO 4.1 beta available at the beginning of next. The new icons are still not complete and I am not sure how we can or should continue here. Replacing them for the final release is probably not a good idea. Work remaining before beta 1) Defect verification 2) Release Notes check, update and finalize the release notes [1] 3) Communications Clarify the communication/promotion for the beta. For example how many users do we want to reach with the beta. 4) Release vote Based on this a possible schedule can be March 4th: availability of AOO 41. Beta RC + start vote March 10th: public availability of AOO 41. Beta (until March 31th) ...: additional snapshot builds based on the beta including showstopper fixes April 2th: availability of AOO 4.1 RC April 7th: public availability of AOO 4.1 Any opinions or feedback Juergen [1] https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes - 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: [RELEASE]: refined AOO 4.1 beta schedule
On 27 February 2014 16:58, Vladislav Stevanovic stevanovicvladis...@gmail.com wrote: Is it too late for update Serbian language? Wlada 2014-02-27 16:50 GMT+01:00 Jürgen Schmidt jogischm...@gmail.com: Hi, we are still verifying some fixes to identify the Beta as real beta, means some branding elements, names etc. And we are working on some serious bugfixes that we have identified already. The current plan is to start the build tomorrow and do the upload over the weekend. That means we should have a RC for AOO 4.1 beta available at the beginning of next. The new icons are still not complete and I am not sure how we can or should continue here. Replacing them for the final release is probably not a good idea. Work remaining before beta 1) Defect verification 2) Release Notes check, update and finalize the release notes [1] 3) Communications Clarify the communication/promotion for the beta. For example how many users do we want to reach with the beta. 4) Release vote Based on this a possible schedule can be March 4th: availability of AOO 41. Beta RC + start vote just for my understanding, dont we need to vote on the beta as well as the release. We send the beta out to general public, that would normally require a vote (might be a fast one). rgds jan I. March 10th: public availability of AOO 41. Beta (until March 31th) ...: additional snapshot builds based on the beta including showstopper fixes April 2th: availability of AOO 4.1 RC April 7th: public availability of AOO 4.1 Any opinions or feedback Juergen [1] https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Ask OpenOffice #2 Top Questions: Now for the answers....
Time to wrap this up. I've gone through the 275 questions from 430 users and picked out the top ones. I dropped the ones that repeated questions we already answered in our last iteration of this. I also combined questions where there were duplicates or repetitions. In some cases I reworded questions for clarity. Here's the top 10, with some partial responses on a few of them. I'll need your help to craft responses for all of them. --- 1) How can it be Microsoft is a platinum sponsor of Apache when OpenOffice is competing with MS Office? Rob: This is an odd question to ask us, but I suppose we can explain how the ASF is a foundation that supports many (100+) open source projects and that a sponsor of AOO does not necessarily participate or endorse every project at Apache. But again, this is an odd question for us. Maybe we can pass it off to Ross Gardler for a better answer? --- 2) A series of questions on proposed features and how we decide on new features, including: a) Is it possible to include a 'Track Change' feature in OpenOffice like the one in MS Word? b) When will OpenOffice be able to support saving in (.doc) for Microsoft Word 2012-2014? c) Does Open Office plan to add capability to print out marginal comments/notes on the document page where they appear instead of as a separate list at the end of the document? d) Will OpenOffice users be able to import a PDF file, update it, and export the updated file? e) How does you decide what features to put into OpenOffice? f) What is the average time it takes you to fix a bug? add a new feature? Rob: I thought we'd lump these all together and give an in-depth response about how features and bug fixes are prioritized in a volunteer-led open source project at Apache. --- 3) What are the long term support and development plans for OpenOffice? Rob: This is an opportunity for us to state our practice of supporting version N and N-1 and point to the consultants page where users can find those who can offer longer term support. --- 4) What are some of the most interesting features in OpenOffice that most users don't know even exist? Rob: It seems most users don't know how to use word competition ;-) But maybe we can nominate 4 or 5 hidden features or underused features that users might not know about? --- 5) What's being done to help realise the universal OpenDocument dream? Rob: We have some material here from our Document Freedom Day blog post, talking about project members who are also active in the OASIS ODF TC and the standardization effort. --- 6) Are there backdoors or spyware in Apache OpenOffice? Rob: Like we'd tell you if there were? ;-)But seriously, this could be a topic of a standalone blog post, and maybe we should do that. We could discuss open source security, how we handle vulnerability reports and the advantage of open source transparency for preventing back doors. --- 7) How many volunteers work on OpenOffice? Rob: We can discuss the various kinds of volunteers in different areas and get some stats. --- 8) Does it cost anything to upload a template online? Rob: No. Odd that this questions got so many votes. Any ideas on why this is a question? --- 9) What is being done to have openoffice return to be the default suite in linux distributions? Rob: Anyone have an answer for this one? --- 10) How can a new volunteer contribute to the OpenOffice project? Rob: Can point them to our get involved page. --- - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: refined AOO 4.1 beta schedule
On Thu, Feb 27, 2014 at 8:11 AM, jan i j...@apache.org wrote: On 27 February 2014 16:58, Vladislav Stevanovic stevanovicvladis...@gmail.com wrote: Is it too late for update Serbian language? Wlada 2014-02-27 16:50 GMT+01:00 Jürgen Schmidt jogischm...@gmail.com: Hi, we are still verifying some fixes to identify the Beta as real beta, means some branding elements, names etc. And we are working on some serious bugfixes that we have identified already. The current plan is to start the build tomorrow and do the upload over the weekend. That means we should have a RC for AOO 4.1 beta available at the beginning of next. The new icons are still not complete and I am not sure how we can or should continue here. Replacing them for the final release is probably not a good idea. Work remaining before beta 1) Defect verification 2) Release Notes check, update and finalize the release notes [1] 3) Communications Clarify the communication/promotion for the beta. For example how many users do we want to reach with the beta. 4) Release vote Based on this a possible schedule can be March 4th: availability of AOO 41. Beta RC + start vote just for my understanding, dont we need to vote on the beta as well as the release. We send the beta out to general public, that would normally require a vote (might be a fast one). rgds jan I. I think this is covered on actually, hopefully, releasing the beta on the 10th. In the past we've required a min of 72 hours for a vote, so this would be cutting things a bit close I guess...but not by much from previous scenarios. March 10th: public availability of AOO 41. Beta (until March 31th) ...: additional snapshot builds based on the beta including showstopper fixes April 2th: availability of AOO 4.1 RC The RC requires an additional vote, right? April 7th: public availability of AOO 4.1 Any opinions or feedback Juergen [1] https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- - MzK Cats do not have to be shown how to have a good time, for they are unfailing ingenious in that respect. -- James Mason
Re: [RELEASE]: refined AOO 4.1 beta schedule
Hi at all Zitat von jan i j...@apache.org: On 27 February 2014 16:58, Vladislav Stevanovic stevanovicvladis...@gmail.com wrote: Is it too late for update Serbian language? Wlada 2014-02-27 16:50 GMT+01:00 Jürgen Schmidt jogischm...@gmail.com: Hi, we are still verifying some fixes to identify the Beta as real beta, means some branding elements, names etc. And we are working on some serious bugfixes that we have identified already. The current plan is to start the build tomorrow and do the upload over the weekend. That means we should have a RC for AOO 4.1 beta available at the beginning of next. The new icons are still not complete and I am not sure how we can or should continue here. Replacing them for the final release is probably not a good idea. Work remaining before beta 1) Defect verification 2) Release Notes check, update and finalize the release notes [1] 3) Communications Clarify the communication/promotion for the beta. For example how many users do we want to reach with the beta. 4) Release vote Based on this a possible schedule can be March 4th: availability of AOO 41. Beta RC + start vote just for my understanding, dont we need to vote on the beta as well as the release. We send the beta out to general public, that would normally require a vote (might be a fast one). I wouldn't make a beta as a RC. After a Beta you have normaly several showstopers to fix. I recall, RC = Release Candidate wich means, that we assume the build is ready for release. Beta... wait two or tree weeks fix showstoppers, and then a RC. And the important tests are not the one in the RC, the important tests are at the build befor RC. Else we make the same mess as in the 4.0.0. Greetings Raphael rgds jan I. March 10th: public availability of AOO 41. Beta (until March 31th) ...: additional snapshot builds based on the beta including showstopper fixes April 2th: availability of AOO 4.1 RC April 7th: public availability of AOO 4.1 Any opinions or feedback Juergen [1] https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes - 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: [RELEASE]: refined AOO 4.1 beta schedule
On Thu, Feb 27, 2014 at 3:31 PM, i...@raphaelbircher.ch wrote: Hi at all Zitat von jan i j...@apache.org: On 27 February 2014 16:58, Vladislav Stevanovic stevanovicvladis...@gmail.com wrote: Is it too late for update Serbian language? Wlada 2014-02-27 16:50 GMT+01:00 Jürgen Schmidt jogischm...@gmail.com: Hi, we are still verifying some fixes to identify the Beta as real beta, means some branding elements, names etc. And we are working on some serious bugfixes that we have identified already. The current plan is to start the build tomorrow and do the upload over the weekend. That means we should have a RC for AOO 4.1 beta available at the beginning of next. The new icons are still not complete and I am not sure how we can or should continue here. Replacing them for the final release is probably not a good idea. Work remaining before beta 1) Defect verification 2) Release Notes check, update and finalize the release notes [1] 3) Communications Clarify the communication/promotion for the beta. For example how many users do we want to reach with the beta. 4) Release vote Based on this a possible schedule can be March 4th: availability of AOO 41. Beta RC + start vote just for my understanding, dont we need to vote on the beta as well as the release. We send the beta out to general public, that would normally require a vote (might be a fast one). I wouldn't make a beta as a RC. After a Beta you have normaly several showstopers to fix. I recall, RC = Release Candidate wich means, that we assume the build is ready for release. Beta... wait two or tree weeks fix showstoppers, and then a RC. And the important tests are not the one in the RC, the important tests are at the build befor RC. Else we make the same mess as in the 4.0.0. It is an Release Candidate because a beta is a Release. When we vote on the RC we agree it is ready for release as a beta. After that we'll fix more bugs and have another RC and vote for that to be released as 4.1. I think the confusion is that we use the word release into two ways: 1) The Apache definition of a release == something that a PMC votes on and approves for publication and public consumption 2) Release as the final version of a product cycle One way to avoid confusion is to use GA for the 2nd meaning (GA= General Availability). If we do that then it is clear: 1) We have a RC for the Beta and then we release the beta 2) Some weeks later, after fixing more bugs we have an RC for the GA and then we release the GA Regards, -Rob Greetings Raphael rgds jan I. March 10th: public availability of AOO 41. Beta (until March 31th) ...: additional snapshot builds based on the beta including showstopper fixes April 2th: availability of AOO 4.1 RC April 7th: public availability of AOO 4.1 Any opinions or feedback Juergen [1] https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes - 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 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: So-called Reporting a problem with the OpenOffice website
Am 02/27/2014 12:46 AM, schrieb Kay Schenk: On 02/09/2014 04:32 AM, Marcus (OOo) wrote: Am 02/09/2014 12:44 PM, schrieb Hagar Delest: Le 09/02/2014 11:42, Marcus (OOo) a écrit : I think we should guide them to the right one. The question is now: What is the best entry channel for website problems? ;-) I think that basic users will click on whatever looks like a way that will get them an answer. So the question is rather how to direct them to the best list and let the users wanting to report a problem with the site dig a bit more. I think that there are much more basic users needing a redirect to the user ML than real troubles with the site. I see we are on the same side. Marcus Well, as it had been a while since we last had any further discussion on this, I took the liberty of incorporating the changes we'd already discussed and agreed upon. The Contact us is a bit longer now, but hopefully it will be more clear to users what's the best thing to do. Thanks for taking over. It seems I've missed my own deadline. ;-( Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: refined AOO 4.1 beta schedule
Am 02/27/2014 09:31 PM, schrieb i...@raphaelbircher.ch: Hi at all Zitat von jan i j...@apache.org: On 27 February 2014 16:58, Vladislav Stevanovic stevanovicvladis...@gmail.com wrote: Is it too late for update Serbian language? Wlada 2014-02-27 16:50 GMT+01:00 Jürgen Schmidt jogischm...@gmail.com: Hi, we are still verifying some fixes to identify the Beta as real beta, means some branding elements, names etc. And we are working on some serious bugfixes that we have identified already. The current plan is to start the build tomorrow and do the upload over the weekend. That means we should have a RC for AOO 4.1 beta available at the beginning of next. The new icons are still not complete and I am not sure how we can or should continue here. Replacing them for the final release is probably not a good idea. Work remaining before beta 1) Defect verification 2) Release Notes check, update and finalize the release notes [1] 3) Communications Clarify the communication/promotion for the beta. For example how many users do we want to reach with the beta. 4) Release vote Based on this a possible schedule can be March 4th: availability of AOO 41. Beta RC + start vote just for my understanding, dont we need to vote on the beta as well as the release. We send the beta out to general public, that would normally require a vote (might be a fast one). I wouldn't make a beta as a RC. After a Beta you have normaly several showstopers to fix. I recall, RC = Release Candidate wich means, that we assume the build is ready for release. Beta... wait two or tree weeks fix showstoppers, and then a RC. And the important tests are not the one in the RC, the important tests are at the build befor RC. Else we make the same mess as in the 4.0.0. RC means (at least for me) that you are done with that what you planned for the coming release. At the moment we can nearly ready for the Beta Release. So making a RC to get it out. Later in the calendar we do another RC when we think 4.1.0 is ready for public use as final release. You can name different release builds as RC - depending on what you want to archive with them - which is more or less only internally relevant. I think this is what Juergen wanted to express. Marcus March 10th: public availability of AOO 41. Beta (until March 31th) ...: additional snapshot builds based on the beta including showstopper fixes April 2th: availability of AOO 4.1 RC April 7th: public availability of AOO 4.1 Any opinions or feedback Juergen [1] https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: refined AOO 4.1 beta schedule
On 27 February 2014 21:59, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 02/27/2014 09:31 PM, schrieb i...@raphaelbircher.ch: Hi at all Zitat von jan i j...@apache.org: On 27 February 2014 16:58, Vladislav Stevanovic stevanovicvladis...@gmail.com wrote: Is it too late for update Serbian language? Wlada 2014-02-27 16:50 GMT+01:00 Jürgen Schmidt jogischm...@gmail.com: Hi, we are still verifying some fixes to identify the Beta as real beta, means some branding elements, names etc. And we are working on some serious bugfixes that we have identified already. The current plan is to start the build tomorrow and do the upload over the weekend. That means we should have a RC for AOO 4.1 beta available at the beginning of next. The new icons are still not complete and I am not sure how we can or should continue here. Replacing them for the final release is probably not a good idea. Work remaining before beta 1) Defect verification 2) Release Notes check, update and finalize the release notes [1] 3) Communications Clarify the communication/promotion for the beta. For example how many users do we want to reach with the beta. 4) Release vote Based on this a possible schedule can be March 4th: availability of AOO 41. Beta RC + start vote just for my understanding, dont we need to vote on the beta as well as the release. We send the beta out to general public, that would normally require a vote (might be a fast one). I wouldn't make a beta as a RC. After a Beta you have normaly several showstopers to fix. I recall, RC = Release Candidate wich means, that we assume the build is ready for release. Beta... wait two or tree weeks fix showstoppers, and then a RC. And the important tests are not the one in the RC, the important tests are at the build befor RC. Else we make the same mess as in the 4.0.0. RC means (at least for me) that you are done with that what you planned for the coming release. At the moment we can nearly ready for the Beta Release. So making a RC to get it out. Later in the calendar we do another RC when we think 4.1.0 is ready for public use as final release. You can name different release builds as RC - depending on what you want to archive with them - which is more or less only internally relevant. I think this is what Juergen wanted to express. the names are less important to me than the votes. Juergens schedule suggested only 1 vote, but it seems I am not the only one who expect (at least) 2 votes (one for Beta and one for GA). I agree with Rob, that the word release is confusing, and the term GA more precise for our purpose. rgds jan I. Marcus March 10th: public availability of AOO 41. Beta (until March 31th) ...: additional snapshot builds based on the beta including showstopper fixes April 2th: availability of AOO 4.1 RC April 7th: public availability of AOO 4.1 Any opinions or feedback Juergen [1] https://cwiki.apache.org/confluence/display/OOOUSERS/ AOO+4.1+Release+Notes - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: refined AOO 4.1 beta schedule
Am 02/27/2014 04:50 PM, schrieb Jürgen Schmidt: Hi, we are still verifying some fixes to identify the Beta as real beta, means some branding elements, names etc. And we are working on some serious bugfixes that we have identified already. The current plan is to start the build tomorrow and do the upload over the weekend. That means we should have a RC for AOO 4.1 beta available at the beginning of next. The new icons are still not complete and I am not sure how we can or should continue here. Replacing them for the final release is probably not a good idea. Work remaining before beta 1) Defect verification 2) Release Notes check, update and finalize the release notes [1] 3) Communications Clarify the communication/promotion for the beta. For example how many users do we want to reach with the beta. 4) Release vote Based on this a possible schedule can be March 4th: availability of AOO 41. Beta RC + start vote March 10th: public availability of AOO 41. Beta (until March 31th) ...: additional snapshot builds based on the beta including showstopper fixes April 2th: availability of AOO 4.1 RC April 7th: public availability of AOO 4.1 Any opinions or feedback I'll try to make one day off to be available on March 10th the whole day, so we can be flexible with announcements and publications. Marcus [1] https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: refined AOO 4.1 beta schedule
Am 02/27/2014 10:05 PM, schrieb jan i: On 27 February 2014 21:59, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 02/27/2014 09:31 PM, schrieb i...@raphaelbircher.ch: Hi at all Zitat von jan ij...@apache.org: On 27 February 2014 16:58, Vladislav Stevanovic stevanovicvladis...@gmail.com wrote: Is it too late for update Serbian language? Wlada 2014-02-27 16:50 GMT+01:00 Jürgen Schmidtjogischm...@gmail.com: Hi, we are still verifying some fixes to identify the Beta as real beta, means some branding elements, names etc. And we are working on some serious bugfixes that we have identified already. The current plan is to start the build tomorrow and do the upload over the weekend. That means we should have a RC for AOO 4.1 beta available at the beginning of next. The new icons are still not complete and I am not sure how we can or should continue here. Replacing them for the final release is probably not a good idea. Work remaining before beta 1) Defect verification 2) Release Notes check, update and finalize the release notes [1] 3) Communications Clarify the communication/promotion for the beta. For example how many users do we want to reach with the beta. 4) Release vote Based on this a possible schedule can be March 4th: availability of AOO 41. Beta RC + start vote just for my understanding, dont we need to vote on the beta as well as the release. We send the beta out to general public, that would normally require a vote (might be a fast one). I wouldn't make a beta as a RC. After a Beta you have normaly several showstopers to fix. I recall, RC = Release Candidate wich means, that we assume the build is ready for release. Beta... wait two or tree weeks fix showstoppers, and then a RC. And the important tests are not the one in the RC, the important tests are at the build befor RC. Else we make the same mess as in the 4.0.0. RC means (at least for me) that you are done with that what you planned for the coming release. At the moment we can nearly ready for the Beta Release. So making a RC to get it out. Later in the calendar we do another RC when we think 4.1.0 is ready for public use as final release. You can name different release builds as RC - depending on what you want to archive with them - which is more or less only internally relevant. I think this is what Juergen wanted to express. the names are less important to me than the votes. Juergens schedule suggested only 1 vote, but it seems I am not the only one who expect (at least) 2 votes (one for Beta and one for GA). I agree with Rob, that the word release is confusing, and the term GA more precise for our purpose. sure, this is also a solution. Maybe indeed the better one. ;-) Marcus March 10th: public availability of AOO 41. Beta (until March 31th) ...: additional snapshot builds based on the beta including showstopper fixes April 2th: availability of AOO 4.1 RC April 7th: public availability of AOO 4.1 Any opinions or feedback Juergen [1] https://cwiki.apache.org/confluence/display/OOOUSERS/ AOO+4.1+Release+Notes - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Ask OpenOffice #2 Top Questions: Now for the answers....
On 02/27/2014 10:02 AM, Rob Weir wrote: Time to wrap this up. I've gone through the 275 questions from 430 users and picked out the top ones. I dropped the ones that repeated questions we already answered in our last iteration of this. I also combined questions where there were duplicates or repetitions. In some cases I reworded questions for clarity. Here's the top 10, with some partial responses on a few of them. I'll need your help to craft responses for all of them. --- 1) How can it be Microsoft is a platinum sponsor of Apache when OpenOffice is competing with MS Office? Rob: This is an odd question to ask us, but I suppose we can explain how the ASF is a foundation that supports many (100+) open source projects and that a sponsor of AOO does not necessarily participate or endorse every project at Apache. But again, this is an odd question for us. Maybe we can pass it off to Ross Gardler for a better answer? --- 2) A series of questions on proposed features and how we decide on new features, including: a) Is it possible to include a 'Track Change' feature in OpenOffice like the one in MS Word? b) When will OpenOffice be able to support saving in (.doc) for Microsoft Word 2012-2014? c) Does Open Office plan to add capability to print out marginal comments/notes on the document page where they appear instead of as a separate list at the end of the document? d) Will OpenOffice users be able to import a PDF file, update it, and export the updated file? e) How does you decide what features to put into OpenOffice? f) What is the average time it takes you to fix a bug? add a new feature? Rob: I thought we'd lump these all together and give an in-depth response about how features and bug fixes are prioritized in a volunteer-led open source project at Apache. The PDF question seems like a much larger animal than some of the others to me. Probably on par with b) -- on a larger scale maybe. It may need a larger/longer explanation on its own. --- 3) What are the long term support and development plans for OpenOffice? Rob: This is an opportunity for us to state our practice of supporting version N and N-1 and point to the consultants page where users can find those who can offer longer term support. --- 4) What are some of the most interesting features in OpenOffice that most users don't know even exist? Rob: It seems most users don't know how to use word competition ;-) But maybe we can nominate 4 or 5 hidden features or underused features that users might not know about? --- 5) What's being done to help realise the universal OpenDocument dream? Rob: We have some material here from our Document Freedom Day blog post, talking about project members who are also active in the OASIS ODF TC and the standardization effort. --- 6) Are there backdoors or spyware in Apache OpenOffice? Rob: Like we'd tell you if there were? ;-)But seriously, this could be a topic of a standalone blog post, and maybe we should do that. We could discuss open source security, how we handle vulnerability reports and the advantage of open source transparency for preventing back doors. --- 7) How many volunteers work on OpenOffice? Rob: We can discuss the various kinds of volunteers in different areas and get some stats. --- 8) Does it cost anything to upload a template online? Rob: No. Odd that this questions got so many votes. Any ideas on why this is a question? --- 9) What is being done to have openoffice return to be the default suite in linux distributions? Rob: Anyone have an answer for this one? --- 10) How can a new volunteer contribute to the OpenOffice project? Rob: Can point them to our get involved page. --- - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- - MzK Cats do not have to be shown how to have a good time, for they are unfailing ingenious in that respect. -- James Mason - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: refined AOO 4.1 beta schedule
Hi Rob Zitat von Rob Weir robw...@apache.org: On Thu, Feb 27, 2014 at 3:31 PM, i...@raphaelbircher.ch wrote: Hi at all Zitat von jan i j...@apache.org: On 27 February 2014 16:58, Vladislav Stevanovic stevanovicvladis...@gmail.com wrote: Is it too late for update Serbian language? Wlada 2014-02-27 16:50 GMT+01:00 Jürgen Schmidt jogischm...@gmail.com: just for my understanding, dont we need to vote on the beta as well as the release. We send the beta out to general public, that would normally require a vote (might be a fast one). I wouldn't make a beta as a RC. After a Beta you have normaly several showstopers to fix. I recall, RC = Release Candidate wich means, that we assume the build is ready for release. Beta... wait two or tree weeks fix showstoppers, and then a RC. And the important tests are not the one in the RC, the important tests are at the build befor RC. Else we make the same mess as in the 4.0.0. It is an Release Candidate because a beta is a Release. When we vote on the RC we agree it is ready for release as a beta. After that we'll fix more bugs and have another RC and vote for that to be released as 4.1. I think the confusion is that we use the word release into two ways: 1) The Apache definition of a release == something that a PMC votes on and approves for publication and public consumption 2) Release as the final version of a product cycle One way to avoid confusion is to use GA for the 2nd meaning (GA= General Availability). If we do that then it is clear: 1) We have a RC for the Beta and then we release the beta 2) Some weeks later, after fixing more bugs we have an RC for the GA and then we release the GA Oh yes, I missunderstud Jürgens answare. I forgot that we have to make a RC for the Beta too. Greetings Raphael - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Ask OpenOffice #2 Top Questions: Now for the answers....
On 27.02.2014 15:00, Kay Schenk wrote: --- 2) A series of questions on proposed features and how we decide on new features, including: a) Is it possible to include a 'Track Change' feature in OpenOffice like the one in MS Word? b) When will OpenOffice be able to support saving in (.doc) for Microsoft Word 2012-2014? c) Does Open Office plan to add capability to print out marginal comments/notes on the document page where they appear instead of as a separate list at the end of the document? d) Will OpenOffice users be able to import a PDF file, update it, and export the updated file? e) How does you decide what features to put into OpenOffice? f) What is the average time it takes you to fix a bug? add a new feature? Rob: I thought we'd lump these all together and give an in-depth response about how features and bug fixes are prioritized in a volunteer-led open source project at Apache. The PDF question seems like a much larger animal than some of the others to me. Probably on par with b) -- on a larger scale maybe. It may need a larger/longer explanation on its own. I see two reasons we do not have that 'roundtrip': (1) The PDF exporter needs to work Page-oriented since PDF is. That is the main reason the import was implemented originally for draw format, not for Writer. When importing to Writer, the Page breaks would not be guaranteed. Also the imported text is not 'floating' text in the classical sense of a Writer paragraph - this was AFAIK not possible with the import method chosen. Thus it would not behave well in Writer when you klick somewhere in such a imported document and start writing. (2) There are enough (even free) programs that add 'overlay' to PDF, e.g. for signing documents, so this is not needed to be done by AOO, too. --- - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Proposal] Update Icons for AOO 4.1
I'm tweaking the source SVGs so that the pixels in lines aren't between two pixels and look blurry. Once the SVGs are done its only a few minutes to generate the different output types. I kept waiting to have free uninterrupted block of time to complete the icons in the two months, which never happened. This last week I realized I'm making better progress if I did one icon each night. I'll keep posting updated zips with source SVGs as each finish. Soon I'll have the source svg's done, then we can worry about generating assets. Samer On Tue, Feb 25, 2014 at 2:50 AM, Jürgen Schmidt jogischm...@gmail.comwrote: On 2/25/14 1:58 AM, Kay Schenk wrote: On 02/24/2014 07:32 AM, Jürgen Schmidt wrote: On 2/19/14 4:18 AM, Samer Mansour wrote: Good eye on the green, that was a mistake, correcting now and uploading a new copy shortly. Yeah @2 for their retina display basically twice the physical pixels per inch (not sure if that statement is true, but its how we figure out the icons.) I know we need windows format, we still have time before the release, Jurgen or if someone else knows what formats and sizes we need that would be a great help. I will check the needed formats asap but important is that you provide the svg's that others can help as well. As always it is not easy to identify how the process work and where the images are stored and where to used ... We have some in default_images and used in probably in the start center and ??? Then we have icons in sysui as *.ico and *.icns Means there is still some work to do but I would like to try to include them for AOO 4.1. Can you share the svg files asap? Juergen Juergen -- It looks like there are svg items included in the zip files -- https://cwiki.apache.org/confluence/pages/viewpageattachments.action?pageId=34834886 I don't know right at the moment if this is all we need. I have seen this but the file type icons are not complete, only impress and math are available. Juergen Samer On Tue, Feb 18, 2014 at 2:56 AM, Andre Fischer awf@gmail.com wrote: On 18.02.2014 04:36, Samer Mansour wrote: I know for windows 48x48 is used in windows 8 in a lot of defaults. I'm hoping I'm not too late to get the list of all icons sizes/formats needed to finish this before the next release. Anyone know when the next release is? On Mon, Feb 17, 2014 at 10:24 PM, Samer Mansour samer...@gmail.com wrote: cwiki is back up now I've uploaded the application icons in a zip to https://cwiki.apache.org/confluence/display/OOOUSERS/ AOO4.1+-+Desktop+Icons Scroll down to feb 17th, I went with my last design and did the final pixel tweaking so anti-aliasing doesn't blur the pixels in the icons. Its the circle with the gull and the context offset in the lower left corner. Samer, thanks for your work. I have one remark and one (possibly stupid) question: - The PNG icons for Calc have slight transparancy in their background color. As this does not exist in the SVG nor in icons for other applications, I assume this is a mistake. - Maybe I have missed this in a previous mail, but what does the @2 part of some of the icons mean? Is that a Mac thing? Regards, Andre Samer On Mon, Feb 17, 2014 at 12:54 PM, Kay Schenk kay.sch...@gmail.com wrote: On 02/17/2014 08:41 AM, Samer Mansour wrote: Sorry about this situation. I will produce the following pngs for macOS today. The cwiki seems to be down, so I can e-mail you the sources and finished products directly icon_16x16.png icon_16...@2.png (32x32) icon_32x326.png icon_32...@2.png (64x64) icon_128x128.png icon_128x...@2.png (256x256) icon_256x256.png icon_256x...@2.png (512x512) icon_512x512.png icon_512x...@2.png (1024x1024) Can you compile a list of formats we need? ie windows and mac, and what ever else we need. Hi Samer -- Since both wikis are currently down, can you put sources people.apache.org area somewhere so we could get to them? We can do the rendering once we have the .svg files without any problem. I think Jürgen is on vacation this week. Thanks for all your wonderful work on these updates. On Thu, Feb 13, 2014 at 4:15 AM, Jürgen Schmidt jogischm...@gmail.com wrote: On 12/16/13 10:19 AM, Jürgen Schmidt wrote: On 12/13/13 6:37 AM, Samer Mansour wrote: Just so you don't think I died in a fire. I'm just under a lot of pressure at my new workplace and I'm working weekends because we're flying by the edge of our seats at this start up. I just ordered my family gifts online. I'm trying to get my priorities right. I will have this done before the new year. Just need to squeeze it in. Hi Samer, no pressure and your new job should have of course a higher prio. Thanks for keeping
Re: Ask OpenOffice #2 Top Questions: Now for the answers....
Am 02/27/2014 11:00 PM, schrieb Kay Schenk: On 02/27/2014 10:02 AM, Rob Weir wrote: Time to wrap this up. I've gone through the 275 questions from 430 users and picked out the top ones. I dropped the ones that repeated questions we already answered in our last iteration of this. I also combined questions where there were duplicates or repetitions. In some cases I reworded questions for clarity. Here's the top 10, with some partial responses on a few of them. I'll need your help to craft responses for all of them. --- 1) How can it be Microsoft is a platinum sponsor of Apache when OpenOffice is competing with MS Office? Rob: This is an odd question to ask us, but I suppose we can explain how the ASF is a foundation that supports many (100+) open source projects and that a sponsor of AOO does not necessarily participate or endorse every project at Apache. But again, this is an odd question for us. Maybe we can pass it off to Ross Gardler for a better answer? Marcus: Or any other Apache member as I don't see us alone to provide an answer. --- 2) A series of questions on proposed features and how we decide on new features, including: a) Is it possible to include a 'Track Change' feature in OpenOffice like the one in MS Word? Marcus: Looks like the user has not yet found the Changes function in the Edit menu. b) When will OpenOffice be able to support saving in (.doc) for Microsoft Word 2012-2014? Marcus: Depends on how the progress of the OSBA code is going. Maybe Oliver or Juergen can tell more? c) Does Open Office plan to add capability to print out marginal comments/notes on the document page where they appear instead of as a separate list at the end of the document? Marcus: When you define a page as Letter or DIN A4, then comments are shown outside of this as there is still space on the monitor. However, I don't know how to do the same when printing on paper. ;-) d) Will OpenOffice users be able to import a PDF file, update it, and export the updated file? Marcus: First we should discuss if we want this as it would be a big implementation effort. If so we would rise to another full-featured PDF editor, beside Adobe. e) How does you decide what features to put into OpenOffice? f) What is the average time it takes you to fix a bug? add a new feature? Rob: I thought we'd lump these all together and give an in-depth response about how features and bug fixes are prioritized in a volunteer-led open source project at Apache. Marcus: IMHO it doesn't make sense to give 2 numbers. Every bug and feature is different and its fix/implemenation depends on so many factors that knowing just the number is senseless. It would be valid for a specific type of bugs/features. Others can look very similar but needs to be treated totally different in the code. It would be hard to explain to an average user. The PDF question seems like a much larger animal than some of the others to me. Probably on par with b) -- on a larger scale maybe. It may need a larger/longer explanation on its own. Armin has provided an interesting answer in the meantime. --- 3) What are the long term support and development plans for OpenOffice? Rob: This is an opportunity for us to state our practice of supporting version N and N-1 and point to the consultants page where users can find those who can offer longer term support. Marcus: To refer to the consultants is a good idea. I don't think that we would have enough ressources to do it on our own. --- 4) What are some of the most interesting features in OpenOffice that most users don't know even exist? Rob: It seems most users don't know how to use word competition ;-) But maybe we can nominate 4 or 5 hidden features or underused features that users might not know about? Marcus: The AutoCorrect feature (see menu Tools - AutoCorrect Options is also a hidden feature - or should I say highly misunderstood? Furthermore, some words about the spell check and that we don't do them on our own but rely on extension. This could maybe hel pto avoid requests like This and that word is wrong - please fit it. --- 5) What's being done to help realise the universal OpenDocument dream? Rob: We have some material here from our Document Freedom Day blog post, talking about project members who are also active in the OASIS ODF TC and the standardization effort. --- 6) Are there backdoors or spyware in Apache OpenOffice? Rob: Like we'd tell you if there were? ;-) But seriously, this could be a topic of a standalone blog post, and maybe we should do that. We could discuss open source security, how we handle vulnerability reports and the advantage of open source transparency for preventing back doors. Marcus: The long-awaited NSA question. ;-) +1
Re: Ask OpenOffice #2 Top Questions: Now for the answers....
On February 27, 2014 2:54:26 PM PST, Marcus (OOo) wrote: 8) Does it cost anything to upload a template online? Rob: No. Odd that this questions got so many votes. Any ideas on why this is a question? Marcus: No, absolutely not. There is nothing on the Sourceforge hosted webpages that would point into this direction. Combine the answer with extensions as it would be the next question. My guess is that it is a combination of: * Unclear instructions on how to upload a template to be used by AOo; * The presence of templates that are not Gratis; * The presence of templates that are not Libre; * Some of the vocabulary used by SourceForge; jonathon -- Your language. Your documents. Your way. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1.0_release_blocker requested: [Bug 87182] Crash on formatting OLE Draw object
Armin Le Grand armin.le.gr...@me.com has asked for 4.1.0_release_blocker: Bug 87182: Crash on formatting OLE Draw object https://issues.apache.org/ooo/show_bug.cgi?id=87182 --- Additional Comments from Armin Le Grand armin.le.gr...@me.com Comitted, done. Since it is a crash less, not unsafe to fix and may also crash when Draw is used as OLE from other apps I request 4.1.0 release blocker flag. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Ask OpenOffice #2 Top Questions: Now for the answers....
On Feb 27, 2014, at 2:28 PM, Armin Le Grand wrote: On 27.02.2014 15:00, Kay Schenk wrote: --- 2) A series of questions on proposed features and how we decide on new features, including: a) Is it possible to include a 'Track Change' feature in OpenOffice like the one in MS Word? b) When will OpenOffice be able to support saving in (.doc) for Microsoft Word 2012-2014? c) Does Open Office plan to add capability to print out marginal comments/notes on the document page where they appear instead of as a separate list at the end of the document? d) Will OpenOffice users be able to import a PDF file, update it, and export the updated file? e) How does you decide what features to put into OpenOffice? f) What is the average time it takes you to fix a bug? add a new feature? Rob: I thought we'd lump these all together and give an in-depth response about how features and bug fixes are prioritized in a volunteer-led open source project at Apache. The PDF question seems like a much larger animal than some of the others to me. Probably on par with b) -- on a larger scale maybe. It may need a larger/longer explanation on its own. I see two reasons we do not have that 'roundtrip': (1) The PDF exporter needs to work Page-oriented since PDF is. That is the main reason the import was implemented originally for draw format, not for Writer. When importing to Writer, the Page breaks would not be guaranteed. Also the imported text is not 'floating' text in the classical sense of a Writer paragraph - this was AFAIK not possible with the import method chosen. Thus it would not behave well in Writer when you klick somewhere in such a imported document and start writing. (2) There are enough (even free) programs that add 'overlay' to PDF, e.g. for signing documents, so this is not needed to be done by AOO, too. I am giving two presentations at Apachecon. One of these is about Osmosis a tool my team at work developed that converts PDFs to editable PowerPoint and HTML5 files. It uses Apache PDFBox and Apache POI. My hope is that this can become a software grant, currently preparing to jump through the necessary corporate hoops. Regards, Dave --- - 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
