SUPPORT : BBEdit : Archived Release Notes : BBEdit 7.0.3 Release Notes
BBEdit 7.0.3 Release Notes
This page documents all feature enhancements and bug fixes included in the BBEdit 7.0.3 maintenance update.
The BBEdit 7.0.2 release notes detail the fixes and improvements made in BBEdit 7.0.2.
Additions
-
There is a new switch in the "Text Files: Opening" preference panel: "Link File's Encoding to HTML/XML Character Set". When this option is selected, BBEdit will use the character set specified in the appropriate HTML meta tag or XML declaration to determine a file's encoding when opening the file. Also, when this option is on, changing an HTML or XML document's character set with the Character Set markup command will adjust the file's encoding to match (as indicated on the Encoding submenu of the File Options popup in the status bar), and changing the file's encoding will adjust the character set declaration (if one exists). This option is on by default.
When this option is off, then BBEdit does not attempt to use the character set specified in the HTML meta tag or XML declaration, but will follow the usual procedure for determining the file's character set. (See "Choosing the Encoding for a Document" on page 25 of the user manual.) The only reason you might want to turn this option off is if you routinely put characters into your document that cannot be represented in the declared character set, e.g. if you will be postprocessing the file by some other means which modifies these characters.
There is a new HTML placeholder: #shortusername#. When running on Mac OS X, this will return the login name (correia) instead of the full user name (Jim Correia). On Mac O 9, it returns the owner name from the sharing control panel, since there is no short name.
The behavior of Close Current Tag has been modified: it no longer inserts an extra return if it doesn't need to, and, if it puts the close tag on a separate line, it matches the indent level to that of the open tag (if you have already moved the insertion point onto a new line, it leaves the indent level alone - that is where you left it)
Fixes
Worked around a behavior in Dreamweaver MX in which choosing "Edit in BBEdit" while in the Dreamweaver "Code View" would result in non-ASCII characters being sent over unencoded.
Dreamweaver MX always expects to see Mac Roman files when synchronizing with BBEdit. We now indulge that particular limitation in Dreamweaver, to prevent it from incorrectly transcoding non-ASCII characters during synchronization.
Previous versions of BBEdit enforced a limitation that you could not compare a Unicode file against a non-Unicode file. Beginning with 7.0.2, this tended to pose a problem, since single-byte files in encodings other than Mac Roman are now represented internally as Unicode in situations where they weren't before, and so attempts to compare them to Mac Roman files would fail without visible explanation. Beginning with this version, no restriction is imposed on comparing two files with differing states of Unicode-ness.
Fixed a bug where the #doctitle# placeholder (actually the utility function that extracts the html document title) wasn't correctly stripping whitespace off the end of the title.
Fixed a bug in the document size tool where garbage was inserted into the window.
When opening an encoded (i.e. non-Mac Roman, non-Unicode) text file, the file is now always represented as Unicode internally, and no attempt is made to guess the file's display script unless absolutely necessary. This improves the performance of opening large encoded files, and also resolves the observed behavior in which some files which contained characters not existing in Mac Roman would open up with a Korean (or possibly Greek) display font.
Fixed bug in which the spelling checker didn't correctly handle possessives and contractions created by the use of the right-hand apostrophe ( ’t ) in Unicode files.
Fixed bug in which the spelling checker didn't correctly handle a possessive or contraction created by the use of an entity. (For example, the string "shouldn’t" in an HTML document.)
Fixed bug in which the spell checker would behave strangely when encountering entities that decoded to word-break characters.
Fixed bug in which a non-Mac Roman (e.g. ISO-Latin1) document containing saved state with a font setting was made dirty when opening.
When saving a file as UTF-16, byte swapped, with no byte-order mark (BOM), the file is now given a type of 'TUTX'. This prevents the file's contents from being misinterpreted when the file is re-opened. (Conversely, files with the type 'TUTX' are assumed to be byte-swapped UTF-16.)
Fixed a regression in the URL encoder where it was complaining/encoding about a ; in situations where it ought not to.
Fixed a bug where the temp file written out for Unix/Perl data was written incorrectly if the source window was represented in memory as Unicode.
Fixed a bug where the temporary Unix/Perl script was written in an incorrect encoding (based on the Unix scripting prefs) if we were executing a disk file instead of a window.
Fixed a bug in the Unix/Perl output where it was always interpreting script (not filter) output as UTF-8 encoding even when the switch had been turned off in the prefs.
Switching the text encoding using the status bar popup of an HTML or XML document with no meta tag or XML pi was non-functional. Fixed.
Fixed bug in which trying to change the display font or size of a browser window would result in an Apple Event error being reported.
When opening a document, its text encoding is now synchronized with the file's script code, if appropriate.
The document's text encoding is no longer changed in response to a font change. This solves the problem of documents which explicitly specified one text encoding (e.g. in an HTML meta tag or XML PI), but which contained characters not representable in that encoding. In that case, the document will be displayed in whatever font is capable of rendering the displayable characters, but the encoding is no longer changed.
The "If a File's Type is Unknown" preference (Text Files: Opening) is now applied when opening files via the Apple Event interface (and from the command-line tool). Thus, if you insist on using a suffix which the OS maps to a non-text-file type, you can add a language mapping for that suffix to the "(none)" language, set the preference to "Map the File Name", and go wild.
Fixed bug in which multi-term file filters didn't work when used to filter a multi-file Find Differences operation.
If an encoding-related error occurs while saving a document, the file on disk is no longer affected.
If unmappable elements are found when saving a document (for example, a tilde in a Shift-JIS document), you are now given the option to cancel the save (so that you can go back and adjust the encoding) or save the file as UTF-8 instead. This differs from the previous behavior in which SUB (0x1A) characters were written into the file and you were alerted after the fact.
Fixed bug in which Command-clicking to resolve a URL didn't work in any non-Mac-Roman file.
Fixed bug in which the popup menu of languages was disabled in the Language preferences when adding or editing a suffix mapping.
Fixed bug in which the command-line tool didn't wait long enough for the application to come up, so files opened this way didn't open if the application had to be launched first.
The Python language module is now multi-byte savvy, and so now works on files that were opened with encodings other than Mac Roman.
Fixed bug in which files opened by Dreamweaver's "Edit in BBEdit" command opened with the text encoding unset, which in turn would cause an error to be reported when trying to save the file.
Fixed bug in which a -50 error would be reported when the default encoding preference (Text Files: Opening) was set to UTF-8 and the file was of zero length.
Fixed bug in which a -8739 error would be reported when opening the Preferences window if the default encoding (Text Files: Opening) had been changed to UTF-8.
Fixed a bug where if you had the directory structure
folder/foo
folder/foo-tooand the current working directory was "folder/foo", dropping "folder/foo-too" into the worksheet inserted the incorrect file path. This also corrects a problem where dropping the current working directory into a worksheet could produce a crash.
the “QuickTime Playback” switch in the Application preferences is now off by default. This should reduce confusion when opening certain text files that QuickTime can also interpret as movies, e.g. SMIL files and .m3u files. If you are updating from a previous version of BBEdit, this switch will be turned off upon launching BBEdit 7.0.3 for the first time. If you were accustomed to using BBEdit as a movie or music player, turn the option back on.