WinEdt Team | 4 Jan 23:07 2010

MiKTeX 2.8: "e" command fails

Inverse Search in YAP works and auto-detection of editor works
fine in YAP's Options. However, the "e" response at the command
prompt when TeX encounters an error fails if the path to the
editor executable contains spaces. For example, the following
message is displayed:

'C:\Program' is not recognized as an internal or external
command, operable program or batch file.

This has been the case with all versions of 2.8 including the
latest update. It worked correctly in MiKTeX 2.7. It appears
that the executable is "stripped" of double quotes when
launched from command prompt...

Best regards,

alex

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
J.Fine | 5 Jan 17:14 2010
Picon
Picon

dvips -D not finding generated font for resolution not 600dpi

Hi

I've a problem: dvips is not finding a generated font.

I'm running MiKTeX2.7, and the problem occurs only when I use the -D parameter, which specifies the
resolution to be used for generated fonts.

Below are some examples of the output I get.  Any suggestions as to what might be going wrong would be much appreciated.

=====
$ dvips -D 1270 tmp/10mu123u6.dvi
This is dvips(k) 5.96dev Copyright 2007 Radical Eye Software (www.radicaleye.com)
' TeX output 2009.12.17:1618' -> 10mu123u6.ps
Trying to make PK font oulogo10 at 1270 DPI...
Creating oulogo10.pk...
Running mf...
This is METAFONT, Version 2.718281 (MiKTeX 2.7)

