Package: whizzytex
Version: 1.3.1-1
Severity: minor
The upstream package of whizzytex includes quite a few examples not included
in the Debian package, including templates for using whizzytex with beamer.
Could your package them ?
Thanks,
--
Boris
-- System Information:
Debian Release: lenny/
On Tue, Jan 03, 2006 at 08:55:38AM -0500, David Roundy wrote:
> If you press ? for help, you'll see that pressing 'c' will show you
> ("count") the number of changes.
Right, sorry :-/ I did not check for new options in the last version.
On the other hand, I had looked in the Changelog in case so
Package: darcs
Version: 1.0.4-2
Severity: normal
Since the current version in unstable (the problem does not manifest itself
with the testing version), darcs record does no longer how many fragment a
patch is made of, e.g.
$ darcs record
hunk ./abcd.tex 1
-\documentclass[orivec]{llncs}
+ \documen
On Wed, Nov 23, 2005 at 09:06:02AM +0100, San Vu-Ngoc wrote:
> Warning: Error: /invalidfileaccess in --file--
> Warning: Operand stack:
> Warning:(/usr/share/texmf/dvips/base/special.pro) (r)
[snip]
> So it this a bug of advi of gs ???
This bug is clearly an incompatibility between the -dSAF
On Fri, Jun 17, 2005 at 09:01:11AM +0900, Junichi Uekawa wrote:
> > Whizzytex in Debian ships with value MULTIPLE set to false. The version of
> > advi in Debian (1.6) is perfectly capable of handling MULTIPLE=true (and is
> > much more useful in that mode).
>
> That's a bit of a subjective commen
Package: whizzytex
Version: 1.2.2-2
Severity: normal
Whizzytex in Debian ships with value MULTIPLE set to false. The version of
advi in Debian (1.6) is perfectly capable of handling MULTIPLE=true (and is
much more useful in that mode).
-- System Information:
Debian Release: 3.1
APT prefers uns
On Mon, Feb 28, 2005 at 01:25:43AM +0100, Marcin Owsiany wrote:
> Ah, so the issue is not that poedit performs some inappropriate
> recoding, but that $EDITOR decides to interpret a file containing just
> US-ASCII file as iso-8859-15, and not as UTF-8. But then after you input
> some non-us-ascii c
On Sun, Feb 27, 2005 at 11:26:06PM +0100, Marcin Owsiany wrote:
> As far as I know, potool knows nothing about encodings, so it should be
> completly transparent to them, and just pass text from the po file in
> whatever encoding it is, unchanged, to the temp file, and back. But I
> may be wrong.
Package: potool
Version: 0.5-2
Severity: wishlist
When using poedit (typically by calling poedit file.po), an editor is
invoked on a temporary file with the remaining strings to be translated. It
would be great if this file was in the same encoding as file.po. On my box I
edit english strings (whi
9 matches
Mail list logo
