Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Andreas

Pages: 1 ... 6 7 [8] 9 10
106
Bug Reports / Re: Don't get what I see, figure messes up
« on: August 08, 2008, 12:45:59 AM »
Quote from: Holmogorov on August 06, 2008, 10:12:16 PM
After exporting to .eps or other format the picture that I am getting is messed up. The shapes are close but they are noticeably far from what i see in WinFig.

I found the problem. A fix will be available in the next release. Thx for pointing me at this!

107
Bug Reports / Re: Don't get what I see, figure messes up
« on: August 07, 2008, 04:34:54 PM »
yes, pstex_t ist just the file name suffix of the TeX file that is generated. pstex export generates two files, one with TeX contents (pstex_t), and one with graphics (EPS).

108
Bug Reports / Re: Don't get what I see, figure messes up
« on: August 07, 2008, 01:19:32 AM »
Can you send me your input and output files?

109
Feature Requests / Re: Smart links mode?
« on: June 09, 2008, 05:14:04 PM »
no, there is none, but it will be in the next release.

110
Bug Reports / Re: Flipping Text
« on: March 05, 2008, 12:04:55 AM »
Yes, it looks like you found a bug. I checked the code and found that I never implemented text flipping. I put it on my todo list. Thanks! Shouldn'tbe so difficult, since text rotation was already done.

111
General Discussion / Re: exporting via eps to other programs
« on: March 03, 2008, 02:23:17 PM »
Quote from: jco255 on March 03, 2008, 07:15:16 AM
I've noticed that a lot of eps-reader programs are not able to load the
eps output format form winfig. for example, i have friends using macromedia
freehand and they cannot import winfig exports such as eps. is there another
way to transfer the vectors? i tried pdf, hpgl, cgm, emf, pdf and svg (although
svg alone worked in inkscape).

This shows again that many Windows programs have a poor PostScript-support. If yous ay "are not able", does that mean they show some error message indicating where exactly the problem is? Generally WinFIG/Xfig produces quite a good PostScript code that is much better than what many Windows programs provide i.e. via PostScript printer drivers.

Exchanging via EMF should work too. I tested with word.

You could still try to load the PS output in GhostView and save from there. Perhaps this creates different header information.

112
Bug Reports / Re: Export generates empty files
« on: February 08, 2008, 05:43:40 PM »
Quote from: DerTroll on February 08, 2008, 09:33:28 AM
Indeed, now the conversion to bitmaps works. But rendering of special-flaged LaTeX-commands is not possible this way. The Logfile shows nothing and there is no Errormessage at command line either. Do I have to put some LaTeX-Paths to the Systempath?!

I never really used the pictex export. Perhaps it's a bug or a feature. Anyway, I recommend using the pstex export. This gives you full PostScript power combined with LaTeX formatting. PSTricks is also a nice alternative.

Quote
But all together a very cool and usefull programm. Never used XFig but always wanted to create presentations with Latex and therefore needed a way to build Powerpoint-like graphics. So thanks for this nice prog and very fast support!

Thanks for the appreciation. I still have a lot of enhancements in mind. Currently I'm working on smart links, which are very useful for flow charts or UML diagrams.

113
Bug Reports / Re: Export generates empty files
« on: February 08, 2008, 01:12:31 AM »
Quote from: DerTroll on February 07, 2008, 03:59:25 PM
Using the export-function generates empty output-files. This occurs using export as bitmap and pictex with no error message.  :'(

The export of bitmap formats and PDF requires a GhostScript installation. Do you have one? If so, try to call fig2dev from the command line like this:

fi2dev-exe -L png infile.fig outfile.png

This should give you a helpful error message, i.e. "gswin32c.exe is not recognized as an internal or external command".

There is a different problem regarding pictex export. fig2dev really seems to crash.

Edit: found the problem. A call to time(&when); was missing in genpictex.c  I will release a fix shortly.

114
WinFIG and LaTeX / Re: pstex ohne Formatierung
« on: November 15, 2007, 12:18:09 AM »
ja, sieht so aus, daß die Größe immer gesetzt wird. Der Parameter "don't set font face, series and style" wirkt sich nicht auf das Setzen der Größe aus. Wäre es so schlimm, die Textobjekte einfach mit der gewünschten Größe in der Zeichnung anzulegen?

Möglicherweise kann man auch irgendwie das Makro SetFigFont vorher so definieren, daß es nichts tut:
\begingroup\makeatletter\ifx\SetFigFont\undefined%
\gdef\SetFigFont#1#2{}%
\fi\endgroup%

bzw.

\begingroup\makeatletter\ifx\SetFigFont\undefined%
\gdef\SetFigFont#1#2#3#4#5{}%
\fi\endgroup%

Scheint zu funkionieren.

