I guess you could always try: http://www.softpedia.com/get/System/ File-Management/Shorts.shtml I haven't used it myself. However, first you will need to decide whether generated docs should be submitted to the svn. There was a recent thread about that. If that is your primary library documentation, then how it was generated is irrelevant. But if you intend to update it (as is the whole point of doxygen), I think it would be better to post it somewhere else public but owned by you (not in the svn) and put in a relocate in the index.html, with the option for the user to generate the docs themselves and overwrite the index.html in their private copy (put in some safeguards to prevent them from checking in inadvertently). HTH, --HB On Nov 11, 2007, at 12:15 PM, Lubomir Bourdev wrote:

I am trying to submit a copy of the GIL documentation into main. The documentation consists of hundreds of files auto-generated by Doxygen. Many of them have longer names than 31 characters, and the svn pre-commit hook fails because of that.

I couldn't figure a way to make Doxygen generate smaller file names and it would be impossible to manually shorten the names of hundreds of files every time we need to generate the files. Can we lift the file name length restriction? Any other solutions?

Thanks, Lubomir

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/ listinfo.cgi/boost

-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Lubomir Bourdev Sent: 11 November 2007 17:16 To: boost@lists.boost.org Subject: [boost] svn pre-commit problem and long file names

I am trying to submit a copy of the GIL documentation into main. The documentation consists of hundreds of files auto-generated by Doxygen. Many of them have longer names than 31 characters, and the svn pre-commit hook fails because of that.

I couldn't figure a way to make Doxygen generate smaller file names and it would be impossible to manually shorten the names of hundreds of files every time we need to generate the files. Can we lift the file name length restriction? Any other solutions?

Reluctantly, I'm coming the view that we should relax the restrictions. IIRC the rationale was based mainly on the wish to be able to burn CDs. However increasingly CD burning software can produce CDs that are less restricted, certainly up to 64 chars using ISO 9660 and Joliet extensions. For example Nero certainly allowed this restrictions to be eased (and more nesting depth too). Windows appears to require short filename for bootable CDs, but I am not sure about other files. Should we start a new thread to discuss this when 1.35 is out? Paul --- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB +44 1539561830 & SMS, Mobile +44 7714 330204 & SMS pbristow@hetp.u-net.com