Bug 104896
| Summary: | Submitting .desktop, .keys and .mime entries | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Gérard Milmeister <gemi> |
| Component: | redhat-menus | Assignee: | Seth Nickell <snickell> |
| Status: | CLOSED UPSTREAM | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | CC: | mitr |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-11-01 17:01:10 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
A nice idea, but should probably be done in the context of freedesktop.org not as a RH specific thing. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 Galeon/1.3.9 Description of problem: Most applications, especially commercial ones, don't come with their .desktop, .keys and .mime files, for example Maple and Mathematica. It would be nice if there was an online form where one could submit missing entries including icons for file types and for applications. Also the mime types already present have missing information such as descriptions and icons. Just like the translation databases their could be such a database where information could be supplied by volunteers. Also I noticed that where .desktop files exist, they sometimes don't turn up in the menu, because the Categories entry isn't matched. It would be nice, if for example Maple had a category named "Mathematics" this would turn up as a new submenu in the main menu (but only if the maple is actually present). A useful extension to the file types preferences would be a flat view that can be sorted by description or extension, because of some inconsistencies it is not always clear where in the hierarchy a mime type would reside. The descriptions of the mime types should also follow a more consistent phrasing (lower-, uppercase etc...) Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Additional info: