Bug 173514
Summary: | RFE: enable dvi support during the fc5 test release phase | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jef Spaleta <jspaleta> |
Component: | evince | Assignee: | Kristian Høgsberg <krh> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | dakingun, dann, motchy+fedora, sundaram, tmraz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-11-17 13:20:40 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: |
Description
Jef Spaleta
2005-11-17 19:41:51 UTC
Additionally id like to point out that tetex-xdvi is one of the few remaining packages in Core that requires openmotif. Moving forward towards being able to move openmotif out of Core has to be an important goal somewhere in the larger plan for Core. And the only way thats going to happen and keep dvi document support in Core is to get it turned on in evince and tested. -jef Jef: This sounds like a great idea. Also, reducing the openmotif dep count by 1 package would make it easier to transition motif to Fedora Extras, and out of the Core OS. Kristian: Any opinion on this? Curious what your thoughts are, etc. TIA Even if evince was to be compiled with xdvi support, evince is NOT a good replacement for xdvi because it is missing a fundamental feature: support for dvi source specials. Source specials allow for bidirectional communication between a tex editor and a dvi viewer, it allows for a dvi document to be opened showing the place in the dvi document that corresponds to the place where the cursor is in the tex editor (and the other way around). This support is fundamental for editing tex documents with hundreds of pages like dissertations, books. Evince does not have this kind of features. If the problem is xdvi being linked with motif, then just compile xdvi with support for another toolkit (like xaw or xaw3d). Replacing xdvi with evince would be a major inconvenience for the people that actually use xdvi on a daily basis. Just my 2 cents. (In reply to comment #4) > Even if evince was to be compiled with xdvi support, evince is NOT a good > replacement for xdvi because it is missing a fundamental feature: support for > dvi source specials. > Please file a different RFE on other feature requests. Whether it is going to replace xdvi or not is not under discussion in this report. That will have to be decided after we experimentally enable and test this option in a development cycle. PING !! I believe the dvi backend is not marked as experimental anymore. |