Less Wrong is a community blog devoted to refining the art of human rationality. Please visit our About page for more information.

PhilGoetz comments on The bias shield - Less Wrong

18 Post author: PhilGoetz 31 December 2011 05:44PM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (65)

You are viewing a single comment's thread.

Comment author: PhilGoetz 30 December 2011 11:50:25PM *  5 points [-]

Anyone know why the website is removing spaces before and after every italicized word in the post, and how I can make it stop?

Comment author: Vladimir_Nesov 31 December 2011 12:03:03AM *  5 points [-]

Fixed. <div> tags present in HTML trigger this bug; there is an issue on LW bug tracker, but developers say it can't be easily fixed, so we are left with having to manually remove the offending tag each time it slips in.

Comment author: wedrifid 31 December 2011 12:17:58AM 1 point [-]

Fixed. <div> tags present in HTML trigger this bug, there is an issue on LW bug tracker, but developers say it can't be easily fixed, except by manually getting rid of the offending tag.

Not easily fixed? Nonsense. Not elegantly fixed perhaps. It can be easily fixed with, by way of proof of concept, regex and a cron job.

Comment author: Vladimir_Nesov 31 December 2011 12:23:31AM *  0 points [-]

Quite. To fix the more heavily misformatted posts, I use a script that in particular does just that for the <div> tags (replacing them with <p>), but sometimes it garbles/discards nonstandard ways of meaningfully marking up the text and needs to be corrected on case-to-case basis. Writing a script that automatically works in general would be harder, require more expertise with peculiarities of HTML, and ideally a test suite to make sure that it doesn't disrupt useful markup. (I fail to see where a cron job might enter the picture.)

Comment author: wedrifid 31 December 2011 12:35:20AM *  1 point [-]

(I fail to see where a cron job might enter the picture.)

Trike has knowledge about the codebase that I do not. It is theoretically possible (albeit unlikely) that the code is constructed such making the correction take place at an appropriate time does not qualify as 'easy'. However information that is available is that Vladimir_Nesov is able to log in and make such corrections via a html interface. To establish with confidence that correction (within the limits of the side effects you mentioned) would be easy without relying on any assumptions about the inner workings of the codebase it is simple to consider simply running a regexing script remotely using Vladimir_Nesov credentials. This establishes an upper bound.

Comment author: Vladimir_Nesov 31 December 2011 12:41:03AM *  0 points [-]

OK. In any case, that doesn't work, because of the mentioned difficulty with creating an automatic script that doesn't damage the text sometimes (it's generally irresponsible to edit a public archive without manually testing the results when probability of damage is nontrivial), though a script that alerts about the presence of <div>'s could ensure that corrections happen more reliably.

Comment author: PhilGoetz 31 December 2011 05:36:04PM 0 points [-]

Thanks! I see it didn't revert when I edited the post, which surprises me.

Comment author: CharlieSheen 31 December 2011 06:11:16PM 1 point [-]

I've encountered this bug too.

Comment author: [deleted] 31 December 2011 05:35:21PM *  1 point [-]

It is an extremely annoying bug. It shows up not just with italicized words, but sometimes with words written in bold and most damning of all, links.

It really saps my will to try and make new posts, I have two or so posts languishing in draft form because I'm tired of working around the bug all the time.

Comment author: wedrifid 31 December 2011 05:55:58PM 0 points [-]

It is an extremely annoying bug. It shows up not just with italicized words, but sometimes with words written in bold and most damning of all, links.

A bug that affects italicized words also affects words written in bold. Inconceivable!

Comment author: CharlieSheen 31 December 2011 06:11:54PM *  4 points [-]

It is an extremely annoying bug. It shows up not just with italicized words, but sometimes with words written in bold and most damning of all, links.

Clearly he meant written in blood. Come on guys, if we are going to be serious about this doomsday cult thing we need to stop jumping each other because of typos, so chill wedrifid.

Comment author: [deleted] 31 December 2011 06:05:43PM *  3 points [-]

Well of course it does, but my brain perceives these as separate separate insults to my weak determination to work through trivial inconveniences! In any case I don't share Eliezer's love for italics, but not being able to spam my articles with a dozen links, is plain unforgivable.

Tis is the season to air grievances after all. :P

Comment author: wedrifid 31 December 2011 06:11:41PM 4 points [-]

but not being able to spam my articles with a dozen links, is plain unforgivable.

Definitely! I love link spam. It formalizes how we use phrases as references to existing concepts and saves on google searches!

Comment author: arundelo 31 December 2011 06:30:11PM 1 point [-]

It may help to think of selecting pieces of text and clicking buttons to turn them into links as the inconvenient part. On the rare occasions when I've made top-level posts, I've edited the HTML source directly (in a real text editor). Happy Festivus!