- Use `https://` (fix#172), including in prompt for URL and relevant code comments (where available and naturally not on namespaces)
- Comment out broken link in svg-editor.html
- Trailing space
README.md previously pointed to binaries on progers's fork. Now that https://github.com/SVG-Edit/svgedit/pull/23 has landed we can update these links to point to the main repository.
This is an update to README.md which merges the main code.googe.com landing page (https://code.google.com/p/svg-edit/) and the existing README.md file.
Actual changes:
* Some editorial license has been used when updating the main project summary, including adding a project logo.
* The recent news section has been updated to include svg-edit 2.8 and the move to github.
* The features section has been dropped as there's no easy way to represent such a list in markdown.
* The further reading section has been updated.
* The dependent projects have been moved to docs/Acknowledgements.md
The binary file links currently point to my github fork. Once we actually create the svg-edit-2.8 release, these should be updated to point to the main project instead of my fork.