headers
Olli J. Marttila | 1 Mar 2011 02:52
Picon
Picon

Re: Issue with Rotated Tables and PS2PDF

28.2.2011 8:00, Swarnendu Biswas kirjoitti:
> Hello,
>
> I want to create a large table in LaTeX sideways, i.e., vertically. This can be done using the rotating
package and sidewaystables
> environment to create rotated tables. We can also use the lscape package to get the same effect. Both these
options are working fine when I am generating a dvi and then creating the pdf from it.
>
> However, I use special symbols in my Xfig figures, and use psfrag for it. Therefore, I first generate the dvi
> file, then the ps file and then the pdf file. But with this approach, the rotated table is not being properly
generated. The output is fine in the intermediate
>   dvi and ps files. But when I am generating the pdf using ps2pdf the
> page orientation of the whole concerned page in the pdf file gets
> distorted to landscape.
>
> It would be nice if someone can help.
>
> Regards,
> Swarnendu Biswas.
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search&  Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> MiKTeX-Users mailing list
> MiKTeX-Users <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/miktex-users
(Continue reading)

Permalink | Reply | 0 comments |
headers
Swarnendu Biswas | 1 Mar 2011 04:37

Re: Issue with Rotated Tables and PS2PDF

Hello,

Yes it is working fine with pdflatex also. 

Thanks and regards,
Swarnendu Biswas.

----- Original Message -----
From: Paul Thompson <Paul.Thompson <at> SanfordHealth.org>
To: miktex-users <at> lists.sourceforge.net
Sent: Tue, 1 Mar 2011 01:44:34 +0530 (IST)
Subject: Re: [MiKTeX] Issue with Rotated Tables and PS2PDF

Can you do this with pdflatex?

Paul A. Thompson, Ph.D.

Additional contact numbers:
Cell: 618-974-0473
Fax: 605-312-6071

-----Original Message-----
From: Swarnendu Biswas [mailto:swarna_cse <at> indiatimes.com] 
Sent: Monday, February 28, 2011 12:01 AM
To: miktex-users <at> lists.sourceforge.net
Subject: [MiKTeX] Issue with Rotated Tables and PS2PDF

Hello, 

I want to create a large table in LaTeX sideways, i.e., vertically. This can be done using the rotating
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ulrike Fischer | 1 Mar 2011 09:42
Picon

Re: Issue with Rotated Tables and PS2PDF

Am Mon, 28 Feb 2011 11:30:40 +0530 (IST) schrieb Swarnendu Biswas:

> Hello, 
> 
> I want to create a large table in LaTeX sideways, i.e., vertically. This can be done using the rotating
package and sidewaystables 
> environment to create rotated tables. We can also use the lscape package to get the same effect. Both these
options are working fine when I am generating a dvi and then creating the pdf from it.
> 
> However, I use special symbols in my Xfig figures, and use psfrag for it. Therefore, I first generate the
dvi 
> file, then the ps file and then the pdf file. But with this approach, the rotated table is not being properly
generated. The output is fine in the intermediate
>  dvi and ps files. But when I am generating the pdf using ps2pdf the 
> page orientation of the whole concerned page in the pdf file gets 
> distorted to landscape.
> 
> It would be nice if someone can help.

Without some code that demonstrates your problem, it is difficult to
know what you mean. In case that you want to avoid the autorotate of
the second page like in the following example, try

ps2pdf -dAutoRotatePages#/None test.ps test.pdf

\documentclass{article}
\usepackage{lscape,lipsum}

\begin{document}
\lipsum[1]
(Continue reading)

Permalink | Reply | 2 comments |
headers
Marko Käning | 1 Mar 2011 10:50
Picon

Re: What causes "rotate 90" warnings

> I think this thread may answer your question - http://www.mail-archive.com/xetex <at> tug.org/msg01528.html
Yep, thanks, that's it.
I just hope there is a way around this.
Doesn't look like it.
But, to tell the truth, I hadn't seen any glitches in the PDF output so 
far. So, I am not too worried.

Thanks,
Marko

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev
Permalink | Reply | 0 comments |
headers
Marko Käning | 1 Mar 2011 10:54
Picon

Re: What causes "rotate 90" warnings

Hi Mike,

yes, you are right, I have to apoligize for my minimalistic approach to 
this issue. I invested too little effort in analyzing the issue myself 
beforehand, I am aware of that. I just hoped I'd find someone who had see 
the same warnings popping up and who knew what to do. ;-)

Anyway, since it looks like it doesn't do any harm to me now - as pointed 
out in my response to David's post a few seconds ago - I just ignore the 
warning.

Thanks,
Marko

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev
Permalink | Reply | 0 comments |
headers
=?iso-8859-15?Q?Agustin_E._Bolz=E1n?= | 1 Mar 2011 16:31

why should I refresh FNDB every time?

I wonder why should I refresh the FNDB every time I

