Re: Sidebar for Developers
Hello, > From: Andre Fischer [mailto:awf@gmail.com] > Yes, exactly. If you have an idea for a demo panel and can > design the > dialog then I can wrap a Java extension around it. > > -Andre It took a long time but here is my example, a simple search for writer. Can you please help me now? The complete example-extension can be found here: http://calc-info.de/files/demo_textsuche.oxt Here is the dialogue: http://openoffice.org/2000/dialog"; xmlns:script="http://openoffice.org/2000/script"; dlg:id="dlg_textsuche" dlg:left="243" dlg:top="165" dlg:width="178" dlg:height="180" dlg:closeable="true" dlg:moveable="true" dlg:title="Demo_Textsuche"> Greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [VOTE]: Release Apache OpenOffice 4.0.1 (RC3)
Considering that: 1. The first two defects[1] are regressions introduced in AOO 4.0 and not AOO 4.0.1 release blockers 2. The installation defect[1] on Redhat6.4 64bit has workaround I agree to release AOO401rc3 (a.k.a. r1524958) as Apache OpenOffice 4.0.1. [1] Bug 123345 - [Regression]Docx embedded table display incorrectly Bug 123346 - [Regression]the bullet display incorrectly when open docx file in AOO Bug 123348 - Cannot integrate AOO 4.0.0 in desktop menu in Redhat6.4 64bit Regards, Yu Zhen On Thu, Sep 26, 2013 at 4:38 PM, Shenfeng Liu wrote: > 2013/9/26 Rob Weir > > > On Wed, Sep 25, 2013 at 8:55 AM, Oliver-Rainer Wittmann > > wrote: > > > Hi, > > > > > > resending as my "reply to list" goes only to qa@o.a.o > > > > > > > > > On 25.09.2013 12:17, Yuzhen Fan wrote: > > >> > > >> -1: > > >> > > >> I vote -1 for RC3 because of these 3 issues, the first two are > function > > >> regressions from 3.4.1 and 4.0.0, the last one is for bad user > > experience > > >> on Redhat 64bit installation. > > >> > > >> Bug 123345 - [Regression]Docx embedded table display incorrectly > > >> Bug 123346 - [Regression]the bullet display incorrectly when open docx > > >> file > > >> in AOO > > >> Bug 123348 - Cannot integrate AOO 4.0.0 in desktop menu in Redhat6.4 > > 64bit > > >> > > > > > > I can confirm that 123345 and 123346 are regressions which had been > > > introduced in AOO 4.0.0 > > > > > > > So these are not new defects in 4.0.1? > > > > I confirmed that the 2 defects are also in 4.0. Then I agree that they are > not 4.0.1 ship blocker. > > - Shenfeng (Simon) > > > > > > > On the one hand I agree that regressions introduced in the latest > release > > > should be fixed in the next release. > > > On the other hand we are already quite far in our planned AOO 4.0.1 > > release > > > schedule and AOO401rc3 contains a lot of important bug fixes and > > > improvements regarding our supported languages. Thus, I strongly vote > for > > > releasing AOO401rc3 as AOO 4.0.1 under these circumstances. > > > From my point of view 123345 and 123346 should be release blocker for > our > > > next release. > > > > > > > It is important that we understand the different role of a minor x.y.1 > > release. > > > > When we have a major release, like 4.0.0, we're making tons of code > > changes, adding new features, and potentially (and very likely > > actually) introducing many regressions. So the QA effort for a major > > release has many aims: > > > > -- test new features > > -- verify new fixes > > -- identify the regressions introduced in the code > > > > We can never test 100% of a product. Maybe computer-based proofs of > > correctness have been done in some chip designs, but generally > > complete coverage is never possible. So we focus on the most-commonly > > used features of the product, across a large matrix of platforms and > > applications. > > > > The goal, if you think about it is: to increase the confidence that > > we are *not* releasing a product that has a bug in it that will make > > it unusable for our users. > > > > We can never guarantee this. We can only increase our confidence in > > this. At whatever finite point we stop our testing it is always > > possible that the next test would have found a killer defect. So the > > challenge in designing a test plan is to identify what tests can be > > performed in a reasonable finite test pass (or passes) that will > > reduce the chances of a killer defect still being in the code. I > > think Yuzhen did a great job at designing the test plans for the > > releases. > > > > The quality approach in a minor maintenance release like 4.0.1 is > > different. We don't make tons of code changes. In fact we are very > > restrictive. We only fixed showstopper bugs that were proposed on the > > mailing list, discussed and approved by the Release Manager. The goal > > is have no new regressions introduced. The goal is to fix targeted > > bugs, and get those fixes out to users quickly. If we didn't think > > that speed of release was an important thing here then we would all be > > working on 4.1.0, not 4.0.1. So the fact that we are working on 4.0.1 > > at all shows that there is some urgency to get bug fixes released. > > > > In any case, if new bugs are found in 4.0.1 testing, I don't think it > > matters whether they were found in RC1, RC2, RC3, during the vote or > > the day after the vote. It doesn't matter who discovered the bug or > > when they discovered it. The question is: How severe is the defect? > > Is it a showstopper? Is it something we hold back 4.0.1 for? Or > > something less severe that we put in 4.1.0? > > > > > > > Regarding issue 123348: > > > As far as I know this issue is not new and already known. I think a > > > workaround exist. Thus, for me this is not a release blocker. > > > > > > Yu Zhen, do you think you can change your mind regarding your vote? > > > > > > > I don't think we should ask anyone to change their votes. A
Re: bug 107063 (needs update)
On Wed, Sep 25, 2013 at 8:41 AM, Regina Henschel wrote: > Hi, > > bugreporte...@hushmail.com schrieb: > >> Stop! Don't invoke the bugzilla guru. >> Looks like I made it. Will invastigate farther. >> That's what I use now: >> http://img18.imageshack.us/i/vk57.png/ >> >> Are there other assignees we should exclude? >> > > You can use the criterion "Time Since Assignee Touched" "is greater than" > "900d". > > Exclude assignee secur...@openoffice.apache.org from search. > > Have you count, how many issues are affected? For example, with >900d I get > 322 bugs. With >360d and restriction to 99000 which is 7%. So expand to more than 12 issues gives perhaps about 8000 > matches. Other complex queries I have tried need so long, that I have not > wait. I guess, that a direct SQL search in the data base can use more > efficient search statements than using the UI. > > I like, that former, inactive assignees are reset to the new default. But > such bulk change needs, that the general notifications are suppressed. I > don't know, whether it is possible to only inform the assignees. So please > wait till it is morning for Rob and he has a change to read this. > Notifications are all-or-nothing. A BZ admin can disable all notifications, run a batch operation, and then re-enable notifications. But we have no easy way to notify only assignees. Back in July I reset the assignment for all issues that had not changed in more than 2000 days. 543 issues were reset in that action. I've also done other resets for issues assigned to defunct openoffice.org, novell.com, sun.com and oracle.com email addresses. There may be others that could be reset as well, but I'm not sure it really helps anything. As a practical matter, no active developer will avoid fixing an issue just because it is assigned to someone else who is not longer active. We all know who is active and who isn't. And even if we did reset everything to the default, and only had currently active developers make self-assignments, this information would be out of date again within a year. Unless someone wants to monitor and remind developers and testers on an ongoing basis, the database reverts to its natural chaotic state. Things that need constant reminding: 1) Unconfirmed issues need to be tested and either confirmed or closed 2) Unconfirmed issues where we are waiting for more information from the user -- if the user does not respond we need to close the issue 3) Issues that are targetted to be fixed in a given release but are not -- these need to have their target set back to the default 4) Issues that are marked as fixed in a release need to be tested and marked as resolved if they are actually fixed. As a BZ Admin I can help get us to a "clean slate" on some of these items, but we really need someone (or a group of volunteers) to take the lead on maintaining the quality of the BZ issues by reminding/nagging the rest of us to keep our issues up to date. There are a lot of report and charting options in BZ, but it requires some knowledge to make the most of them.I'm happy to help get someone started on this if anyone is interested. Regards, -Rob - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
draft 4.0.1 announcement blog post
https://blogs.apache.org/preview/OOo/?previewEntry=announcing_apache_openoffice_4_0 Short and direct. Is there anything else worth mentioning, from a project perspective? I tried to avoid simply repeating what the release notes already say. If I understand correctly we'll go live with the announcement on Tuesday. So we'll want to ensure the website download page is ready first. -Rob - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: draft 4.0.1 announcement blog post
Does that need to be "MS Excel"? On Thu, Sep 26, 2013 at 11:02 AM, Rob Weir wrote: > > https://blogs.apache.org/preview/OOo/?previewEntry=announcing_apache_openoffice_4_0 > > Short and direct. > > Is there anything else worth mentioning, from a project perspective? > I tried to avoid simply repeating what the release notes already say. > > If I understand correctly we'll go live with the announcement on > Tuesday. So we'll want to ensure the website download page is ready > first. > > -Rob > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: draft 4.0.1 announcement blog post
On Thu, Sep 26, 2013 at 11:27 AM, Donald Whytock wrote: > Does that need to be "MS Excel"? > It should, yes. I'll correct. -Rob > > On Thu, Sep 26, 2013 at 11:02 AM, Rob Weir wrote: > >> >> https://blogs.apache.org/preview/OOo/?previewEntry=announcing_apache_openoffice_4_0 >> >> Short and direct. >> >> Is there anything else worth mentioning, from a project perspective? >> I tried to avoid simply repeating what the release notes already say. >> >> If I understand correctly we'll go live with the announcement on >> Tuesday. So we'll want to ensure the website download page is ready >> first. >> >> -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
Re: New AOO 4.0 review article (PC World)
On Wed, Sep 25, 2013 at 4:49 PM, Rob Weir wrote: > > http://www.pcworld.com/article/2048446/apache-openoffice-4-0-review-new-features-easier-to-use-still-free.html > > Title is "Apache OpenOffice 4.0 review: New features, easier to use, still > free" > > Does someone want to work on the pseudo-Victorian dictionary? There might be demand for a language pack that includes "programmetry" and "'pon". Don
Any good bug fixing stories for 4.0.1
For more "human interest" for the announcement blog post. Does anyone have a good story about one or more of the bug fixes? For example, did anyone work with a user who did us a service by making an extra effort to help us reproduce and narrow down a defect? Any interesting technical lessons from a bug fix? Any good stories of clever debugging that lead to a fix? Please share a few sentences if you have a good story. Thanks! -Rob - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Windows 64 bit and printers
On Thu, Sep 19, 2013 at 9:51 PM, Raphael Bircher wrote: > Hi Rob, * > > Am 20.09.13 03:35, schrieb Rob Weir: > >> On Sep 19, 2013, at 6:09 PM, Rory O'Farrell wrote: >> >>> I cannot remember if I asked this before or not. >>> >> You did ask before, and I responded that I've had no problems printing >> to an networked HP color Laserjet from 64-bit Windows 8. >> >> So there is likely a more complicated reason for these other reports, >> unfortunately > > Rob, is your driver 64 bit or 32 bit? Without doing a Test right now, this > could be a problem. Maybe AOO can communicate with 32 bit driver, but not > with 64 bit. Or we have only a problem with same 64 bit drivers. > I assume it is a 64-bit driver. It is a recent model HP color laser, running on Windows 8 64-bit. Is there any way to tell whether it is 64-bit or 32-bit? I look at the driver properties dialogs and didn't see anything relevant. -Rob > Greetings Raphael > > > - > 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: draft 4.0.1 announcement blog post
Am 09/26/2013 05:02 PM, schrieb Rob Weir: https://blogs.apache.org/preview/OOo/?previewEntry=announcing_apache_openoffice_4_0 Short and direct. Is there anything else worth mentioning, from a project perspective? I tried to avoid simply repeating what the release notes already say. To mention the "MS Excel export improvement" is really important as it was (one of) the topic with the highest number of reported 4.0.0 issues (with 6 duplicates and 9 votes). If I understand correctly we'll go live with the announcement on Tuesday. So we'll want to ensure the website download page is ready first. Yes, let me check on Monday evening (Hamburg time) if it's already working. Then we can do the public announcement on Tuesday with working download links. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Building for MAC OS, gcc 4.0
Following the Building guide for MAC, I need help. My gcc version is 4.2, and the configure script outputs a warning that it needs 4.0. Is it a blocker? Do I need to install another gcc? > ... checking the GNU gcc compiler version... configure: error: You need to use > the gcc-4.0 compiler (gcc 4.2.1 won't work with the MacOSX10.4u.sdk) - set > CC accordingly > Guide I'm following step-by-step: http://wiki.openoffice.org/wiki/Documentation/Building_Guide/Building_on_MacOSX I'd be glad if someone can be a guide on the build process, because I'm a bit lost from the autoconf step onwards. Thanks, Tal
Re: bug 107063 (needs update)
>> You can use the criterion "Time Since Assignee Touched" "is >>greater than" Did not see that thanks. >Back in July I reset the assignment for all issues that had not >changed in more than 2000 days. Today is September 26, 2013 so that means that 2000 days before today would be April 5, 2008. [1] Can you please tell me why the assignee of the issue https://issues.apache.org/ooo/show_bug.cgi?id=20525 was not reset? Cause when looking at the History there is nothing after 2004-06-17 15:00:01 UTC (besides a comment on 2007-05-03 12:24:50 UTC ). Can you please tell me how to find bugs of a certain assignee? I want to get all bugs listed which are from the assignee ooo . When (in the Advanced Search) I select "Assignee" in "Custom Search" and choose "is equal to" and then set the value to ooo it does not work. Using "is equal to any of the strings" instead of "is equal to" does not work as well -> ? Trying to use regular expression and typing ^ooo$ does also not work. (^ooo works but then I get also things like ooo*) >We all know who is active and who isn't. Did not know that. >Notifications are all-or-nothing. A BZ admin can disable all >notifications, run a batch operation, and then re-enable >notifications. But we have no easy way to notify only assignees. What would happen if you leave the notification enabled and then reset all the assignee fields? thx [1]http://www.convertunits.com/dates/daysfromnow/-2000 On 26.09.2013 at 3:39 PM, "Rob Weir" wrote: > >On Wed, Sep 25, 2013 at 8:41 AM, Regina Henschel > wrote: >> Hi, >> >> bugreporte...@hushmail.com schrieb: >> >>> Stop! Don't invoke the bugzilla guru. >>> Looks like I made it. Will invastigate farther. >>> That's what I use now: >>> http://img18.imageshack.us/i/vk57.png/ >>> >>> Are there other assignees we should exclude? >>> >> >> You can use the criterion "Time Since Assignee Touched" "is >greater than" >> "900d". >> >> Exclude assignee secur...@openoffice.apache.org from search. >> >> Have you count, how many issues are affected? For example, with >>900d I get >> 322 bugs. With >360d and restriction to 99000get 70 bugs, >> which is 7%. So expand to more than 12 issues gives perhaps >about 8000 >> matches. Other complex queries I have tried need so long, that I >have not >> wait. I guess, that a direct SQL search in the data base can use >more >> efficient search statements than using the UI. >> >> I like, that former, inactive assignees are reset to the new >default. But >> such bulk change needs, that the general notifications are >suppressed. I >> don't know, whether it is possible to only inform the assignees. >So please >> wait till it is morning for Rob and he has a change to read this. >> > >Notifications are all-or-nothing. A BZ admin can disable all >notifications, run a batch operation, and then re-enable >notifications. But we have no easy way to notify only assignees. > >Back in July I reset the assignment for all issues that had not >changed in more than 2000 days. 543 issues were reset in that >action. I've also done other resets for issues assigned to defunct >openoffice.org, novell.com, sun.com and oracle.com email addresses. > >There may be others that could be reset as well, but I'm not sure >it >really helps anything. As a practical matter, no active developer >will avoid fixing an issue just because it is assigned to someone >else >who is not longer active. We all know who is active and who isn't. >And even if we did reset everything to the default, and only had >currently active developers make self-assignments, this information >would be out of date again within a year. Unless someone wants to >monitor and remind developers and testers on an ongoing basis, the >database reverts to its natural chaotic state. > >Things that need constant reminding: > >1) Unconfirmed issues need to be tested and either confirmed or >closed > >2) Unconfirmed issues where we are waiting for more information >from >the user -- if the user does not respond we need to close the issue > >3) Issues that are targetted to be fixed in a given release but are >not -- these need to have their target set back to the default > >4) Issues that are marked as fixed in a release need to be tested >and >marked as resolved if they are actually fixed. > >As a BZ Admin I can help get us to a "clean slate" on some of these >items, but we really need someone (or a group of volunteers) to >take >the lead on maintaining the quality of the BZ issues by >reminding/nagging the rest of us to keep our issues up to date. >There are a lot of report and charting options in BZ, but it >requires >some knowledge to make the most of them.I'm happy to help get >someone started on this if anyone is interested. > >Regards, > >-Rob > >--- >-- >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: bug 107063 (needs update)
On Thu, Sep 26, 2013 at 4:50 PM, wrote: >>> You can use the criterion "Time Since Assignee Touched" "is >>>greater than" > Did not see that thanks. > >>Back in July I reset the assignment for all issues that had not >>changed in more than 2000 days. > > Today is September 26, 2013 so that means that 2000 days before today would > be April 5, 2008. [1] > Can you please tell me why the assignee of the issue > https://issues.apache.org/ooo/show_bug.cgi?id=20525 was not reset? > Cause when looking at the History there is nothing after 2004-06-17 15:00:01 > UTC (besides a comment on 2007-05-03 12:24:50 UTC ). > I used the "time since assignee touched" field. It looks like in this case the assignee changed his email address. I don't know if that impacted the query strategy. But you can find all the issues that I did reset by searching for the comment string "Reset assignee on issues not touched by assignee in more than 2000 days." > Can you please tell me how to find bugs of a certain assignee? > I want to get all bugs listed which are from the assignee ooo . > When (in the Advanced Search) I select "Assignee" in "Custom Search" and > choose "is equal to" and then set > the value to ooo it does not work. Using "is equal to any of the strings" > instead of "is equal to" does > not work as well -> ? > I'd use the "Search by People" section. The first of the three groups there is already set up to search for assignee. One of the search options is for "contains", so you can then just enter "ooo". > Trying to use regular expression and typing ^ooo$ does also not work. (^ooo > works but then I get also things like ooo*) > If you use the advanced search options then you need to select "matches regular expression" rather than "is equal to". >>We all know who is active and who isn't. > Did not know that. > >>Notifications are all-or-nothing. A BZ admin can disable all >>notifications, run a batch operation, and then re-enable >>notifications. But we have no easy way to notify only assignees. > > What would happen if you leave the notification enabled and then reset all > the assignee fields? > It would not be pretty. It would trigger notifications to be emailed to the old assignee, but also everyone that commented on the issue previously, or added themselves to cc. So a rough guess, for N old issues you would generate 4x email notifications. Doing this for a handful, 10 or 20 issues is fine. But not for thousands. If you do this you will end up owing Scotch to Apache Infra admins for the extra work they have to do to clean up the mess ;-) Regards, -Rob > thx > > [1]http://www.convertunits.com/dates/daysfromnow/-2000 > > On 26.09.2013 at 3:39 PM, "Rob Weir" wrote: >> >>On Wed, Sep 25, 2013 at 8:41 AM, Regina Henschel >> wrote: >>> Hi, >>> >>> bugreporte...@hushmail.com schrieb: >>> Stop! Don't invoke the bugzilla guru. Looks like I made it. Will invastigate farther. That's what I use now: http://img18.imageshack.us/i/vk57.png/ Are there other assignees we should exclude? >>> >>> You can use the criterion "Time Since Assignee Touched" "is >>greater than" >>> "900d". >>> >>> Exclude assignee secur...@openoffice.apache.org from search. >>> >>> Have you count, how many issues are affected? For example, with >>>900d I get >>> 322 bugs. With >360d and restriction to 99000>get 70 bugs, >>> which is 7%. So expand to more than 12 issues gives perhaps >>about 8000 >>> matches. Other complex queries I have tried need so long, that I >>have not >>> wait. I guess, that a direct SQL search in the data base can use >>more >>> efficient search statements than using the UI. >>> >>> I like, that former, inactive assignees are reset to the new >>default. But >>> such bulk change needs, that the general notifications are >>suppressed. I >>> don't know, whether it is possible to only inform the assignees. >>So please >>> wait till it is morning for Rob and he has a change to read this. >>> >> >>Notifications are all-or-nothing. A BZ admin can disable all >>notifications, run a batch operation, and then re-enable >>notifications. But we have no easy way to notify only assignees. >> >>Back in July I reset the assignment for all issues that had not >>changed in more than 2000 days. 543 issues were reset in that >>action. I've also done other resets for issues assigned to defunct >>openoffice.org, novell.com, sun.com and oracle.com email addresses. >> >>There may be others that could be reset as well, but I'm not sure >>it >>really helps anything. As a practical matter, no active developer >>will avoid fixing an issue just because it is assigned to someone >>else >>who is not longer active. We all know who is active and who isn't. >>And even if we did reset everything to the default, and only had >>currently active developers make self-assignments, this information >>would be out of date again within a year. Unless someone wants to >>monitor and remind develo
Re: A little more eye candy for 4.0.1 release
On Sun, Sep 22, 2013 at 2:14 PM, Drew Jensen wrote: > Hi, > > Added a couple of wallpaper and web art images to the wiki at: > > > https://cwiki.apache.org/confluence/download/attachments/34022580/AOO-4_0_1-wallpaper.zip > and > > https://cwiki.apache.org/confluence/download/attachments/34022580/AOO-4_0_1-web_art.zip > > Let me know if any of this can be used - The wallpaper files are 100% dog > food, the web art files in BLUE are straight dog food and the others > included a little love from GIMP > > I tagged two of the wallpaper files with a CC BY_ND license. I did so for > only one reason, I did not want to introduce the new graphics on these two > pieces and encourage their use as branding items and the license would > allow any use, including commercial, but you can not 'riff' off that image > or any pieces of it.. Now, it doesn't make sense to others here I would not > be surprised and have no problem removing it. Just let me know. > > Otherwise, I'll be on-line tomorrow again and will update the other files > then along with some more thoughts on the branding language I'm trying to > establish...which I don't want to do without consent here. > > Thanks, > > //drew > These are cute! I'm sure someone will have some fun with them. :) -- - MzK "Truth is stranger than fiction, but it is because Fiction is obliged to stick to possibilities. Truth isn't." -- "Following the Equator", Mark Twain
Re: Reminder: Time to update your entry in the Directory of Volunteers
Николай Нинков wrote: > Because the translation of Bulgarian is almost ready, please do for me a dev > snapshot with the Bulgarian translation to carry out the necessary tests. > I do not want to promise but I will try to handle the tests so that you turn > the Bulgarian translation in the new Release 4.0.1. I have to admit that I don't know how get a *sdf file out of pootle. But if someone can provide me with the latest *sdf file for Bulgarian I'd volunteer to do a snapshot build for it. I extend that offer also for Danish as that just got ready. The builds would be quite similar to the soon to be expected AOO 4.0.1, but only similar because the revision number approved for the official 4.0.1 release would not have the latest *sdf files. I look forward to the near future when we'll be able to skip the SDF step and use the pootle files directly. > Wish me success. I wish you a lot of success! ;-) Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Where can I find the new AOO4-Logo as a vector format?
Hello, I need a scalable format of the new AOO4 logo, where can I find it? Greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
