Hi John, On Wednesday, 7. August 2013 16:04:31 John Maddock wrote:
John, as I outlined in the original post to the list, having them set to binary mime type causes issues due to the inconsistent line endings of some SVG files. While image/svg+xml is correct for serving the files in a webpage, it's not really a good choice for storing in a repository.
Sorry I missed the original message. I don't really care what it's set to as long as I can point the browser to: http://svn.boost.org/svn/boost/trunk/libs/math/doc/equations/airy.svg and see the image, not the XML.
Well, please take a look at the conversion result at https://github.com/boostorg/math/blob/master/doc/equations/airy.svg It seems that github delivers the source. You may want to open an extra thread for this,
Sorry, but what problem does mixed line endings in these actually cause?
Well, the files get converted to the platforms native line ending on git clone using the .gitattributes files or so. In the end, this leads to modified files immediately after the clone, which is undesirable.
They're intended to be viewed as images, they should never be edited as source as they're script generated.
Well, then why have they mixed eols? Can the script be fixed? And I guess I can edited them using inkscape ;-) Okay, I'll think about it. But the safest way would be to just correct the eols and leave the mime-type as-is. What happens to github is another story. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold@gmx.eu ! Germany