(C:/LTS-TeX/fonts\fonts\source\oulogo10.mf
The letter T [1]
The letter h [2]
The letter e [3]
The letter O [4]
The letter p [5]
The letter n [6]
The letter U [7]
The letter i [8]
The letter v [9]
The letter r [10]
The letter s [11]
(Continue reading)

J.Fine | 5 Jan 17:18 2010
Picon
Picon

Re: dvips -D not finding generated font for resolution not 600dpi

Hi

I get the same problem with cm fonts.  For example
===
$ tex story\\end
This is TeX, Version 3.1415926 (MiKTeX 2.7)
("C:\Program Files\MiKTeX 2.7\tex\plain\base\story.tex" [1])
Output written on story.dvi (1 page, 680 bytes).
Transcript written on story.log.

jf3243 <at> pclt1384 ~/My Documents/SmallProjects/tex_courses/mu123/build_10mu123u6
$ dvips -V -D 1270 story.dvi
This is dvips(k) 5.96dev Copyright 2007 Radical Eye Software (www.radicaleye.com)
' TeX output 2010.01.05:1618' -> story.ps
Trying to make PK font cmbx10 at 1270 DPI...
The PK font file "C:\Documents and Settings\All Users\Application
Data\MiKTeX\2.7\fonts/pk/linoone/public/cm/dpi1270\cmbx10.pk" already exists.
c:\Program Files\MiKTeX 2.7\miktex\bin\dvips.exe: Font cmbx10 not found, characters will be left blank.
Trying to make PK font cmsl10 at 1270 DPI...
The PK font file "C:\Documents and Settings\All Users\Application
Data\MiKTeX\2.7\fonts/pk/linoone/public/cm/dpi1270\cmsl10.pk" already exists.
c:\Program Files\MiKTeX 2.7\miktex\bin\dvips.exe: Font cmsl10 not found, characters will be left blank.
Trying to make PK font cmr10 at 1270 DPI...
The PK font file "C:\Documents and Settings\All Users\Application
Data\MiKTeX\2.7\fonts/pk/linoone/public/cm/dpi1270\cmr10.pk" already exists.
c:\Program Files\MiKTeX 2.7\miktex\bin\dvips.exe: Font cmr10 not found, characters will be left blank.
<C:/Program Files/MiKTeX 2.7/dvips/base/tex.pro>. [1]
===

--
(Continue reading)

Bruce Babcock | 8 Jan 16:27 2010
Picon

pdftex problem

Under XP, from a command line, if I enter

pdftex foo.tex

I get foo.pdf, but when I view the pdf it looks like a A4 output.

However, if I enter

tex foo.tex

then

dvips foo.dvi

then

ps2pdf foo.ps

I get foo.pdf and when I view the pdf it gives me a Letter output.

So, my questions is how do I configure pdftex so it will produce a 
letter output instead a A4 output.

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
(Continue reading)

George N. White III | 8 Jan 18:13 2010
Picon

Re: pdftex problem

On Fri, Jan 8, 2010 at 11:27 AM, Bruce Babcock <babcock <at> math.psu.edu> wrote:

> Under XP, from a command line, if I enter
>
> pdftex foo.tex
>
> I get foo.pdf, but when I view the pdf it looks like a A4 output.
>
> However, if I enter
>
> tex foo.tex
>
> then
>
> dvips foo.dvi
>
> then
>
> ps2pdf foo.ps
>
> I get foo.pdf and when I view the pdf it gives me a Letter output.
>
> So, my questions is how do I configure pdftex so it will produce a
> letter output instead a A4 output.

You don't mention what version of MiKTeX -- older versions used a
different configuration for pdftex.

The paper size used by recent pdftex is set in pdftexconfig.tex, but you should
not edit that files directly, but follow the adice in the comments.  You can
(Continue reading)

Bruce Babcock | 9 Jan 03:04 2010
Picon

Re: pdftex problem

George,

Sorry, I am running MiKTeX 2.8.

I ran "kpsewhich pdftexconfig.tex"  and in pdftexconfig.tex it told me to

initexmf --edit-config-file pdftex

and in this file I made

page_width 8.5 true in
page_height 11 true in

and saved the changes.  I then ran pdftex foo.tex and again when I 
looked at the foo.pdf, I still had an A4 ouput and not a Letter. :(

So do you (or any others) have further ideas to try?

bruce

went to the followed the instructions

George N. White III wrote:
> On Fri, Jan 8, 2010 at 11:27 AM, Bruce Babcock <babcock <at> math.psu.edu> wrote:
> 
>> Under XP, from a command line, if I enter
>>
>> pdftex foo.tex
>>
>> I get foo.pdf, but when I view the pdf it looks like a A4 output.
(Continue reading)

David Allsopp | 9 Jan 08:48 2010

Re: pdftex problem

Bruce Babcock wrote:
> George,
> 
> Sorry, I am running MiKTeX 2.8.
> 
> I ran "kpsewhich pdftexconfig.tex"  and in pdftexconfig.tex it told me
> to
> 
> initexmf --edit-config-file pdftex
> 
> and in this file I made
> 
> page_width 8.5 true in
> page_height 11 true in
> 
> and saved the changes.  I then ran pdftex foo.tex and again when I
> looked at the foo.pdf, I still had an A4 ouput and not a Letter. :(
> 
> So do you (or any others) have further ideas to try?

Which TeX format are you using? The format (or file) can override the page
specification using \pdfpagewidth or \pdfpageheight. To see whether your
change has worked, run:

$ pdftex
This is pdfTeX, Version 3.1415926-1.40.10 (MiKTeX 2.8)
**\showthe\pdfpagewidth
> 597.50787pt.
<*> \showthe\pdfwidth

(Continue reading)

Bruce Babcock | 9 Jan 11:44 2010
Picon

Re: pdftex problem

David Allsopp wrote:

 > $ pdftex
 > This is pdfTeX, Version 3.1415926-1.40.10 (MiKTeX 2.8)
 > **\showthe\pdfpagewidth
 >> 597.50787pt.
 > <*> \showthe\pdfwidth
 >
 > is the output for A4. For US letter, it should be 614.295pt

When I entered "pdftex" followed by "**\showthe\pdfpagewidth" I got  the 
message

entering extended mode
 > 614.295pt.

So, the output is for US letter.  Yet, running "pdftex foo.tex" still 
moved the page number at the bottom of the page up, like 1" and what I 
was calling A4 may be wrong?  Yet, in foo.tex if at the top of the file 
I enter

\pdfpagewidth 8.5 true in
\pdfpageheight 11 true in

and then run "pdftex foo.tex" the problem is solved.  So, this does 
solve my problem.  But, should this be necessary?

> Bruce Babcock wrote:
>> George,
>>
(Continue reading)

Ulrike Fischer | 9 Jan 13:17 2010
Picon

Re: pdftex problem


am Samstag, 9. Januar 2010 um 03:04 schrieb Bruce Babcock:

> George,

> Sorry, I am running MiKTeX 2.8.

> I ran "kpsewhich pdftexconfig.tex"  and in pdftexconfig.tex it told me to

> initexmf --edit-config-file pdftex

> and in this file I made

> page_width 8.5 true in
> page_height 11 true in

> and saved the changes.  I then ran pdftex foo.tex and again when I 
> looked at the foo.pdf, I still had an A4 ouput and not a Letter. :(

pdftex.cfg is used during the format generation: Its content is copied
to pdftexconfig.tex and this file is input by the .ini used for the
format. So changes in pdftex.cfg will have an effect only after you
regenerate the format.

But it shouldn't be necessary to set the default paper size in
pdftex.cfg. There is a drop down menu for this in miktex settings.

> When I entered "pdftex" followed by "**\showthe\pdfpagewidth" I got  the
> message
> 
(Continue reading)

Benoit RIVET | 9 Jan 15:00 2010
Picon

Compiling Miktex Tools on Mac OS X.6

I just subscribe to the Miktex User List, and it's not clear to me where I can find archives of past
conversation, so please do accept my apology if my problems have already been reported and/or solved previously.

I'm trying to compile the latest version of miktex tools on a brand new Mac OS X.6 (Snow Leopard) system. I
stumbled on a first bug about malloc (while about 31% of compiling was finished) :

error: malloc.h: No such file or directory

which the log file said was related to line 26 of gram.y (in Build Utilities/c4p).

Googling this error gave me a simple fix : changing line 26 of gram.y (in Build Utilities/c4p) from

#include <malloc.h>

to 

#include <malloc/malloc.h>

helped solve the problem. Compiling again gives another challenging problem. Here is the relevant part of
the compilation log :

Scanning dependencies of target ui-Qt-static
[ 56%] Building CXX object Libraries/MiKTeX/UI/Qt-static/CMakeFiles/ui-Qt-static.dir/__/Qt/ConnectionSettingsDialog.cpp.o
In file included from /Library/Frameworks/QtCore.framework/Headers/qnamespace.h:45,
                 from /Library/Frameworks/QtCore.framework/Headers/qobjectdefs.h:45,
                 from /Library/Frameworks/QtCore.framework/Headers/qobject.h:47,
                 from /Library/Frameworks/QtCore.framework/Headers/qiodevice.h:46,
                 from /Library/Frameworks/QtCore.framework/Headers/qxmlstream.h:45,
                 from /Library/Frameworks/QtCore.framework/Headers/QtCore:3,
                 from /Library/Frameworks/QtGui.framework/Headers/QtGui:3,
(Continue reading)


Gmane