Harish Kumar Holla | 7 Mar 2012 06:46
Gravatar

Running biber from winedt

How to run biber from wiedt. ( for bibtex there is a button and clicking it will do the job). Is there a way to have such a thing for biber?

--



--with regards

Dr. Harish Kumar

Stefan Pinnow | 7 Mar 2012 07:19
Picon

RE: Running biber from winedt

Hallo Dr. Kumar,

> How to run biber from wiedt. ( for bibtex there is a button and clicking
> it will do the job). Is there a way to have such a thing for biber?

if you use WinEdt 6.0 and MiKTeX it is not so hard to implement.
	http://lmgtfy.com/?q=winedt+biber

Best regards,
Stefan Pinnow

Henning Haida | 7 Mar 2012 09:44
Picon

RE: Running biber from winedt

Hi,

Quoting Stefan Pinnow <Mo-Gul <at> gmx.net>:
> if you use WinEdt 6.0 and MiKTeX it is not so hard to implement.

It seems, the idea is to change the EnvVar for bibtex, Ulrike Fischer  
suggested:

Copy or adapt the texify entries in mainmenu.ini and add a  
SetEnvVar-command. E.g.:

   ITEM="TeXify + biber"
     CAPTION="TeXify + biber"
     IMAGE="TeXTeXify"
     SAVE_INPUT=1
     MACRO="SetEnvVar('BIBTEX','path\to\biber.exe');  
Exe('%b\Exec\TeX\TeXify.edt');"
     SHORTCUT="24664::Shift+Ctrl+X" //adapt
     REQ_FILTER=:"%!M=TeX"|"%!M=TeX:STY"

I did so and tried both 'biber.exe' and the full path. However, it  
didn't work, same problem as reportet here,  
https://groups.google.com/forum/#!msg/de.comp.text.tex/i7h-sND1wHs/T8CSuJux1tUJ. (I can add
that I had to comment the shortcut for default texify, but also the new user menu didn't work when invoked
directly via the  
menu).

What works for me is the following: Options --> Execution Modes -->  
Console Application --> BibTeX. Executable: biber.exe. Well, I  
entirely pass bibtex, but then pdftexify and the like invoke biber  
automatically and I can also use the default "bibtex"-Button to run  
biber, which is just fine for me.

Kindest regards
  Henning

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Stefan Pinnow | 7 Mar 2012 20:54
Picon

RE: Running biber from winedt

Hello Henning,

>> if you use WinEdt 6.0 and MiKTeX it is not so hard to implement.
> 
> It seems, the idea is to change the EnvVar for bibtex, Ulrike Fischer
> suggested:
> 
> Copy or adapt the texify entries in mainmenu.ini and add a SetEnvVar-
> command. E.g.:
> 
>    ITEM="TeXify + biber"
>      CAPTION="TeXify + biber"
>      IMAGE="TeXTeXify"
>      SAVE_INPUT=1
>      MACRO="SetEnvVar('BIBTEX','path\to\biber.exe');  
> Exe('%b\Exec\TeX\TeXify.edt');"
>      SHORTCUT="24664::Shift+Ctrl+X" //adapt
>      REQ_FILTER=:"%!M=TeX"|"%!M=TeX:STY"> 
> 
> I did so and tried both 'biber.exe' and the full path. However, it
> didn't work, same problem as reportet here,
> https://groups.google.com/forum/#!msg/de.comp.text.tex/i7h-
> sND1wHs/T8CSuJux1tUJ. (I can add that I had to comment the shortcut for
> default texify, but also the new user menu didn't work when invoked
> directly via the menu).

what works for me is the MainMenu entry

    ITEM="PDFTeXify + biber"
      CAPTION="PDFTeXify + biber"
      IMAGE="TeXPDFTeXify"
      SAVE_INPUT=1

MACRO="DeleteFile('%O\%N.aux');SetEnvVar('BIBTEX','biber.exe');Exe('%b\Exec\
TeX\PDFTeXify.edt');"
//      SHORTCUT="24656::Shift+Ctrl+P"
      REQ_FILTER=:"%!M=TeX"|"%!M=TeX:STY"

and the lines

% ===================================================================
% for biber backend
\makeatletter
    \providecommand\bibstyle <at> faked{}
    \providecommand\bibdata <at> faked{}
    \AtBeginDocument{%
        \immediate\write\ <at> mainaux{\noexpand\bibstyle <at> faked}%
        \immediate\write\ <at> mainaux{\noexpand\bibdata <at> faked}%
    }
\makeatother
% ===================================================================

somewhere in the preamble (this was also stated in the first hit of my
google search link).

Best regards,
Stefan

Karl Koeller | 8 Mar 2012 07:00

Re: Running biber from winedt

Dear all,

if you have the patience to wait (no more than) a month, the new version 
7 of WinEdt will have full support for biber...

It will suffice to change the definition of the BibTeX accessory from 
bibtex.exe to biber.exe in Execution Modes interface to properly run 
Biber as a standalone accessory (through the BibTeX button) and through 
[PDF]TeXify button.

In the last case, there will be no more need to add something like

