#1471 Jump to error does not work for certain filenames and paths

2.02_Stable
open
nobody
None
6
2014-11-30
2014-03-24
Jan Prikryl
No

If I have a file on a path that contains accented characters (it would be C:\Users\Prikryl\Dropbox\MSAP\Cvičení\Domácí příprava\2013-2014 in my case), and the file does not compile due to an error, when I go to the Build Output window and click the error icon TeXnicCenter refuses to jump to the corresponding source file line. If I move the file to another directory tree so that the path does not contain any accented characters, everything works as expected.

I suppose that the build output parser has difficulties in decoding the TeX compiler output due to the accented characters, which seem to be in my case UTF-8, being emitted to the log as UTF-8:

This is pdfTeX, Version 3.1415926-2.5-1.40.14 (MiKTeX 2.9) (preloaded format=pdflatex 2013.8.30)  24 MAR 2014 10:44
entering extended mode
**msp-dp-2014-02.tex
("C:\Users\Prikryl\Dropbox\MSAP\Cvičení\Domácí příprava\2013-2014\msp-dp-2014-02.tex"
LaTeX2e <2011/06/27>
[...]

but in the Build Output window I can see that the characters are garbled (it seems that one cannot copy and paste the contents of the windows, so I am trying to re-create it as close to reality as possible):

pdflatex> This is pdfTeX, Version 3.1415926-2.5-1.40.14 (MiKTeX 2.9) (preloaded format=pdflatex 2013.8.30)  24 MAR 2014 11:20
pdflatex> entering extended mode
pdflatex> **msp-dp-2014-02.tex
pdflatex> ("C:\Users\Prikryl\Dropbox\MSAP\Cvičení\Domácí příprava\2013-2014\msp-dp-2014-02.tex"
pdflatex> LaTeX2e <2011/06/27>
[...]

It seems that the space in the directory name is handled correctly. Jumping to the error line works for the same file if I put it in C:\Users\Prikryl\Dropbox\Common Files, but it does not work in C:\Users\Prikryl\Dropbox\ěščřžýá.

Thanks for looking into this.

Discussion


Anonymous

Cancel  Add attachments





Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks