j4_james
Changing a character's width from wide to narrow after it has already been output is fraught with problems for a terminal. Imagine trying to write a "narrow" text presentation emoji in the bottom right corner of the screen. You'd think it should fit, but the emoji is received before the VS-15 selector, and that doesn't fit, so the terminal is forced to wrap the text, triggering a scroll of the entire page. By the time the VS-15 arrives, there's no way to undo all of that.
And for another example, try using IRM (insert replace mode) to insert a text presentation emoji in the middle of some existing text. If it was really narrow, you'd expect it to insert enough space for just one character, but it actually inserts two spaces, only occupying one of them, and then leaving an unexpected gap. And the more of these "narrow" characters you insert, the bigger the gap becomes.
VS-16 changing a text presentation character from narrow to wide doesn't share these problems. And that behaviour is supported by the spec text, which says that emoji should generally have a square aspect ratio. And at one time the East Asian Width spec specifically mentioned VS-16 making narrow characters wide (but said nothing about VS-15 making wide characters narrow).
People just use "ANSI" as a shorthand for ANSI X3.64-1979. And that was the standard that DEC used for their VT100+ range of terminals, which in turn became the de facto standard from which most modern terminal emulators are derived. If you read the DEC documentation, you'll find many references to "ANSI standard", "ANSI controls", "ANSI colors", etc. I don't think this is because they were ignorant of the subject matter, considering that they were members of the committee that produced that standard.
And ECMA-48 is essentially just the European equivalent of ANSI X3.64, and was developed in parallel. But obviously an American company like DEC or Microsoft would more likely be working from the American version of the standard rather than the European one.
> However, it has exemptions for health and religious reasons.
Also make sure your modem settings in MAME match the settings configured on the VT102. I have them both set to 19200 baud 8N1. I've just done a quick test now, and I can definitely make it through tests 1 and 2 in vttest without the output getting corrupted.
I should also mention that I've got the RS232 device set to null_modem (which is hooked up to a socat instance via MAME's bitbanger feature), rather than the pty configuration that they're using. I'm not sure if that could make a difference to the way the flow control works.
See: https://en.wikipedia.org/wiki/Copyright_and_Related_Rights_R...
This means you can create a filename in Windows using the character \uF03A, and that character will show up in the WSL shell as a colon. You can even do the same thing with "regular" characters, e.g. using \uF061 instead of "a", and produce a filename that appears to be ASCII in the WSL shell, but is not actually accessible.
The thing is, why should an English speaking person get a warning when they visit a Cyrillic url, but a Russian speaking person doesn't get a warning when visiting a url with Latin characters? Why is apple.com assumed to be legitimate and аррІе.com is considered the fraud?
In fact I'm almost sure that browsers originally used to disable IDNs using some kind of scheme that relied on language preferences back when they first started being used. I suspect they eventually abandoned that approach for this very reason. It only seems like a good idea if you're English speaking (or at least some other Latin-based language).
On the "downside", though, you miss out on the social media sharing buttons, and auto-loading of the next article when you get to the bottom of the page.
Naval vessels are kind of an interesting case though. They also fly the H flag when they have a pilot on board, but when they do so it's in combination with the answering pennant at the top of the hoist. I believe this is a standard practice when communicating with merchant marine vessels to indicate that the signal is based on the ICS rules and not the naval signal book which can mean something completely different. Naval vessels also often display their call sign using these signal flags when arriving and departing from port.
[1] http://uk.businessinsider.com/googles-new-11-storey-office-i...
[1] https://msdn.microsoft.com/en-us/library/aa940293(v=winembed...
For example, it may surprise you to know that http://www.еа.com and http://www.ea.com are two different websites, despite the URLs appearing identical. Edge at least renders the IDN version in its punycode form, but in Firefox and Chrome the URLs are indistinguishable. It's quite possible that's a result of my messing with the IDN settings in the past, though - I'm curious what others see for those links.
The fact that the code was encrypted meant the debugger couldn't disassemble it in any meaningful way, and also made it impossible to set a breakpoint (since the breakpoint would just end up being "decrypted" into some other opcode that would inevitably crash). The debugger also couldn't step through the code, because taking over the single step interrupt would prevent the decrypter from running, so you'd just be stepping through garbage.
The way I worked around this was by writing a debugger that could hook the single step interrupt in such a way that it still forwarded the interrupt onto the previous hook. I still couldn't set breakpoints, but I could step through the code, watching it decode itself as it proceeded.
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=128055
That said, I'm still not a big fan of the new look. I also prefer the apps section at the end rather than mixed in with my employment history.
Definitely not recommended in production. Other than the obvious inefficiency, it was only supported in Chrome fairly recently (even though the CSS escaping rules have remained largely unchanged for 20 years or so). In this case, though, the game itself depended on recent bug fixes in Chrome, so there wasn't much point in worrying about compatibility with older versions.
Also, the exact wording for the office part of the test is "Do programmers have quiet working conditions?" This usually means that working conditions might possibly be quiet if nobody else happened to be in the office at the same time as you. While many claim quiet working conditions, I've never seen one that actually provided private offices.
This is anecdotal of course, and just based on looking at photographs they've included on their website or Stack Overflow page, but every job I've viewed recently appears to have an open plan office. In some of the photos you even see people standing around having impromptu meetings in the middle of a group of desks where others are trying to work.
Remember this is just the companies that are actually claiming to provide programmers with quiet working conditions. I can't imagine what the noisy ones are like.
[1] https://msdn.microsoft.com/en-us/library/windows/desktop/dd3...