The (otherwise beautiful, functional, and handy) HTML export function turns out not to play very well with SVN. Now, it could be argued that since the OO document is really the 'source', I shouldn't be checking the HTML export into SVN at all, but let's just take it for granted that this is a reasonable thing to want to do.
The problem is that when OO creates the folder for the HTML content, it replaces entirely any preexisting export folder. That means that the existing foo.html/.svn folder is deleted, and a fresh (SVN-less) folder put in its place, which makes SVN very grumpy.
Could there be some consideration for leaving an existing folder (and contents) in place when doing a re-export, simply overwriting whichever files have actually changed?
The problem is that when OO creates the folder for the HTML content, it replaces entirely any preexisting export folder. That means that the existing foo.html/.svn folder is deleted, and a fresh (SVN-less) folder put in its place, which makes SVN very grumpy.
Could there be some consideration for leaving an existing folder (and contents) in place when doing a re-export, simply overwriting whichever files have actually changed?