# TeXcount cannot fine \input files with a command in the path?

UPDATE: The problem I am having is due to having Python code inside a PythonTeX pycode environment. Seems this causes a parsing error with the TeXcount Perl script.

I want to use TeXcount to count the words in my thesis. However, I have either run into a limitation of TeXcount or it's difficult to find an explanation (via documentation, here, forums, etc.) detailing how to alleviate my issue.

I have all the chapters in my thesis in a subfolder from the main .tex document. I call these via the following line (or similar, depending on the chapter name, obviously):

\include{\chaptersPath/background_information}


Within many of those chapter files, I have additional files stored a directory deeper for major topics/themes of that chapter, such as:

\input{\chaptersPath/background_information/literature}


The document compiles fine. And honestly, I'm not here currently to debate whether my file and directory structure is proper, the most efficient, etc.

I have tried defining \chaptersPath variously as:

\newcommand{\buildFilesPath}{_build_files}%


or

\edef\buildFilesPath{./_build_files}%


Same behavior for both - The problem I have is that having this command or definition in the \input doesn't seem to expand for texcount. TeXcount complains that the file is not found:

[1;31m!!! File not found or not readable: \chaptersPath/background_information !!![0m


I tried using -auxdir and -dir, but these seem to not make TeXcount happy because those commands are still in the \input calls.

I also tried including \immediate\write18{texcount \jobname.tex -inc -out=\buildFilesPath/\jobname.sum} in the preamble thinking perhaps it would recognize those commands (replaced with plain text path details). I was wrong; it doesn't. Funny thing here is that \buildFilesPath and \jobname do get recognized.

Lastly, I've tried playing around with including \expandafter and this is totally not useful as well. It seems the texcount.exe (even within the \immediate\write18 method simply cannot expand those file path definitions).

Question: Is it possible to resolve this problem somehow, while maintaining those commands defining the file/chapter paths?

I realize I can just go through and hardcode all the paths manually. But this is rather crappy for flexibility, if I want to create a new document using much of the same (La)TeX preamble and base .tex document but with a different file/folder structure. The current way requires just one change rather than finding and replacing a bunch of stuff every time.

• texcount is a perl script, so you should probably not expect it to be able to expand LaTeX commands. Jan 12, 2017 at 8:48
• Fair enough. I probably didn't word it as well as I could. First, I was wondering if there was a way around the lack of expansion. Second, I thought that by using it via \immediate\write18, perhaps it had access to the expansions while LaTeX was in the process of compiling (perhaps putting it in a shipout or somewhere similar). Honestly, I wasn't sure and was hoping for insight from learned people such as yourself! Jan 12, 2017 at 12:30

As daleif has pointed out in a comment, TeXcount does not actually expand LaTeX commands, and so it does not expand the path in \chaptersPath when trying to locate the included files.

There is a trick that might work. TeXcount can take instructions embedded in the LaTeX document as comments on the form %TC:.... One such instruction is %TC:subst which does a simple substitution of a macro with an arbitrary text string. Eg, you could try including somewhere at the top of the document (eg right after the definition of \chaptersPath) the command  %TC:subst \chaptersPath /my/chapters/path  and see if that does the job. This basically does a simple search and replace. You may have to fiddle around a bit to get the path right (absolute path or relative path?). I'm not entirely sure how it will handle tex files included inside included tex files, but I guess you'll find out if that works out.

Update on bug in TeXcount that causes problems

The TeXcount solution, as well as other uses file inclusion using \include, may fail due to a bug in TeXcount.

When using \include to include a TeX file, the .tex file type is not required. TeXcount was supposed to add .tex to the file name if not already there, but this seems to have failed and was the root cause of the difficulty of getting the solution to work.

This bug can be bypassed by ensuring all file inclusion using \include contain the .tex file type.

An alternative is to fix the code of TeXcount which is quite simple. Just find the function definition sub _parse_include_file and change the line  if (!$file=~/\.tex$/i) {$file.='.tex';}  to  if ($file!~/\.tex$/i) {$file.='.tex';}  and TeXcount should append .tex to the file name when required.

• I like that better than my approach -- if it works of course. Jan 12, 2017 at 9:47
• Where is %TC: subst documented? I wanted to try the suggestion, but it does not seem to work Jan 12, 2017 at 12:39
• First, thanks for bringing this up. I didn't notice these options because I was just focused on the command line options. Without a huge amount of playing around, I found a couple things. First, it only works one level deep (i.e. it can find files in \chaptersPath but if that file in turn calls one or more \inputs at a deeper folder, then a File not found or not readable message pops up again). It does seem to be a relative path to the folder where texcount is run from (i.e. NOT the .tex folder...unless that happens to be where you run texcount from) Jan 12, 2017 at 12:43
• @daleif after seeing this, I realized it's near the bottom of http://app.uio.no/ifi/texcount/documentation.html in the "TeXcount instructions" section Jan 12, 2017 at 12:45
• @whatisit ahh, details was not listed in the -help page for it. Jan 12, 2017 at 13:47

As @daleif said in the comments, TeXcount can't parse TeX, being a Perl script.

I don't do Perl so faced with a similar issue I wrote somethign in Python to pre-process the master tex file.

Here's the python script adapted for a minmal version of your case. I call it tc-paths.py:

import fileinput # see https://docs.python.org/2/library/fileinput.html
import os
chaptersPath=None
chaptersPathMacro=r'\chaptersPath'
chaptersPathDef=r'\def'+chaptersPathMacro
outfilename=None

for line in fileinput.input():
if outfilename==None:
outfilename=os.path.splitext(fileinput.filename())[0]+'-temp'+os.path.splitext(fileinput.filename())[1]
print ('Writing to: '+outfilename)
outfile=open(outfilename,'w')
if chaptersPathDef in line:
startpos=line.find('{',line.find(chaptersPathDef)+len(chaptersPathDef))+1
endpos=line.find('}',startpos)
chaptersPath=line[startpos:endpos]
print (r'\chaptersPath='+chaptersPath)
outline=line
elif r'\input{'+chaptersPathMacro in line:
print ('Found '+chaptersPathMacro+' in line %d'%fileinput.lineno())
outline=line.replace(chaptersPathMacro,chaptersPath)
else:
outline=line
outfile.write(outline)


run it with python tc-paths.py my-master-file.tex, and it will output to my-master-file-temp.tex

A sample input tex file:

\documentclass{article}
\def\chaptersPath{../Chris}
\begin{document}
\input{\chaptersPath/chap1.tex}
\end{document}


And the output:

\documentclass{article}
\def\chaptersPath{../Chris}
\begin{document}
\input{../Chris/chap1.tex}
\end{document}


Then you run texcount on the -temp.tex file.

• This script was tested using python 2.7 on windows (hence the lack of #!/usr/bin/python). I think it should work on python 3 as well. My use of TeXcount with following \input/\include was all on Linux, so if I've forgotten something in the gap, please let me know. Jan 12, 2017 at 9:50
• Thanks for the help on this! Let me look more into @einar-rødland's answer and I'll come back to this if necessary. Jan 12, 2017 at 12:47
• As I've been playing around with @einar-rødland's suggestion, I realized I should check with you also about this. If you use this script, does TeXcount then work for two level deep \input / \include? Or have you not tried? Jan 12, 2017 at 22:42
• See the update I included at the top of my original question. It turns out that TeXcount seems to work fine, as long as I use the %TC:substr command in my main .tex file. I would recommend this for you. The problem turned out to be caused by using the PythonTeX package and then having Python code inside the preamble (which happens to print out various commands which load images). It seems this can break TeXcount's parsing ability in a document. Jan 12, 2017 at 23:55
• @whatisit my second level inputs were just tikz figures and tables so I didn't care whether texcount found them or not. Since my thesis I haven't had to worry about texcount. Jan 13, 2017 at 6:54