Bug#935968: texlive-latex-extra: Font U/esint/m/n/10.95=esint10 at 10.95pt not loadable: Metric (TFM) file not found

2019-08-28 Thread Karl Berry
esint10.mf is empty, besides comments and a lone \endinput Is this on purpose? No, I just didn't notice. In the 2019/07/19 update of esint, esint10.mf is supposed to be generated from esint.dtx, while only that stub file in fact shows up. I am not sure. Running the

Bug#824260: [tlbuild] texlive build failures on Debian - upmendex

2016-05-14 Thread Karl Berry
Do you think (or AKira) that this is the problem for mips? For sparc I am a bit stymed. Yes, it's all about BigEndian architectures (and ICU and upmendex). (And don't bother explaining that sparc is endian-neutral, the practical reality is that it is still bigendian in our world.) And the

Bug#815205: another texinfo.tex bug in \scanmacro

2016-04-12 Thread Karl Berry
On another front: @iftex @macro cl{name} {@smallertt@phantom{concurrency:}@llap{cl:}}\name\ @end macro @end iftex What's inside @iftex is supposed to be valid Texinfo. (Just like @ifinfo, etc.) To lapse into plain/raw TeX, @tex should be used. That's why it exists. (Of

Bug#790626: Argument of \\ has an extra } ??

2015-07-05 Thread Karl Berry
> l.56 \initial {\\} Works for me with current texinfo.tex and the input below (to force creating the \initial line). I don't doubt there was a bug in some version of texinfo.tex in this regard, but I routinely run Texinfo documents with \indexentries, so I doubt it existed for long. -k ---

Bug#709146: [tlbuild] ttf2pk versus ttf2pk2

2013-10-09 Thread Karl Berry
Is there a reason for it, and why do we not switch to ttf2pk2 and get rid of one more lib in libs? Peter removed freetype1 and ttf2pk in the sources some time ago, so they'll be gone in TL 2014. karl -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of

Bug#709146: [tlbuild] ttf2pk versus ttf2pk2

2013-05-22 Thread Karl Berry
> Hi Karl, hi all, We need peb's input on this. I expect it can be done for TL'14. Thanks, karl -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#666647: Still cannot use LaTeX with cyrillic symbols

2012-07-22 Thread Karl Berry
FWIW, I agree with Norbert's analysis regarding cyrfonts and have nothing to add ... k -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#675109: evince: DVI support broken

2012-05-29 Thread Karl Berry
Is there something that has been checked in *after 2012-05-16 r26437 | peter | 2012-05-16 09:44:41 +0200 shows kpse_cnf_get being re-exported. I see nothing in cnf.c now that would stop the symbol from being exported. Maybe you did your build just before that change? Don't know how else to

Bug#673016: API breakage, dropped header file cnf.h

2012-05-15 Thread Karl Berry
np> somewhere between 20120410 and20120510 it seems that cnf.h is not installed anymore. Peter changed kpathsea/Makefile.am not to install cnf.h and several other .h's. I'm not sure why, or if he and I discussed it. Peter? k On Di, 15 Mai 2012, Michael Biebl wrote: > Packa

Bug#635382: [tex-live] Bug#635382: new release of latex-unicode

2012-04-19 Thread Karl Berry
By the way, the package is already called â€œucsâ€ in TeXLive. I know :). How can I change the package and directory name on CTAN? In general, request the change of CTAN maintainers when you make the upload, and they will discuss it with you. And yes, I would upload with th

Bug#635382: [tex-live] Bug#635382: new release of latex-unicode

2012-04-18 Thread Karl Berry
I wonder whether it is sensible to always call the package ucs Please do. There are far too many gratuitious name differences already, and ucs is at least a little more specific than "unicode". Thanks, k -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject o

Bug#602566: [tex-k] dvi2ps segfault based on bug in libkpathsea

2010-11-09 Thread Karl Berry
I attach the two patches, both apply (with some fuzzyness) to current sources in TeX Live. I agree with Peter. I installed the second patch. Thanks, Mathias and all! karl -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Co

Bug#562291: dvi2dvi: FTBFS: types.h:66: error: expected specifier-qualifier-list before 'str_llist_type'

2010-03-23 Thread Karl Berry
9 #ifdef KPATHSEA 10 #include 11 #include 12 #include 13 #endif In general, I think #include must come first, and should replace the #include . /usr/include/kpathsea/types.h:66: error: expected specifier-qualif

Bug#561427: [tex-k] compile error of ptex with new libkpathsea 2009

