Re:Google fires employee who leaked memo on raises
by roel_v on Thursday November 11, 2010 @03:08AM
(#1893252)
You could use a pattern of one or two spaces after each sentence. Encode an id in that. If text is copy and pasted and not processed with a s/ / /g, that most likely won't be detected by the copy-and-paster (especially when it's all done in a variable width font).
[ Parent
| on HN ]
Re:Google fires employee who leaked memo on raises
by roel_v on Thursday November 11, 2010 @03:54AM
(#1893339)
Looks like HN does remove double spaces, what I meant was obviously s/[space][space]/[space]/g :)
Re:Google fires employee who leaked memo on raises
by modeless on Thursday November 11, 2010 @05:18AM
(#1893462)
It's not HN, it's a feature of HTML. All whitespace characters (including tabs and newlines) are condensed to a single space, and leading/trailing spaces are removed. So if you have a habit of double-spacing after sentences, HTML simply ignores you, unless you use <pre> or .
Re:Google fires employee who leaked memo on raises
by roel_v on Thursday November 11, 2010 @06:19AM
(#1893551)
Ah didn't know that. Well that would make the single/double space encoding of an id much harder.
Re:Google fires employee who leaked memo on raises
by grncdr on Thursday November 11, 2010 @11:52AM
(#1894335)
Actually, it makes it more effective if anything. The browser displays it as a single whitespace, but the source isn't altered, (and therefore easily checkable).
Re:Google fires employee who leaked memo on raises
by roel_v on Thursday November 11, 2010 @12:16PM
(#1894444)
Yeah but if a user copy/pastes it from his email client into his blog posting system, the double spaces are stripped, too (I checked it with Firefox, maybe other browsers work differently). It would only work I think if the single/doubles space pattern was preserved across copy/paste operations.