3 Dec 2005 22:21

### larm0900

I have next code

\documentclass{amsbook}
\usepackage{cmap}
\def\UseRussian{}
\usepackage[cp1251]{inputenc}
\usepackage[english,russian]{babel}
\selectlanguage{russian}
\usepackage{epigraph}
\begin{document}
\title{Mathematical Principles of\\General Relativistic Quantum Theory}
\begin{abstract}
I tell about different mathematical tool that is important in general
relativity.
\end{abstract}
\epigraph{Without question, intellect seems to be faint
when we think about problems standing in face of it}
{Einstein}
\end{document}

I got error

! Font T2A/cmr/m/n/9=larm0900 at 9.0pt not loadable: Metric (TFM) file not
foun
d.
relax
l.19       {Einstein}

I wasn't able to read the size data for this font,


4 Dec 2005 16:47

### RE: larm0900

I try your code via winedt texify and winedt pdftexify and all is ok (no
message). You need to reinstall miktex from beginning. I do this if I have
such problems that other don't have. But this is a very lazy solution but
efficient if you don't have time.

Best regards

Pierre

Here is the log file if it could help

This is pdfeTeX, Version 3.141592-1.21a-2.2 (MiKTeX 2.4) (preloaded
format=latex 2005.11.26)  4 DEC 2005 16:37
entering extended mode
**amsbo.tex
(amsbo.tex
LaTeX2e <2003/12/01>
Babel <v3.8g> and hyphenation patterns for english, french, german, ngerman,
du
(C:\texmf\tex\latex\amscls\amsbook.cls
Document Class: amsbook 2004/08/06 v2.20
\linespacing=\dimen102
\normalparindent=\dimen103
\normaltopskip=\skip41
(C:\texmf\tex\latex\amsmath\amsmath.sty
Package: amsmath 2000/07/18 v2.13 AMS math features
\ <at> mathmargin=\skip42

For additional information on amsmath, use the ?' option.


4 Dec 2005 23:53

### append LaTeX search path

Hi,

is there an alternative to TEXINPUTS - which seems to be ignored with
MiKTeX -- other than command line switch -include-directory'? I'm
trying to append LaTeX's search path in a portable make file that works
with MiKTeX as well as with unix flavors of LaTeX, e.g., tetex.
Unfortunately, the letter seems to ignore -include-directory'. It would
be sad if there's no portable solution to extend the path. Any ideas?

Regards
Stephan Hennig

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files

5 Dec 2005 09:32

### Re: append LaTeX search path

On Sun, Dec 04, 2005 at 11:53:58PM +0100, Stephan Hennig wrote:
> Hi,
>
> is there an alternative to TEXINPUTS - which seems to be ignored with
> MiKTeX -- other than command line switch -include-directory'? I'm
> trying to append LaTeX's search path in a portable make file that works
> with MiKTeX as well as with unix flavors of LaTeX, e.g., tetex.
> Unfortunately, the letter seems to ignore -include-directory'. It would
> be sad if there's no portable solution to extend the path. Any ideas?
>
> Regards
> Stephan Hennig

You can put extra input files in subdirectories and refer to
them as something like sub/file' or sub/file.tex'. Other
_relative_ paths work as well: \usepackage{../styles/mystyle}'

You could also use a project-specific texmf tree, containing just
the extra LaTeX files. Activating and deactivating an extra texmf
tree in MikTeX involves modifying registry entries, which would
require some sort of scripting language, and regenerating the
filename database, for which there is a commandline command, viz.
initexmf --update-fndb'. It would be a good solution if your
project required a lot of custom stuff.

But if it is just some stylefiles and graphics, relative paths is
the way to go.

--

--
Siep Kroonenberg


5 Dec 2005 16:15

### Re: append LaTeX search path

Siep Kroonenberg schrieb:
> On Sun, Dec 04, 2005 at 11:53:58PM +0100, Stephan Hennig wrote:
>>
>> is there an alternative to TEXINPUTS - which seems to be ignored with
>> MiKTeX -- other than command line switch -include-directory'?
>
> You can put extra input files in subdirectories and refer to
> them as something like sub/file' or sub/file.tex'. Other
> _relative_ paths work as well: \usepackage{../styles/mystyle}'
>
> You could also use a project-specific texmf tree, containing just
> the extra LaTeX files. [...] It would be a good solution if your
> project required a lot of custom stuff.

-- more straight forward -- solution is difficult to implement since I'm
working with lots of source files (200+), that either input files from
other directories or are input from files in other directories. Moreover
I don't like to add file system information in source files. It would be
hard to change or at least needs manual review.

The latter solution seems more appropriate. However, I don't know yet
how a portable solution with a new texmf tree looks like.

That's why I'm currently evaluating a third solution: trying to get
system information through the make file and acting distribution
dependent. That's still not satisfying. I'm still wondering why MiKTeX
isn't sensible to TEXINPUTS.

Regards


5 Dec 2005 16:45

### Re: Using Adobe Palatino and non-CMR Math Fonts on Windows

Success in getting Palatino and Mathematica fonts to work
in MikTeX.  Thanks very much for getting me started.

The problem turned out to be a bit simpler than what I
had expected - it was basically getting the font names
to correspond to the file names in the TeX prolog we
were using to set up the formatting.  Thereafter everything
fell into place.  I will note that I did experiment a bit
with "initexmf -u" and putting things in localtexmf.
After getting brave enough to try that, it turned out
they weren't necessary.  However, without the
encouragement from the mailing list, it would probably
have taken a good deal longer to do.

Again, thanks - and season's greetings.

Bruce R. Barkstrom

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files

6 Dec 2005 16:12

### a perfect dvi with .eps files creates a very bad pdf ?!

Dear all,

I will be very grateful if you can help me with a problem concerning the tex-file of my PhD thesis.
I use Matlab to create my eps files. Since the original files are with large bounding box (BB) I  change it manually either in the .txt code of the .eps file or by the ghostview options. As a result I have a tight bounding box, no warnings. It seems that the new eps is healthy.

In the tex file I include the graphics in the standard way:

\begin{figure}[hpbt]
\centering
\includegraphics[width=1\textwidth]{test.eps}\\
\caption{caption}
\label{test1}
\end{figure}

As an alternative I have tried also the following:
I take the original .eps file from MATLAB (with the large BB) and include it as:

\begin{figure}[hpbt]
\centering
\epsfig{file=test.eps, bbllx=84, bblly=229, bburx=426,
bbury=486,width=1\textwidth}
\caption{caption}
\label{test1}
\end{figure}

In both ways I get a perfect DVI file!!

However the problem is to create a pdf.
I tried
dvi->pdf
or
dvi->ps->pdf

but always the .eps files from MATLAB show up with large white borders around the graphics that eat part of the text.

Do you have an idea what I can do about that?

Best regards,
Margarita

6 Dec 2005 16:30

### Re: a perfect dvi with .eps files creates a very bad pdf ?!

Actually, the problem is in matlab  eps file. I do my figures in
matlab usually, and it puts a white square begind every figure it
creates... the best way is to use some eps editor (like CorelDraw) and
delete unnecessary ps elements.

Regards, Dario.

It is not a miktex/latex problem after all! :)

On 12/6/05, Margarita Simeonova <mimeona <at> googlemail.com> wrote:
> Dear all,
>
> I will be very grateful if you can help me with a problem concerning the
> tex-file of my PhD thesis.
> I use Matlab to create my eps files. Since the original files are with large
> bounding box (BB) I  change it manually either in the .txt code of the .eps
> file or by the ghostview options. As a result I have a tight bounding box,
> no warnings. It seems that the new eps is healthy.
>
> In the tex file I include the graphics in the standard way:
>
> \begin{figure}[hpbt]
> \centering
>   \includegraphics[width=1\textwidth]{test.eps}\\
> \caption{caption}
>  \label{test1}
> \end{figure}
>
> As an alternative I have tried also the following:
> I take the original .eps file from MATLAB (with the large BB) and include it
> as:
>
> \begin{figure}[hpbt]
> \centering
> \epsfig{file=test.eps, bbllx=84, bblly=229, bburx=426,
> bbury=486,width=1\textwidth}
> \caption{caption}
> \label{test1}
> \end{figure}
>
> In both ways I get a perfect DVI file!!
>
> However the problem is to create a pdf.
> I tried
>  dvi->pdf
> or
> dvi->ps->pdf
>
> but always the .eps files from MATLAB show up with large white borders
> around the graphics that eat part of the text.
>
> Do you have an idea what I can do about that?
>
> Best regards,
> Margarita

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files

6 Dec 2005 17:16

### Re: a perfect dvi with .eps files creates a very bad pdf ?!

Dear Margarita,

I agree with other commenters that this is a problem with the way you
build your eps files in MATLAB, and is not a miktex problem.  I have
written textbooks containing hundreds of MATLAB created files and miktex
without facing the problem you describe.  If you simply let MATLAB use
its defaults and then save with the command

>> print -depsc <filename>

you should have no difficulty.  However, some times you want the figure
to be a different size than the default.  In such a case you should take
more care in the m-file you use to construct the graphic.  I will send
you an example off line in order not to abuse the privileges of this
news group, which is not devoted to MATLAB.

John

Margarita Simeonova wrote:

> Dear all,
>
> I will be very grateful if you can help me with a problem concerning
> the tex-file of my PhD thesis.
> I use Matlab to create my eps files. Since the original files are with
> large bounding box (BB) I  change it manually either in the .txt code
> of the .eps file or by the ghostview options. As a result I have a
> tight bounding box, no warnings. It seems that the new eps is healthy.
>
> In the tex file I include the graphics in the standard way:
>
> \begin{figure}[hpbt]
> \centering
>   \includegraphics[width=1\textwidth]{test.eps}\\
> \caption{caption}
>  \label{test1}
> \end{figure}
>
> As an alternative I have tried also the following:
> I take the original .eps file from MATLAB (with the large BB) and
> include it as:
>
> \begin{figure}[hpbt]
> \centering
> \epsfig{file=test.eps, bbllx=84, bblly=229, bburx=426,
> bbury=486,width=1\textwidth}
> \caption{caption}
> \label{test1}
> \end{figure}
>
> In both ways I get a perfect DVI file!!
>
> However the problem is to create a pdf.
> I tried
>  dvi->pdf
> or
> dvi->ps->pdf
>
> but always the .eps files from MATLAB show up with large white borders
> around the graphics that eat part of the text.
>
> Do you have an idea what I can do about that?
>
> Best regards,
> Margarita

--

--
John C. Polking
(713) 348-4841 (Office)
Department of Mathematics        (713) 348-4829 (Dept of Math)
Rice University                  (713) 348-6120 (FAX)
PO Box 1892                      polking <at> rice.edu
Houston, TX 77251                http://math.rice.edu/~polking

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
`