News for hackers. Stuff that matters.
Re:Why is printing “B” dramatically slower than printing “#”? by koenigdavidmj on Monday February 24, 2014 @07:25PM (#7294343)
Entirely unrelated, but this headline made me notice that Chrome finally supports entering " in the find-in-page box and having it match so-called smart quotes.
Re:Why is printing “B” dramatically slower than printing “#”? by oneeyedpigeon on Monday February 24, 2014 @07:48PM (#7294435)
Yup, it's definitely done that for a while. It does become a pain when you actually want to locate quotes that need smartening up, though.
Re:Why is printing “B” dramatically slower than printing “#”? by GauntletWizard on Monday February 24, 2014 @07:59PM (#7294478)
Why? Why would you do that to the world? Smart quotes are about the dumbest concept that has ever existed.
Re:Why is printing “B” dramatically slower than printing “#”? by oneeyedpigeon on Monday February 24, 2014 @08:59PM (#7294737)
‘Smart quotes’ are actually more typographically ‘correct’; that key on your keyboard is a prime symbol which is NOT the same as an apostrophe or a single quote mark. Apart from reducing ambiguity, they also look a lot nicer (in decent fonts), particularly at larger font sizes. I cringe when I see a prime (or ‘straight quote’) symbol being misused on TV or in print.
Re:Why is printing “B” dramatically slower than printing “#”? by talmand on Tuesday February 25, 2014 @11:09AM (#7298369)
Just curious, how do you feel if a font, let's say it is a decent font, is designed to make the apostrophe look like a prime symbol?
Re:Why is printing “B” dramatically slower than printing “#”? by omaranto on Monday February 24, 2014 @08:35PM (#7294628)
What's so dumb about them? Do you like your opening and closing parenthesis to be the same, too?
Re:Why is printing “B” dramatically slower than printing “#”? by raldi on Monday February 24, 2014 @09:02PM (#7294753)
No, which is why they have separate keys on my keyboard, unlike smartquotes, so I can always easily specify exactly which I want.

Also nobody magically switches my parentheses around out from under me.

Re:Why is printing “B” dramatically slower than printing “#”? by oneeyedpigeon on Monday February 24, 2014 @09:10PM (#7294788)
There are many wonderful characters that don't have their own individual keys on your keyboard. Heck, there are a lot of characters that require at least one meta key to be pressed in combination with another key, and single quote marks are accessible in exactly that way on my keyboard too (Mac, YMMV).

And, yes, autocorrect can be a PITA, especially when it's not actually getting things correct, but that's a different, albeit related, issue. We should really refer to quote marks, or apostrophe (which are often rendered as curly, and are the characters that autocorrect switches to), and the prime symbol (which is the unadulterated character that you get with the non-meta-pressed key on your keyboard), rather than using the term 'smart quotes'.

Re:Why is printing “B” dramatically slower than printing “#”? by kps on Monday February 24, 2014 @11:41PM (#7295626)
Not to detract from the substance of your post, but the unshifted keyboard key pretty much universally generates an ASCII apostrophe (U+0027, '), not a prime (U+2032, ′, as used for feet and minutes, and while I'm babbling, the addition of a second prime for seconds is not a coincidence).

~~~~ wavy lines starting flashback ~~~~

ASCII 1967, in conjunction with its European counterpart ECMA-6, permitted the visual appearance of some characters, including the apostrophe, to be modified so that they could be used as accents when overstruck¹:

  ' " , ^ ` ~
  ˊ ¨ ¸ ˆ ˋ ˉ (using the modern Unicode spacing modifiers)
Later versions of ECMA-6 suggested that the accent interpretation be used only when the character was actually overstruck:

  In the 7-bit character set, some printing symbol may be
  designed to permit their use for the composition of ac-
  cented letters when necessary for general interchange of
  information. A sequence of three characters, comprising
  a letter, BACKSPACE and one of these symbols, is needed
  for this composition; the symbol is then regarded as a dia-
  critical sign. It should be noted that these symbols take
  on their diacritical significance only when they precede or
  follow the character BACKSPACE; for example, the symbol
  corresponding to the code combination 2/7 normally has the
  significance of APOSTROPHE, but becomes the diacritical
  sign ACUTE ACCENT when preceded or followed by the character
  BACKSPACE.²
Although this was fine for the printing teletypes in use when ASCII was first designed, early video terminals were too dumb to handle overstrikes, so it never caught on.

¹Revised American Standard Code for Information Interchange, from http://www.wps.com/J/codes/Revised-ASCII/index.html

²ECMA-6: 7-Bit coded Character Set, 4th Edition, August 1973, from http://www.ecma-international.org/publications/files/ECMA-ST...

~~~~ wavy lines ending flashback ~~~~

Re:Why is printing “B” dramatically slower than printing “#”? by raldi on Tuesday February 25, 2014 @01:33AM (#7296037)
Please don't abuse tildes in this way; use the proper Unicode wavy-line character: ⌇
Re:Why is printing “B” dramatically slower than printing “#”? by cnvogel on Tuesday February 25, 2014 @02:08AM (#7296131)
But your wavy line has the wrong orientation...

  2307 ⌇ WAVY LINE http://www.unicode.org/charts/PDF/U2300.pdf
What you most likely intended to present as an alternative is the...

  301C 〜 WAVE DASH http://www.unicode.org/charts/PDF/U3000.pdf
