Bug 203559 - does not display dvi file correctly
Summary: does not display dvi file correctly
Status: RESOLVED FIXED
Alias: None
Product: okular
Classification: Applications
Component: DVI backend (show other bugs)
Version: 0.14.4
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-12 13:02 UTC by Marijn Schouten
Modified: 2021-03-10 05:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
metafont file for capital A (191 bytes, text/plain)
2009-08-12 13:06 UTC, Marijn Schouten 		Details
dvi output of "mf A.mf && gftodvi A.2602gf" (1.18 KB, application/octet-stream)
2009-08-12 13:08 UTC, Marijn Schouten 		Details
A.dvi viewed with okular (45.80 KB, image/png)
2009-08-12 13:11 UTC, Marijn Schouten 		Details
A.dvi viewed with xdvi (9.35 KB, image/png)
2009-08-12 13:12 UTC, Marijn Schouten 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marijn Schouten 2009-08-12 13:02:33 UTC 
Version:           4.3.0 (using KDE 4.3.0)
Compiler:          gcc-4.3.3 
OS:                Linux
Installed from:    Gentoo Packages

Dvi file generated by metapost does not display correctly in okular, but does in xdvi.
Comment 1 Marijn Schouten 2009-08-12 13:06:04 UTC 
Created attachment 36089 [details]
metafont file for capital A
Comment 2 Marijn Schouten 2009-08-12 13:08:27 UTC 
Created attachment 36090 [details]
dvi output of "mf A.mf && gftodvi A.2602gf"
Comment 3 Marijn Schouten 2009-08-12 13:11:43 UTC 
Created attachment 36091 [details]
A.dvi viewed with okular
Comment 4 Marijn Schouten 2009-08-12 13:12:55 UTC 
Created attachment 36092 [details]
A.dvi viewed with xdvi
Comment 5 Marijn Schouten 2009-08-12 13:15:38 UTC 
Downstream bug report: http://bugs.gentoo.org/show_bug.cgi?id=257677
Comment 6 Justin Zobel 2021-03-09 23:59:19 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.