On Thu, 27 Jan 2000 12:49:03 -0800, Karl Nelson wrote:
>> On Thu, 27 Jan 2000 11:47:55 +1000 (GMT+1000), Allan Rae wrote:
>>
>> >The first draft of libsigc++ integration uses a slightly modified version
>> >of the libsigc++ configure.in in the sigc++ directory. Hmmm, does NT let
>> >you have a
At least in one of the files that would not index, I found the problem
by exporting to LaTeX and running latex on the .tex file. It complained
about subfigure captions on imported .ps files. They did not show up
anyway, so I turned them off. Then my index showed up. Very weird I
would say.
But les
On Thu, 27 Jan 2000, Dr. Ing. Roland Krause wrote:
> Allan,
> long post indeed.
and getting longer...
>
> > I've cut down the number of signal and slot templates that are generated
> > (Signal0-Signal2 only for now
>
> I do not really see why you are doing this. At present it would be
> bette
Hi,
these messages refer to lyx-devel of January, 27th.
Happy debugging,
Michael
--
==
Michael Schmittphone: +49 451 500 3725
Institute for Telematics secretary: +49 451 500 3
> On Thu, 27 Jan 2000 11:47:55 +1000 (GMT+1000), Allan Rae wrote:
>
> >The first draft of libsigc++ integration uses a slightly modified version
> >of the libsigc++ configure.in in the sigc++ directory. Hmmm, does NT let
> >you have a directory called "sigc++"? What about OS/2?
>
> OS/2-HPFS (
Guys
Thanks for your assistance re the fonts. I think it's easier to stick with the
\usepackage{pslatex} to overcome the rendering of the fonts in Acroread.
I've attached the pdfslide.lyx and pdfslide.layout.
The resulting PDF file can be found at
http://www.soton.ac.uk/~bscazz/pdfslide.pdf
Allan,
long post indeed.
Allan Rae wrote:
> I noticed you filed a report to the libsigc++ list.
Yes, I havent gotten any replies, I have not subscribed to the list but the issue
was:
libsigc++ version 0.8.5 compiles and works on cygnus b20 NT version 0.8.6 does not
compile due to a faulty confi
OK, I just tried an example here with tetex-0.9 using pdflatex:
font encoding OT1 --> Type1 fonts (vector fonts)
font encoding T1 --> Type3 fonts (bitmapped)
Viewing the pdf file with
Ghostview: Type3 fonts look better than Type1 fonts (Ghostview can
anti-alias bitmapped fonts but n
Hi all,
Just to let you know that cross-referencing doesn't work with my build
of lyx-1.1.4pre2. When you click on a cross-reference on any new file
and even on the tutorial.lyx and userguide.lyx files, lyx doesn't move
the prompt as it used to do. Moreover, if you'd like to insert a
cross-refere
> "Horst" == Horst G Kausch <[EMAIL PROTECTED]> writes:
Horst> With modern tetex distributions you get a good set of Type1
Horst> fonts for the standard Computer Modern fonts but not for the
Horst> ecmr* fonts! Hence the problems with PDF output when using font
Horst> encoding T1. \usepackage
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>
> > "Ben" == Ben Cazzolato <[EMAIL PROTECTED]> writes:
>
> Ben> I have a problem with the latex that Lyx is generating, in
> Ben> particular the following command which is found in the first few
> Ben> lines: \usepackage[T1]{fontenc}
>
> Th
> "Ben" == Ben Cazzolato <[EMAIL PROTECTED]> writes:
Ben> Guys I'm in the process of making Lyx compatible with pdfslide
Ben> since it gives a little more flexibility than foils or standard
Ben> slides.
Ben> I have a problem with the latex that Lyx is generating, in
Ben> particular the follo
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> It seems to me that we have managed to remove the worst bugs and
Lars> is absolutely no worse off than 1.1.3.
Lars> I know there are some space issues, and some "update dvi"
Lars> reports, I do not understand how this happens
Guys
I'm in the process of making Lyx compatible with pdfslide since it gives a
little more flexibility than foils or standard slides.
I have a problem with the latex that Lyx is generating, in particular the
following command which is found in the first few lines:
\usepackage[T1]{fontenc}
Wit
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes:
Amir> Well, that's pretty lame, even if you're trying to hide it by
Amir> writing it in french. Could you perhaps convince one of the
Amir> french translators to write up a quick web page in french?
The problem right now is rather to convi
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> I must admit then that I am not sure what the correct should be,
Lars> perhaps we should revert to the original code.
Probably.
Lars> I am not even sure that --format is needed. Perhpas we should
Lars> try to drop it.
Lars>
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> mmm...I want to do that...but so far I have not dared.
Lars> Eventually "using" should not be used in headers at all, and as
Lars> little as possible in filescope.
You mean we'll be forced to add std:: in front of all STL iden
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> [EMAIL PROTECTED] writes: | Are ascii format archives (plzzeee
Lars> not html) | of the lyx mailing lists available anywhere?
Lars> To my knowledge no. (unless they serve as basis for the html
Lars> pages somewhere.)
It i
On Thu, 27 Jan 2000 11:47:55 +1000 (GMT+1000), Allan Rae wrote:
>The first draft of libsigc++ integration uses a slightly modified version
>of the libsigc++ configure.in in the sigc++ directory. Hmmm, does NT let
>you have a directory called "sigc++"? What about OS/2?
OS/2-HPFS (the standard):
19 matches
Mail list logo