unicode smiley ➩ ☺
Re:Why is printing “B” dramatically slower than printing “#”? by oneeyedpigeon on Tuesday February 25, 2014 @03:55AM (#7296414)
OK, looks like I need to go back to school for a bit before attempting to comment on this again! Thanks for the history lesson.
Re:Why is printing “B” dramatically slower than printing “#”? by deathanatos on Monday February 24, 2014 @11:06PM (#7295424)
They don't have a dedicated key, I suppose, (but then again, you have to hit <shift> to get parens…) but smart quotes are <option>+{ and <option>+<shift>+{ on OS X, and configured to be <compose>, <, " and <compose>, >, " on my Linux machine.

Smart quote are a bit of a pain, but they do look nice. Really I prefer em dash, en dash, ellipses; I regret that OS doesn't have a keyboard entry for bullet. (Then, Linux doesn't either, other than entering in the code point directly with Ctrl+Shift+U or whatever it is.)

Re:Why is printing “B” dramatically slower than printing “#”? by roryokane on Tuesday February 25, 2014 @12:40AM (#7295868)
On OS X, you can type a bullet • with <option>+8.

You can also edit your keyboard layout to make certain characters possible or easier to type, using Ukelele (http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=...) for OS X.

I created a custom layout using Ukelele that makes typing smart quotes easier. With it, opening ‘ and closing ’ single smart quotes are <option>+[ and <option>+] instead of <option>+{ and <option>+<shift>+{, and double smart quotes “ ” are similarly more intuitive to type. I use it all the time. You can try it out yourself by downloading it from http://a.pomf.se/bipwcr.zip and moving the two files into “~/Library/Keyboard Layouts/”.

Re:Why is printing “B” dramatically slower than printing “#”? by mattdw on Tuesday February 25, 2014 @12:41AM (#7295875)
option-8 on my mac keyboard is •.
Re:Why is printing “B” dramatically slower than printing “#”? by ygra on Tuesday February 25, 2014 @03:32AM (#7296350)
German Wikipedia uses proper quotes instead of the straight variety. I did a lot of wikignoming a while ago and fixing quotes (and non-breaking spaces, and citation formats) was among the things I did. Being able to quickly find straight quotes on the page is very helpful in that regard.
Re:Why is printing “B” dramatically slower than printing “#”? by w1ntermute on Monday February 24, 2014 @08:11PM (#7294529)
Meanwhile, Firefox continues to distinguish between e and é when searching, despite Chrome having fixed this bug years ago.
Re:Why is printing “B” dramatically slower than printing “#”? by reubenmorais on Monday February 24, 2014 @09:29PM (#7294915)
> this bug

"9001 Wrong Things Programmers Assume About Internationalization"

This behavior should at a minimum be locale-aware. I would be surprised if Firefox did that by default in my pt-BR profile.

Re:Why is printing “B” dramatically slower than printing “#”? by chavesn on Tuesday February 25, 2014 @12:47AM (#7295902)
(I'm not programming this kind of thing so please forgive my ignorance.)

Is that loose of a search not actually desirable in "find in page" instances?

In other words, are there many words where 'e' matching 'é' would actually generate a false positive? This is the only case I could see that would be problematic.

And even then "find in page" is usually used as quick navigation to the minimum matching search (high recall) and not about excluding all possible mismatches (high precision).

Re:Why is printing “B” dramatically slower than printing “#”? by logicchains on Tuesday February 25, 2014 @01:39AM (#7296048)
There are words in other languages, French for instance, that with an accent changed or removed have completely different meaning.
Re:Why is printing “B” dramatically slower than printing “#”? by bausson on Tuesday February 25, 2014 @03:36AM (#7296367)
That is sadly true.

It's even worse than that. 'e' is the most used letter in french, but 'é' and 'è' are quite used too. 'ê' and 'ë' being rarer, but still existing.

So, I am exaggerating it a bit, but you can compare it to having to search for words with the consonants, because every vowel is considered the same by your search algorithm.

Yes, I'm pushing it, but you see the problem it can easily become in huge pages.

Re:Why is printing “B” dramatically slower than printing “#”? by JetSpiegel on Tuesday February 25, 2014 @05:44AM (#7296799)
Why sadly?
Re:Why is printing “B” dramatically slower than printing “#”? by bausson on Tuesday February 25, 2014 @08:35AM (#7297470)
What is sad for me is chrome new way of handling thing, not french accents (which can be a bother, but they're cute, so that's ok).

Most pages nowadays are small enough that it won't be a bother, but their still are some cases (newspaper posts, blog analysis, etc...) where accent sensitiveness will be an issue.

Re:Why is printing “B” dramatically slower than printing “#”? by ygra on Tuesday February 25, 2014 @03:33AM (#7296357)
It should probably be aware to the language of the page, not your own.
Re:Why is printing “B” dramatically slower than printing “#”? by lmm on Tuesday February 25, 2014 @05:22AM (#7296728)
No, no, no. The user needs to be able to predict the behaviour.
[deleted]
Re:Why is printing “B” dramatically slower than printing “#”? by lmm on Tuesday February 25, 2014 @11:02AM (#7298324)
"Nice things" like searching for "cafe" on page A, finding "café" and thus concluding that search works like that, then searching for "cafe" on page B, not finding anything, and then discovering that page B actually did say "café"?
Re:Why is printing “B” dramatically slower than printing “#”? by scott_karana on Monday February 24, 2014 @08:30PM (#7294602)
Does it depend on the locale, perhaps?
Re:Why is printing “B” dramatically slower than printing “#”? by wbsun on Monday February 24, 2014 @10:56PM (#7295375)
Ah, this is off topic and let me close it to show off my power... hmm, are we on SO?
Re:Why is printing “B” dramatically slower than printing “#”? by shurcooL on Monday February 24, 2014 @07:31PM (#7294370)
I recall it doing that (for other symbols too) for quite a while. At least 4-6+ months, on stable channel.