How to download your program?
I was in need of an office program for my job applications, and a search on google directed me to your openoffice.I had great difficulties downloading the software on your download site: http://www.openoffice.org/download/index.htmlIcould not find a link where i could download this, only extensions and templates, while this could be interesting they are worthless without the main program.So i downloaded kingsoft office instead, because they were easily obtainable, but i had problems utilizing their program.Then i did more (several) google search for openoffice download, and after dismissing CNET and other ways to get your software i finally got a downloadable solution. I do not know what i did or how i got there, but i can say that I am now happy with your software and have got the documents i needed written and PDF-ified I write this so that other can enjoy the benefit of using your very great software.Please make a link to download Apache openoffice.exe on yor website. I tro, håp og kjærlighet Øyvind Sørensen
Re: Extensions wish list placementt?
On 3/22/14 12:27 AM, Kay Schenk wrote: On Fri, Mar 21, 2014 at 4:05 PM, Andrea Pescetti pesce...@apache.orgwrote: On 20/03/2014 Kay Schenk wrote: Every once in a while a topic arises on this list and gets a response like that might be a good idea for an extension. Right, but most of the times it is just a wish. The API available to extension developers does not allow to do everything. So it is very important to distinguish between responses that take into consideration what can really be done with an extension and responses that don't. Of course, this is critical! * Is is a good idea to steer new developers into extension development maybe as an introductory step? Probably it would be more effective to have more, well-defined and verified (in the sense above, i.e., that someone with the needed knowledge has verified them) easy tasks. Building an extension still requires skills. As far as development goes, creating an extension *might be* easier than coding changes to source. Of course, extension development is not as easy as some of our easy tasks. yes and no, you can make a lot mistakes with extension but the same is true for core changes. My experience from the past showed that extension are quite good for features that are not interested for all in the same way. External product integration for example where you need a commercial license. The connector is free but make no sense without the other product. This can help to grow the eco system. And my experience showed also that often core changes are necessary to make specific extensions possible. In general I would always prefer new features directly in the core and in ideally implemented in C++. And in the end it is easier to maintain. Our bundled extension concept needs some rework ... Volunteers should start with bug fixing, debugging existing code and nail down a problem on the root cause can be of course a challenge and motivation. You can learn a lot about the existing code and do over time more complicate things. But better starting small and grow over time than starting big, failing and lose motivation after some initial posts ;-) Juergen * and, assuming we can track down some of proposed extensions, where is a good place to record these for future reference? It seems we have https://wiki.openoffice.org/wiki/Extensions/Ideas ; but looking at https://wiki.openoffice.org/w/index.php?title=Extensions/ Ideas/Calcaction=history I see no indications that we are using it the right way (again: checking that it is possible with the current API to implement those ideas). It would be good to ask the API list for a quick validation of that page. Ok, thanks for this info -- I will check it out and confer with the API list as well. What occurred to me after I sent this would be to just log them into BZ under the extension category, and enhancements. No need to create another special area. Regards, Andrea. - 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
4.1.0_release_blocker granted: [Issue 124375] Active optional hyphens invisible in exported tagged-PDF on Mac
j...@apache.org has granted j...@apache.org's request for 4.1.0_release_blocker: Issue 124375: Active optional hyphens invisible in exported tagged-PDF on Mac https://issues.apache.org/ooo/show_bug.cgi?id=124375 --- Additional Comments from j...@apache.org grant showstopper flag because it is a regression - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
review granted: [Issue 124375] Active optional hyphens invisible in exported tagged-PDF on Mac : [Attachment 82940] patch to force soft-hyphen visibility with CoreText
j...@apache.org has granted h...@apache.org h...@apache.org's request for review: Issue 124375: Active optional hyphens invisible in exported tagged-PDF on Mac https://issues.apache.org/ooo/show_bug.cgi?id=124375 Attachment 82940: patch to force soft-hyphen visibility with CoreText https://issues.apache.org/ooo/attachment.cgi?id=82940action=edit --- Additional Comments from j...@apache.org reviewed, the fix looks good to me - 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: [Issue 124443] Update bundled German (de_*) dictionaries for OpenOffice 4.1.0
j...@apache.org has granted Andrea Pescetti pesce...@apache.org's request for 4.1.0_release_blocker: Issue 124443: Update bundled German (de_*) dictionaries for OpenOffice 4.1.0 https://issues.apache.org/ooo/show_bug.cgi?id=124443 --- 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: How to download your program?
Am 24.03.2014 um 05:51 schrieb øyvind sørensen: I was in need of an office program for my job applications, and a search on google directed me to your openoffice.I had great difficulties downloading the software on your download site: http://www.openoffice.org/download/index.htmlIcould Maybe you try without the iCloud. http://www.openoffice.org/download/index.html not find a link where i could download this, only extensions and templates, while this could be interesting they are worthless without the main program.So i downloaded kingsoft office instead, because they were easily obtainable, but i had problems utilizing their program.Then i did more (several) google search for openoffice download, and after dismissing CNET and other ways to get your software i finally got a downloadable solution. I do not know what i did or how i got there, but i can say that I am now happy with your software and have got the documents i needed written and PDF-ified I write this so that other can enjoy the benefit of using your very great software.Please make a link to download Apache openoffice.exe on yor website. I tro, håp og kjærlighet Øyvind Sørensen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Bug/Issue: There and back again
I never saw an announcement of this, so I am writing this summary instead. The AOO Bugzilla issue tracker has a feature that turns text of the form 'bug number' into an HTML link to the referenced bug. Some days ago this suddenly changed and only the pattern 'issue number' was recognized, see also bug 124460. Apparently this has been fixed. Now both patterns work in parallel. It would be nice if in the future there would be an announcement before such a change where made and we had the chance to discuss it. Regards, Andre - 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: [Issue 124357] Update bundled spellchecker for gd
j...@apache.org has granted 4.1.0_release_blocker: Issue 124357: Update bundled spellchecker for gd https://issues.apache.org/ooo/show_bug.cgi?id=124357 --- Additional Comments from j...@apache.org grant showstopper flag, requested dictionary update - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Be careful before the release
We're on a good way to a healthy AOO 4.1 release so we should avoid the pitfalls that prevented a timely AOO 4.1 Beta release. Let's examine this negative example a bit further, so we can all learn from it: A commit [1] stopped the Beta and forced the only respin that was needed despite the massive changes+improvements that went into the code base. [1] http://svn.apache.org/r1547732 The commit broke the installation of language packs and this breakage wasn't discussed before. The responsible developer sneaked that train-wreck in with a mega-patch under a non-suspicious comment. I don't remember him discussing the breakage of language packs before and that the creation of patches could negatively influences the usability of the language packs wasn't discussed either. Of course one could say It happens, but since that developer gets VERY annoying if It happens to anyone else the same casual attitude would be inappropriate. What's worse is that the commit comment [2] for unbreaking the language packs was Wrong initialization of . which is completely unusable. It didn't even mention language packs. That they were broken and now they are fixed. And what's that '.' Is this some magic hyper-linked dot? We should better use commit messages that can stand on their own. [2] http://svn.apache.org/r1573613 So in short: Be careful, be professional, don't do unto others what you wouldn't want them do unto you, and yes It happens and we have to deal with it. Positively if possible that is. Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: https://issues.apache.org/ooo/show_bug.cgi?id=118731
Hi Kay, On 23.03.2014 22:12, Kay Schenk wrote: This seems to be resolved at least by my testing. Can we can others on additional platforms to confirm so we can mark this as resolved? It may have been resolved with changes to frames in writer. Unfortunately there was no more feedback from r4zoli on this, I was never absolutely sure about his initial problem description. In principle it's about usual Writer GrahicFrames (FlyFrames); these may contain any type of graphic, including SVG, linked or embedded. There were multiple changes here in recent versions, e.g. SVG is handled as vector data now to have better exports and similar. Checked with the AOO4.1.0 beta and the bugdoc from comment 8. I can import http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/svg/get-aoo_300x100.svg?revision=1413471view=co directly using insert/from file (not the same URL ening in get-aoo_300x100.svg?view=log http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/svg/get-aoo_300x100.svg?view=log as in the bugdoc). If this is not what the task is about we would need a better, explicit step-by-step description how to reproduce and what exactly is what seems to be wrong. HTH! Sincerely, Armin -- ALG
AOO 4.1 Full Regression Test Starts! Call for volunteers!
Hi All, We have released AOO 4.1 Beta sucessfully on Mar 9 with voting, the next test stage is FPR(full regression test) targeting for release candidate of GA [1]. This is the call for volunteers on FPR, on Linux Redhat 64bit, Linux Redhat 32bit, Linux Ubuntu 64bit, Mac 10.9, Windows 7 and Windows 8. If you have interest and can help over the next few weeks, please send a note to the QA mailing list (q...@openoffice.apache.org). If you have a Testlink account[2] send your ID as well as what platform you can help test(if you haven't a Testlink account, you can register one). You should also get installation sets from trunk [3] and report issues in Bugzilla [4]. You may want to see detail instructions in Test Guidence [5]. [1] https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Planning [2] http://aootesting.adfinis-sygroup.org/index.php [3] http://ci.apache.org/projects/openoffice/ [4] https://issues.apache.org/ooo/ [5] https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Full+Regression+Test+Guidance Thanks! Regards, Yu Zhen
German authorities want to improve AOO - LibO
Hi, is someone from Germany observing this? http://www.heise.de/open/meldung/Behoerden-wollen-Libre-OpenOffice-verbessern-2152858.html Best regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Be careful before the release
On 24.03.2014 10:22, Herbert Duerr wrote: We're on a good way to a healthy AOO 4.1 release so we should avoid the pitfalls that prevented a timely AOO 4.1 Beta release. Let's examine this negative example a bit further, so we can all learn from it: A commit [1] stopped the Beta and forced the only respin that was needed despite the massive changes+improvements that went into the code base. [1] http://svn.apache.org/r1547732 The commit broke the installation of language packs and this breakage wasn't discussed before. The responsible developer sneaked that train-wreck in with a mega-patch under a non-suspicious comment. I don't remember him discussing the breakage of language packs before and that the creation of patches could negatively influences the usability of the language packs wasn't discussed either. I was the one who caused this build breaker and I am sorry for it. It was not the first and will not be the last build breaker that I introduced. I did not announce it in advance, because -- maybe this is hard to believe -- I did not do it on purpose. I also don't have a crystal ball that let's me see my future errors. Otherwise all my code changes would be error free, which, sadly, they are not. It was an honest mistake in a very complex feature (enabling our build system to create patches). I made the error in a file that was directly linked to the new feature. I did not see, at the time, that it would affect the regular build. Of course one could say It happens, but since that developer gets VERY annoying if It happens to anyone else the same casual attitude would be inappropriate. What's worse is that the commit comment [2] for unbreaking the language packs was Wrong initialization of . which is completely unusable. It didn't even mention language packs. That they were broken and now they are fixed. And what's that '.' Is this some magic hyper-linked dot? We should better use commit messages that can stand on their own. You are absolutely right. As an explanation, but not as excuse: what happend with this particular comment is, if I recall correctly, that I accidentally hit RETURN in mid-sentence. And then I was too lazy to look up SVN documentation and find out how to fix the comment. Instead I relied on all the necessary information being present in the issue description (for example see https://issues.apache.org/ooo/show_bug.cgi?id=124272#c11) and provided the correct comment in the issue (https://issues.apache.org/ooo/show_bug.cgi?id=124272#c14). I had the chance to fix the broken comment when I merged the change into trunk. But that seemed to me to be a bit dishonest, like I where trying to cover up a mistake. [2] http://svn.apache.org/r1573613 So in short: Be careful, be professional, don't do unto others what you wouldn't want them do unto you, and yes It happens and we have to deal with it. Positively if possible that is. I am not exactly sure what that is supposed to mean. If you have a problem with anything I have done, except from the build breaker, please be more explicit. I just have one wish. I don't have a problem with my errors being pointed out in the public. After more than a decade as developer in an open source project I have grown a thick skin. But please don't do that to others. That might discourage potential developers from joining our project. Regards, Andre Herbert - 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
[Bug 124496} Regression – Not all fonts available on Macs
Not all fonts are available on Macs (US English). This is a regression from AOO 4.0.1 https://issues.apache.org/ooo/show_bug.cgi?id=124496 -- _ Larry I. Gusaas Moose Jaw, Saskatchewan Canada Website: http://larry-gusaas.com An artist is never ahead of his time but most people are far behind theirs. - Edgard Varese - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Be careful before the release
For the continued success of Apache OpenOffice, Why can't we all just get along?-- Rodney King On Mon, Mar 24, 2014 at 3:26 AM, Andre Fischer awf@gmail.com wrote: On 24.03.2014 10:22, Herbert Duerr wrote: We're on a good way to a healthy AOO 4.1 release so we should avoid the pitfalls that prevented a timely AOO 4.1 Beta release. Let's examine this negative example a bit further, so we can all learn from it: A commit [1] stopped the Beta and forced the only respin that was needed despite the massive changes+improvements that went into the code base. [1] http://svn.apache.org/r1547732 The commit broke the installation of language packs and this breakage wasn't discussed before. The responsible developer sneaked that train-wreck in with a mega-patch under a non-suspicious comment. I don't remember him discussing the breakage of language packs before and that the creation of patches could negatively influences the usability of the language packs wasn't discussed either. I was the one who caused this build breaker and I am sorry for it. It was not the first and will not be the last build breaker that I introduced. I did not announce it in advance, because -- maybe this is hard to believe -- I did not do it on purpose. I also don't have a crystal ball that let's me see my future errors. Otherwise all my code changes would be error free, which, sadly, they are not. It was an honest mistake in a very complex feature (enabling our build system to create patches). I made the error in a file that was directly linked to the new feature. I did not see, at the time, that it would affect the regular build. Of course one could say It happens, but since that developer gets VERY annoying if It happens to anyone else the same casual attitude would be inappropriate. What's worse is that the commit comment [2] for unbreaking the language packs was Wrong initialization of . which is completely unusable. It didn't even mention language packs. That they were broken and now they are fixed. And what's that '.' Is this some magic hyper-linked dot? We should better use commit messages that can stand on their own. You are absolutely right. As an explanation, but not as excuse: what happend with this particular comment is, if I recall correctly, that I accidentally hit RETURN in mid-sentence. And then I was too lazy to look up SVN documentation and find out how to fix the comment. Instead I relied on all the necessary information being present in the issue description (for example see https://issues.apache.org/ooo/show_bug.cgi?id=124272#c11) and provided the correct comment in the issue (https://issues.apache.org/ooo/show_bug.cgi?id=124272#c14). I had the chance to fix the broken comment when I merged the change into trunk. But that seemed to me to be a bit dishonest, like I where trying to cover up a mistake. [2] http://svn.apache.org/r1573613 So in short: Be careful, be professional, don't do unto others what you wouldn't want them do unto you, and yes It happens and we have to deal with it. Positively if possible that is. I am not exactly sure what that is supposed to mean. If you have a problem with anything I have done, except from the build breaker, please be more explicit. I just have one wish. I don't have a problem with my errors being pointed out in the public. After more than a decade as developer in an open source project I have grown a thick skin. But please don't do that to others. That might discourage potential developers from joining our project. Regards, Andre Herbert - 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 -- Jose R R http://www.metztli-it.com - NEW Apache OpenOffice 4.0.1! Download for GNU/Linux, Mac OS, Windows. - Daylight Saving Time in USA Canada ends: Sunday, November 02, 2014 - - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Comments on IAccessible2 Implementation with Screen Readers
Forwarding to David. Welcome David! I am a developer for IA2 implementation in AOO. During IAccessible2 development, James Teh and Michael Curran filed a lot of critical issues, gave great support on technical and even delivered patches for this issue. That is we got a great support from NVDA. The problems you mentioned about JAWS, I think maybe the current version of JAWS does not know AOO as an IA2 application.We can involve JAWS by giving them feedback on that. About ZoomText and Window-eyes, we did not test IA2 with them, maybe they got a problem like JAWS. Because AT tools need to apply different specific strategies to different applications. So if AOO and AT tools want to get a better compatibility, they need to collaborate on IA2 implementation. On Mon, Mar 24, 2014 at 6:09 PM, Yuzhen Fan fanyuz...@gmail.com wrote: Hi David, Thanks for your help offering on tests. Currently, we have 2 major testing work: 1. Full Regression Testing on AOO 4.1 - Led by me (need your assistance on IA2 related testing) 2. Regression bug checking - Led by Rainer Bielefeld (need your assistance on IA2 related bugs' checking) Please let me know if you are interested for any of above work, or both, then we will send you detail information and instruction. Thanks again! On Fri, Mar 21, 2014 at 11:21 PM, David Goldfield dgold...@asb.org wrote: Hello. I am new to this list and I hope that my comments are being directed to the right group. If they should be directed to another list, please let me know and I will comply with the proper guidelines. First, I'll introduce myself by telling you that I'm visually impaired, am a user and teacher of several screen readers and I have been in the assistive technology field, providing training and support to blind and visually impaired computer users for over twenty years. I'm a big fan and advocate of open source software. At home, I use NVDA as my screen reader. At work, I also use JAWS, Window-eyes, MAGic and Zoomtext. I've been working on and off with various versions of OpenOffice for some time, doing some accessibility testing with screen readers and wanted to report on how the latest 4.1 beta is working with today's screen readers. First, I'll tell you that I've been doing my testing on a Windows 7 Pro 32-bit system. We have NVDA 2014.1, the latest build of JAWS 15 and Window-eyes 8.4. As of this writing, these are the latest publicly available versions of these programs. I suppose that NVDA is an exception, since they release master and next builds of current snapshots but I have not tested the latest versions of these snapshots. First, I am absolutely thrilled that OpenOffice is implementing IAccessible2. In theory, this should make the programs extremely compatible with today's screen readers. The two programs I've been working with are Writer and Calc. I have not done extensive testing yet but just want to make sure I can easily track documents, menus and dialogs without any real drama. So far, NVDA handles OO4.1 the best, tracking the caret with no issues and reading cell coordinates in Calc. Window-eyes 8.4 consistently crashes whenever I try to open Writer or Calc. I wrote to GW Micro's support. They wrote back, asking how they could duplicate the problem and soon afterward they told me that a post 8.4 build was not experiencing any issues. It is likely that I will have to wait for the next public beta of Window-eyes to be posted before I can do any further testing. JAWS 15 was totally unreliable in Calc, not reading most of the cells as I use arrow keys to move through them. Occasionally, cell info was read but not most of the time. Writer's performance with JAWS was a bit better but still inconsistent. Here are the comments I sent to Freedom Scientific. 1. When in Writer, when I type the first line of text in a document and press enter, JAWS says edit Has Flows From. This does not seem to happen when pressing enter for subsequent lines. 2. When reviewing a document in Writer 4.1, sometimes one line will be read when I'm actually reading another. As an example, if I move from the second line down to the third line, JAWS sometimes still reads the second line. This behavior does not always occur but it happens regularly enough that I felt it should be reported. Once, while reviewing a document character by character, JAWS says blank instead of the actual character under the cursor and I had to perform a screen refresh. Freedom Scientific's initial response was disappointing, indicating that JAWS currently does not support OpenOffice and then I was told about their support for Microsoft Office. While I have nothing against screen readers supporting Microsoft Office, many of my consumers can't easily afford another expensive piece of software and they deserve a good, solid, robust alternative. I
Re: Incubator still has SVN tree
On 23 March 2014 08:52, Andrea Pescetti pesce...@apache.org wrote: sebb wrote: There is still an SVN tree under Incubator: https://svn.apache.org/repos/asf/incubator/ooo/ I assume this was all transferred to the main ASF SVN area at https://svn.apache.org/repos/asf/openoffice/ If so, please can someone tidy up the Incubator tree? It was indeed all transferred, and the old copy made read-only by Infra. It wasn't deleted since we still had releases and documentation around that referred to the Incubator. I believe it is now safe to delete it. I don't know who can do it. I didn't try, but maybe we need to contact Infra since it is read-only. I can remove the read-only marker if you wish, in which case anyone on the IPMC - or an ASF member - can remove it. Our project site https://openoffice.apache.org/ only had one page referring to the Incubator. It was very outdated, we didn't have anything linking to it and I've now removed it. See http://svn.apache.org/viewvc/openoffice/site/trunk/content/release-process.mdtext?revision=1418982view=markup in case we need to restore it. Regards, Andrea. - 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: Incubator still has SVN tree
On 24 March 2014 13:51, Herbert Duerr h...@apache.org wrote: On 23.03.2014 09:52, Andrea Pescetti wrote: sebb wrote: There is still an SVN tree under Incubator: https://svn.apache.org/repos/asf/incubator/ooo/ I assume this was all transferred to the main ASF SVN area at https://svn.apache.org/repos/asf/openoffice/ If so, please can someone tidy up the Incubator tree? It was indeed all transferred, and the old copy made read-only by Infra. It wasn't deleted since we still had releases and documentation around that referred to the Incubator. There are still many e.g. Wiki pages that reference the incubator locations. I updated some of them but there are still plenty left, e.g. about the branch aw080, netbeans, OOXML, etc. I suggest to update them to their new location at https://svn.apache.org/repos/asf/openoffice For links that should continue to point into the incubator directory, e.g. because the branch was integrated and removed at the new location SVN offers the possibility to reference older branches using the https://svn.apache.org/repos/asf/!svn/bc/155/incubator/ooo/trunk/ notation. Although that should work, I think it could be confusing. IMO it would be better to find the appropriate entry in the new SVN layout. If there is no such entry, is there really a need to keep the reference to the incubator-only SVN tree? Herbert - 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: Incubator still has SVN tree
On 24.03.2014 15:13, sebb wrote: On 24 March 2014 13:51, Herbert Duerr h...@apache.org wrote: On 23.03.2014 09:52, Andrea Pescetti wrote: sebb wrote: There is still an SVN tree under Incubator: https://svn.apache.org/repos/asf/incubator/ooo/ I assume this was all transferred to the main ASF SVN area at https://svn.apache.org/repos/asf/openoffice/ If so, please can someone tidy up the Incubator tree? It was indeed all transferred, and the old copy made read-only by Infra. It wasn't deleted since we still had releases and documentation around that referred to the Incubator. There are still many e.g. Wiki pages that reference the incubator locations. I updated some of them but there are still plenty left, e.g. about the branch aw080, netbeans, OOXML, etc. I suggest to update them to their new location at https://svn.apache.org/repos/asf/openoffice For links that should continue to point into the incubator directory, e.g. because the branch was integrated and removed at the new location SVN offers the possibility to reference older branches using the https://svn.apache.org/repos/asf/!svn/bc/155/incubator/ooo/trunk/ notation. Although that should work, I think it could be confusing. IMO it would be better to find the appropriate entry in the new SVN layout. If there is no such entry, is there really a need to keep the reference to the incubator-only SVN tree? I mostly agree. For the pages that I already updated I was able to change all references to their new repository location. But for sub-project specific pages the status is not always obvious which alternative would be most suitable: - update them to their new repository location - keep the link into the incubator location - are the pages are still relevant or could/should they be deleted. AFAIK it is not easy to resurrect deleted Wiki pages, so doing that on still somewhat interesting pages would be a net loss. The best solution would be to check the problematic pages and their links. So if anyone has more insight into their status please update them: A quick google search found pages about the object inspector extension, the netbeans extension, the aw080 branch, OOXML, etc. Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
URL-location for latest beanshell provider source code ?
While going after the current implementation of a script provider, I would like to target the beanshell implemantion. Found an URL (via the web) pointing to: http://svn.apache.org/repos/asf/openoffice/trunk/main/scripting/java/com/sun/star/script/framework/provider/beanshell/ Just double-checking: would that be the URL to the latest version? If not where should I start to research/find the latest version? ---rony
Re: How to download your program?
I suspect that what the OP meant to write was: I was in need of an office program for my job applications, and a search on google directed me to your openoffice.I had great difficulties downloading the software on your download site: http://www.openoffice.org/download/index.html I could not find a link where i could download this, only extensions and templates, while this could be interesting they are worthless without the main program. (I have editted the above to add a couple of spaces only) If so, then perhaps the autodetection was not working for the OP. On 24 March 2014 08:10, Raphael Bircher rbirc...@apache.org wrote: Am 24.03.2014 um 05:51 schrieb øyvind sørensen: I was in need of an office program for my job applications, and a search on google directed me to your openoffice.I had great difficulties downloading the software on your download site: http://www.openoffice.org/download/index.htmlIcould Maybe you try without the iCloud. http://www.openoffice.org/download/index.html not find a link where i could download this, only extensions and templates, while this could be interesting they are worthless without the main program.So i downloaded kingsoft office instead, because they were easily obtainable, but i had problems utilizing their program.Then i did more (several) google search for openoffice download, and after dismissing CNET and other ways to get your software i finally got a downloadable solution. I do not know what i did or how i got there, but i can say that I am now happy with your software and have got the documents i needed written and PDF-ified I write this so that other can enjoy the benefit of using your very great software.Please make a link to download Apache openoffice.exe on yor website. I tro, håp og kjærlighet Øyvind Sørensen - 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: URL-location for latest beanshell provider source code ?
On 3/24/14 4:00 PM, Rony G. Flatscher (Apache) wrote: While going after the current implementation of a script provider, I would like to target the beanshell implemantion. Found an URL (via the web) pointing to: http://svn.apache.org/repos/asf/openoffice/trunk/main/scripting/java/com/sun/star/script/framework/provider/beanshell/ Just double-checking: would that be the URL to the latest version? If not where should I start to research/find the latest version? the link goes directly in trunk of our svn repository, means trunk contains the latest and greatest version and that is the place to start Juergen ---rony - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: URL-location for latest beanshell provider source code ?
On 24.03.2014 16:32, Jürgen Schmidt wrote: On 3/24/14 4:00 PM, Rony G. Flatscher (Apache) wrote: While going after the current implementation of a script provider, I would like to target the beanshell implemantion. Found an URL (via the web) pointing to: http://svn.apache.org/repos/asf/openoffice/trunk/main/scripting/java/com/sun/star/script/framework/provider/beanshell/ Just double-checking: would that be the URL to the latest version? If not where should I start to research/find the latest version? the link goes directly in trunk of our svn repository, means trunk contains the latest and greatest version and that is the place to start :-) Jürgen, thank you very much for reassuring this! ---rony - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Extensions wish list placementt?
On Mon, Mar 24, 2014 at 12:24 AM, Jürgen Schmidt jogischm...@gmail.comwrote: On 3/22/14 12:27 AM, Kay Schenk wrote: On Fri, Mar 21, 2014 at 4:05 PM, Andrea Pescetti pesce...@apache.org wrote: On 20/03/2014 Kay Schenk wrote: Every once in a while a topic arises on this list and gets a response like that might be a good idea for an extension. Right, but most of the times it is just a wish. The API available to extension developers does not allow to do everything. So it is very important to distinguish between responses that take into consideration what can really be done with an extension and responses that don't. Of course, this is critical! * Is is a good idea to steer new developers into extension development maybe as an introductory step? Probably it would be more effective to have more, well-defined and verified (in the sense above, i.e., that someone with the needed knowledge has verified them) easy tasks. Building an extension still requires skills. As far as development goes, creating an extension *might be* easier than coding changes to source. Of course, extension development is not as easy as some of our easy tasks. yes and no, you can make a lot mistakes with extension but the same is true for core changes. My experience from the past showed that extension are quite good for features that are not interested for all in the same way. External product integration for example where you need a commercial license. The connector is free but make no sense without the other product. This can help to grow the eco system. This makes sense and generally what I would think of when I think about extensions. And my experience showed also that often core changes are necessary to make specific extensions possible. hmmm...not something I would have thought. OK. In general I would always prefer new features directly in the core and in ideally implemented in C++. And in the end it is easier to maintain. Our bundled extension concept needs some rework ... Volunteers should start with bug fixing, debugging existing code and nail down a problem on the root cause can be of course a challenge and motivation. You can learn a lot about the existing code and do over time more complicate things. But better starting small and grow over time than starting big, failing and lose motivation after some initial posts ;-) Juergen Rest of your comments duly noted. * and, assuming we can track down some of proposed extensions, where is a good place to record these for future reference? It seems we have https://wiki.openoffice.org/wiki/Extensions/Ideas ; but looking at https://wiki.openoffice.org/w/index.php?title=Extensions/ Ideas/Calcaction=history I see no indications that we are using it the right way (again: checking that it is possible with the current API to implement those ideas). It would be good to ask the API list for a quick validation of that page. Ok, thanks for this info -- I will check it out and confer with the API list as well. What occurred to me after I sent this would be to just log them into BZ under the extension category, and enhancements. No need to create another special area. Regards, Andrea. - 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 -- - 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: https://issues.apache.org/ooo/show_bug.cgi?id=118731
On Mon, Mar 24, 2014 at 2:33 AM, Armin Le Grand armin.le.gr...@me.comwrote: Hi Kay, On 23.03.2014 22:12, Kay Schenk wrote: This seems to be resolved at least by my testing. Can we can others on additional platforms to confirm so we can mark this as resolved? It may have been resolved with changes to frames in writer. Unfortunately there was no more feedback from r4zoli on this, I was never absolutely sure about his initial problem description. In principle it's about usual Writer GrahicFrames (FlyFrames); these may contain any type of graphic, including SVG, linked or embedded. There were multiple changes here in recent versions, e.g. SVG is handled as vector data now to have better exports and similar. Checked with the AOO4.1.0 beta and the bugdoc from comment 8. I can import http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/ content/images/AOO_logos/svg/get-aoo_300x100.svg?revision=1413471view=co directly using insert/from file (not the same URL ening in get-aoo_300x100.svg?view=log http://svn.apache.org/viewvc/ openoffice/ooo-site/trunk/content/images/AOO_logos/svg/ get-aoo_300x100.svg?view=log as in the bugdoc). If this is not what the task is about we would need a better, explicit step-by-step description how to reproduce and what exactly is what seems to be wrong. HTH! Sincerely, Armin -- ALG I actually added to this issue, initiated by r4zoli, because I could not import an svg file into a frame in Writer, and I thought this was basically what the issue was about. Other objects, normal pictures, etc, were OK, just NOT svg files. I thought this was the same basic issue initiated by r4zoli. In any case, the problem I was having seems solved now, with my testing of the 4.1 Beta. -- - 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: German authorities want to improve AOO - LibO
On Mon, Mar 24, 2014 at 12:09 PM, Louis Suárez-Potts lui...@gmail.com wrote: Hi, On 2014-03-24, at 06:18, Rainer Bielefeld rainerbielefeld_ooo...@bielefeldundbuss.de wrote: Hi, is someone from Germany observing this? http://www.heise.de/open/meldung/Behoerden-wollen-Libre-OpenOffice-verbessern-2152858.html I had a discussion on improving OO with the lead of the (mostly German) Open Source Business Alliance, Peter G. Sounded great… but the emphasis for him was on LibreOffice. Not AOO. The English press release is here: http://www.osb-alliance.de/en/working-groups/projekte/major-features-in-loaoo/ That links to a PDF where they describe the requirements. On page 5 it says: The code implementing the use cases must be delivered to OSBA in two versions: one suitable for LibreOffice integration, one suitable for Apache OpenOffice integration. That means each version of the code changes must be developed, rebased and tested against a commit of the respective project that is not older than 60 days at the time of the delivery. And then later on that page: The contractor must publish the software source code developed for this project under license suitable for integration in the respective projects, ideally dual licensed Apache License Version 2.0, and Mozilla Public License Version 2.0. The contractor may choose to publish under Apache License Version 2.0 only. So it looks like regardless of who bids and wins, the results will be available for AOO to use as well. Regards, -Rob Best regards Rainer -louis - 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: How to download your program?
Am 03/24/2014 05:51 AM, schrieb øyvind sørensen: I was in need of an office program for my job applications, and a search on google directed me to your openoffice.I had great difficulties downloading the software on your download site: http://www.openoffice.org/download/index.htmlIcould not find a link where i could download this, only extensions and templates, while this could be interesting they are worthless without the main program.So i downloaded kingsoft office instead, because they were easily obtainable, but i had problems utilizing their program.Then i did more (several) google search for openoffice download, and after dismissing CNET and other ways to get your software i finally got a downloadable solution. I do not know what i did or how i got there, but i can say that I am now happy with your software and have got the documents i needed written and PDF-ified I write this so that other can enjoy the benefit of using your very great software.Please make a link to downloadApache openoffice.exe on yor website. I tro, håp og kjærlighet Øyvind Sørensen Thanks for letting us know that you have a problem to download OpenOffice. I would like to help you here. Please give me some more information for investigation: Is it correct that only 2 blue boxes are visible and no other colored boxes, when going to: http://www.openoffice.org/download/ Please copypaste the complete text from the following table: http://www.openoffice.org/download/test/analyze.html Thanks in advance for your help. BTW: Please be careful from where you download software. Nowadays it's very easy to get malware, viruses, etc. that lets you get mad when trying to get rid of it. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Introduction
Good Afternoon! I am, a stay at home mom from Chicago. I am looking to make a career change and learn new skills to re-enter the workforce after 5 years. I am excited for this learning opportunity. Danette
Re: URL-location for latest beanshell provider source code ?
Rony G. Flatscher (Apache) wrote: While going after the current implementation of a script provider, I would like to target the beanshell implemantion. This is only marginally related to what you are doing now, but note that Beanshell itself was proposed for becoming an Incubator project, even if the effort is now stalled (I think nobody has taken care of all the initial reviews, grants, etc yet): http://wiki.apache.org/incubator/BeanShellProposal So if, done this, you would like to help bring Beanshell itself to Apache the first steps are already done! Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: URL-location for latest beanshell provider source code ?
Buona sera Andrea, On 24.03.2014 22:48, Andrea Pescetti wrote: Rony G. Flatscher (Apache) wrote: While going after the current implementation of a script provider, I would like to target the beanshell implemantion. This is only marginally related to what you are doing now, but note that Beanshell itself was proposed for becoming an Incubator project, even if the effort is now stalled (I think nobody has taken care of all the initial reviews, grants, etc yet): http://wiki.apache.org/incubator/BeanShellProposal So if, done this, you would like to help bring Beanshell itself to Apache the first steps are already done! If I can help from the second line, whatever has to be done there, yes. Unfortunately, I have been tied down heavily with too many tasks to be able to step up into the front line for this initiative, which I too think is very important, especially for AOO! ---rony P.S.: My current interest in beanshell here is to double-check while researching a problem I have been experiencing on MacOSX-AOO with a ScriptProvider for ooRexx, which I had developed and am maintaining. (The same code works flawlessly dispatching ooRexx scripts on 32- and 64-bit.) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
