Apparently, the website used Releases:1.5:Notes:Web format for the final 1.0 notes, while the Release Notes RTF used a different format :p
* * * DRAFT * * *
About Camino® 1.5
After over a year of hard work by devoted volunteers, the Camino Project is proud to give you Camino 1.5. This latest version fixes hundreds of bugs and implements many new features, providing all users with an improved browsing experience.
Camino 1.5 brings you a heavily-updated version of the only native Mac OS X browser using Mozilla’s Gecko rendering engine. This release displays web pages with Gecko 1.8.1, the same rendering engine used by the popular Firefox 2 web browser. Gecko 1.8.1 includes thousands of new bug fixes over the version used by Camino 1.0, providing users even better web page compatibility.
The features listed below are just some of the many changes in Camino 1.5.
Please don't hesitate to contact us with feedback regarding Camino 1.5; we'd love to know what you think! still not sure about this for the RTF notes
Note: Due to major changes in Camino, Mac OS X 10.2 is no longer supported. Users still running Mac OS X 10.2.8 should continue to use Camino 1.0.5.
Features in Camino 1.5
The following are the highlights of the changes and improvements made since the Camino 1.0 release. A full list is available on our website [lnk?]. (still need to be ordered properly)
- Improved tabbed browsing - Camino now supports forcing links that would open new windows into new tabs instead (“single-window mode”) and returning to the original tab after viewing a page in a new tab (“tab jumpback”).
- Spelling - Spell-checking using the Mac OS X spelling dictionaries is now enabled in web page text fields.
- Feed detection - When a web page offers an Atom or RSS feed, Camino will detect the feed and offer to pass it to the system’s default feed reading application.
- Session saving - Camino can remember which pages were open when quitting and restore them the next time it opens. Camino will also offer to restore pages open before a crash.
- Keychain compatibility - Camino can now read Keychain entries saved by Safari and can also share entries with Safari.
- Pop-up blocking - The new pop-up notification offers more powerful control for managing pop-ups.
- Plug-in blocking - Camino 1.5 provides an option to disable all plugins and also includes the ability to block Flash animations until the user clicks on them (“Flashblock”).
- Window zooming - The Zoom command now resizes the window to fit the current page’s content instead of making the window full-screen.
- Downloading - A new optional toolbar icon in the Downloads window allows users to move downloaded files to the Trash. In addition, two new preferences were added: one to remove successfully completed downloads automatically and one to clear the download list upon quitting Camino.
- Searching - The search field in the toolbar is now resizable, and the context menu for selected text in web pages now includes a “Search” item. new clause needs help
- Cookie management - Camino now includes an option to accept cookies only for the current session.
- User interface polish - Camino 1.5 includes a major reorganization of menus and keyboard shortcuts and redesigned preference panes.
For information about other issues or problems, please visit our Help page [lnk].
- Some users have experienced a situation where pages would appear not to load after clicking on a link. In this case, resizing the browser window may allow the page to display properly.
- Microsoft’s Windows Media Player (WMP) plugin causes major rendering issues in Camino. Since Microsoft has discontinued WMP on Mac OS X, Camino no longer supports the use of the WMP plugin; instead, all users should download the free Flip4Mac (F4M) plugin, version 2.1 or higher, from http://www.flip4mac.com/. Version 2.1 causes pages containing WMP content to become white when scrolled in Camino; there is currently no ETA for a fixed version of the F4M plugin.
- Camino erroneously claims that the default Japanese and Traditional Chinese fonts are “missing” when they are actually installed; this is due to a mismatch between Carbon and Cocoa font names. Changing these fonts using the Camino user interface will result in incorrect fonts being chosen and will cause some characters to fail to display. Users should either keep the default fonts or change the font preferences manually, ensuring the Carbon versions of the font names are used.