1

What does one need to do to get the fancy-preview script going
with only a Windows Tex Live installation thus far.

The basics have been discussed on tex.SE here and here.

[Quick digression: we use bibtex;
does fancy-preview work with bibtex?]

Installing Perl:

Windows Tex Live supposedly comes with Perl:

Tex Live's site somewhat ominously states that it comes with "its own version of Perl."
which I take to mean that:

  • it comes with Perl, without notable changes, or
  • it's a modified version, cooked up to do whatever Windows Tex Live needs.

Running Perl:

I tried to run: perl fancy-preview <filename>; however,
I received the error 'perl' is not recognized as an internal or external command.

I think I need to link the program to the command prompt somehow. Any suggestions? [Closest thing I found.]

I copied the ..\texlive\2015\tlpkg\tlperl folder to a local directory,
and I placed my file with the perl.exe binary.

The command prompt then pointed out that fancy-preview.pl was not found.

I feel like there's some steps which need to be taken
such that these things are all found.

Calling these files with Tex Works:

Also, is there a method to call these straight from TexWorks? pdflatex.exe is called fine enough. arara makes multiple calls even easier.

Is there a method to call perl fancy-preview for the file? Is there a method to automate it into an arara batch?

Installing Other Prerequisites:

Besides Perl, the fancy-preview documentation and site
point out that additional programs are needed (beyond a pdf reader..).

Are these included by default with fancy-preview.sty?

The Tex Live manager pulls up fancy-preview.sty when I search for them
but this may just be because they are mentioned in the documentation.

closed as off-topic by cfr, Mensch, Andrew, user13907, Zarko Aug 20 '16 at 3:54

  • This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    If you don't mind using biblatex. there is a user-friendly alternative without the need for external Perl and fancy-preview: tex.stackexchange.com/a/111932 – AlexG Aug 19 '16 at 19:20
  • @AlexG Pfffft. Forget fancy-preview. Follow the link above. – kando Aug 19 '16 at 19:39
  • 5
    I'm voting to close this question as off-topic because the OP has decided to use a solution covered in a different Q&A, but this question is not a duplicate because it uses a different system for bibliographies. See comments on question. – cfr Aug 19 '16 at 23:02
  • @cfr Is the question off-topic? I was looking for a tooltips bibliography solution, and AlexG informed me that my expected method had been superceded with a much easier method. Can he at least post his comment as an answer, as it will completely solve everything I was concerned about? More importantly, his suggested method wasn't something which was popping up in my searches. – kando Aug 22 '16 at 12:24
  • 1
    No. It is just that there are a limited number of reasons for closing a question. When none of them fits, we use one which doesn't really fit and add an explanation in the comment. The question wasn't off-topic, but you decided that an alternative strategy was better, where that strategy is explained in response to another question and wouldn't work as an answer to this one. If you had still wanted an answer to this question, I wouldn't have voted to close it. Technically, the question is still perfectly fine, but when the asker no longer wants an answer, it is often better to close. – cfr Aug 22 '16 at 15:22