testing comment title containing UTF-8 chars; posting format: "Plain Old Text"
SOURCE DATA: cut-and-paste of parent text's reversed and inverted (upside-down and backward) version of: "an the site now handle this?" into both the subject field and the comment field.
When initially pasted in, the subject text looked correct.
When initially pasted in, the comment text looked correct.
Pressed preview button
In "Preview Comment" area, saw subject text change to mojibake.
In "Preview Comment" area, saw comment text change to mojibake.
In "Edit Comment" area, saw subject text entry field change to a *sequence* of: ampersand, pound sign (aka sharp, hash mark, number sign, or octothorpe), digits, semicolon.
In "Edit Comment" area, saw cut-and-pasted text appear as originally pasted (and as appeared in parent post).
(Score: 1) by martyb on Sunday February 16 2014, @10:53PM
testing comment title containing UTF-8 chars; posting format: "Plain Old Text"
SOURCE DATA: cut-and-paste of parent text's reversed and inverted (upside-down and backward) version of: "an the site now handle this?" into both the subject field and the comment field.
When initially pasted in, the subject text looked correct.
When initially pasted in, the comment text looked correct.
Pressed preview button
In "Preview Comment" area, saw subject text change to mojibake.
In "Preview Comment" area, saw comment text change to mojibake.
In "Edit Comment" area, saw subject text entry field change to a *sequence* of: ampersand, pound sign (aka sharp, hash mark, number sign, or octothorpe), digits, semicolon.
In "Edit Comment" area, saw cut-and-pasted text appear as originally pasted (and as appeared in parent post).