# nlct/bib2gls

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

# Files located in local texmf path are not determined correctly #3

Closed
opened this Issue Nov 28, 2018 · 8 comments

## Comments

Projects
None yet
2 participants

### martinKorp commented Nov 28, 2018 • edited

 If the .bib files of glossaries are placed in the local texmf path it seems that their path is not determined correctly. I.e., if we run bib2gls we get the following error message ( is a placeholder for the .tex file and  is a placeholder for the glossary .bib file): bib2gls version 1.7 (2018-08-18) Reading .aux Error: Illegal char <:> at index 4: c:\c:\Users\mkorp\texmf\bibtex\bib\.bib Transcript written to .glg. C:\texlive\2018\bin\win32\runscript.tlu:803: command failed with exit code 3: java.exe -jar c:\texlive\2018\texmf-dist\scripts\bib2gls\bib2gls.jar ""  Under Linux everything works perfectly. It seems to occur only under Windows.
Owner

### nlct commented Nov 28, 2018

 It looks like the c:\ drive part is being replicated for some reason. What do you get if you run kpsewhich .bib from the command prompt?

### martinKorp commented Nov 28, 2018

 If I run kpsewhich .bib from the command prompt I get the correct path, i.e., c:\Users\mkorp\texmf\bibtex\bib\.bib. As you indicated already it seems that c:\ is for some reason added or duplicated.
Owner

### nlct commented Nov 28, 2018

 If you have the testidx package installed the following MWE will also use kpsewhich to find the .bib files: \documentclass{article} \usepackage[T1]{fontenc} \usepackage[utf8]{inputenc} \usepackage[bib2gls]{testidx-glossaries} \tstidxmakegloss \begin{document} \testidx \tstidxprintglossaries \end{document} I'm guessing this will cause the same error. You can use that for testing if you like. Can you run bib2gls with --debug and check the transcript for the lines: Running kpsewhich '' Processed returned:  and the stack trace information (just the first .bib file information is sufficient) .

### martinKorp commented Nov 29, 2018

 I have now setup the MWE and copied the necessary .bib files into my local texmf path. As expected I got the same error. Please find below the corresponding output (including the trace information): Checking write access for C:\Projects\test.glstex Initialising resource test.glstex. File not found: testidx-glossaries-mathsym.bib Running kpsewhich 'testidx-glossaries-mathsym.bib' Processed returned: c:/Users/mkorp/texmf/bibtex/bib/testidx-glossaries-mathsym.bib Error: Illegal char <:> at index 4: c:\c:\Users\mkorp\texmf\bibtex\bib\testidx-glossaries-mathsym.bib java.nio.file.InvalidPathException: Illegal char <:> at index 4: c:\c:\Users\mkorp\texmf\bibtex\bib\testidx-glossaries-mathsym.bib at sun.nio.fs.WindowsPathParser.normalize(Unknown Source) at sun.nio.fs.WindowsPathParser.parse(Unknown Source) at sun.nio.fs.WindowsPathParser.parse(Unknown Source) at sun.nio.fs.WindowsPath.parse(Unknown Source) at sun.nio.fs.WindowsFileSystem.getPath(Unknown Source) at java.io.File.toPath(Unknown Source) at com.dickimawbooks.texparserlib.TeXPath.init(TeXPath.java:228) at com.dickimawbooks.texparserlib.TeXPath.(TeXPath.java:51) at com.dickimawbooks.bib2gls.Bib2Gls.getBibFilePath(Bib2Gls.java:2674) at com.dickimawbooks.bib2gls.GlsResource.init(GlsResource.java:109) at com.dickimawbooks.bib2gls.GlsResource.(GlsResource.java:53) at com.dickimawbooks.bib2gls.Bib2Gls.process(Bib2Gls.java:1722) at com.dickimawbooks.bib2gls.Bib2Gls.main(Bib2Gls.java:4336) 
Owner

### nlct commented Nov 29, 2018

 Thank you. I'll investigate and get it fixed.
Owner

### nlct commented Nov 30, 2018

 This should hopefully now be fixed in version 1.8, which I've just uploaded to CTAN.

### martinKorp commented Dec 3, 2018

 Thanks a lot for fixing the issue that fast. I have tested it quickly and it works now without any problems.

Owner

### nlct commented Dec 3, 2018

 That's great. Thank you for the feedback.
to join this conversation on GitHub. Already have an account? Sign in to comment