- Win64
- All users
- Winedt 8.1 64 bit
- Admin Install (C:\Program Files\WinEdt Team\WinEdt 8).
- Enable User Profile creation
Решение проблемы с визуализацией в yap:
(1) The tex executable has a bug.
(2) The DVI viewer has a bug.
(3) The DVI viewer's configuration file (if any) contains
an error (this is really a subitem of (1) unless one
edits that file oneself).
(4) The DVI file has become corrupted.
(5) The DVI file contains a \special not recognized
by the DVI viewer (or not in the format expected).
I have encountered all of these. I see (5) on a regular
basis and ignore it. But I have also induced (3) more
than a few times through experimentation (with an old
viewer called windvi). I have seen (4) in downloaded
files, and have reported bugs in class (1) and (2) a couple
of times over the years.
However, with all the different TeX engines around now,
I suppose it is also possible a "non-standard" DVI file
could be created by one of them, and that a viewer might
have a problem with that.
Finally, if a viewer needs to read a .map file for fonts,
it might encounter an invalid line in it. It is also
conceivable mktexpk might be reporting an error in bitmap
font generatio
- When you see the file in YAP viewer, go to view->render and change it to "dvips"
- In YAP viewer goto view->options->display->default render method and change it to Dvips
(1) The tex executable has a bug.
(2) The DVI viewer has a bug.
(3) The DVI viewer's configuration file (if any) contains
an error (this is really a subitem of (1) unless one
edits that file oneself).
(4) The DVI file has become corrupted.
(5) The DVI file contains a \special not recognized
by the DVI viewer (or not in the format expected).
I have encountered all of these. I see (5) on a regular
basis and ignore it. But I have also induced (3) more
than a few times through experimentation (with an old
viewer called windvi). I have seen (4) in downloaded
files, and have reported bugs in class (1) and (2) a couple
of times over the years.
However, with all the different TeX engines around now,
I suppose it is also possible a "non-standard" DVI file
could be created by one of them, and that a viewer might
have a problem with that.
Finally, if a viewer needs to read a .map file for fonts,
it might encounter an invalid line in it. It is also
conceivable mktexpk might be reporting an error in bitmap
font generatio
Комментариев нет:
Отправить комментарий