On Mar 7, 2:07 am, Tobias Beer <[email protected]> wrote:
> Great, thanks! Would you mind explaining briefly what the problem was with
> the UTF-8 character encoding?

After TW2.7.0 was released, it was reported that it was failing to
pass a test for "valid UTF-8" encoding, due to the presence of a
single byte 0xFF (which is outside the 0x00-0x7F range for single-byte
characters... i.e. 7-bit ASCII encoding).  By using a binary/hex
editor to search the content of the file, the errant byte was located
within a quoted string used as a literal parameter being passed in
function deep within the jQuery 1.8.1 code.

Jeremy and I did a number of experiments to attempt to isolate the
cause of the introduction of the errant byte (e.g., was it a result of
a one-time build error or a problem with with TW5 build tools, etc.).
As part of this investigation, we decided to see if the *current*
revision of jQuery contained the same quoted string of binary
values... or even anything similar.  What we found is that jQuery1.8.3
had actually replaced the content of the errant quoted string
parameter, and now uses "\U..." syntax to represent the same binary
values that were previously embedded directly.

Thus, although we didn't actually determine the origin of the problem,
we did find a robust solution by updating the embedded jQuery library
from v1.8.1 to v1.8.3, thereby bypassing the problem entirely.  (I
suspect that other users of jQuery may have run into similar issues,
prompting the change to their implementation).

The good news is that, with the updated jQuery library in place, the
assembled TW2.7.1b1 file now passes the normal 'validity checks' for
UTF-8 encoding.

-e

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" 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].
Visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to