On Sat, 2009-12-26 at 18:59 -0800, Jon Cruz wrote:
- you might highly doubt users behave that way... but I have
*observed* users behave that way again and again and in many different contexts.
<user view> Linking: Years ago, using a page layout application, the images were linked, and I had to remember to include the original files when sending the layout file. Really no big deal. Linking is the way the web works, so it's easy to understand. It makes sense to me not to include binary data in a text based XML file format such as SVG.
Bundling the file together with the linked images the way ODF does makes some sense for file storage and transportability - but embedding the file, by UUencoding or Base64 or something doesn't make sense to me, because it can't be edited with a text-editor - which in my view, is one of the key features of SVG for future-proofing and digital archiving. </user view>
What does the SVG standard suggest? What's wrong with the current 'save as' compressed svg with media (*.zip) option... perhaps some documentation or asking heathenx to do a screencast on this topic would help those users who are unfamiliar with this standard practice?
Or perhaps a warning on save that can be turned off by expert users?
'you have pasted / inserted an external bitmap image in this file, would you like to save as compressed svg with media'?
- Donna