Talk:Device independent file format

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing  
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 ???  This article has not yet received a rating on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
Former good article nominee Device independent file format was a good articles nominee, but did not meet the good article criteria at the time. There are suggestions below for improving the article. Once these issues have been addressed, the article can be renominated. Editors may also seek a reassessment of the decision if they believe there was a mistake.
February 19, 2007 Good article nominee Not listed

I didn't bother to move this from DVI, it needs a reference or something:

A lack of easy-to-use DVI software on microcomputers may be one of the reasons TeX did not compete against systems such as Adobe Acrobat.—The preceding unsigned comment was added by ( (talkcontribs) 15:57, 15 March 2003.

I'm not even sure it's true. Maybe it just needs a lot of qualifications. Note that a lot of people using TeX today (esp. on Windows) use it by generating a PDF and viewing the output in Acrobat Reader. (Of course, I don't think TeX was ever "competing" with Acrobat: they do different things.) —The preceding unsigned comment was added by (talk) 07:29, 19 September 2004

I don't think TeX was ever "competing" with Acrobat: they do different things.

In particular, Acrobat is more "portable" in the sense that the fonts are (usually) embedded. With a DVI file, there can be problems when attempting to view on another system having fonts with the same name but different metrics. So, I agree that DVI never really competed against Acrobat (apples and quinces). —The preceding unsigned comment was added by (talk) 18:32, 19 August 2005

It says on the page that Donald Knuth was the designer. This is completely wrong -- it was in fact designed by David Fuchs in 1979 (see dvitype.web). —The preceding unsigned comment was added by (talk) 11:26, 15 March 2006

I'd fixed this before reading the talk page, but the next time you notice a mistake, feel free to correct it without waiting for permission. grendel|khan 19:08, 30 July 2006 (UTC)

Licenses of many fonts available in TeX distributions don't allow any modifications without changing the name of the file, so metrics should be the same. Example from


—The preceding unsigned comment was added by (talk) 2006-12-30T14:07:59

GA nomination failed[edit]

I have failed the article according to the GA criteria. The article is not broad enough, with only two sections of information. If you can, add a picture or two with the appropriate licenses, perhaps one you've taken yourself. The article also needs a lot more references. Include inline citations to increase the verifiability of the article. Once these issues are addressed, among the other criteria, please consider resubmitting again for GAC. --Nehrams2020 17:34, 19 February 2007 (UTC)

The lion[edit]

Does anyone know the significance of the lion? And if so would they be so good as to add that information to the article? I see it crops up in numerous packages, including the KDE desktop icon for DVI files, the xdvi viewer program, the Kile editor, etc. Thanks! --Bigdaddyedward 14:24, 21 August 2007 (UTC)

It's the TeX mascot.--Oneiros 14:52, 21 August 2007 (UTC)


I've created a new article titled xdvi. It's still quite stubby. Have fun improving and extending it. Michael Hardy (talk) 16:56, 4 May 2012 (UTC)

dvipdfm and recent TeX distros[edit]

It appears it was actually dropped from MikTeX 2.9 (which only has binary for it for version 2.7) and also by Tex Live 2014. The CTAN page for dvipdfm doesn't mention inclusion in any distros, whereas the one for dvipdfmx lists MikTeX and TL, and also notes that "Dvipdfmx, if “called” with the name dvipdfm, op­er­ates in a “dvipdfm com­pat­i­bil­ity” mode, so that users of the both pack­ages need only keep one ex­e­cutable." It also seems pretty clear from that page that the CTAN guys are now the maintainers of dvipdfmx. JMP EAX (talk) 13:14, 3 August 2014 (UTC)

Apparently that change happened before 2011 [1]. JMP EAX (talk) 13:34, 3 August 2014 (UTC)

And around 2012 they were working to merge XeTeX's fork (xdvipdfmx) [2]. I'm not yet sure what, if anything came of that effort. JMP EAX (talk) 13:36, 3 August 2014 (UTC)

dvipdf (by Lesenko)[edit]

Apparently it was released, although perhaps way too late; I found this Windows(?) version from around 2000: [3]. I think it became (part of or precursor of) BakoMa TeX eventually. JMP EAX (talk) 14:49, 3 August 2014 (UTC)

External links modified[edit]

Hello fellow Wikipedians,

I have just modified 4 external links on Device independent file format. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

You may set the |checked=, on this template, to true or failed to let other editors know you reviewed the change. If you find any errors, please use the tools below to fix them or call an editor by setting |needhelp= to your help request.

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

If you are unable to use these tools, you may set |needhelp=<your help request> on this template to request help from an experienced user. Please include details about your problem, to help other editors.

Cheers.—InternetArchiveBot (Report bug) 15:38, 7 December 2017 (UTC)