File: FAQ.html

package info (click to toggle)
whizzytex 1.3.3-0.2
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 4,932 kB
  • sloc: lisp: 3,605; sh: 1,621; ml: 366; makefile: 240
file content (216 lines) | stat: -rw-r--r-- 16,783 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
<!DOCTYPE html>
<html >
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="generator" content="hevea 2.23">
<style type="text/css">
.li-itemize{margin:1ex 0ex;}
.li-enumerate{margin:1ex 0ex;}
.dd-description{margin:0ex 0ex 1ex 4ex;}
.dt-description{margin:0ex;}
.toc{list-style:none;}
.footnotetext{margin:0ex; padding:0ex;}
div.footnotetext P{margin:0px; text-indent:1em;}
.thefootnotes{text-align:left;margin:0ex;}
.dt-thefootnotes{margin:0em;}
.dd-thefootnotes{margin:0em 0em 0em 2em;}
.footnoterule{margin:1em auto 1em 0px;width:50%;}
.caption{padding-left:2ex; padding-right:2ex; margin-left:auto; margin-right:auto}
.title{margin:2ex auto;text-align:center}
.titlemain{margin:1ex 2ex 2ex 1ex;}
.titlerest{margin:0ex 2ex;}
.center{text-align:center;margin-left:auto;margin-right:auto;}
.flushleft{text-align:left;margin-left:0ex;margin-right:auto;}
.flushright{text-align:right;margin-left:auto;margin-right:0ex;}
div table{margin-left:inherit;margin-right:inherit;margin-bottom:2px;margin-top:2px}
td table{margin:auto;}
table{border-collapse:collapse;}
td{padding:0;}
.cellpadding0 tr td{padding:0;}
.cellpadding1 tr td{padding:1px;}
pre{text-align:left;margin-left:0ex;margin-right:auto;}
blockquote{margin-left:4ex;margin-right:4ex;text-align:left;}
td p{margin:0px;}
.boxed{border:1px solid black}
.textboxed{border:1px solid black}
.vbar{border:none;width:2px;background-color:black;}
.hbar{border:none;height:2px;width:100%;background-color:black;}
.hfill{border:none;height:1px;width:200%;background-color:black;}
.vdisplay{border-collapse:separate;border-spacing:2px;width:auto; empty-cells:show; border:2px solid red;}
.vdcell{white-space:nowrap;padding:0px; border:2px solid green;}
.display{border-collapse:separate;border-spacing:2px;width:auto; border:none;}
.dcell{white-space:nowrap;padding:0px; border:none;}
.dcenter{margin:0ex auto;}
.vdcenter{border:solid #FF8000 2px; margin:0ex auto;}
.minipage{text-align:left; margin-left:0em; margin-right:auto;}
.marginpar{border:solid thin black; width:20%; text-align:left;}
.marginparleft{float:left; margin-left:0ex; margin-right:1ex;}
.marginparright{float:right; margin-left:1ex; margin-right:0ex;}
.theorem{text-align:left;margin:1ex auto 1ex 0ex;}
.part{margin:2ex auto;text-align:center}
</style>
<title>WhizzyTeX Frequently Asked Questions
</title>
</head>
<body >
<!--HEVEA command line is: hevea -o FAQ.html -fix -exec xxdate.exe FAQ.tex -->
<!--CUT STYLE article--><!--CUT DEF section 1 --><table class="title"><tr><td style="padding:1ex"><h1 class="titlemain"><span style="color:blue">WhizzyTeX</span> Frequently Asked Questions</h1><h3 class="titlerest">Didier R&#XE9;my</h3><h3 class="titlerest">Last Modified: September&#XA0;20, 2015</h3></td></tr>
</table><!--TOC section id="sec1" Contents-->
<h2 id="sec1" class="section">Contents</h2><!--SEC END --><ul class="toc"><li class="li-toc">
<a href="#sec2">1&#XA0;&#XA0;Where to find it</a>
</li><li class="li-toc"><a href="#sec3">2&#XA0;&#XA0;Is this a Bug?</a>
</li><li class="li-toc"><a href="#sec4">3&#XA0;&#XA0;Known problems</a>
</li><li class="li-toc"><a href="#sec5">4&#XA0;&#XA0;Using WhizzyT<sub>E</sub>X with platex</a>
</li><li class="li-toc"><a href="#sec6">5&#XA0;&#XA0;Using WhizzyT<sub>E</sub>X under Windows</a>
</li><li class="li-toc"><a href="#sec8">6&#XA0;&#XA0;Using Virtual Fonts with Active-DVI</a>
</li><li class="li-toc"><a href="#sec9">7&#XA0;&#XA0;Known bogus latex packages</a>
<ul class="toc"><li class="li-toc">
<a href="#sec10">7.1&#XA0;&#XA0;ieee.cls [2000/01/11]</a>
</li></ul>
</li></ul>
<!--TOC section id="sec2" Where to find it-->
<h2 id="sec2" class="section">1&#XA0;&#XA0;Where to find it</h2><!--SEC END --><p>The URL is <a href="http://cristal.inria.fr/whizzytex/"><span style="font-family:monospace">http://cristal.inria.fr/whizzytex/</span></a></p><p>The last major release is 1.3.1
and the stable version is 1.3.3</p><p>The last version of the FAQ can be found at 
<a href="http://cristal.inria.fr/whizzytex/FAQ.html"><span style="font-family:monospace">http://cristal.inria.fr/whizzytex/FAQ.html</span></a></p><p><a id="isitabug"></a>
</p>
<!--TOC section id="sec3" Is this a Bug?-->
<h2 id="sec3" class="section">2&#XA0;&#XA0;Is this a Bug?</h2><!--SEC END --><p>Before reporting a bug, have you checked that the source file correctly
compiles and previews with the <em>latex</em>, <em>previewer</em>
and <em>options</em> used in WhizzyT<sub>E</sub>X?
(In recent versions of WhizzyT<sub>E</sub>X you may see the previewer&#X2019;s command from 
<span style="font-family:monospace">Emacs</span> using the menu <span style="font-family:monospace">View log...</span> and selecting
<span style="font-family:monospace">command</span>.) </p><p>You may also check the latex log files (<span style="font-family:monospace">format</span>, and
<span style="font-family:monospace">latex</span>, <span style="font-family:monospace">slice</span>). In particular, <span style="font-family:monospace">format</span> will show
you the version of <span style="font-family:monospace">whizzytex.sty</span> that has been loaded. Loading an
old version will likely not work! (You may also check the Emacs version of
whizzytex (from the <span style="font-family:monospace">Help</span> entry of <span style="font-family:monospace">Whizzy</span> menu). </p><p>Since the latex <span style="font-family:monospace">color</span> package is implicitly loaded, you 
should also check the compatibility with this package by 
by explicitly including <code>\usepackage{color}</code> right before the
<code>\begin{document}</code> (because whizzytex would load this package last) 
and checking that it still compiles with <em>latex</em>.</p><p>In <span style="font-family:monospace">advi</span> mode (when option <span style="font-family:monospace">-advi</span> is used), the
<span style="font-family:monospace">advi</span> package is also implicitly loaded. So you should then also try
to latex your source with the package <span style="font-family:monospace">advi</span> explicitly loaded before
all other packages, since some errors may be indirectly due to this
<span style="font-family:monospace">advi</span> and not to WhizzyT<sub>E</sub>X itself&#X2014;then send your bug report
to <a href="http://cristal.inria.fr/advi/">Active-DVI</a>.</p><p>Also, do not forget to check your version number before repporting a bug. 
See the value of variable <span style="font-family:monospace">whizzytex-mode</span> in Emacs manually or
through the Emacs on-line documentation of <span style="font-family:monospace">whizzytex-mode</span>. 
This version number should be identical to the one of
<span style="font-family:monospace">whizzytex.sty</span>, which is displayed on the welcoming page when
starting WhizzyTeX, and also to the one of the script <span style="font-family:monospace">whizzytex</span>,
which you can check with the shell command <span style="font-family:monospace">whizzytex -version</span>.
If these three version numbers do not match, you have a broken
installation, maybe a file of old version takes priority, which you can
solve by deleled the old file or adjusting the corresponding PATH variable.</p>
<!--TOC section id="sec4" Known problems-->
<h2 id="sec4" class="section">3&#XA0;&#XA0;Known problems</h2><!--SEC END --><p>Fixed refers to last stable version.
</p><ol class="enumerate" type=1><li class="li-enumerate">WhizzyT<sub>E</sub>X uses hard links and hence does not work on file systems that do
not support them, such as VFAT.</li><li class="li-enumerate">It has been reported with old versions that sometimes the cursor jumps to the
end of the buffer while typing fast, and the mark is left a few characters
before where the point was when the cursor jumped.<p>The problem should be <span style="font-style:italic">Fixed in versions </span>&#X2265;<span style="font-style:italic"> </span><span style="font-style:italic">1.3.3</span>. </p><p>Otherwise, an (imperfect) workaround is to reduce the slicing speed
<em>e.g.</em> by the follow setting (you may need to adjust the value):
</p><pre class="verbatim">        (setq whizzy-load-factor 0.1)
</pre></li><li class="li-enumerate">Its does not work with the <code>x-symbol</code> package.<p>The <code>x-symbol</code> package may now work together with WhizzyT<sub>E</sub>X, provided
you have a version of <span style="font-family:monospace">x-symbol</span> greater than v4.3.3. However, the
option Page-to-point may still not work (under <code>x-symbol</code>, the cursor
would be inserted at the end of the buffer instead of at the
current-position). Then, you may use the following alternative.</p><p>Alternatively, with (X)Emacs version 21 and above, you may set
<code>whizzy-write-annotate</code> to nil to tell WhizzyT<sub>E</sub>X not to use
<code>write-region-annotation-functions</code>. The slice will be write slower, but
in a way so that the <code>x-symbol</code> package should always be compatible with 
WhizzyT<sub>E</sub>X. </p><p>You may also wish to set <code>'x-symbol-auto-conversion-method</code> to
<code>'fast</code>.</p></li><li class="li-enumerate">How can a click in the <code>advi</code> window reposition the point
in the emacs window?<p>First, you should be using the <code>advi</code> previewer. Then, check the
documentation of <code>advi</code>, since bindings may depend on versions. This is
likely to be <code>shift-left-mouse</code> or <code>left-mouse</code>.</p><p>There might also be a short-cut that temporarily rebinds
<code>shift-xxx-mouse</code> to <code>xxx-mouse</code>. This can be toggled by typing
<code>e</code> in the <code>advi</code> or by calling <code>advi</code> with the option
<code>-edit</code>. 
Note that <code>shift-midddle-click</code> and <code>shift-right-click</code> (or their
shortcut versions) are used for <code>move</code> and <code>resize</code> commands when
WhizzyEditting.</p></li></ol>
<!--TOC section id="sec5" Using WhizzyT<sub>E</sub>X with platex-->
<h2 id="sec5" class="section">4&#XA0;&#XA0;Using WhizzyT<sub>E</sub>X with platex</h2><!--SEC END --><p>WhizzyT<sub>E</sub>X has been designed to work with standard LaTeX.
However, it should also work with other implementations of LaTeX, as long
as they allow the creation of new formats. </p><p>As an example, to make it work with <code>platex</code> you can edit 
the script <code>whizzytex</code> and change some findings as follows
(in the experimental version): 
</p><pre class="verbatim">INITEX="platex -ini"
LATEX=platex
FORMAT=platex
BIBTEX=jbibtex
FMT=fmt
</pre><p><a id="cygwin"></a>
</p>
<!--TOC section id="sec6" Using WhizzyT<sub>E</sub>X under Windows-->
<h2 id="sec6" class="section">5&#XA0;&#XA0;Using WhizzyT<sub>E</sub>X under Windows</h2><!--SEC END --><p>WhizzyT<sub>E</sub>X is designed for <code>Unix</code> plateforms. However, Marciano
Siniscalchi reported that it successfully worked on his
Window plateform under Cygwin (1.5.5-1), using <span style="font-family:monospace">Cygwin/Xfree 4.3</span> and
<span style="font-family:monospace">xdvi</span> from <span style="font-family:monospace">tetex 2.0.2-13</span>.</p><p>The following modifications to the <span style="font-family:monospace">whizzytex</span> script are
necessary:
</p><ul class="itemize"><li class="li-itemize">Fix the <code>xdvi</code> script by replacing <code>xdvi.bin</code>
by <code>exec xdvi.bin</code> on the last line of the script
(as in some Linux distribs).</li><li class="li-itemize">Fix the <code>whizzytex</code> script by replacing the line
<pre class="verbatim">        preview() {mv $WHIZZY.dvi $WHIZZY.$VIEW; }
</pre>with
<pre class="verbatim">        preview() {cp $WHIZZY.dvi $WHIZZY.$VIEW; rm $WHIZZY.dvi}
</pre>(Permission to rename the .wdvi file is denied while
<code>xdvi</code> is displaying it).</li><li class="li-itemize">Replace all occurrences of <span style="font-family:monospace">ulimit</span> with <span style="font-family:monospace">true</span> as
<span style="font-family:monospace">ulimit</span> is not implemented on Cygwin. Then, when WhizzyT<sub>E</sub>X falls
into a loop during latex-ing, which is possible on some input, WhizzyT<sub>E</sub>X
will not be able to get it out. (When such cases occur, you&#X2019;ll have to quit
and restart whizzytex by hand&#X2014;after your source file has been fixed.)</li><li class="li-itemize">Replace all instances of <span style="font-family:monospace">wdvi</span> with <span style="font-family:monospace">w.dvi</span>
(as <span style="font-family:monospace">Yap</span> automatically adds <span style="font-family:monospace">.dvi</span> to a file name
not ending with <span style="font-family:monospace">.dvi</span> and then complains about not finding the
file).</li></ul><p>
Unfortunately, Cygwin/XFree86 is quite slow compared to XFree86 under
Linux, etc. An alternative is to use a commercial X server, such as
XWin32 from StarNet (www.xwin32.com). MI/X from Microimages
(www.microimages.com) is another alternative, but since it is
XFree86-based, it is not as fast as XWin32.
Performance, even with XWin32, is still inferior to Linux.</p><!--TOC subsection id="sec7" Using <span style="font-family:monospace">yap</span> instead of <span style="font-family:monospace">xdvi</span> under Cygwin-->
<h3 id="sec7" class="subsection">Using <span style="font-family:monospace">yap</span> instead of <span style="font-family:monospace">xdvi</span> under Cygwin</h3><!--SEC END --><p>
Gregory Borota has reported much better performances with 
<span style="font-family:monospace">yap</span> than with <span style="font-family:monospace">xdvi</span> under Cygwin.
He has written a small wrapper interface around <span style="font-family:monospace">yap</span> to make it look
like <span style="font-family:monospace">xdvi</span> for WhizzyT<sub>E</sub>X and patched the source of WhizzyTeX
accordingly. See the README and INSTAL file coming with his
<a href="whizzytex-yap-.tgz"><span style="font-family:monospace">whizzytex-yap-.tgz</span></a> patch, 
<em>coming with absolutely no warranty</em>. </p><p>See also the detailed
<a href="http://hellmund.dk/whizzy.html">installation guide</a> written by
Gunnar Hellmund.</p>
<!--TOC section id="sec8" Using Virtual Fonts with Active-DVI-->
<h2 id="sec8" class="section">6&#XA0;&#XA0;Using Virtual Fonts with Active-DVI</h2><!--SEC END --><p><a href="http://cristal.inria.fr/advi/">Active-DVI</a>
does not currently handle virtual fonts (when called with virtual fonts, it
usually shows a more or less blank screen). This can be fixed by expanding
virtual fonts with <span style="font-family:monospace">dvicopy</span> prior to display as explained on the
Active-DVI FAQ.</p><p>In WhizzyT<sub>E</sub>X, this can be done automatically by passing the option
<span style="font-family:monospace">-dvicopy dvicopy</span> or equivalently setting
</p><pre class="verbatim">        DVICOPY=dvicopy
</pre><p>in <span style="font-family:monospace">.whizzytexrc</span> configuration file in the working directory.</p>
<!--TOC section id="sec9" Known bogus latex packages-->
<h2 id="sec9" class="section">7&#XA0;&#XA0;Known bogus latex packages</h2><!--SEC END -->
<!--TOC subsection id="sec10" ieee.cls [2000/01/11]-->
<h3 id="sec10" class="subsection">7.1&#XA0;&#XA0;ieee.cls [2000/01/11]</h3><!--SEC END --><p>This package introduced a bug in the redefinition of <code>\@xfloaf</code> 
that makes it incompatible with the <span style="font-family:monospace">color</span> package</p><p>To fix it, your must redefine it as follows:
</p><pre class="verbatim"><span style="font-size:small">\def\@xfloat#1#2{\ifhmode \@bsphack\@floatpenalty -\@Mii\else
    \@floatpenalty-\@Miii\fi\def\@captype{#1}\ifinner
      \@parmoderr\@floatpenalty\z@
     \else\@next\@currbox\@freelist{\@tempcnta\csname ftype@#1\endcsname
       \multiply\@tempcnta\@xxxii\advance\@tempcnta\sixt@@n
       \@tfor \@tempa :=#2\do
                        {\if\@tempa h\advance\@tempcnta \@ne\fi
                         \if\@tempa t\advance\@tempcnta \tw@\fi
                         \if\@tempa b\advance\@tempcnta 4\relax\fi
                         \if\@tempa p\advance\@tempcnta 8\relax\fi
         }\global\count\@currbox\@tempcnta}\@fltovf\fi
    \global\setbox\@currbox \color@vbox \normalcolor \vbox\bgroup
    \def\baselinestretch{1}\small\normalsize
    \hsize\columnwidth \@parboxrestore}
</span></pre><!--CUT END -->
<!--HTMLFOOT-->
<!--ENDHTML-->
<!--FOOTER-->
<hr style="height:2"><blockquote class="quote"><em>This document was translated from L<sup>A</sup>T<sub>E</sub>X by
</em><a href="http://hevea.inria.fr/index.html"><em>H</em><em><span style="font-size:small"><sup>E</sup></span></em><em>V</em><em><span style="font-size:small"><sup>E</sup></span></em><em>A</em></a><em>.</em></blockquote></body>
</html>