loginfo interface appears not to support module/file names with s paces?

[Bulgrien, Kevin]

I inherited a large project that contains many files and directories with
spaces in file names.  As CVS is used on site, I would like to continue
to use CVS for this project.

The server has a loginfo (post-commit) script that runs out of the loginfo
file, but it is breaking because it appears to me that the API to the
loginfo script appears not to support spaces in file/directory names
well.  I am using 1.11.17 at present.

A contrived example:

  .
  |-- 1\ dir
      |-- 1\ 0
      `-- 1\ 1
  
$ cvs commit "1 dir/1 0" "1 dir/1 1"

For an entry of ALL /path/to/script %{sVv} in loginfo, a bash script returns
${*} as:

module file1,oldversion1,newversion1 file2,oldversion2,newversion2

1 dir 1 0,NONE,1.1 1 1,NONE,1.1

Further, ${1} also appears to be:

module file1,oldversion1,newversion1 file2,oldversion2,newversion2

1 dir 1 0,NONE,1.1 1 1,NONE,1.1

It is not obvious to me what appropriate parse rules might be used to
determine
what the directory and file names are.  Am I missing something, or has
anyone
dealt with this particular issue before?

I can imagine a way to parse out the data for file2 and any subsequent
files,
by using knowledge of the format of the version number, but I am having some
difficulty seeing how to distinguish the module name from file1.

I was hoping that $1 would be the module name and that $2 and subsequent
parameters would be the files in that module, but unless I have made an
error,
this does not appear to be the case.

--- 
Kevin R. Bulgrien
Design and Development Engineer
General Dynamics C4 Systems
http://www.gdsatcom.com/