Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | OpenOffice.org mime types are rejected as attachments | ||
---|---|---|---|
Product: | Infrastructure | Reporter: | Frank Schönheit <frank.schoenheit> |
Component: | Bugzilla | Assignee: | Unknown <non-migrated> |
Status: | CLOSED FIXED | QA Contact: | issues@www <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, lohmaier, stx123 |
Version: | current | Keywords: | oooqa |
Target Milestone: | CEE Rubicon | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
Frank Schönheit
2002-09-09 07:48:30 UTC
Hi IZ is just an app. to implement this enhancement would take a very long time, as it is not, afaik, on the roadmap. closing with wontfix. louis Sorry, I do not really see your point. I understand that Issuezilla is "just an app", but I do not see how this contradicts the possibility to be enhanced. Furthermore, "would take a long time 'cause it's not on the roadmap" is not really satisfying. I continue to think that IssueZilla should integrate seemless with OpenOffice.org (finally, IssueZille is _about_ OpenOffice.org), and the need to save my .sxw attachements (or click away some dialog every time, or associate such a generic mime type as "application/octet-stream" with OpenOffice.org) does not really sound like "seemless" to me. What would be the effort to put this enhancement onto the roadmap? Sorry, but rejecting an enhancement "because it's not planned" (without discussing about feasibility and reasonability) is somewhat .... well, unorthodox at least. Hi, may be this should be considered for a future version of SC's bugtracking system. Frank You seem to have misinterpreted my comments and I regret I was not clearer. You needed to specify this as an enhancement you wish implemented. It would be nice if SourceCast were to do all that Ooo wanted it to do. It may be designed so that it does accept the mime type. I will request it. IssueZilla itself will be replaced in the near future--next year. I would hope that its replacement, Scarab, would accept the mime types. louis Louis, thanks for the clarification. Sorry for ranting (ehm - it's an inborn problem of mine to rant before asking, I really have to work on this :). I really read your original comment as basically "won't do because it's not planned". Sorry. I am really looking forward to this often-mentioned uber-tool Scarab :) Frank Hi passing on to support. Brian/kenneth: would you update the whiteboard status of this? I'd like to see, too, about the process of adding mimetypes. thanks Louis Opened internal RFE. Hi Frank, I raised this to our enhancement engineering person & he is going to look into this issue. I will update this issue with the response upon receiving this information. Let us know if this is not an adequate response to this issue. Thanks, Eric Hi Frank, I just got this repsonse. No it is not possible to add mime-types through the ui at this time. The mimetypes that appear in the Add attachment sections are hardcoded into the template. Scarab does attempt to set the mimetype based on file extension, so in most cases it is not necessary to manually set the mimetype. The mapping is specified in a configuration file, though, and it is not possible to update that via the ui either. Eric, thanks for the information. In this case, if I understand it correctly, shouldn't the configuration file be updated to properly recognize the OpenOffice.org extensions? Hi Frank, Engineering has a couple more questions on this issue. If the file extention is automatically interpretted? Will they need to add MIME types? If so, what is the list that they use today? Thanks, Eric Eric, sorry, I am not clear about your question...? What this bug is originally about is that users should be able to attach an OpenOffice.org document to an IssueZilla bug, giving it a mime type which would allow to be associated with OOo directly. Currently, "application/vnd.sun.xml.writer" is rejected by IZ, and "application/octet-stream" is too generic to be of real use. If I understand your previous comment properly, there is a configuration somewhere which decides which mime type to use automatically, depending on the extension of the file. Did I understand this wrong? If not, why is engineering asking about the content of this configuraton? :) Confused Frank Hi Frank, Let me go back to engineering with your latest update & see if we can clarify this. I will follow up on this issue as soon as I get another engineering update. Thanks for you patience here. Eric Frank, just a note: this issue has been reassigned to you... Stefan, thanks, I indeed did not notice this (from the Issuezilla mails, I find it hard to distinguish the ones I get because I am the submitter from the ones where I am the owner). Eric: why? :) I am surely the last who can do anything about this, at least in state NEW. So unless you decide this is a WONTFIX, INVALID, or WORKSFORME (I doubt the latter :), it does not make sense to assign the bug to me, sorry. As I feel that we did reach neither WONTFIX nor INVALID, I assign this back to you. the general support@openoffice.org may be the more suitable owner ... Frank - Can you provide a list of all the openoffice mime types you would like to have included? I am reassigning this issue to you as I am awaiting a your response. Please reassign back to support when you comment. Action plan: Wait for a response. Timeframe: Upon response. application/vnd.sun.xml.calc - OpenOffice.org Spreadsheet application/vnd.sun.xml.chart - OpenOffice.org Chart application/vnd.sun.xml.draw - OpenOffice.org Draw application/vnd.sun.xml.impress - OpenOffice.org Presentation application/vnd.sun.xml.math - OpenOffice.org Formula application/vnd.sun.xml.writer - OpenOffice.org Text Document application/vnd.sun.xml.writer.global - OpenOffice.org Master Document Frank, thanks for the feedback, I will pass this along to our engineers. In the future, when you reply to a collab support rep, please use the generic (support@oo.o) email address. That way, our entire support team can identify it as our issue. Action Plan: Update the internal issue with this new information. Timeframe: Update this issue in one week. Brian, This issue is particularly sensitive and should be given some priority. Let me know what I can do. Louis > In the future, when you reply to a collab support rep,
> please use the generic (support@oo.o) email address
will do, sorry.
*** Issue 6937 has been marked as a duplicate of this issue. *** Louis, raised the priority: P4 -> P3 I wasn't aware of the duplicates. transfering the link from issue 6937: http://framework.openoffice.org/documentation/mimetypes/mimetypes.html the list of mime types there is far more comprehensive than what I wrote above. This is the list of OO mime types that have been added to the Scarab product: application/vnd.sun.xml.writer sxw application/vnd.sun.xml.writer.template stw application/vnd.sun.xml.writer.global sxg application/vnd.sun.xml.calc sxc application/vnd.sun.xml.calc.template stc application/vnd.sun.xml.impress sxi application/vnd.sun.xml.impress.template sti application/vnd.sun.xml.draw sxd application/vnd.sun.xml.draw.template std application/vnd.sun.xml.math sxm application/vnd.stardivision.writer sdw vor application/vnd.stardivision.writer-global sgl application/vnd.stardivision.calc sdc application/vnd.stardivision.impress sdd sdp application/vnd.stardivision.draw sda application/vnd.stardivision.math smf Scarab is still in the process of having these mime types completely incorporated. Once, it has been completely updated with these new mime types, I will close this issue. Timeframe: Update by 01/03/03. All the appropriate OOo mime types have been added to the scarab product. As such, closing this issue with a "resolved-later" status. I am _really_ eager to see this Scarab working some day - 'til now, it's somewhat unsatisfying to see these "later" resolutions, but okay .... Thanks, anyway. I reopen this issue to make sure that not only OOos mime-types are added to scarab, but the Microsoft-Office ones as well. If this work is already done, sorry for the inconvenience. But I think that asking before the new system is intruduced is better than having to wait until the next update... *** Issue 598 has been marked as a duplicate of this issue. *** msoffice types are included in scarab. As agreed by Louis I will close these resolved fixed support-owned issues now. If you have trouble with that, please re-open the issue. As agreed by Louis I will close these resolved fixed support-owned issues now. If you have trouble with that, please re-open the issue. re-opening it ('cause the issue again came up in the mailing lists). This issue is *not* FIXED, at most, it's RESOLVED LATER. Saying my ob-clause, again: It's really unsatisfying to see all these issues being resolved as LATER - this is something which happened for *months* (if not years) to all RFE's, with pointing to the famous succcessor Scarab. Anyway, somebody please resolve this as LATER, instead of FIXED, so that the real state is reflected, and that people have a better chance finding it. fs, do you want to help us work on the upgrade site, 2.6? if so, let me know directly. louis. *** Issue 22490 has been marked as a duplicate of this issue. *** *** Issue 12204 has been marked as a duplicate of this issue. *** Setting milestone as 'CEE Consid-future' and adding PT marker to SWB Regards, Karishma Support Operations CollabNet Support is currently reviewing the issues under Resolved-Later. If the issues are fixed currently in any of the present CEE releases, then it will be marked as Resolved-Fixed. There might be a few issues which might not be in our future roadmap which might be closed as Wontfix unless it does not lie under any custom request. This is available in PT Setting The TM |