2009-12-19 Thread Karl Berry
> /home/hille/ptex-bin-3.1.10+0.04b/tetex-src-3.0/texk/web2c/ptex-src-3.1.10/tex2.c:3476: > undefined reference to `kpse_make_tex_discard_errors' I speculate that a different (old) types.h is being read in the tex*.c compilations, because otherwise the identifier kpse_make_tex_discard_err

Bug#534199: [tex-live] Bug#534199: texlive-formats-extra: does not install: 5 year bug

2009-06-23 Thread Karl Berry
We either have to patch latex.ltx No. or patch the .ini files to contain scrollmode? Yes. Go ahead and do it if you want, or wait for me if you have to :). karl -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact li

Bug#531595: [tex-live] Supporting old releases: Using LaTeX after more than 5 years

2009-06-11 Thread Karl Berry
I attach the patch against current TeX Live's fmtutil in Build/source/texk/tetex/fmtutil. Looks fine to me. I applied it. Thanks, karl -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#531595: [tldistro] Supporting old releases: Using LaTeX after more than 5 years

2009-06-07 Thread Karl Berry
Therefore I suggest to patch fmtutil's error detection mechanism and add a special case for LaTeX's 5-year-warning. I didn't know/had forgotten LaTeX had such a warning. Should I write such a patch, would it be accepted? Yes. Thanks, Karl -- To UNSUBSCRIBE, email to debian-bugs

Bug#518800: [tex-live] lamsarrow.sty non-free?

2009-03-10 Thread Karl Berry
%- LamS-TeX copyright - % COPYRIGHT (C) 1989, 1990, 1991 by the Texplorators Corporation, % 1572 West Gray #377, Houston, TX 77019-4948 (ALL RIGHTS RESERVED) %-- That copyrig

Bug#491354: texlive-fonts-extra: No license statement for wsuipa fonts

2008-07-23 Thread Karl Berry
IMHO this is not enough for removal neither from TeX Live upsream nor Debian. I don't plan to remove the wsuipa fonts without some actual confirmation that they are nonfree. Until then, I assume it is carelessness, as in so many other cases. I guess I'll write Pierre MacKay (UW prof,

Bug#419239: [tex-live] Bug#419235: Do you want to keep on maintaining pbox-tex?

2008-02-04 Thread Karl Berry
On CTAN, there's the dtx and ins file and a pbox.pdf, which seems to I updated pbox in TL; now pbox.pdf is included. Thanks, karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#451268: wrong direntries from makeinfo 4.11

2007-12-19 Thread Karl Berry
With 4.11 PLUS your patch from the above it is still happening, Ah, the case before had a @dircategory. I didn't try without. (I surmise that's the difference, anyway.) - insert_string ("START-INFO-DIR-ENTRY\n"); + add_word ("START-INFO-DIR-ENTRY\n"); I installed it. Tha

Bug#451954: Subtle problem with gettext.info

2007-11-24 Thread Karl Berry
INFO-DIR-SECTION GNU Gettext Utilities START-INFO-DIR-ENTRY This is gettext.info, produced by makeinfo version 4.11 from gettext.texi. It's a (quite unfortunate) bug, and I think I've fixed it for the next Texinfo release. karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with

Bug#380128: info: Incorrect (?) (unclear) copyright statement

2006-08-08 Thread Karl Berry
Hi Helge, Then this topic should be discussed in an appropriate form at some I know of no appropriate "forum", but I'll ask rms at some point about changing and standardizing the wording of --version output for GNU packages. Best, karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a

Bug#380128: info: Incorrect (?) (unclear) copyright statement

2006-08-08 Thread Karl Berry
> That sound fine for me. But also if you issue: > info --version Oh. My mistake. help2man just includes the output of --version, I forgot that. > Also here the "version 2 or (at your option) any later version" is > missing. Thats what caused me to open this bug: both the man p

Bug#380128: info: Incorrect (?) (unclear) copyright statement

2006-08-07 Thread Karl Berry
Hi Norbert, Maybe this email got lost somewhere, so Sorry, I've been away. > > Since the file COPYING is not shipped by Debian, I could not check there. Of course the COPYING file in Texinfo is just the GPL, as it is in virtually every (original) GNU distribution. Changing every

Bug#363061: [tex-live] Unclear License of AMSLaTeX

2006-04-28 Thread Karl Berry
- the current LPPL allows to change the internal identification as an alternative to renaming the file, and Indeed, this is the main difference between the "Knuth" license and the current LPPL, as I know you know. - it does not permit to distribute changed versions, even when renam

Bug#357009: Inclusion of new texinfo.tex breaks other packages

2006-03-16 Thread Karl Berry
texinfo.tex and advised me to include the current texinfo.tex, as it will not break other things. Well, I hope I didn't make quite such a blanket statement! What I know is that the currently distributed texinfo.tex (tug.org/tex/texinfo.tex) fixes many bugs over the one in 4.8. Of course

Bug#356853: [tex-live] Bug#356853: tetex-extra: No license information for bbm fonts

2006-03-14 Thread Karl Berry
have any licensing information. They are catalogue'ed as "unknown" and have no license statement in the files. Sigh. I'm sure Gilles simply copied an older version of the CM files which did not have license statements, and intended the same license as CM (inasmuch as he thought about it

Bug#345604: [tex-live] Re: ConTeXt documentation in "commercial" products

2006-01-19 Thread Karl Berry
since there is never the guarantee Guarantees aren't necessary, in my mind. With context, there is probably no way to guarantee that anyone can ever get exactly the same result as you unless they come over to your office and duplicate your disks :). (Probably not even that would be enough.)