> Well, several weeks passed but I didn't receive any reply from the
> author, [...] I found
> out that the problem is a missing part in the PostScript output, see
> attachment [1]. [...]
I can now confirm, that this fix works for both beta3 and beta4 - at
least for me and my files. Let's just
Well, several weeks passed but I didn't receive any reply from the author, I've
tried on SourceForge bug tracker and on the user mailing list. So I tried to
investigate this problem by myself and compared the output of pgf 2.00 (working)
and pgf 2.10 (non-working). I found out that the problem is a
On Mon, 10 Jan 2011 01:31:06 +0100
Michal wrote:
> I've experimented a little and found out that using pdflatex on
> 0lyxpreview.tex I've send earlier and then gswin32c on the resulting
> *pdf* file (instead of on the ps one generated via latex, as the
> original Python script does) produced t
I've experimented a little and found out that using pdflatex on
0lyxpreview.tex I've send earlier and then gswin32c on the resulting
*pdf* file (instead of on the ps one generated via latex, as the
original Python script does) produced two correct pngs without errors.
Could it be the corre
> maybe they dont do it intentionaly. i would contact them...
I did it, let's wait and see.
venom00
veno...@arcadiaclub.com wrote:
> I wanted this feature so much that I worked it out, and now they broke the
> compatibility with preview-latex!
maybe they dont do it intentionaly. i would contact them...
pavel
I've updated my MiKTeX installation, between the packages that need update there
were pgf and pgfplots, and they're used by tikz.
Now your example doesn't work neither for me, I think one of those two packages
broke something with the preview-latex package, since they still work with
ps2pdf.
pstric
> In the zip file you'll find the contents of the temp dir,
> along with
> the following files deep inside:
> _script.bat - the script executing the python script and the
> gswin32c command
> _script-*.txt - various outputs of the script after executing it
> from the same directory, sh
The list is refusing the zip file as 'prohibited contents', so I've
put it online temporarily. Please download from
http://msys.info/lyx/
On Sun, 9 Jan 2011 12:18:09 +0100
wrote:
> [...]
> Are you sure yours is a clean install? ...
Well, the previous log file wasn't from a clean i
> i believe that fixing http://www.lyx.org/trac/ticket/6720 would solve
> this issue as well (in the sense that one error wouldn't kill
> all other
> previews...)
I'll (try to) take care of that, now that I understand the problem :D
venom00
> I've been able to 'catch' one
> subprocess that is
> executed right after opening the document, then it
> disappeared (after a
> second or two). Its commandline appeared in the messages
> (attached, line
> 2696), along with the information that it failed.
Well, that's the standard conversion
veno...@arcadiaclub.com wrote:
> Correct me if I'm wrong, but as I understand, right now I'm
> encountering two separate problems:
> - because of your patch, LyX 2.0beta2 should be able to render
> 'pstricks' LaTeX instant previews correctly (that's impressive!)
> - even if this renderi
It works fine for me (in my old version, between beta1 and beta2 and in the
current trunk version), could you give us any additional information?
Take a look to the processes running (maybe with Process Explorer [1]) and tell
us if there's some process, created by lyx.exe, taking up too much CPU an
> > I'd like to report a regression. As I recall, there have been some
> > changes in beta2 wrt the instant preview machinery.
>
> please put it into our bug tracker.
> thanks, pavel
Done, as #7222.
Regards,
Michał Skrzypek
Michal wrote:
> I am using WinXP SP3 (Polish) with MikTeX 2.9.3972. I've also
> confirmed the following with a fresh snapshot of XP SP3 inside
> VirtualBox 4.0.0 (LyX 2.0beta2 only).
>
> I'd like to report a regression. As I recall, there have been some
> changes in beta2 wrt the instant p
15 matches
Mail list logo
