Bibtex Windows Api Error 161
Contents |
from GoogleSign inHidden fieldsSearch for groups or messages
bug is not limited to MiKTeX. It is a miktex 2.9 download general authorindex problem that can occur on any Windows miktex windows machine. When authorindex runs on a NETWORK drive (and other times?) this error latex download occurs: ===== bibtex: Windows API error 161: The specified path is invalid. BibTeX error. Aborting leaving all temporary files _autidx_.* ===== This https://groups.google.com/d/topic/comp.text.tex/g-atLBpC1hc error is a Windows specific problem in the "authorindex" Perl script. The resolution, by Christian Schenk: ===== Date: 2007-06-21 13:26 Sender: csc (Christian Schenk) Logged In: YES user_id=67066 Originator: NO Thank you. The bug is in the authorindex.pl script on lines 215 and 276: the http://newsgroups.derkeiler.com/Archive/Comp/comp.text.tex/2007-06/msg01386.html Unix path separator (:) is used when the environment variable BSTINPIUTS/BIBINPUTS is set. This does not work under Windows. Please replace ".:" with ".;" on both lines. ===== In MiKTeX, this script is located at: \Program Files\MiKTeX 2.6\scripts\perl\authorindex\authorindex.pl Eventually, authorindex will need to be modified so that ";" is used as the PATH separator for Windows and ":" in UNIX. Meanwhile, those getting the error above should manually make this change. --Ted . References: authorindex, miktex, and API error From: Ted Pavlic Prev by Date: Re: Flow charts in LaTeX - package recommendation Next by Date: Re: subfigure caption centering Previous by thread: authorindex, miktex, and API error Next by thread: thebibliography new page prevent Index(es): Date Thread Flag as inappropriate (AWS) Security UNIX Linux Coding Usenet ArchiveAboutPrivacyImprint newsgroups.derkeiler.com >Archive >Comp >comp.text.tex >2007-06
Other Tedly Sites Thursday, June 21, 2007 authorindex bug fix on Windows (API error and PATH separator) This is from a USENET news thread. I repost it here http://phaseportrait.blogspot.com/2007/06/authorindex-bug-fix-on-windows-api.html so that it gets indexed by more search engines.This is a summary of https://github.com/retorquere/zotero-better-bibtex/issues/126 the bug and resolution listed in MiKTeX bug #1739147:This bug is not limited to MiKTeX. It is a general authorindex problem that can occur on any Windows machine.When authorindex runs on a NETWORK drive (and other times?) this error occurs:=====bibtex: Windows API error 161: The specified path is invalid.BibTeX error. Aborting leaving all windows api temporary files _autidx_.*=====This error is a Windows specific problem in the "authorindex" Perl script. The resolution, by Christian Schenk:=====Date: 2007-06-21 13:26Sender: csc (Christian Schenk)Logged In: YES user_id=67066Originator: NOThank you. The bug is in the authorindex.pl script on lines 215 and 276:the Unix path separator (:) is used when the environment variableBSTINPIUTS/BIBINPUTS is set. This does not work under Windows. Pleasereplace ".:" with ".;" on both lines.=====In windows api error MiKTeX, this script is located at:\Program Files\MiKTeX 2.6\scripts\perl\authorindex\authorindex.plEventually, authorindex will need to be modified so that ";" is used as the PATH separator for Windows and ":" in UNIX. Meanwhile, those getting the error above should manually make this change.--Ted Posted by Ted Pavlic at 1:59 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: authorindex, bugs, latex, software, TeX/LaTeX, texlatex, typesetting No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) About Me View my complete profile More Information Ted's Home PageTwitter (@TedPavlic)Tumblr (TedPavlic) microblogInstagram (tedliman):gf/sg/fg/wsg/isp/grid/instacnvsSwypos (Tumblr microblog)Other Tedly sites Popular Posts The Sony SMP-N200 (or SMP-N100) is the only streaming player you need; eschew the Roku! Bounding Boxes and EPS to PDF Conversion (in LaTeX) natbib-compatible BibTeX style (BST) file for Springer LNCS publications sinc interpolation in MATLAB Bush Gives $50-60 Million Dollars to Whiskey-selling Convenience Stores Archive ► 2016 (1) ► March (1) ► 2015 (2) ► January (2) ► 2014 (1) ► December (1) ► 2013 (2) ► February (1) ► January (1) ► 2012 (10) ► October (1) ► August (1) ► July (1) ► June (1) ► April (1) ► February (2) ► January (
Support Search GitHub This repository Watch 30 Star 279 Fork 40 retorquere/zotero-better-bibtex Code Issues 7 Pull requests 0 Projects 0 Wiki Pulse Graphs New issue Feature Request: Option to emit relative paths for "file" field in Bib(La)Tex export #126 Closed mhminai opened this Issue Dec 20, 2014 · 29 comments Projects None yet Labels enhancement Milestone No milestone Assignees No one assigned 4 participants mhminai commented Dec 20, 2014 In Short When we export a bibtex without exporting the files, the path in the "file" field is absolute. Which does make a lot of sense as we can possible save this exported bibtex anywhere. Would it be possible to emit the relative paths for (at least) those attachments which are located in the "Base Directory" option of Zotero. Internally Zotero does appear to use relative paths for links to files that are in the tree of this directory. It seems that this is possible as some discussion in Issue #21 shows. In Detail I am using Zotero as a reference manager while finetuning a workflow for writing academic papers using pandoc. Pandoc requires a bibtex file for reference management, hence the need to export from Zotero to bibtex. I also intend to use docear, possibly from a different computer. I am using Zotero in combination with zotfile, zotero-better-bibtex and zotero-bib-autoexport. Zotero allows me to quickly retrieve metadata for my PDFs. Then zotfile allows me to move all the PDFs to a common folder (say "Literature") and renaming them to "AuthorYYYY.pdf", while modifying the zotero entry to have a link to the file. I then use BBT to generate bibtex keys compatible with the filename (an option for this could also be a cool feature, but I digress). Now if the bibtex had relative paths, I could simply pop the generated .bib file in my Literature folder, and Voila, I would have a self contained folder with a .bib file having the PDFs linked, while still retaining all functionality of Zotero itself. This allows me to put the Literature folder on dropbox and use (view, no point in modifying the bibtex as it would get overwritten by zotero-bib-autoexport) it from any computer with basic bibtex support. Also allows docear to function seamlessly with Zotero. Considerations I would like to avoid multiple copies of the PDF at all costs, if possible. I use my home a