Re: [DISCUSS] possible blog topic -- AOO and Linux: a marriage made in heaven! :)
On 04/23/2014 03:16 PM, Andrea Pescetti wrote: > On 20/04/2014 Kay Schenk wrote: >> Many Linux distros maintain "community" repositories and perhaps its >> easiest to use that sort of mechanism for reintegration. > > Not to diminish this thread (on the contrary, there were a number of > good messages, insightful remarks and a very diverse participation, I'm > finding it very inspirational so far!), but indeed it would be time to > stop talking and start doing. Indeed! :) I will be summarizing this thread and putting it on cwiki in our planning area just to make it easier to again find all these good ideas. > > The "community repositories" solution outlined by Kay above is the > simplest one in our case. As a project, we are able to do (and we > actually do!) things that are much more complex than that. Onward and upward to learning how to build and put AOO into the community repository at openSUSE! :) > > Official support in distributions is more difficult to obtain and > requires obeying different policies, so I see it as a second step. But a > first, feasible, step, is to experiment with unofficial repositories > that allow terminal-averse Linux users (they exist, it seems) to get > OpenOffice 4.1. I'm interested in doing some work personally in this > direction, and I've already taken some basic steps; if anyone wants to > join the effort, please say so and we may get it done sooner! > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > -- - MzK "Life is either a daring adventure, or nothing." -- Helen Keller - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [DISCUSS] possible blog topic -- AOO and Linux: a marriage made in heaven! :)
On 20/04/2014 Kay Schenk wrote: Many Linux distros maintain "community" repositories and perhaps its easiest to use that sort of mechanism for reintegration. Not to diminish this thread (on the contrary, there were a number of good messages, insightful remarks and a very diverse participation, I'm finding it very inspirational so far!), but indeed it would be time to stop talking and start doing. The "community repositories" solution outlined by Kay above is the simplest one in our case. As a project, we are able to do (and we actually do!) things that are much more complex than that. Official support in distributions is more difficult to obtain and requires obeying different policies, so I see it as a second step. But a first, feasible, step, is to experiment with unofficial repositories that allow terminal-averse Linux users (they exist, it seems) to get OpenOffice 4.1. I'm interested in doing some work personally in this direction, and I've already taken some basic steps; if anyone wants to join the effort, please say so and we may get it done sooner! Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
apacheCon Europe Budapest 17-21 november, prices and other info
Hi. Just a little advance information. you can find the homepage here: apachecon.eu Call for papers is open now and until June 25, let together show that AOO is a big project in ASF (there are currently 10 proposals, and 1 is about AOO). As usual prices escalate as we get closer. rbowen wrote "We will announce the schedule on July 28, but registration is open already, and the prices are best right now. Eu799 through August 1, Eu1099 through November, and Eu1399 thereafter. Committers are always Eu275". I look forward to see a big AOO community in budapest. rgds jan I.
Statistic for user community meetings.
Hi. Can someone help me to gather a statistic of how many people participate in openoffice user conferences ? I tried to find how many participates in: - apachecon europe (AOO talks) - german user group meetings - other user group meetings I understand the numbers might not be something we want share public, so feel free to mail me direct. The numbers will only be used to get a feeling for event sizes (which of course depend on many factors like price) and will not be publized. thanks in advance for the help. rgds jan I.
Re: Re:Re: Re: Display About OpenOffice
Hi Osimeno, I installed the AOO 4.1 RC3 Chinese version on my RHEL 6.5 (64bit English version). But I cannot reproduce your problem. Because all UI strings use Unicode for encoding, I think it should not be related to locale settings. And if possible you can try to change it back to Chinese and see if the issue can be solved. On Sat, Apr 19, 2014 at 12:08 PM, osimeno wrote: > hi, > Do you need some other infomation ? I had reintasll the software,but > it can't resolve the problem. > > Thank You! > 在 2014-04-16 20:20:08，osimeno 写道： > > Hi ： > I used chinese on redhat，but i had changed the language to > english，the problem always be there。 > > > > > > At 2014-04-16 14:16:53,"Yuzhen Fan" wrote: > > Dear osimeno, > > What's the locale in your Redhat? > > Steve, could you please have a look at this problem? Thanks! > > > On Tue, Apr 15, 2014 at 3:36 PM, osimeno wrote: > >> >> Dear Yuzhen Fan,Marcus: >> >> Here is the pirture.The attachment. >> Thanks~ >> >> >> >> >> >> At 2014-04-15 03:39:04,"Marcus (OOo)" wrote: >> >Am 04/14/2014 12:26 PM, schrieb Yuzhen Fan: >> >> Hi >> >> >> >> Please send the picture you mentioned as attachment, I guess you just >> >> pasted it as RTF in your original email which is not displayed. >> >> >> >> On Mon, Apr 14, 2014 at 9:46 AM, osimeno wrote: >> >> >> >>> >> >>> Thanks dear Marcus, >> >>> I send a picture on last mail,maybe you can't see >> >>> that.The problem is there are some characters display like box,some >> >>> characters display chinese very well.I want to show chinese all,but i >> >>> don't >> >>> know how to do. >> > >> >I'm sorry but I'm not familiar with Chinese. Please send your question >> >to the Users mailing list. I'm sure there are much more people with >> >Chinese skills who can help you. See here: >> > >> >http://openoffice.apache.org/mailing-lists.html#users-mailing-list-public >> >> > >> >Thanks >> > >> >Marcus >> > >> > >> > >> >>> At 2014-04-12 03:16:45,"Marcus (OOo)" wrote: >> Am 04/11/2014 07:38 AM, schrieb osimeno: >> > Hi, >> > I had installed the openoffice 4,there are some problems maybe you can >> > help me. >> > My system is rhel6.3_X64 and use chinese . >> > My first step : tar -xvf openoffice -C /usr/src/ >> > My second step : cd /usr/src/zh-CN/RPMS >> > rpm - ivh openoffice-* >> > My third step : cd desktop* >> > rpm -ivh openoffice4.0-redhat* >> > And i had reboot the system. >> > the problem is that: >> > >> > so can you help me? >> >> Unfortunately, you don't have mentioned the actual problem or error >> message. Nevertheless I would recommend you to use the users mailing >> list for discussing problems: >> >> http://openoffice.apache.org/mailing-lists.html#users-mailing-list-public >> >> Marcus >> >> >> >> > > > -- > Regards, > Yu Zhen > > > > > > -- Best Regards, Steve Yin
Re: Anything we can do about premature redistribution?
On 3/7/14, Rob Weir wrote: > On Fri, Mar 7, 2014 at 10:23 AM, Jürgen Schmidt > wrote: >> On 3/7/14 4:21 PM, Oliver-Rainer Wittmann wrote: >>> Hi, >>> >>> On 07.03.2014 15:22, Rob Weir wrote: Evidently we're already released, on some websites at least: http://linux.softpedia.com/get/Office/Office-Suites/Apache-OpenOffice-253.shtml How much do we care about this? The risk, I suppose, is on Softpedia, that we could find a last-minute defect in the NOTICE or other legal files, and they find themselves distributing a package that is not correct. But the practical risk there is small. The greater risk is to users, that we find a last-minute fatal bug that causes us to cancel the vote, but there are versions of the Release Candidate still floating around. That can hurt the AOO reputation if that happened. I'm not sure we can prevent this from happening, and still have an open and transparent voting process. But maybe there is something we can do to discourage it? >>> >>> >>> softpedia is not the only one: >>> - http://www.chip.de/downloads/OpenOffice_14324674.html >>> - http://www.computerbase.de/downloads/office/ >>> >> >> I think we can create a blog explaining the voting procedure and make >> clear where we are in the process and that it is the RC of the Beta only. >> > > Or maybe a disclaimer in the voting thread email? Next time we could > say something like: > > "Note: All Apache releases require a vote of the PMC lasting at > least 72-hours. We do not officially release until after that vote > has concluded. We appreciate the enthusiasm of our users and 3rd > party distributors and their efforts to publicize our releases and > share them with a broader audience. But we ask that you do not > publicize a release until the vote has concluded and the vote results > posted. This is for the safety of the users. It is always possible > for a last minute defect to be reported in a Release Candidate causing > us to cancel an in-progress vote. in fact this has occurred before. > So be safe and wait for the release process to conclude." > > I'm guessing that they hear about the RC from the email list, not the > wiki, so it might make sense to put a message like this in the vote > email. Not sure email would be as effective as on the website (in this case, the cWiki page). Do softpedia find out about these RCs from the ML or the wiki? > > -Rob > > >> But I don't know if this would really help to avoid confusion. >> >> Juergen >> >> >>> >>> Best regards, Oliver. >>> -Rob - 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 >> > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Anything we can do about premature redistribution?
On 3/7/14, Rob Weir wrote: > Evidently we're already released, on some websites at least: > > http://linux.softpedia.com/get/Office/Office-Suites/Apache-OpenOffice-253.shtml > > How much do we care about this? The risk, I suppose, is on > Softpedia, that we could find a last-minute defect in the NOTICE or > other legal files, and they find themselves distributing a package > that is not correct. But the practical risk there is small. > > The greater risk is to users, that we find a last-minute fatal bug > that causes us to cancel the vote, but there are versions of the > Release Candidate still floating around. That can hurt the AOO > reputation if that happened. This is implied on the 'Beta' label that was added on softpedia. Every beta product assumes that bugs, even critical could surface. > > I'm not sure we can prevent this from happening, and still have an > open and transparent voting process. But maybe there is something we > can do to discourage it? At the bottom of the website it says Feedback. Of course you could legally contact the parent company about the issue but I dont think that's necessary. > > -Rob > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Anything we can do about premature redistribution?
2014-04-23 1:37 GMT+02:00 Andrea Pescetti : > On 22/04/2014 Roberto Galoppini wrote: > >> 2014-04-22 0:14 GMT+02:00 Andrea Pescetti: >> >>> http://www.openoffice.org/download/devbuilds.html >>> >> Andrea are you saying we should re-route RCs download requests coming from >> all referrals (but openoffice.org and sourceforge.net) to that page? >> > > That would be the proposal, yes. Add apache.org to the whitelisted > referrals. > > > Please confirm my understand is correct and provide me with the exact >> directory/files so that I can ask our SiteOps to implement that right away >> > > I don't think we already have the files online. The files to be redirected > are the Release Candidates, and I may be wrong but I assume that RC4 is not > yet on SourceForge and will be uploaded during or immediately after the > vote. Ok, I'm assuming those files will be in a directory called 4.1? Please let me know, so that I can move with this plan accordingly. Roberto > During this period (lasting a few days) we don't want to allow downloads > until we send out the official release news. Reason: we may (and we did it > already) decide to push a last-minute fix even when a release has been > approved but is not distributed yet. > > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: OpenOffice bugs and confidential documents
On Wed, Apr 23, 2014 at 3:03 AM, Andrea Pescetti wrote: > When someone complained that OpenOffice crashed on their company documents, > I've always answered that either they made the documents available in > Bugzilla or we couldn't do anything about it. Now it happened to me and I > realize that my suggestion is easier said than done! > > I received a DOCX document that OpenOffice Writer cannot open (crash). The > company that sent it to me cannot make it public: it's a confidential work > document. > > In general how can we handle this? It's very important for the project to > have a good reputation in companies, so if we crash on company templates we > should be able to know it and fix it. > > What options do we have available? Do we accept private attachments in > Bugzilla? Can a properly obtained stack trace replace the need for the > actual document, maybe? Other options? > We have the technical ability to do this in Bugzilla. We do that with security-related bugs, for example. They are only visible to those on the security team. The entire bug report is restricted, not just the attachment. But I don't think this is a good practice to do in general. I don't think we want volunteers to consider themselves responsible for the handling of their confidential documents. -Rob > Note: in my case I already asked for, and received, a working ODT version. > I'm interested in the generic discussion. > > 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: Which SQL commands support OpenOffice Base?
Some very good documentation on using base is on the forums. https://forum.openoffice.org/en/forum/viewforum.php?f=83&sid=5afbe506f0a8c7c597dc6e637a086e39 On 4/23/14, F C. Costero wrote: > Hello! > If you create a Base file using the menu File -> New -> Database -> Create > a New Database, you will get a Base file that runs HSQLDB version 1.8 as an > embedded database. The SQL documentation for that is here: > http://www.hsqldb.org/doc/1.8/guide/ch09.html. I would not recommend using > the embedded mode for critical work because of the possibility of data > loss. The data loss is not due to instability of HSQLDB but to the nature > of the embedded mode. > If you create a Base file using the menu File -> New -> Database -> Connect > to an Existing Database, you can connect to an external database through > JDBC, ODBC or any of the other listed methods. This means you can connect > to any database engine of your choosing and use its version of SQL. > More detailed answers are best provided on the user mailing list or on the > forums at https://forum.openoffice.org/ > Best regards, > Francis > > > On Wed, Apr 23, 2014 at 3:40 AM, Dima Sidorenko > wrote: > >> Hello!. >> >> Which SQL commands support OpenOffice Base?, What server database used in >> OpenOffice Base?, Dialects which are supported in OpenOffice Base? >> >> Sincerely, >> >> Sidorenko Dmitriy. >> > -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OpenOffice bugs and confidential documents
On Wed, Apr 23, 2014 at 9:27 AM, Alexandro Colorado wrote: > On 4/23/14, Rob Weir wrote: >> On Wed, Apr 23, 2014 at 6:53 AM, Rory O'Farrell wrote: >>> On Wed, 23 Apr 2014 12:34:33 +0200 >>> dav...@flossconsulting.it wrote: >>> > What options do we have available? Do we accept private attachments in > Bugzilla? Can a properly obtained stack trace replace the need for the > actual document, maybe? Other options? What about anonymize the DOCX by searching and replacing any simple char with X char? With MS Office of course Davide > > Note: in my case I already asked for, and received, a working ODT > version. I'm interested in the generic discussion. > > Regards, > Andrea. >>> >>> One can't anonymize an unopenable file! It would have to be done using the >>> generating application. >>> >> >> But it is possible, in theory to do something like this with the >> Apache ODF Toolkit (incubating). > > Isnt the ODF Toolkit for ODF only?? What would that help on a DOCX document? > True, but you could use Apache POI for DocX files. It is a similar library. -Rob >> >> But it is tricky, especially if the document has embedded documents, >> OLE embeddings, images with confidential information, etc. You could > > Probably some binary blob is causing the file to be unable to be open by AOO. > >> need to replace it all. But the stuff you replace might be the source >> of the crash. >> >> A safer way is for the person who edited the document to do a binary >> search for the issue, e.g., creating test documents containing the >> first half of the document and another with the 2nd half. See which > > Agree. > >> one crashes. Then divide that test document. And so on, until you've >> narrowed down what is causing the crash. Of course, not all crashes >> can be narrowed down that way, but many can. >> >> -Rob >> >>> >>> -- >>> Rory O'Farrell >>> >>> - >>> 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 >> >> > > > -- > Alexandro Colorado > Apache OpenOffice Contributor > http://www.openoffice.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: Which SQL commands support OpenOffice Base?
Hello! If you create a Base file using the menu File -> New -> Database -> Create a New Database, you will get a Base file that runs HSQLDB version 1.8 as an embedded database. The SQL documentation for that is here: http://www.hsqldb.org/doc/1.8/guide/ch09.html. I would not recommend using the embedded mode for critical work because of the possibility of data loss. The data loss is not due to instability of HSQLDB but to the nature of the embedded mode. If you create a Base file using the menu File -> New -> Database -> Connect to an Existing Database, you can connect to an external database through JDBC, ODBC or any of the other listed methods. This means you can connect to any database engine of your choosing and use its version of SQL. More detailed answers are best provided on the user mailing list or on the forums at https://forum.openoffice.org/ Best regards, Francis On Wed, Apr 23, 2014 at 3:40 AM, Dima Sidorenko wrote: > Hello!. > > Which SQL commands support OpenOffice Base?, What server database used in > OpenOffice Base?, Dialects which are supported in OpenOffice Base? > > Sincerely, > > Sidorenko Dmitriy. >
Re: OpenOffice bugs and confidential documents
On 4/23/14, Rob Weir wrote: > On Wed, Apr 23, 2014 at 6:53 AM, Rory O'Farrell wrote: >> On Wed, 23 Apr 2014 12:34:33 +0200 >> dav...@flossconsulting.it wrote: >> >>> >>> > What options do we have available? Do we accept private attachments in >>> > Bugzilla? Can a properly obtained stack trace replace the need for the >>> > actual document, maybe? Other options? >>> >>> What about anonymize the DOCX by searching and replacing any simple char >>> with X char? >>> With MS Office of course >>> >>> Davide >>> >>> >>> > >>> > Note: in my case I already asked for, and received, a working ODT >>> > version. I'm interested in the generic discussion. >>> > >>> > Regards, >>> > Andrea. >> >> One can't anonymize an unopenable file! It would have to be done using the >> generating application. >> > > But it is possible, in theory to do something like this with the > Apache ODF Toolkit (incubating). Isnt the ODF Toolkit for ODF only?? What would that help on a DOCX document? > > But it is tricky, especially if the document has embedded documents, > OLE embeddings, images with confidential information, etc. You could Probably some binary blob is causing the file to be unable to be open by AOO. > need to replace it all. But the stuff you replace might be the source > of the crash. > > A safer way is for the person who edited the document to do a binary > search for the issue, e.g., creating test documents containing the > first half of the document and another with the 2nd half. See which Agree. > one crashes. Then divide that test document. And so on, until you've > narrowed down what is causing the crash. Of course, not all crashes > can be narrowed down that way, but many can. > > -Rob > >> >> -- >> Rory O'Farrell >> >> - >> 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 > > -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Which SQL commands support OpenOffice Base?
Hi, Wed, 23 Apr 2014 14:40:09 +0500 от Dima Sidorenko <>: >Hello!. > >Which SQL commands support OpenOffice Base?, What server database used in >OpenOffice Base?, Dialects which are supported in OpenOffice Base? > >Sincerely, > >Sidorenko Dmitriy. > https://wiki.openoffice.org/wiki/Built-in_functions_and_Stored_Procedures -- Yakov Reztsov
Re: OpenOffice bugs and confidential documents
On Wed, 23 Apr 2014 08:35:25 -0400 Rob Weir wrote: > On Wed, Apr 23, 2014 at 6:53 AM, Rory O'Farrell wrote: > > On Wed, 23 Apr 2014 12:34:33 +0200 > > dav...@flossconsulting.it wrote: > > > >> > >> > What options do we have available? Do we accept private attachments in > >> > Bugzilla? Can a properly obtained stack trace replace the need for the > >> > actual document, maybe? Other options? > >> > >> What about anonymize the DOCX by searching and replacing any simple char > >> with X char? > >> With MS Office of course > >> > >> Davide > >> > >> > >> > > >> > Note: in my case I already asked for, and received, a working ODT > >> > version. I'm interested in the generic discussion. > >> > > >> > Regards, > >> > Andrea. > > > > One can't anonymize an unopenable file! It would have to be done using the > > generating application. > > > > But it is possible, in theory to do something like this with the > Apache ODF Toolkit (incubating). > > But it is tricky, especially if the document has embedded documents, > OLE embeddings, images with confidential information, etc. You could > need to replace it all. But the stuff you replace might be the source > of the crash. > > A safer way is for the person who edited the document to do a binary > search for the issue, e.g., creating test documents containing the > first half of the document and another with the 2nd half. See which > one crashes. Then divide that test document. And so on, until you've > narrowed down what is causing the crash. Of course, not all crashes > can be narrowed down that way, but many can. > > -Rob > For what it's worth, I have come across a few cases of files that crash when OpenOffice attempts to open them, but which can open correctly if /Insert /File into a blank OpenOffice document of the correct type. -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OpenOffice bugs and confidential documents
On Wed, Apr 23, 2014 at 6:53 AM, Rory O'Farrell wrote: > On Wed, 23 Apr 2014 12:34:33 +0200 > dav...@flossconsulting.it wrote: > >> >> > What options do we have available? Do we accept private attachments in >> > Bugzilla? Can a properly obtained stack trace replace the need for the >> > actual document, maybe? Other options? >> >> What about anonymize the DOCX by searching and replacing any simple char >> with X char? >> With MS Office of course >> >> Davide >> >> >> > >> > Note: in my case I already asked for, and received, a working ODT >> > version. I'm interested in the generic discussion. >> > >> > Regards, >> > Andrea. > > One can't anonymize an unopenable file! It would have to be done using the > generating application. > But it is possible, in theory to do something like this with the Apache ODF Toolkit (incubating). But it is tricky, especially if the document has embedded documents, OLE embeddings, images with confidential information, etc. You could need to replace it all. But the stuff you replace might be the source of the crash. A safer way is for the person who edited the document to do a binary search for the issue, e.g., creating test documents containing the first half of the document and another with the 2nd half. See which one crashes. Then divide that test document. And so on, until you've narrowed down what is causing the crash. Of course, not all crashes can be narrowed down that way, but many can. -Rob > > -- > Rory O'Farrell > > - > 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: OpenOffice bugs and confidential documents
On 4/23/14, Rory O'Farrell wrote: > On Wed, 23 Apr 2014 12:34:33 +0200 > dav...@flossconsulting.it wrote: > >> >> > What options do we have available? Do we accept private attachments in >> > Bugzilla? Can a properly obtained stack trace replace the need for the >> > actual document, maybe? Other options? >> >> What about anonymize the DOCX by searching and replacing any simple char >> with X char? >> With MS Office of course >> >> Davide >> >> >> > >> > Note: in my case I already asked for, and received, a working ODT >> > version. I'm interested in the generic discussion. >> > >> > Regards, >> > Andrea. > > One can't anonymize an unopenable file! It would have to be done using the > generating application. DOCX is also a Zip-XML fileformat, so you can do some ASCII procssing and parsing script there are scripts that could (or could not) open it. You have this for example: https://pypi.python.org/pypi/ooxml/0.2 > > > -- > Rory O'Farrell > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OpenOffice bugs and confidential documents
Hi, On 23.04.2014 09:03, Andrea Pescetti wrote: When someone complained that OpenOffice crashed on their company documents, I've always answered that either they made the documents available in Bugzilla or we couldn't do anything about it. Now it happened to me and I realize that my suggestion is easier said than done! I received a DOCX document that OpenOffice Writer cannot open (crash). The company that sent it to me cannot make it public: it's a confidential work document. In general how can we handle this? It's very important for the project to have a good reputation in companies, so if we crash on company templates we should be able to know it and fix it. What options do we have available? Do we accept private attachments in Bugzilla? Can a properly obtained stack trace replace the need for the actual document, maybe? Other options? Note: in my case I already asked for, and received, a working ODT version. I'm interested in the generic discussion. Yes, such use cases are hard to handle in a public and transparent working open-source community. The already made suggestion to consult a professional in our OpenOffice eco-system and secure the document by a corresponding contract is one way. Another one would be to simply trust a certain community member who is able and willing to solve the problem and share the document with this community member. I do not think that we as an open-source project at Apache are in the position to provide a service for such business-making use cases. That is of course the area of the professional eco-system around OpenOffice as stated above. Best regards, Oliver. 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: OpenOffice bugs and confidential documents
On Wed, 23 Apr 2014 12:34:33 +0200 dav...@flossconsulting.it wrote: > > > What options do we have available? Do we accept private attachments in > > Bugzilla? Can a properly obtained stack trace replace the need for the > > actual document, maybe? Other options? > > What about anonymize the DOCX by searching and replacing any simple char > with X char? > With MS Office of course > > Davide > > > > > > Note: in my case I already asked for, and received, a working ODT > > version. I'm interested in the generic discussion. > > > > Regards, > > Andrea. One can't anonymize an unopenable file! It would have to be done using the generating application. -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OpenOffice bugs and confidential documents
What options do we have available? Do we accept private attachments in Bugzilla? Can a properly obtained stack trace replace the need for the actual document, maybe? Other options? What about anonymize the DOCX by searching and replacing any simple char with X char? With MS Office of course Davide Note: in my case I already asked for, and received, a working ODT version. I'm interested in the generic discussion. 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
Which SQL commands support OpenOffice Base?
Hello!. Which SQL commands support OpenOffice Base?, What server database used in OpenOffice Base?, Dialects which are supported in OpenOffice Base? Sincerely, Sidorenko Dmitriy.
Re: OpenOffice bugs and confidential documents
I think this need to be handle by a real company that can provide NDA documentation for this and should be a for-pay serrvice. IMHO. That said, they could also try to scrap the data from the document in order to replicate the issue. On 4/23/14, Jürgen Schmidt wrote: > On 4/23/14 9:03 AM, Andrea Pescetti wrote: >> When someone complained that OpenOffice crashed on their company >> documents, I've always answered that either they made the documents >> available in Bugzilla or we couldn't do anything about it. Now it >> happened to me and I realize that my suggestion is easier said than done! >> >> I received a DOCX document that OpenOffice Writer cannot open (crash). >> The company that sent it to me cannot make it public: it's a >> confidential work document. >> >> In general how can we handle this? It's very important for the project >> to have a good reputation in companies, so if we crash on company >> templates we should be able to know it and fix it. >> >> What options do we have available? Do we accept private attachments in >> Bugzilla? Can a properly obtained stack trace replace the need for the >> actual document, maybe? Other options? >> >> Note: in my case I already asked for, and received, a working ODT >> version. I'm interested in the generic discussion. > > I understand the problem and we know this situation. I believe it is > not easy to address in an open source project. Either the documents can > be cleaned up and confidential data get removed or the company contacted > another company where special agreements can be done. > > If you need more than the community project can provide it is possible > to buy professional help and support. Not everything is for free and > that has nothing to do with good or bad reputation. It's up to the > company, either they can provide a clean document containing the problem > or buy professional support/service. > > I personally don't want to deal with confidential data/documents in > public or in the bugtracker. > > Juergen > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OpenOffice bugs and confidential documents
On 4/23/14 9:03 AM, Andrea Pescetti wrote: > When someone complained that OpenOffice crashed on their company > documents, I've always answered that either they made the documents > available in Bugzilla or we couldn't do anything about it. Now it > happened to me and I realize that my suggestion is easier said than done! > > I received a DOCX document that OpenOffice Writer cannot open (crash). > The company that sent it to me cannot make it public: it's a > confidential work document. > > In general how can we handle this? It's very important for the project > to have a good reputation in companies, so if we crash on company > templates we should be able to know it and fix it. > > What options do we have available? Do we accept private attachments in > Bugzilla? Can a properly obtained stack trace replace the need for the > actual document, maybe? Other options? > > Note: in my case I already asked for, and received, a working ODT > version. I'm interested in the generic discussion. I understand the problem and we know this situation. I believe it is not easy to address in an open source project. Either the documents can be cleaned up and confidential data get removed or the company contacted another company where special agreements can be done. If you need more than the community project can provide it is possible to buy professional help and support. Not everything is for free and that has nothing to do with good or bad reputation. It's up to the company, either they can provide a clean document containing the problem or buy professional support/service. I personally don't want to deal with confidential data/documents in public or in the bugtracker. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Server status: What's Up; What's Down?
On 4/23/14 8:12 AM, Alexandro Colorado wrote: > Is the CI currently up? I am getting 404 erorrs from the 4.0.1 RC4 branch. > http://ci.apache.org/projects/openoffice/milestones/4.1.0-rc/binaries/en-US/ > > And I went up to milestone to find that nothing is there: > http://ci.apache.org/projects/openoffice/milestones/ exactly there is nothing, I proposed yesterday a changed RC4 on rev. 1589052 and mentioned that it is expected today. But even this is not possible because the upload has not started yet. I hope I have now or get today the necessary access rights back. Juergen > > On 4/22/14, Marcus (OOo) wrote: >> Am 04/22/2014 09:33 PM, schrieb Jörg Schmidt: From: Jürgen Schmidt [mailto:jogischm...@gmail.com] >>> http://monitoring.apache.org/status/ it seems to be ok on the monitoring page but I am not sure if they are really working. >>> >>> >>> I fear that does not work properly yet. >> >> Right, Joe Schaefer from the ASF Infrastructure team has written today >> afternoon (CEST) here onteh dev@ ML that the CMS is not yet working and >> that the team is working on it. >> >> Marcus >> >> >> - >> 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
OpenOffice bugs and confidential documents
When someone complained that OpenOffice crashed on their company documents, I've always answered that either they made the documents available in Bugzilla or we couldn't do anything about it. Now it happened to me and I realize that my suggestion is easier said than done! I received a DOCX document that OpenOffice Writer cannot open (crash). The company that sent it to me cannot make it public: it's a confidential work document. In general how can we handle this? It's very important for the project to have a good reputation in companies, so if we crash on company templates we should be able to know it and fix it. What options do we have available? Do we accept private attachments in Bugzilla? Can a properly obtained stack trace replace the need for the actual document, maybe? Other options? Note: in my case I already asked for, and received, a working ODT version. I'm interested in the generic discussion. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
