I'm pretty sure this stupid hybid GPU system is the reason I need Sony-specific drivers and the Intel/nVidia default graphic drivers just make things run super super slow. I do suspect the current 8/8.1 drivers will work just fine on 10 though, but Sony's official position is to not install Windows 10 until after November right now.
Given how bad the stock Intel and nVidia drivers make my Vaio Flip 15 function compared to the modified Sony ones, I'm pretty worried about upgrading to Windows 10. Drivers aren't going to be available until November according to Sony - http://esupport.sony.com/US/p/... - because mine came with 8 (not 8.1) preinstalled, even though 8.1 was out at the time.
Except while that is called "Hyphen-Minus" and can be used for two things, Unicode does try to solve that problem by having:
00AD Soft Hyphen
2011 Non-Breaking Hyphen
2012 Figure Dash
2013 En Dash
2014 Em Dash
2015 Horizontal Bar
2212 Minus Sign
2796 Heavy Minus Sign
There is no "Mathematical Hiragana No" glyph defined by Unicode, and as such, it should never be rendered in a different font just because somebody *might* use it in a formula. The application is wrong, and there is no bug in Unicode.
I'm aware of the problems with the han unification and certain Kanji being displayed "wrong" because the Chinese equivalent is drawn significantly different from the Japanese Kanji, but this doesn't seem to be anything close to that kind of problem. I'm also aware of the Unicode block U+1D400 "Mathematical Alphanumeric Symbols" which is what should be used for formulas. Any application that is rendering one particular character in the Hiragana block in a different font than the rest of the Hiragana block, is quite frankly, just rendering it wrong. The bug is with the application as far as I'm concerned, and this clearly does not impact default system rendering or any common web browsers as far as I can see either.
Hotmail/MSN/Outlook mail is well known for just not delivering lots of legitimate mail now. You may not see spam there, but you may not get mail from a friend who doesn't use common webmail like gmail or Yahoo. The mail does not even go to your junk/spam folders, and it does not get bounced to the sender. They just silently accept and delete incoming mail, without any notification.
I'd, personally, rather see spam getting through than email become a useless technology that fades away because people can't rely on it anymore.
The character in question is Hiragana "No", codepoint U+306E. As far as I can tell, this has existed since Unicode 1.1 and there are no differences in the Unicode metadata when compared to any other Hiragana glyph. It is marked as IsAlphabetic=True, Category=Other Letter, and NumbericType=None for example. So are all the other common Hiragana glyphs. If there is a bug, it's clearly with some specific application, and not Unicode or Unicode metadata. Compare http://www.fileformat.info/inf... with any other Hiragana glyph, like http://www.fileformat.info/inf... (Hiragana "Ha").
http://vanilla-js.com/ is probably much more worth learning and using. The *ONLY* reason to be using jQuery is for IE8 support, but I've long since required IE9+ for all freelance work I do, and do everything in CSS and Vanilla JS now.
Can this be used to root your phone (as in, install SuperSU), and can this be done without tripping Knox?
Can this be then mitigated by a simple hosts entry for the domain used to check for updates? (Pretty sure the answer here would yes - if skslm.swiftkey.net points to 127.0.0.1, no rouge WiFi's DNS is going to be able to change that).
Windows does render ClearType fonts into the subpixels BEFORE scaling up though, completely negating the subpixel rendering benefits, and actually making fonts look significantly worse as a result.
The whole scale-up solution for applications that don't declare DPI aware in the manifest resource would be a lot better if they at least reverted to greyscale subpixel font rendering first...
It's because unless your app declares itself HiDPI-aware in the manifest file (Skype does not do this) then Windows will pretend that it's still 96dpi and then just scale up the UI 200% (for 192dpi screens). But it's not as simple as adding the line to the manifest file. You actually have to write your software without the assumption of 96dpi dialogs, and use the system API functions to query the proper scales. Most developers never seem to even know about those functions though, so you end up with a random mix of too-big and too-small things.
Even if Microsoft's scaling approach didn't render fonts into the subpixels BEFORE scaling up the 200%, it would still look really blurry and horrible compared to just fixing the code in Skype to actually take advantage of higher resolution. Apple's approach just gives you grey blurry edges around fonts and blurry graphics vs Microsoft's red and blue blurry edges around fonts and blurry graphics.
Maybe they can finally make it looks readable on HiDPI (192dpi) screens like my 2880x1620 laptop. The font pixelation is so horrible you can't use the chat at all.
So this is why they removed the super-useful feature that used to let you group your subscriptions into named groups until a few weeks ago? Because it was called "collections" and they wanted to repurpose the name for some useless video game thing nobody is going to use?
Click the menu icon in the top left of the upgrade reservation thing, then pick Check your PC. On my VERY new Sony VAIO Flip 15, which came with Windows 8, I get the message "These devices aren't fully compatible with Windows 10" -> Intel(R) HD Graphics Family -> You'll experience problems with your display.
So what does this mean? If I let the upgrade happen on July 29, my screen goes black after that? How can such a new video "card" be unsupported? (It's the built-in display on the Core i7-4500U this thing has). Is it because I also have the Nvidia GeForce GT 735M on here, with that GPU-switching technology (Optimus?) that so many new laptops have now?
No, why not offer the free upgrade to Vista+ instead of 7+ (for legitimate installs)?
I don't quite get why the cut-off is Windows 7 and not Vista? The hardware requirements are basically the same from Vista to 10, and internally that would cover a free upgrade to 10.0 for Windows versions 6.0 to 6.3.
Not to mention getting home users off IE9 would be a big plus for the web in general (assuming you've already just dropped IE8 users like you should have).