i) add a figure to a tex file (because MikTeX can't fine the file...)

ii) every time I change the name of a tex file, because I get:

! I can't find file `nnnn.aux'.
<to be read again> 
                   \relax 
l.353 \end{document}
Please type another input file name:

As far as I remember, when I used to use version 2.4-2.6, MikTeX had
no problem to find the graphics files if they were in the same folder
as the main tex file. Nowadays, I have to update de database every
time I add a figure to my text.

Am I doing anything wrong or is this the way MikTeX works today?

Best regards,

Agustin

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev
(Continue reading)

Permalink | Reply | 2 comments |
headers
egc | 1 Mar 2011 18:36
Picon

recent update breaks 2.9 in multiple ways...

OK, so did the update this morning. Now,

1\ relative paths to anything (e.g., image files) are broken

Simple minimal example -- first with figure in same directory as .tex file

\documentclass[11pt,letterpaper]{article}
\usepackage{graphicx}
\begin{document}
\begin{figure}[h]
   \begin{center}
       \includegraphics[scale=3,keepaspectratio=true]{fig1.eps}
   \end{center}
\end{figure}
\end{document}

Works fine. Now, move figure to upstream directory, compile fails -- 
can't find fig1.eps:

\documentclass[11pt,letterpaper]{article}
\usepackage{graphicx}
\begin{document}
\begin{figure}[h]
   \begin{center}
       \includegraphics[scale=3,keepaspectratio=true]{../fig1.eps}
   \end{center}
\end{figure}
\end{document}

2\ yap no longer auto renders, and whatever rendering it now uses seems
(Continue reading)

Permalink | Reply | 2 comments |
headers
egc | 1 Mar 2011 18:17
Picon

2.9 | upgrade breaks /includegraphics

Did a recent upgrade this morning -- including the miktex .bin. Seems as 
if something has changed (yet again) in how paths are handled for 
graphics. Such that, things which compiled an hour ago (before the 
update), no longer do -- lots of errors about not being able to find 
graphics.

Sigh.

So, I have a skeleton file for \including lots of chapters. In each 
chapter I have something like

\begin{figure}[ht]
   \begin{center}

\includegraphics[scale=0.8,keepaspectratio=true]{../chapter0/figs/ch0_fig2.eps}
       \end{center}
       \end{figure}

If someone tells me I need to use absolute path names now (or something 
like that) I'm going to say bad words. ;-) I'd have to change ~1500 
images in 28 chapters, for just a single one of my books.

So, what has changed, and what flip do I need to switch to make it work 
the way it used to? I already have the env variable set to let me be 
'unsafe'. What else?

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
(Continue reading)

Permalink | Reply | 1 comment |
headers
egc | 1 Mar 2011 23:34
Picon

recent 2.9 update breaks relative paths

Pre-updarte, following compiles perfectly:

Doing the latest 2.9 upgrade to MikTeX seems to break several things --
most critical of which is that support for relative paths seems to be
completely broken. For example,

\documentclass[11pt,letterpaper]{article}
\usepackage{graphicx}
\begin{document}
\begin{figure}[h]
    \begin{center}
        \includegraphics[scale=3,keepaspectratio=true]{../fig1.eps}
    \end{center}
\end{figure}
\end{document}

Immediately post-updated (replicated on 2 different machines), can no longer
find the image file. I've confirmed that*anything*  that uses relative
paths is now broken, after the update.

And yes, I've already set the env variable to allow such 'unsafe things'
as relative paths.

This is really a critical change, for me. I have 100's to 1000's of images for my books that I generally
include using relative paths. The recent update complete breaks this.

Is there a workaround? And please don't tell me the change is 'for security'. If I wanted someone to change
something (or prohibit something) they though 'unsafe', I'd get a Mac (and let 'Steve' tell me what is and
is not acceptable). ;-)
(Continue reading)

Permalink | Reply | 7 comments |
headers
Ulrike Fischer | 2 Mar 2011 09:11
Picon

Re: why should I refresh FNDB every time?

Am Tue, 1 Mar 2011 12:31:23 -0300 schrieb Agustin E. Bolzán:

> I wonder why should I refresh the FNDB every time I
> 
> i) add a figure to a tex file (because MikTeX can't fine the file...)
> 
> ii) every time I change the name of a tex file, because I get:
> 
> ! I can't find file `nnnn.aux'.
> <to be read again> 
>                    \relax 
> l.353 \end{document}
> Please type another input file name:
> 
> As far as I remember, when I used to use version 2.4-2.6, MikTeX had
> no problem to find the graphics files if they were in the same folder
> as the main tex file. Nowadays, I have to update de database every
> time I add a figure to my text.
> 
> Am I doing anything wrong or is this the way MikTeX works today?

Problably you have stored your document in a texmf-tree. Don't do
this. Move it to a folder where you would also store e.g. a word
document.

--

-- 
Ulrike Fischer 

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
(Continue reading)

Permalink | Reply | 0 comments |

Gmane