[www-dev] Re: New Site Up and Running
On 02/25/11 00:06, s...@openoffice.org wrote: Hi, http://openoffice.org now points to the new site. just fyi, not working since last night The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /. Reason: Error reading from remote server The data migration has finished and the infrastructure is ready for us. You will receive a message to activate your account in the next days. For the curious there is http://kenai.com/projects/ooo-migration/pages/QuickHelp Incoming mails are still queued and will be delivered in a day or two. In the meantime problems can be raised at discuss at ooo-migration.kenai.com But outbound mail works fine. More detailed information is available at http://kenai.com/projects/ooo-migration/pages/Home Greetings Stefan -- -- Rich -- To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: sy...@openoffice.org with Subject: help
Re: [dev] Should assertions abort?
Frank Schoenheit, Sun Microsystems Germany wrote: Hi, issue 109142 (http://www.openoffice.org/issues/show_bug.cgi?id=109142) requests to change the behavior of assertions (OSL_ASSERT/DBG_ASSERT and friends) to abort if their condition is not met. The current behavior is that the assertion text is reported to the user, usually by a message box. All of the above applies to non-product builds only, in particular, the request, as I understand it, is *not* to extend assertions to product builds. ... But making assertions abort instead of just being reported would worsen the situation, IMO: We have that many assertions in non-product builds because a) too few developers actually use non-product builds (which means they silently introduce new ones) and b) fixing existing assertions is not a priority [1]. Aborting in case of an assertion would just make a) much worse. Also, it would put the burden onto the shoulders of those actually *using* the non-product builds, not of those *causing* the pain. I.e., it would punish the wrong people. a strong NO to the question in subject. strong support to the opinion expressed in this email, for asserts not to abort. speaking as a user here, not a coder - if software can continue with operating, it should. yes, it should warn me, but it should run as long as possible, either allowing me to save the document, copy data out of it or whatever. i'd like to point out one thing i've noticed in other projects with user vs developer mentality. if a user reports program closing, it is a _crash_ for them. you might call that assert, controlled quit - it does not matter. at all. to the user, software crashed. and that is the last thing i want from any software, especially one i rely some of my most important data ever to. ... -- Rich - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Should assertions abort?
Stephan Bergmann wrote: On 02/12/10 09:30, Rich wrote: speaking as a user here, not a coder - if software can continue with operating, it should. yes, it should warn me, but it should run as long as possible, either allowing me to save the document, copy data out of it or whatever. The irony is, once you have hit a programming error, you can no longer have confidence in the program's behavior. It could happen that the data you still manage to save is subtly corrupted, so subtly that you do not notice immediately. This is indeed a dilemma, and there is no golden way out. That said, in the event of a crash (which would include the abort from an assertion in a non-product build) OOo already tries to save your open documents (and it appears to be somewhat effective at it). i'd like to point out one thing i've noticed in other projects with user vs developer mentality. if a user reports program closing, it is a _crash_ for them. you might call that assert, controlled quit - it does not matter. at all. to the user, software crashed. and that is the last thing i want from any software, especially one i rely some of my most important data ever to. Sure, nobody wants to suffer the consequences of programming errors. However, the software industry happens to be in a state where errors are a frequent reality. The question, then, is how best to carry on once a programming error has been encountered (if the software has the luxury at all to even notice). Fail fast (abort) has the potential to cause the least data loss and the least confusion (the program does not continue running in an uncontrolled state, corrupting the user's data or giving wrong answers to the user). yes, that i can totally agree to. so we should distinguish two things here (which you already did in the previous email). 1. a problem, caused by outside data - opening a corrupted document, image or whatever - should never ever result in closure; 2. a problem inside code. yeah, i understand that often figuring out which one has happened is hard or impossible, but hey :) so we're interested in second category only here. still, i'd argue that software should attempt to let me revive as much of data as possible... it should not carry on ignoring the error, of course. it should popup some message, tell me to save my work and restart it. maybe it should add some nagging bar to inform me about it all the time and motivate to restart it. what i have encountered in oo.org several times - i'm working on 4 or 5 documents at the same time, let's say 3 text documents and 2 presentations. if suddenly a problem arises in presentation code, i definitely do not want it to close and lose my changes to the text documents. i want to be notified and given a chance to check them. while automatic saving for recovery is useful, it is also not easy enough to use and efficient : 1. it seems to ignore the fact that i have saved the document and offers it for restoring as well. that takes more time. 2. after all those files are restored i have to manually check each for differences from the manually saved versions (it is possible that either manually saved or automatically saved version is newer). again, this is cumbersome or near impossible for some types of documents. 3. if one of the input files triggered the failure, oo.org will crash again upon restoring them. yes, theoretically i can recover them manually from profile and remove, or i could hit cancel at first and then save files when prompted (but i am never sure when i will be offered to save them, and there is no way for user to know that there will be such a chance - huge usability problem, imho) while problems with recovery are semi-offtopic, i hope they help to highlight reasons why i'd prefer a chance to salvage the data myself, especially when working on many files of different types. i completely understand the argument about masked failures and data corruption risks. and i can't agree with them enough :) i'm not arguing against being in-your-face about such problems - it's just that i've been burned by such problems with oo.org and other software before, and lost data (or time :) ) Carry on regardless (ignoring the detection that the program has reached an uncontrolled state; what effectively happens when assertions are disabled in production systems) can be considered unacceptable behavior. It potentially leads to corrupting the user's data or giving wrong answers to the user, with the user not being aware that those answers are wrong. Working around the detected *programming error* is probably the best for the user, but, as I outlined in my other response, nothing you can expect to happen in OOo in the near future (probably as unlikely as OOo not having any program errors to begin with). a short summary - i'd prefer working around it only for as long as it would take for me to decide what data i want out and get
Re: [dev] Should assertions abort?
bjoern michaelsen - Sun Microsystems - Hamburg Germany wrote: On Fri, 12 Feb 2010 10:30:59 +0200 Rich ric...@nakts.net wrote: speaking as a user here, not a coder - if software can continue with operating, it should. yes, it should warn me, but it should run as long as possible, either allowing me to save the document, copy data out of it or whatever. We are talking about product builds, so this does not effect and affect (pun intended) end-users. (non-product, i assume ?) oh, it does. if you want any testers at all from the community :) it was discussed almost a year ago on this same mailing list - if you want testers, make test builds usable. of course, if the plan is to use these non-product builds for developers only, then i stand corrected and have no opinion on the issue :) BR, Bjoern -- Rich - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Should assertions abort?
Frank Schoenheit, Sun Microsystems Germany wrote: Hi Rich, (non-product, i assume ?) oh, it does. if you want any testers at all from the community :) it was discussed almost a year ago on this same mailing list - if you want testers, make test builds usable. On the medium run, it indeed might be interesting to give out non-product builds for developer snapshots (perhaps even exclusively). So, we indeed should keep end users in mind when discussing about non-product builds. reading your other build about non-prod builds allowing to find issues sooner, i think that indeed has a potential to increase quality a lot. which reminds me... i stumbled upon a problem where pre-3.3 would corrupt my documents, but 3.1.1 would work just fine. http://www.openoffice.org/issues/show_bug.cgi?id=107775 would trying to reproduce with non-prod allow to find cause for the corruption ? i'm afraid to upgrade to 3.2 because of this issue, i spent two days diagnosing the problem and trying to recover my documents - if i could discover the cause by some additional work, that would motivate me a lot. also... if it would, then i'm back to the strong opinion about oo.org not closing as long as possible to allow me to recover data from non-prod builds, which i might start using on a more regular basis. Ciao Frank -- Rich - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Should assertions abort?
bjoern michaelsen - Sun Microsystems - Hamburg Germany wrote: On Fri, 12 Feb 2010 12:43:29 +0100 Malte Timmermann malte.timmerm...@sun.com wrote: -1 for discussing here whether or not QA should use non-pros, because it IMHO has absolutely no influence on how assertions should behave. And if you want QA to use non-pros, they for sure would give up quite soon when assertions always abort. With assertions being assertions and give up meaning reporting it, thats exactly the desired behavior. nope. not meaning that for sure. give up means stop using anything but some older, proven to be stable, version. just like me. make development versions hard or impossible to use, and nobody will. also, i think question whether qa should use non-prod builds is very on topic - this decision will pretty much determine that. Current situation: - assertions might be anything from a informal I didnt expect this external data to a critical internal state corrupt Desired situation: - assertions are only internal state corrupt messages and should abort - everything else is tracing, logging For example, Frank is claiming his asserts are all serious issues and thus shouldnt be degraded to mere traces. So keeping his asserts as assertions, even if they abort should not scare anyone, right? Best Regards, Bjoern -- Rich - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] BUG REPORT -- Open Office Writer Version 3.1.0
On 2009.10.05. 19:35, Randal South wrote: Dear Ladies and Gentlemen: I was wondering if there is a bug reporter that I can report problems to? I am using Open Office Writer Version 3.1.0 with Sogou, an IME for Chinese characters. Unfortunately Sogou's most of the Chinese characters are not showing up in Open Office. Sogou is specifically written for both Open Office as well as Microsoft office. http://qa.openoffice.org/ooQAReloaded/ooQA-ReportBugs.html you'll have to register first, then you can report new problems. usually it is suggested to search for already reported problems ;) This is a critical error that should be fixed as soon as possible. It limits the functionality of Open Office. Randal South randalso...@att.net -- Rich - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Nice tool for better and faster issue reporting/description
On 2009.09.09. 20:51, Sebastien Plisson wrote: Hi, I thought it could be great to describe issues by just recording a short screencast of what is going on then insert the URL of the recording in the bugzilla entry. The company I work for offer a free-really simple tool to record your screen without installation. Users and developers could use it easily to communicate about their experience with OO. For more information, bookmarklet, etc you can check it at http://www.screenjelly.com What do you think ? flash based. personally, i would not use it for that reason (flash is not in an acceptable state on linux). Sebastien aka PliPli -- Rich - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Please fix these security flaws that could be considered bugs ...
On 2009.04.16. 12:38, Frank Schönheit - Sun Microsystems Germany wrote: Hi Malte, Wrt the wish to automatically remove entries where the document is no longer available: This is not so obvious for me. I sometimes open documents from encrypted containers or network shares which I mount on demand only, or from USB devices, so opening the menu in the wrong time would remove these items (not that I would care about it... ). I wish we'd had a The document ... does not exist anymore. Do you want to remove the entry from the 'Recent Files' list? [Yes] [No] message box for this purpose, raised when the user chose such a not-existent-anymore file. and maybe checking for unavailable files when the menu is opened, and making them visually different (either disabled, or coloured differently). threaded, of course, so that it does not block the menu, but updates it in the background, even while it is open :) Ciao Frank -- Rich - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] amount of stopper / regressions for 3.1 release
On 2009.03.17. 19:56, Mathias Bauer wrote: Hi, Oliver-Rainer Wittmann - Software Engineer - Sun Microsystems wrote: Hi all, Thorsten Ziehm wrote: ... IMHO, we do not find critical problems (show stoppers) in DEV builds very early, only half of them are found early according to my experience. Some data about the show stoppers, which I have fixed in the last days: thinking about time when bugs are found i got reminded about one issue - actually getting the dev/testing builds. i'll admit ignorance about how these things are handled, but that might also help to understand how many possible testers would see it. from my point of view, dev snapshots aren't always available fast enough, and quite often in dev series only every other build is available to public. of course, this means less testing and testing later in the development process. for example, currently supposedly OOO310_m6 is available, public download - m5 supposedly DEV300_m43 is available, public download - m41 ideally, dev snapshouts would be built distributed automatically as soon as possible, and all of them. otherwise testers of development versions will either always come in later in the cycle, or only dedicated qa involved people will do testing, who know where/how to get a more recent dev snapshot - but that probably wouldn't quite qualify as a sufficient real world usage... ISSUE INTRODUCED IN FOUND IN i99822 DEV300m2 (2008-03-12) OOO310m3 (2009-02-26) i99876 DEV300m30 (2008-08-25) OOO310m3 i99665 DEV300m39 (2009-01-16) OOO310m3 i100043 OOO310m1OOO310m4 (2009-03-04) i100014 OOO310m2OOO310m4 i100132 DEV300m38 (2008-12-22) OOO310m4 i100035 SRCm248 (2008-02-21)OOO310m4 This issue is special, because it was a memory problem, that by accident was not detected. Thus, it should not be counted in this statistic. Looking at this concrete data, I personally can say that we find more or less half of the show stoppers early. I'm currently investigating the blocker list. Here's a rough summary: from 77 issues 42 have been introduced before feature freeze (IIRC that was in DEV300_m39). 9 issues are regression on the OOO310 code line, the others still are not classified, but I'm working on it. I will follow up with the complete results later. Interestingly a considerable amount of showstoppers have been present already in 3.0.1, some in 3.0 and a very few even in older versions. Some of them even weren't regressions at all. An interesting problem is http://www.openoffice.org/issues/show_bug.cgi?id=100235 This issue was introduced very early (DEV300_m26 or so), but couldn't be found before we had localized builds. Regards, Mathias -- Rich - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] amount of stopper / regressions for 3.1 release
On 2009.03.13. 12:08, Frank Schönheit - Sun Microsystems Germany wrote: Hi Ingrid, that now bite us, most of them have been found by users or testers *working* with the program. Adding more CWS test runs and so shortening the time for real-life testing will not help us but make things worse. I don't agree. Preventing the integration of bugs earlier in the production phase especially before the integration into the master trunk would give us much more freedom. Now we always need to react on show stoppers and react and react and uh then the release time line is on risk. All that, because the bugs are already in the product. If you instead detect the bugs before they are integrated into the product you can keep cool, refuse the bad CWS and thus not the release is on risk but only the single bad CWS. Hmmm ... difficult. On the one hand, I agree (and this is what you can read in every QA handbook) that finding bugs earlier reduces the overall costs. On the other hand, I suppose (! - that's an interesting facet to find out when analyzing the current show stoppers: found by whom?) that in fact the majority of problems are found during real-life usage. And nobody will use a CWS in real life. So, getting the CWS into the MWS early has its advantages, too. seeing as my bug made the list, i'll chime in. i've reported quite some bugs, absolute majority being found in real life usage. but i'm not the casual user, as i run dev snapshots most of the time, which increases chances of stumbling upon bugs. i'd like to think i'm not the only one who does that ;), so i think this is the group that would find most of the stoppers in real life scenarios (that slipped past automated testing). important factor would be to get as many users (and developers !) as possible doing the same. i think you already have guessed where i'm heading - stability and usability (as in fit for purpose) of dev snapshots. if dev snapshot has a critical problem that prevents me from using it i'll regress to last stable version, and, quite likely, will stay with it for a while. that means i won't find some other bug that will prevent somebody else from using a dev build and finding yet another bug and so on ;) many opensource projects tend to keep trunk relatively stable to increase the proportion of users why stay on trunk, and use trunk themselves. thus breakages are discovered sooner. summary - while release early, release often is very important, stable dev snapshots are as important. Ciao Frank -- Rich - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] amount of stopper / regressions for 3.1 release
On 2009.03.13. 12:37, Frank Schönheit - Sun Microsystems Germany wrote: Hi Rich, summary - while release early, release often is very important, stable dev snapshots are as important. Yes, but how to reach that? In theory, trunk is always stable, since every CWS has undergone tests (before integration) which ensure that it doesn't break anything. Okay, enough laughing. haha. almost got me there :) Finally, that's exactly the problem here: Too many serious bugs slip Dev/QA's attention in the CWS, and are found on trunk only. If we fix that, trunk will automatically be much more stable. Easy to say, hard to do. when i wrote serious problems i meant something similar to a recent issue in a dev build where simply accessing tools-options crashed oo.org. i believe that reducing the amount of such simple to find problems would be a notable step forward, and what's important - these tests should be relatively easy to automate. i'll admit ignorance on current automated testing processes, but stuff that would walk through all menu options (with some advanced custom paths), a repository of testdocs in various formats etcetc. this, of course, correlates with testing process discussions on this thread, which means more work creating tests - but i'm trying to hilight simple problems that somehow slip past this process. i mean, if crash on opening options slipped past it, there aren't enough of these simple checks which, i hope, would take less developer (or even qa) time to develop. if test creation is too complex and there are ways to simplify it, that could be made a priority. such a change would improve long term quality and reduce workload, so it seems to be worth concentrating on. obviously, that's just a small improvement, seen through my lens, which should be viewed in context with other things already mentioned. Ciao Frank -- Rich - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Who can closes an issue[ was: Fwd: [l10n-dev] Spanish version : issue in OLH
On 2008.11.26. 11:55, Nguyen Vu Hung wrote: Hi all, Sorry for duplicate myself but what do you think about this proposal? * trac to IssueZilla! i'm not a dev and i have no say at these issues (pun intended), but to relieve devs from answering this, i'll make a quite educated guess that this is unlikely to say the least ;) first, it would be a massive, massive effort. not something to be undertaken, especially as issuezilla was (relatively) recently upgraded. if devs get annoyed enough, maybe we could see a move to bugzilla one day, but i don't see that one happening in the coming years either. On Thu, Nov 20, 2008 at 2:18 PM, Nguyen Vu Hung [EMAIL PROTECTED] wrote: On Thu, Nov 13, 2008 at 10:50 AM, Caio Tiago Oliveira Well... I'm not sure, but I think Issuezilla has been discontinued, so we shouldn't expect news. I am quite unhappy with what IssueZilla provides. Plus, it is a closed source so we can't extend or change it. trac[1] is widely used among opensource community. A Ticket in trac is equivalent to an Issue in IZ. The workflow of QA process is quite similar to IZ. Another salepoint of trac is that it supports wiki format. trac can also act as an svn. But a problem is that we must install trac in the same server as svn because at the moment, trac cannot read remote svn. trac also has it builtin wiki. I don't know if OOo wiki needs it( of course, wiki format is a big salepoint of trac). [1] http://trac.edgewall.org/ -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] SVN and lineends
On 2008.10.30. 16:06, Eike Rathke wrote: Hi Heiner, On Wednesday, 2008-10-29 19:14:07 +0100, Heiner Rechtien wrote: modifying a .cxx file on Windows, and committing it to SVN, followed by a svn diff -r PREV file, shows me that *the complete* file changed with the commit. Doing a svn diff -r PREV -x --ignore-eol-style file shows me only the changes which I just did. This makes me wonder, because so far, with CVS, we did not have that problem. Even a Lf-only source when edited in MS-Dev did not change line ends, AFAIK. What does cause this change? We use a hacked CVS client inside the Hamburg environment. It kills any CR in a non binary file no matter what. Sigh.. so that MS-Dev editor appears to be still broken in this regard. Shouldn't we set to svn:eol-style property to a reasonable value (native, probably) for all our source files, globally? Probably not, see my previous mail I sent just a minute ago. Reading http://svnbook.red-bean.com/nightly/de/svn.advanced.props.file-portability.html#svn.advanced.props.special.eol-style | Note that Subversion will actually store the file in the repository | using normalized LF EOL markers regardless of the operating system. This | is basically transparent to the user, though. the 'native' style may be a solution to this problem. I wish we could tell SVN to do that always, not only with native style. I hope that works also when committing a file on *ix that was checked out on Windows. Still, the patch scenario mentioned in my previous mail applies. May need some extra care to be taken when applying patches received from Windows users on *ix platforms. one could set pre-commit hook to sed all crlf to lf, but that still wouldn't help any with cross-platform patches. Eike -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] application/octet-stream files in SVN repository
On 2008.10.27. 21:03, Jens-Heiner Rechtien wrote: Stephan Bergmann wrote: svn propget svn:mime-type --depth files svn://svn.services.openoffice.org/ooo/trunk/[EMAIL PROTECTED] shows that all of STLport-4.0.patch STLport-4.5-0119.patch STLport-4.5.patch dos_lineends.patch win32_custom.sh win32_sdk.sh are classified as application/octet-stream (and so, e.g., svn diff on them will not report anything useful). All of them consistently use LF line ends, except for dos_lineends.path, which consistently uses CRLF line ends. Why are all those files, erroneously in my opinion, classified as application/octet-stream? Either these files were flagged as binary files in CVS or the Subversion import file type detection heuristic didn't work, so SVN choosed the save way (import the file as binary). The mime type can be changed, text would be best for the patches and in addition the svn:eolstyle should be set to CRLF. just rambling here... wouldn't 'svn:eol-type native' make the most sense ? Heiner -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Volunteer for #5487
On 2008.10.09. 03:49, Ariel Constenla-Haile wrote: Hola Leandro, Leandro Doctors escribió: Hi I'm interested in helping with #5487[0]. this issue is already assigned to a developer: mod, who implemented the Notes2 functionality for Writer, and he is surely already working on that (if not yet finished!); so you may think about picking another issue (if you're a beginner with OOo core, search for the one with keyword easy2dev). it's status is still set to NEW, though - and it is an ooold issue. so maybe it is worth contacting dev who has it assigned to right now and ask whether any help is needed (yes, i am interested in enhanced functionality in this area ;) ). I have programming skills. How can I contribute? You can start checking the sources and trying to build. Start with http://wiki.services.openoffice.org/wiki/I_want_to_be_an_OpenOffice.org_developer Regards Ariel. Cheers, Leandro [0] http://www.openoffice.org/issues/show_bug.cgi?id=5487 -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] SVN Hooks for formatting
On 2008.10.08. 18:37, Mathias Bauer wrote: bjoern michaelsen - Sun Microsystems - Hamburg Germany wrote: On 10/06/08 09:57, Caolán McNamara wrote: And subversion (like cvs) has a precommit hook that can e.g. reject files with tabs in them. e.g. http://wordaligned.org/articles/a-subversion-pre-commit-hook +1 I would really appreciate such a hook, I just didnt dare to propose this yet. Have Fun, Björn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Sounds good for me also. Perhaps we can use that to also fix the problem with certain Windows editors: they turn line ends of files checked out with Cygwin into garbage. This happens because they add Windows lineends to the Unix line ends instead of replacing them or - even better - switch to an edit mode with Unix line ends. i don't know what i am talking about, but maybe you want 'svn:eol native' ? http://svnbook.red-bean.com/en/1.5/svn.advanced.props.file-portability.html#svn.advanced.props.special.eol-style also http://svnbook.red-bean.com/en/1.5/svn.advanced.props.html#svn.advanced.props.auto might be relevant Ciao, Mathias -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Cross refererencing headings - OO300 RC 1
On 2008.09.20. 12:21, Barnpiece wrote: This feature works fine on headings in new documents. I have an old document which is copied to make new versions each month. Heading 3 (which I do not use) shows up in Crossreference/headings. But Heading 1 and 2 do not. I must have altered something in customising these. What is the definitive setting (or settings) which determine if a Heading is included in the Crossreference/headings list? just guessing here - tools - outline numbering selected styles ? Richard -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] mediawiki extension status
On 2008.07.16. 19:53, Mathias Bauer wrote: Rich wrote: hi. i wanted to ask about the status of mediawiki extension, especially about phase 2 - Provide an extension to OpenOffice.org to load, edit and republish MediaWiki pages with OpenOffice.org (as stated on http://wiki.services.openoffice.org/wiki/MediaWiki_Extension/Project_Scope_Statement). latest meeting, according to http://wiki.services.openoffice.org/wiki/MediaWiki_Extension/Meetings, has been on last meeting 12-Dec-2007 - and last email about mediawiki i could find on [EMAIL PROTECTED] archives was on february this year. sorry for not using [EMAIL PROTECTED], i'm not subscribed there - and i think this extension, if finished, has a huge potential :) We didn't work on loading wiki pages and it is not very probable that this will change in the next months. We are observing what's going on elsewhere wrt. conversion from Mediawiki format to odt, but we are currently not working on an own import filter. If someone is interested in doing so we will give support as much as we can. thanks for the answer. that's a shame, i was very excited about such a feature :) also, maybe it's a good idea to update that wiki page to reflect the current state ? Ciao, Mathias -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] mediawiki extension status
hi. i wanted to ask about the status of mediawiki extension, especially about phase 2 - Provide an extension to OpenOffice.org to load, edit and republish MediaWiki pages with OpenOffice.org (as stated on http://wiki.services.openoffice.org/wiki/MediaWiki_Extension/Project_Scope_Statement). latest meeting, according to http://wiki.services.openoffice.org/wiki/MediaWiki_Extension/Meetings, has been on last meeting 12-Dec-2007 - and last email about mediawiki i could find on [EMAIL PROTECTED] archives was on february this year. sorry for not using [EMAIL PROTECTED], i'm not subscribed there - and i think this extension, if finished, has a huge potential :) -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Development at a Glance - Weekly Update CW09
On 2008.02.29. 16:51, Dieter Loeschky wrote: Hi, here is the weekly update for calendar week 09: http://blogs.sun.com/GullFOSS/entry/development_at_a_glance_weekly42 i'm reading here : Finished: ... Writer: MediaWiki Extension but at http://wiki.services.openoffice.org/wiki/MediaWiki_Extension/Project_Scope_Statement : Current Status draft, not yet approved by sponsors i guess the latter is a bit outdated ? ps. thanks for the weeklies :) Regards, Dieter -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Probable GPL violations - Butler Office Pro
On 2008.01.21. 17:37, weekendadventure wrote: Sun own the copyright of OpenOffice.org. Therefore they are not required to abide to the (L)GPL for code they own. Similarly, they can relicense the code under a different license to whoever they want. They do (own the copyright)? So they got people to do the programming for them through open source and then copyright it and monopolize the ability to hmm. well, actually, they bought stardivision and opensourced staroffice. guess what, it was named openoffice.org... also, could you please enable some standard quoting ? it is very difficult to understand who wrote what :) use it commercially through StarOffice? Hmmm-- and everyone is complaining that a few high school kids are making a few bucks on eBay? I think maybe we should ask Star to release their code... -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Any workaround for auto file extension always on?
On 2008.01.09. 10:38, Frank Schönheit - Sun Microsystems Germany wrote: Hello Joe, The option for Automatic file name extension is to be removed from all file save dialogs as of OOo 2.4: http://qa.openoffice.org/issues/show_bug.cgi?id=73876 As far as I can see, that will also remove any capability to save a file with an arbitrary user-specified extension. Before this change, the user could disable the auto option and type any name.extension in the file name box, and that name would be used verbatim. Once the option is gone (always on), this will be impossible. Actually, I consider this a bug. I tried in a recent OOH680m1 build, and in fact, it is impossible to save a plain text file ending with .csv: You need to choose the Text (.txt) filter in the save dialog, and when you enter foo.csv and press Save, then foo.csv.txt is created. I agree to you that this is a severe limitation. Also, I consider this a regression, and an unwanted side effect of the removal. As far as I know, the intention was that now the dialog should behave as if the Automatic file name extension option is always on. However, when you try this in OOo 2.3.1, then the extension is only added when there is no other extension. Today, the extension is always added, which is merely nonsense, IMO. wouldn't that fail to work with filenames that include dots ? i quite often use filenames like 2008.01.09-something. older versions of oo.org mocked me by replacing 09-something with he extension :) comparing to a list of known extensions doesn't sound too feasible, too - so the proposed solution doesn't seem to work ok with any filename including dots. You should visit IssueZilla, and submit an issue for this. I'd say the request should be to not append an extension if the user already provided one. If you'll report the issue number here, I'll definitely jump in and support your request :) Ciao Frank -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] eis suggestion
hi. i have some very minor feature suggestion for eis that i didn't want to clutter issuezilla with - and rfc821 wasn't on irc ;) i would guess there is some most often performed action by guest user - for me it is almost exclusively Child workspace - Search. maybe it would be worth making it the default page after logging in (or some other page if there are statistics that show other page being the most accessed by that user). -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Invalid export type
On 2007.12.10. 07:06, Linux Mercedes wrote: Rich, As far as I know this is the final 2.3.0. I downloaded the installer from the main site where all the non-nerds =P go to get the distribution. Could you send me a link to issuezilla? Thanks. http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-HowToStart.html --Nathan Rich wrote: On 2007.11.20. 03:35, Nathan Jarus wrote: Hi all, Ok, this is a stupid request, but I was looking at the available export types in Windows OO2.3 and I noticed the type - which I proceeded to try to export my document as. It closed the dialog, and after a moment notified me that I had exported it with an invalid parameter.So what exactly is the purpose of type --? And couldn't we just take it out, to make it easier for users? hmm. is that final 2.3.0 version of oo.org ? i guess that's simply a separator, and i could not select it using m235 on linux. if you can reproduce it with latest snapshots and can't find a report in issuezilla, it's probably worth filing one. Thanks, Nathan -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Invalid export type
On 2007.11.20. 03:35, Nathan Jarus wrote: Hi all, Ok, this is a stupid request, but I was looking at the available export types in Windows OO2.3 and I noticed the type - which I proceeded to try to export my document as. It closed the dialog, and after a moment notified me that I had exported it with an invalid parameter.So what exactly is the purpose of type --? And couldn't we just take it out, to make it easier for users? hmm. is that final 2.3.0 version of oo.org ? i guess that's simply a separator, and i could not select it using m235 on linux. if you can reproduce it with latest snapshots and can't find a report in issuezilla, it's probably worth filing one. Thanks, Nathan -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Where to download old OOo versions ?
some mirrors do carry some of the older versions, for example, ftp://ftp.nluug.nl/pub/office/openoffice/stable/ has 2.0.4. how to tell which mirror has which versions i have no idea :) On 2007.10.10. 12:22, PA Galmes wrote: Hello, for some tests purposes, I need to download OOo 2.0, 2.0.1, 2.0.2... Does somebody knows where to find those versions ? On the download mirrors, it seems that only 2.1, 2.2, 2.2.1 and 2.3 are accessible. Regards, -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Development at a Glance - Weekly Update gone ?
where have Development at a Glance - Weekly Update series gone ? they provided nic overview of what's going on - in a user-friendly way :) is this a matter of vacation, will there be future weekly updates ? -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] 470 versions in issuezilla, can we drop a couple of hundred ?
On 2007.06.22. 16:45, Caolan McNamara wrote: There are 470, four hundred and seventy! versions listed by issuezilla for e.g. tools. Can we cull these to at least remove all the milestones current - 5, and consider dropping the release candidates and the 1.0.X releases. this would be awesome. i've mentioned this a couple of times here and there, but that lead to nothing :) it's not like anybody would accept a bugreport for 99% of those versions anyway... and it is a pain to find the correct version in a huge dropdown. thanks for bringing this up again :) Who's the contact for the versions, collabnet ? C. -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Renaming #openoffice.org into #dev.openoffice.org?
i'm no dev, but +1 :) Caio Tiago Oliveira wrote: Pavel Janík, 17-01-2007 18:31: Hi, ... renaming current #openoffice.org channel to #dev.openoffice.org ... What about the #users.openoffice.org? #openoffice.org would be for general talking (including to support users) and we would still having a #users.openoffice.org or it would be dropped? currently, the users channel is surprisingly inactive. scattering users even more would not be good - maybe if in the future it gets overcrowded, a split could happen. also, as ain mentioned, a pretty large percentage of questions are above average difficulty level, and, in my opinion, too many of them stay unanswered. ... -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Calc, disable saving in Excel 5/95 format?
Andreas Schlüns wrote: ... If that is fine for you I could tell you how you can deploy this change as an extension. Of course packages are the best way to make such changes. Because the share layer will might be changed if the next update will be installed (!) ... your changes there will be lost then. A package can be installed using Tools-Extension Manager Please use the attached file to disable the MS Excel 5.0 filter. it seems attachment was stripped, as usual - maybe you could put it up for download somewhere ? If you wish to make changes inside the package, you can unzip it (internaly it's a normal zip file). Open the XCU file and edit it. Ciao, Mathias Ciao Andreas -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fwd: [dev] Announcement: OpenOffice.org Premium 2.0.3 has released
hmm. and there i was, thinking that was irony... in the end you will be left with a single, blank image probably :) KAMI wrote: CPHennessy írta: On Wed August 30 2006 13:05, srinivasa rao gantenapalli wrote: Hi Kami, Frankly, to me what ever you have written here doesn't make any sense. I guess I made my point clear. Either add an Indian map that is recognized by Indian government or don't include any Indian map. You have another option, face the law when someone sues you. And remove Nazi symbols (as they are illegal in many European countries), and images which are illegal in Israel, and then you have those images or words which many feel are immoral. I see, I will remove they... -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Memory consumption of X server
Thorsten Behrens wrote: Francis Giraldeau [EMAIL PROTECTED] writes: I search settings that will save Xorg memory usage. OpenOffice seems to use a huge amount of ram, through X server, in some situations (for example, printing with transparency). Yes, thats true - transparency is emulated by rendering the affected portions of the page into a bitmap. Search for 'ReduceTransparency' in the OOo configuration (Common.xcs), and set that to true. The underlying reason for this (mis)behaviour is that our bitmap implementation keeps the Pixmap around, once one's there. And unfortunately, during printing, at lot of those bitmaps are generated per page. This is generally fixable, though not particularly easy. this seems very similar to issue i filed some time ago : http://qa.openoffice.org/issues/show_bug.cgi?id=44069 unless this is a completely different thing, why the same file shows no such problem with 1.1.* versions ? First, you might try these three configuration settings: ReduceBitmaps ReducedBitmapResolution ReducedBitmapIncludesTransparency (also in Common.xcs, and on the UI via Tools-Options-Print) HTH, -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fwd: [dev] Announcement: OpenOffice.org Premium 2.0.3 has released
srinivasa rao gantenapalli wrote: Hi Kami, Frankly, to me what ever you have written here doesn't make any sense. quite an arrogant position... I guess I made my point clear. Either add an Indian map that is recognized by Indian government or don't include any Indian map. You have another option, face the law when someone sues you. on what basis ? you know, being polite and reasonable can achieve much more than threatening to sue. want to provoke a slashdot discussion titled oo.org sideproject threatened to sue over a map ? -Srini On 8/30/06, KAMI [EMAIL PROTECTED] wrote: ... Could you please provide the correct version of map? These maps come from fr.openoffice.org team's map projects. Please report this problem to they. I will solve this problem at least by delete, but I am more happy If we have the correct version. Also you can report this error to our bugtracking system (for OOo Premium related issues) here: http://sourceforge.net/tracker/?group_id=170021atid=852678 What is current state of Kashmir? I read from Wikipedia: http://en.wikipedia.org/wiki/Kashmir http://en.wikipedia.org/wiki/India http://en.wikipedia.org/wiki/Jammu_and_Kashmir Government Flag of Jammu and KashmirThe Indian Constitution grants Jammu and Kashmir special autonomous status as a temporary provision ; however some Kashmiri political parties demand greater autonomy and sovereignty. Jammu and Kashmir has a multi party democratic system of governance. Main political parties include the National Conference,the Indian National Congress (INC) and the Jammu and Kashmir People's Democratic Party (PDP). Presently, Indian National Congress and its ally PDP hold the maximum number of seats in the Jammu and Kashmir state assembly. After Mufti Mohammed Sayeed of the PDP completed his third year as Chief Minister, as per the power sharing agreement between the PDP-Congress alliance reached in late 2002, Congress leader Ghulam Nabi Azad replaced Mufti on November 2005. This section is a stub. You can help by adding to it. KAMI Regards, Srinivas ... -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] upgrading oo.org on windows
our windows support person has told me that it is not possible to easily upgrade oo.org, keeping all configuration, user data and so on - without uninstalling oo.org. with linux systems that use rpm, this is handled very easily, with others it can be achieved by scripting. could somebody provide pointers how to perform automated update of oo.org (for example, from 2.0.0 to 2.0.3) using provided msi packages ? -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Re: Build ID INSANITY...
Charles Marcus wrote: .. Regardless - please, just put the Build Number in the 'About' window like every other piece of software I've ever used does it. this has been brought up a lot of times. more or less everybody agrees that this dialog is suboptimal and then it all goes away. there issues about this, the collective one would probably be this : http://www.openoffice.org/issues/show_bug.cgi?id=11465 one that deals with more precise version numbers : http://www.openoffice.org/issues/show_bug.cgi?id=58850 Charles -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] New OO-Api wrapper noa
Haris Peco wrote: .. it doesn't work with gtk (gnome), but it is OO bug - simple OfficeBean doesn't work on gnome to There is plugin for eclipse and i try it - it work fine except this OO bug for Gnome plugin is on same page ubion.ion.ag if you have gnome desktop call this export SAL_USE_VCLPLUGIN=kde or oh. thanks for this one ;) i had no idea qt bindings were available in oo.org. maybe we'll get a single kde-integration package as well someday ? :) turns out it's not the gtk theme that has been fixed (on my slackware box it still flickers and doesn't work properly), it's that qt theme is available. even though it seems to have slightly bigger objects (fonts, icons), i might try migrating to it from generic widgets that i like a lot :) somehow i missed this, if it was announced. thank you, oo.org developers :) export SAL_USE_VCLPLUGIN=gen -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Snapshots
go to download from the main site, choose your operating system and any one site. click on non-javascript download. find a good mirror, navigate to ../../developer and see what builds are available. m139 was available on most mirrors yesterday :) Matt Needles wrote: Will someone please direct me to the URL with links to latest snapshot binaries. I want to keep testing these. Thanks! Matt -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Snapshots
well, just as any previous dev build of oo.org final ;) you get a bunch of rpms (yep, i dislike them somewhat...) that you just have to install either by native/not so native rpm tool or convert them to some useful format. there are instructions available for most distributions online. Matt Needles wrote: Thanks Rich and Joost! Now if I can just figure how to install it:) Matt -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] memory usage debugging
i have a running oo.org instance that is, in my opinion, taking somewhat too much memory (it has no documents or components open). is there any way to determine what uses the memory and would this information be useful ? i would be thankful for a fast answer, if possible, as i intend to kill it soon ;) PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 17225 rich 15 0 320m 144m 20m S 0.0 29.3 21:32.05 soffice.bin -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] OpenOffice.org 2.0 Release Candidate
which dev build does this rc correspond to ? Louis Suarez-Potts wrote: All, OpenOffice.org 2.0 has gone from being a Beta to a Release Candidate .. -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