> % ===================================================================
> % for biber backend
> \makeatletter
>      \providecommand\bibstyle <at> faked{}
>      \providecommand\bibdata <at> faked{}
>      \AtBeginDocument{%
>          \immediate\write\ <at> mainaux{\noexpand\bibstyle <at> faked}%
>          \immediate\write\ <at> mainaux{\noexpand\bibdata <at> faked}%
>      }
> \makeatother
> % ===================================================================

in your documents preamble.

In fact, WinEdt will take care of running Biber even if TeXify is not able to do that.

Regards to all,

Karl

Henning Haida | 8 Mar 2012 09:51
Picon

RE: Running biber from winedt

Hi Stefan,

Quoting Stefan Pinnow <Mo-Gul <at> gmx.net>:
> and the lines
>
> % ===================================================================
> % for biber backend
> \makeatletter
>     \providecommand\bibstyle <at> faked{}
>     \providecommand\bibdata <at> faked{}
>     \AtBeginDocument{%
>         \immediate\write\ <at> mainaux{\noexpand\bibstyle <at> faked}%
>         \immediate\write\ <at> mainaux{\noexpand\bibdata <at> faked}%
>     }
> \makeatother
> % ===================================================================
>
> somewhere in the preamble (this was also stated in the first hit of my
> google search link).

Thanks for clarification! However, it is not very attractive to change  
the tex-file, although this method is working.

Perhaps a future version of WinEdt could have a global option whether  
to use bibtex, bibtex8 or biber (or something else?) as default  
program within texify et al.

Regards
  Henning

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Henning Haida | 8 Mar 2012 09:58
Picon

Re: Running biber from winedt

Hi,

Quoting Karl Koeller <karlkoeller <at> googlemail.com>:
> if you have the patience to wait (no more than) a month, the new
> version 7 of WinEdt will have full support for biber...
>
> It will suffice to change the definition of the BibTeX accessory from
> bibtex.exe to biber.exe in Execution Modes interface to properly run
> Biber as a standalone accessory (through the BibTeX button) and through
> [PDF]TeXify button.

One can do that already with WinEdt 6 (I do so). I'm not sure about  
users who need both, bibtex and biber. Anyway, the possible keyboard  
shortcuts are limited ;-).

Regards
  Henning

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Karl Koeller | 8 Mar 2012 13:06

Re: Running biber from winedt

Il 08/03/2012 9.58, Henning Haida ha scritto:
> Hi,
>
> Quoting Karl Koeller <karlkoeller <at> googlemail.com>:
>> if you have the patience to wait (no more than) a month, the new
>> version 7 of WinEdt will have full support for biber...
>>
>> It will suffice to change the definition of the BibTeX accessory from
>> bibtex.exe to biber.exe in Execution Modes interface to properly run
>> Biber as a standalone accessory (through the BibTeX button) and through
>> [PDF]TeXify button.
>
> One can do that already with WinEdt 6 (I do so). I'm not sure about 
> users who need both, bibtex and biber. Anyway, the possible keyboard 
> shortcuts are limited ;-).

WinEdt 6 has "partial" support for biber and bibtex8. In fact there are 
problems when it comes to multiple bibliographies (biber) and both can 
fail when using an auxiliary folder for auxiliary files.

Also you have to execute additional macros and add stuff to documents 
preamble if you want texify to recognize biber.

All these issues are solved in version 7!

Regards

Karl

Albert Kapune | 9 Mar 2012 13:12

Moving Winedt 5.5 to a macine with non-admin rights

Hello,

I have an old WinEdt 5.5 installation an a computer with the option
»enable user profile«. I want to move this installation to a machine in my
office where I do not have admin rights keeping my settings and adaptations.

As far as I know one can move an installation without the option »enable
user profile« from a machine with admin rights to another one without
rights by simply copying – but how can I transfer my installation without
loosing my settings?

Thank you and kind regards
Albert

--

-- 
Dr. Albert Kapune
Brunnenstrasse 1
D-59514 Welver-Nateln
Telefon: (02384) 911012
Telefax: (02384) 911011

Albert Kapune | 9 Mar 2012 23:23

Re: Moving Winedt 5.5 to a macine with non-admin rights


I found the simple solution myself: I copied my settings from my profile
directory structure to Winedt’s program directory structure (and disabled
the automatic profile creation in the configuration wizard). After that I
could easyly move the installation to the computer without admin rights.

Kind regards
Albert

Albert Kapune schrieb am 09.03.2012 13:12 folgendes:

> Hello,
> 
> I have an old WinEdt 5.5 installation an a computer with the option 
> »enable user profile«. I want to move this installation to a machine in
> my office where I do not have admin rights keeping my settings and
> adaptations.
> 
> As far as I know one can move an installation without the option
> »enable user profile« from a machine with admin rights to another one
> without rights by simply copying – but how can I transfer my
> installation without loosing my settings?
> 
> Thank you and kind regards Albert
> 

--

-- 
Dr. Albert Kapune
Brunnenstrasse 1
D-59514 Welver-Nateln
Telefon: (02384) 911012
Telefax: (02384) 911011


Gmane