Re: Bug on macOS X and Microsoft Word 2003 XML format
Tested using OpenOffice 4.1.5 & macOS 10.13.3 High Sierra Saved an existing .odt & a .doc file as "Microsoft Word 2003 XML (.xml)" Both files saved and reopened. Larry On 2018-02-13, 4:56 PM Andrea Pescetti wrote concerning "Bug on macOS X and Microsoft Word 2003 XML format": A bug has been reported on the Italian mailing list but I'd like to get verification by a Mac user. To reproduce: 1. Be on High Sierra (but it would be useful to check with other versions too; the reporter says everything worked correctly, with OpenOffice 4.1.5, before upgrading to High Sierra). OpenOffice 4.1.5. 2. Create a new text document, write "Test", save as "Microsoft Word 2003 XML (.xml)" - a rather rare format, but we officially support it. 3. One should be able to save the document and reopen it correctly. The reporter says he gets "Write error" on High Sierra with 4.1.5 (and the file is not saved), while his previous macOS version worked fine with 4.1.5. Note: .odt and .doc work well; only that specific format is problematic. Also note: I couldn't reproduce the issue on Linux. The bug would not be particularly important in itself, but the many build attempts with XML libraries on macOS make this worth checking. Regards, Andrea. __ -- _ 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
Bug on macOS X and Microsoft Word 2003 XML format
A bug has been reported on the Italian mailing list but I'd like to get verification by a Mac user. To reproduce: 1. Be on High Sierra (but it would be useful to check with other versions too; the reporter says everything worked correctly, with OpenOffice 4.1.5, before upgrading to High Sierra). OpenOffice 4.1.5. 2. Create a new text document, write "Test", save as "Microsoft Word 2003 XML (.xml)" - a rather rare format, but we officially support it. 3. One should be able to save the document and reopen it correctly. The reporter says he gets "Write error" on High Sierra with 4.1.5 (and the file is not saved), while his previous macOS version worked fine with 4.1.5. Note: .odt and .doc work well; only that specific format is problematic. Also note: I couldn't reproduce the issue on Linux. The bug would not be particularly important in itself, but the many build attempts with XML libraries on macOS make this worth checking. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Possible new Volunteer
On 12/02/2018 Peter Kovacs wrote: Steve here is volunteering to help. See below. Can someone guide him further? Sure. For documentation see here: https://s.apache.org/bCco - help welcome, and refer to Keith's mail there for some pointers. Also I am not sure about what the exact situation is on donations. What is the current situation here? See https://www.openoffice.org/donations.html - donations welcome, and they go to the Apache Software Foundation, the main expenditure being on the infrastructure that OpenOffice shares with the other ASF projects. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [proposal] going Agile
Marcus wrote: @all: What do you think is the first topic we should start with? I think the only reasonable way forward is that Peter chooses one of the many available tasks (digital signatures? Java 9 support? MSVC update? .docx export? you name it) and experiments the workflow limited to it. Even if it is a relatively small project, one can decompose it in many subtasks: none of these is "too simple" for an experiment. This way the rest of the project can continue as always, while we have a proof of concept that can involve volunteers and so on. Once the proof of concept is completed, it can serve as a model for expanding it. Otherwise my feeling is that we will waste too much time discussing the theory and making it perfect, but getting nowhere in practice. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [proposal] going Agile
Am 12.02.2018 um 22:15 schrieb Peter Kovacs: On 10.02.2018 13:26, Marcus wrote: Therefore let me summarize: - Use BZ for the development work (e.g, fixing a specific bug). - Work in Jira for the project tasks and technical coordination (e.g., Windows signing). - Use Confluence for project work and as documentation base. - Take the Agile Board functions in Jira if it fits for us. - Also we can see what we need to do to claim "We are working along Kanban rules". ok, lets try this. great However I think we should keep an eye on bandwith needs. That is a good point from Damjan. We are not only a first world thing. We are for everyone and everyone that is willing should have a chance to participate. I have seen also in the discussion that we would like to support other Open Source Projects if we can. We should therefor concider that Jira is only a intermediate solution, to be used until we have a replacement in Bugzilla. Do you agree with my observation? Sure, we can try to participate in other projects. However, I thing we have much to do in our own project. PS: I just wantot repeat a sentence from above: I'm not totally pro or contra your proposal. I just want to express my opinion why not everything you've proposed is fitting for us. My priority is to get a better overview of what needs to be done and that we work better together, so we have a better chance in including new people. I will have an eye on topics what volunteers need. I am looking forward that we break those eggs one after another together. I think I did this one wrong, because I started of what I would like to do and got into a confrontation role, which I did not want to. Tooling and Scrum Framework was not in my center of my goals but It was very important in the discussion. I am a real slow and bad learner. I hope no one takes this personal. I am imaptioned. I apologies to myself and to all others for my uttelress clumsyness. Don't worry too much. Many proposals need to be discussed before coming to a common understanding - and an agreement. Thanks for starting this discussion and to try to improve the project with new ideas. I thank you all for the open discussion and the shown courage to speak up. I believe that these are values that make us work together. Even without Scrum. ;) I hope maybe that others are inspired by this and speak up to. You are all Welcome! One good thing in Scrum is: fail fast (do something and stop when it's not working before wasting more money/time). So, let's try to implement some ideas and watch closely if it's worth the effort. @all: What do you think is the first topic we should start with? Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Package name
Hi all, when I look at: https://svn.apache.org/repos/asf/openoffice/trunk/main/setup_native/source/packinfo/packinfo_office.txt the package names look reasonable to me. All except one (copied from the installed DEB package): openoffice-ooofonts - Mailcap module for Apache OpenOffice 4.1.5 Why is a package containing fonts called mailcap module? Regards, Matthias smime.p7s Description: S/MIME Cryptographic Signature
