fix Unicode handling in parser (#1884)
There was an implicit assumption that first character within surrogate header range implies the next character must form a surrogate pair, which is not necessarily true.
This commit is contained in:
@@ -215,16 +215,6 @@ function OutputStream(options) {
|
||||
var might_add_newline = 0;
|
||||
var last = "";
|
||||
|
||||
function last_char() {
|
||||
var char = last.charAt(last.length - 1);
|
||||
|
||||
if (is_surrogate_pair_tail(char)) {
|
||||
return last.charAt(last.length - 2) + char;
|
||||
}
|
||||
|
||||
return char;
|
||||
};
|
||||
|
||||
var ensure_line_len = options.max_line_len ? function() {
|
||||
if (current_col > options.max_line_len) {
|
||||
if (might_add_newline) {
|
||||
@@ -247,7 +237,7 @@ function OutputStream(options) {
|
||||
function print(str) {
|
||||
str = String(str);
|
||||
var ch = get_full_char(str, 0);
|
||||
var prev = last_char();
|
||||
var prev = get_full_char(last, last.length - 1);
|
||||
if (might_need_semicolon) {
|
||||
might_need_semicolon = false;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user