This question comes from a question asked yesterday here, the comments of which lead me to believe this separate question might be appropriate.
To explain again: a small group of individuals have been given a .xlsx file (newer excel) which they will, over the course of the school semester, work on individually. Said file contains numerous workbooks, with each members of the group being assigned n number of workbooks to work on.
As of now, said file is stored in an svn repository whose host allows a web-interface which adds the slight convenience of allowing members to see comments/updates/communicate its web page.
From my last question I gathered that SVN may not be the best solution to this given that it doesn't handle binary files well. From that source, and form my own research thereafter I've a few ideas on we can accomplish the Title of this question:
Split said .xlsx file into its various workbooks by number of group members. When assignment is due the workbooks (I assume) could be merged into a single .xlsx file. This will allow group to have the storage features of svn, allow other members the ability to view member m's work, and allow members to view comments.
Explore the use of msofficesvn
This question then can be restated in more detail as: How can/should we keep up with this file? Assuming the features of SVN would be useful for the group (merging, seeing differences, comments, etc.) which of these could achieve by other means and what are those means?