Do you want to capitalize on the Biotech Revolution

From Fabrice.Popineau@supelec.fr Sun Mar 11 15:02:00 2001 From: Fabrice.Popineau@supelec.fr (Fabrice Popineau) Date: 11 Mar 2001 16:02:00 +0100 Subject: [fptex] Re: Using fonts from other sources In-Reply-To: <3.0.6.32.20010310224238.007c6120@pop.us.inter.net> ("George A. Stewart"'s message of "Sat, 10 Mar 2001 22:42:38 -0500") References: <3.0.6.32.20010310224238.007c6120@pop.us.inter.net> Message-ID: * George A Stewart writes: > I purchased the Lucida Bright Expert package from Y & Y. It includes > tfm and pfb (glyph) files, which is a large number of files. The > font naming convention is not the same that is used in the TeXLive > 5d distribution. I do not want to rename the files. > I have already used the Lucida font files successfully with a > proprietary version of TeX, known as PCTeX. The files are located in > the following directories: > \PCTeXv4\fonts\user\tfm and \psfonts\pfb > TFMFONTS = > .;{$TEXMF/fonts,$VARTEXFONTS}/tfm//;/PCTeXv4/fonts/user/tfm > ^^^^^^^^^^^^^^^^^^^^^^^^ and You can do that, but I would put a drive specification before /PCTeXv4 > MISCFONTS = .;$TEXMF/fonts/misc//;/;/psfonts ^^^^^^^^^ ^^^^ Are you sure ? It means to look for the files ate root of the current drive, whatevever it is. > The TeX program on TeXLive 5d, fpTex, is able to process a document > which uses these fonts, and it creates a valid dvi file without > errors, but windvi and dvips are not able to process the resulting > dvi file. They cannot find the files they need. On the other hand, > my proprietary PCTeX system is able to read and properly display the > dvi file created by fptex including the Lucida font references. Probably because the right .map files aren't there to allow dvips or windvi to find that these are type1 fonts. I do not have Lucida fonts from Y&Y, but I thought that on CTAN (and hence on the TeXLive) there were files the files needed to use these fonts ? Also, if I'm right, they use a specific encoding (LY1 or something like this). > What do I need to do so that windvi and dvips can handle the non > standard font names (which are kept outsidce the TDS file structure > bugt are communicated to it via texmf.cnf? The paths you setup there are ok, but it is not enough. Forwarding to the fptex list if somebody there can help (Sebastian ?) Fabrice From Fabrice.Popineau@supelec.fr Mon Mar 12 07:58:32 2001 From: Fabrice.Popineau@supelec.fr (Fabrice Popineau) Date: 12 Mar 2001 08:58:32 +0100 Subject: [fptex] newest pdftex win32 version Message-ID: I have updated the standalone win32 binaries for texlive : ftp://ftp.dante.de/pub/fptex/standalone/pdftex-0.14h-pretest-20010310-win32.zip -- Fabrice From biotechinfo2006@yahoo.com Fri Mar 23 13:00:26 2001 From: biotechinfo2006@yahoo.com (biotechinfo2006@yahoo.com) Date: Fri, 23 Mar 2001 13:00:26 Subject: [fptex] FREE Biotech Stock Info! 125 Message-ID: <135.547096.560985@msn.com> Do you want to capitalize on the Biotech Revolution

Do you want to capitalize on the Biotech Revolution? Would you like to add groundbreaking biotech, pharmaceutical and medical device companies to your portfolio mix? Does hearing about exciting IPO and private placement offerings from life sciences companies interest you?

The exclusive Ruddy-Carlisle Biotech Infoline service keeps you abreast of investment opportunities in the life sciences space. Just sign up for it once and get important information instantly delivered to study at your leisure. Our service is 100% FREE! Sign up!

Ruddy-Carlisle Biotech Infoline:

Instantly delivers key life sciences investment information directly to you!
Learn about biotech, pharmaceutical & medical device investment opportunities before others!
Includes IPO & private placement information!
100% FREE!

For the entire last decade there were only three profitable biotech companies. At the end of this year, ten are projected. At the end of 2003, over forty are projected! The genomic promise is about to be delivered and investors know it. The Ruddy-Carlisle Biotech Infoline provides you with critical, decision-making, information that aids the chance of investment success in this lucrative space. Sign up!

Please Note- Your information will only be shared with companies that are in the life sciences space and pass our rigorous inspection. Only the best opportunities will come to you. Ruddy-Carlisle respects your privacy. Sign up!

List Removal Instructions- Simply click here: remove to be instantly and permanently removed from our list. Send the blank email to the address specified. Please do not try to reply to this message. From S.Pepping@elsevier.nl Tue Mar 27 08:29:25 2001 From: S.Pepping@elsevier.nl (Pepping, Simon (ELS)) Date: Tue, 27 Mar 2001 09:29:25 +0200 Subject: [fptex] EuroTeX 2001: Call for papers Message-ID: <4FAD455E0BA3D31196270008C784DAE20271E55F@elsamssonyx.elsevier.nl> Attached please find the Call for Contributions for EuroTeX 2001. For the Program Committee, Simon Pepping Elsevier Science s.pepping@elsevier.nl From S.Pepping@elsevier.nl Tue Mar 27 08:30:25 2001 From: S.Pepping@elsevier.nl (Pepping, Simon (ELS)) Date: Tue, 27 Mar 2001 09:30:25 +0200 Subject: [fptex] EuroTeX 2001: Call for papers Message-ID: <4FAD455E0BA3D31196270008C784DAE20271E560@elsamssonyx.elsevier.nl> This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C0B68F.8CB94BCA Content-Type: text/plain; charset="iso-8859-1" Attached please find the Call for Contributions for EuroTeX 2001. For the Program Committee, Simon Pepping Elsevier Science s.pepping@elsevier.nl ------_=_NextPart_000_01C0B68F.8CB94BCA Content-Type: application/octet-stream; name="call-for-papers.tex" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="call-for-papers.tex" \documentclass[a4paper]{artikel3} \renewcommand{\rmdefault}{phv} \renewcommand{\sfdefault}{phv} \renewcommand{\ttdefault}{pcr} \fontfamily{\rmdefault}\selectfont \usepackage{url} \usepackage[colorlinks]{hyperref} \newcommand{\euromail}{\href{mailto:eurotex-pc@ntg.nl}{eurotex-pc@ntg.nl= }}% \newcommand{\euroweb}{\href{http://www.ntg.nl/eurotex}{www.ntg.nl/eurote= x}}% \addtolength{\textwidth}{2cm} \addtolength{\textheight}{36pt} \pagestyle{empty} \begin{document} \title{Call for Contributions for Euro\TeX~2001} \date{21 March 2001} \author{The Program Committee} \maketitle The Euro\TeX\ conference 2001 will take place from September 23rd to September 27th in the Netherlands. The conference will be held in an old abbey, Rolduc, near the city of Kerkrade. Participants will be welcomed on Sunday evening the 23rd of September. The conference proper will start on Monday and continue until Wednesday. On Thursday courses and tutorials may be given. The theme of the conference is:=20 \begin{center} \TeX\ and Meta\\ the Good, the Bad and the Ugly Bits \end{center} So, what are "Good, Bad and Ugly Bits"? Traditionally we tend to focus on Good Bits because they are so rewarding. It feels good to see a beautifully typeset document that you were able to produce using all the power that \TeX\ and Metafont/MetaPost provide. We try to forget how many Bad Bits we had to overcome, and are proud that we found more or less elegant ways to program around them. Nevertheless, some of these difficulties should be regarded as Ugly Bits that would not exist in an ideal world. What can we do?=20 First of all, keep up the Good Bits and extend them if possible. Analyze the Bad Bits, learn from them, and find easy and generic ways to get around them. Find the Ugly Bits and eradicate them! Let's make progress! Of course we need a lot of discussion to distinguish between Good, Bad and Ugly, and about ways to deal with them. We invite you all to demonstrate either of these bits. Feel free to present your application (Good, not Bad or Ugly) at the conference! At this conference we would like to take a new view on contributions. \begin{itemize} \item Of course we welcome a presentation accompanied by a written paper, as usual. \item But does it bother you to write a paper, or does your contribution seem fit for an interesting presentation but not for a written paper? We will welcome the presentation equally much, and do with only a short summary on paper or even entirely without the paper work. \item Or do you find yourself in the opposite situation: You would like to clarify your new package or other work extensively on paper but believe that it would be unsuitable to cover it equally extensively in an oral presentation? Feel free to let us have your paper and at the conference present only the highlights. \item Or do you believe your ideas only warrant a short presentation without a paper? It is equally welcome. \end{itemize} We do expect from each contributor a \emph{short summary} of the proposed contribution. This summary will inform the Program Committee of your plan. And at the conference it will be the introduction to your contribution, or your complete contribution if that is what you propose. We invite you to submit your proposal for a contribution to the conference. You can send it by email to \euromail. If you have no access to e-mail you can send your contribution to: \begin{flushleft} Euro\TeX\ 2001 program committee\\ Spuiboulevard 269\\ 3311 GP Dordrecht\\ The Netherlands. \end{flushleft} In such a case we would ask you to submit your paper in electronic form on a floppy disk. We are working with the following time schedule: \begin{center} \begin{tabular}{ll} may 10 & deadline for receiving proposals\\ june 10 & deadline for receiving full draft papers\\ july 11 & end of review\\ august 11 & deadline for receiving final, reviewed papers\\ \end{tabular} \end{center} An up-to-date list of contributions as well as more information about the conference can be found at \euroweb. \end{document} ------_=_NextPart_000_01C0B68F.8CB94BCA-- From Fabrice.Popineau@supelec.fr Fri Mar 30 08:30:57 2001 From: Fabrice.Popineau@supelec.fr (Fabrice Popineau) Date: 30 Mar 2001 09:30:57 +0200 Subject: [fptex] gs 6.62 Message-ID: There seems to be a bug in it, indepently of the fact that the gs dll api will change. So currently, gsftopk fails to work with it. -- Fabrice