Good { morning, afternoon, evening },

We're working on an update to BBEdit 11 to address a few recently reported issues.

Note that this is a _pre-release_ version. The intent is to fix bugs and address areas of improvement based on what our customers have reported. However, since the software is at this point not fully tested, there _may_ be bugs and regressions. If this prospect makes you nervous, then sticking with the public release versions is your best course of action. Nobody will be offended if you choose to do so; you're under no obligation to install and use anything but a public release. :-)

Following is a summary of the changes in the software since the last pre-release build <https://groups.google.com/d/msg/bbedit/aSWIfXqjbr0/-tk39Qr04OQJ>. The change notes are organized into additions, changes, and fixes, and are annotated where appropriate with case numbers. So if you recognize a number corresponding to a support case that was opened for you, you can now verify that it's been fixed correctly. Please take the time to review the changes before using the new build -- it'll be worth your time.

One final note: If you run into a bug in a pre-release version, PLEASE DO NOT REPORT THE BUG TO THE LIST. This includes asking about whether others have seen the same problem. Instead, please send a bug report to <[email protected]> and we will deal with it there. This will help us keep the list discussion on topic and productive for all list members.

============================================================================

version 11.0.2 (3497)   (2014-12-04)

*   BBEdit now requires OS X 10.8.5 or later. It will not run on any
    previous version of the OS.

Additions
---------

    o   (none in this build)

Changes
-------

    o   (none in this build)

Fixes
-----

*   [300354] Made changes to reduce the transient memory needs of
    the internally factored text transformations (Zap Gremlins and
    others), which will help reduce the incidence of out-of-memory
    errors from occurring when applying these transforms to very
    large documents.

*   [300354] Made a change to reduce the amount of transient memory
    required by line ending conversion when saving files with Windows
    line endings.

*   [300392] Made a change so that the `documentDidSave` attachment
    script is called as the very last step, most notably after
    re-enabling file observing, so that if the attachment makes any
    changes to the file on disk, it will get reloaded.

*   [300311] Fixed bug in which the Strict Hierarchical formatter
    would unconditionally left-justify `pre`, `textarea`, `script`,
    and `style` tags.

*   The user manual is now downloaded using `https`, and the world
    is once again safe for democracy.

*   [300052] Fixed bug in which clicking in either document-view
    panel of a Find Differences window would cause the list of
    differences to scroll to the top.

*   [298088] Fixed bug in which the HTML syntax checker would report
    errors for correctly formed attributes whose required value was
    "empty", that is, the presence of the attribute itself was the
    correct syntax.

*   [299545] Restored code which ensures correct text layout if the
    legacy OS `AppleAntiAliasingThreshold` preferences key is present
    and specifies a text size larger than the current display font
    size.

=end=

The package can be downloaded from our web server:

    <http://pine.barebones.com/rhombus/BBEdit-11.0.2_3497.zip>

Enjoy,

R.
--
Rich Siegel                                 Bare Bones Software, Inc.
<[email protected]>                      <http://www.barebones.com/>

--
This is the BBEdit Talk public discussion group. If you have a feature request or would like to report a problem, please email
"[email protected]" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>

--- You received this message because you are subscribed to the Google Groups "BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].

Reply via email to