115
WinFIG and LaTeX / Re: eps file including latex formular
« on: November 03, 2007, 03:13:39 PM »
really, you only have to sort out your suffix problem. The files itself have not changed. If it does not work, you are including the wrong file in the wrong place or with the wrong name.

I do the following:
1. create a FIG file winfig.fig
2. export to pstex_t
3. now I have winfig.pstex_t with LaTeX text and winfig.eps with graphics.
4. I write a LaTeX document with the name foo.tex

foo.tex contains the following:

\documentclass[11pt]{article}
\usepackage{color}
\usepackage{graphicx}
\begin{document}

\input{winfig.pstex_t}

\end{document}


That works. I can call latex and have foo.dvi after that.

The following works too:
\documentclass[11pt]{article}
\usepackage{color}
\usepackage{graphicx}
\begin{document}

\begin{figure}
\input{winfig.pstex_t}
\end{figure}

\end{document}


Btw your first suggestion that the EPS file contains the formula is a nice idea, but not possible, because WinFIG shows the formula as graphics, which is a pixel bitmap. It is possible to have that in an EPS file, but the resolution is fixed. The printed results would look ugly. It is much better to have LaTeX create a PostScript version of the formula and print that. The printer driver can convert that to the appropriate resolution.

116
WinFIG and LaTeX / Re: eps file including latex formular
« on: October 31, 2007, 11:52:50 AM »
Quote from: scho on October 30, 2007, 11:01:39 PM
When I export to eps file, the included latex formular is remains not converted although I already have the converted formular in the WinFIG window.
It would be convinient if we have eps figure including converted latex formular directly.

The EPS cannot contain the latex formula. Sounds interesting, but is not the way it works right now. You have to export using PSTEX. Then you have the LaTeX file, which makes an "include" on the EPS file.

Quote
So I had to export to pstex, but still I have a problem.
On the version 2.2, the figure is converted to pstex_t file and "eps" file.
What I need are just pstex_t and "pstex" file.
(On older version, I have got pstex_t and "pstex" files with no problem.)

Yes, the suffix was  changed in 2.1 already from pstex to eps. But the include directove was also changed from
\includegraphics{foo.pstex}
to
\includegraphics{foo.eps}

So, it should still work. You have a LaTex file with suffix pstex_t, which has an include directive on an EPS file with suffix eps.

117
Feature Requests / Re: MOVE object
« on: October 31, 2007, 11:47:21 AM »
There is a new "Select" button. It is the first one in the toolbar (with the arrow). To move an object very little choose that "Select" tool, select the item in the drawing and use the cursor keys to move pixel-wise. This is the most convenient way.

118
WinFIG and LaTeX / Re: Viewing LaTex strings in WinFIG
« on: October 05, 2007, 03:48:11 PM »
Quote from: mcguyton on October 04, 2007, 01:37:13 AM
From reading your discussion, it seems I have to add strings in the registry named:
HKEY_LOCAL_MACHINE\SOFTWARE\AFPL Ghostscript\8.50\GS_DLL
HKEY_LOCAL_MACHINE\SOFTWARE\AFPL Ghostscript\8.50\GS_BIN

The first is enough.

Quote
What do I put in those strings?
My Ghostscript executable is at: C:\Cygwin\Bin\gs.exe

Then put  C:\Cygwin\Bin

Perhaps you also install an AFLP GhostScript version 8.53. Your version 8.5 is a bit outdated, but this is not the problem here.

Quote
The winfig.log file is attached.  Any ideas on how I should get this to work?

The log file contains:
/usr/bin/dvips: ! DVI file can't be opened.

This tells me that LaTeX did not produce a DVI file. What version of LaTeX are you using? I tested with MiKTeX. Try to configure the commands in the preferences to work with your LaTeX.

If the problem persists, you can still deactivate the TeX preview in the preferences. I think I will make this the default in the next release.

119
WinFIG and LaTeX / Re: special -> exit
« on: September 13, 2007, 07:26:12 PM »
I never heard of TeXLive, but I think MiKTeX ist the "mainstream" TeX for Windows. It's difficult to be compatible with all flavours. I tried by providing the editable command paths.

120
WinFIG and LaTeX / Re: special -> exit
« on: September 12, 2007, 09:24:05 PM »
The error indicates that the call to LaTeX did not work and no DVI file was created.

Does the following command work on the command line?

latex -quiet -job-name OUTFILE INFILE

replace OUTFILE and INFILE by some example paths like

latex -quiet -job-name c:\temp\foo.div c:\temp\foo.tex

c:\temp\foo.tex must be a real LaTeX file. If this is not working, find the latex command that works for you and configure in the preferences dialog. Perhaps you need to specify the full path to the latex command. In that case you probably also have to configure the dvips command.

What TeX version are you using? I tested with MiKTeX 2.6

Pages: 1 ... 6 7 [8] 9 10