So the prize for winning is a $60 hard drive, plus $40? Damn, I don't know why people aren't just jumping all over that!
Also, disassembling the drive is against the rules of the challenge, unless you're a "established data recovery business... or a National government law enforcement or intelligence agency".
The Coup back in 2006 was to remove corrupt Prime Minister Thaksin Shinawatra who has since been indicted for corruption regarding the abuse of his position to get the tax free sale of his families share of SingTel this amounted to roughly 1.4 Billion US dollars
How is that a problem? According to a law passed during his predecessor's administration (Chuan Leekpai), capital gains from stock sales are tax exempt. Whether the transaction was ethical is a question, but not its legality. The Securities and Exchange Commission investigated and didn't find any wrongdoing: "The investigation concluded that Prime Minister Thaksin Shinawatra and his daughter Pinthongta are clear from all wrongdoing"-- http://www.abc.net.au/news/stories/2006/02/23/1577084.htm. I don't know what "abuse of his position" you're referring to--I could sell stock tax-free too (if I had any, that is), and I'm nobody in particular.
BTW, the transaction in question is his sale of his shares of Shin Corp, the company he founded, not SingTel. They were sold to Temasek Holdings, the parent holding company of SingTel.
You got some of the facts of the situation wrong... there's no anti-monarchy sentiment on either side--the clash is between the rich elite in Bangkok who traditionally held political power (and tended to disenfranchise the rural majority) vs. said rural majority.
Summary: the people elected a Prime Minister who gave a lot of aid to the rural poor (mainly at the expense of the rich elite). He was extremely popular, and was actually elected to a second term (unprecedented in Thai history... Thailand hasn't quite gotten the hang of this "democracy" business and tends to depose their elected officials). Well, the rich folk were getting POed about all their money being taken to help the poor, so they protested, and managed to get the army to stage a coup d'etat. After a period of junta rule, they have elections, and the people vote in the current Prime Minister, a guy who has the same policy as his ousted predecessor. The rich folks are now steaming mad that the majority like someone who'll pay attention to their needs, so they protest again. They're now saying that democracy won't work in Thailand, since the rural hicks aren't smart enough to vote: only 30% of parliament should be elected by the people--the other 70% should be appointed (and of course, the rich elite should be the ones doing the appointing). So far, the rich protesters have temporarily taken over a TV station, blockaded and vandalized airports, and are currently occupying the government house (sort of like the White House). In any other country, if a mob took over government offices, the police would go disperse them, but the Thai government is leery about using force, since past governments have had a bad history of killing anti-government protesters--the police can't even use tear gas. After over a week of anti-government protests, a group of rural pro-government protesters arrived, and they got into a fight, with one guy getting shot and killed (last I heard, it was still unclear which side the guy was on, but most news outlets were saying he was on the pro-government side), and numerous others injured.
FWIW, here are a few articles that give more details: article 1 and article 2
Interesting work of fiction you wrote there. But as with all fiction set in real life locations, it would read better if you had gotten some of the facts correct. As many have replied, "Phuket" is not pronounced "fuck it". U-Tapao AFB is not a short boat ride from Phuket either. They're about 650 km (400 miles) apart as the crow flies, but the main problem with getting from U-Tapao to Phuket by boat is that the Isthmus of Kra is in the way. U-Tapao is on the Gulf of Thailand side, and Phuket is on the Andaman Sea side. Satthahip and Ban Chang are to the north of U-Tapao, BTW. The Thai currency is a "baht", not a "bhat". Etc...
Anyway, work on that and the rest of it, and post another revision. Best of luck!
You left out the part of "any item of equipment designed, made, or adapted to manufacture a controlled substance or a controlled substance analogue." This sounds like your standard burglary tools clause, and these are probably not actually illegal in TX on their own.
If intent to manufacture a controlled substance is what makes it illegal, why does TX require a permit to buy/sell/transfer laboratory glassware? And to obtain the permit, you have to allow them to come inspect your home (or wherever you're keeping the glassware) at "any reasonable time".
There are glassware retailers that won't sell to Texans without a permit. For example, this place. Some eBay sellers have the same policy too.
Besides "a filter" is on the list, and it would be laughable to think that everyone who goes to their local big box to buy an AC filter or some cheese cloth is now a criminal.
It actually says "filter funnels", not just any old filter. However, "transformers" are on the restricted list--everyone with any sort of electronic equipment owns dozens of those.
I'm not sure what it would even mean for the hardware to be designed for only one OS. Can you give an example of how a Winmodem is designed only for Windows? In any case, seeing that Winmodems work fine in Linux, a non-Windows OS, whether they're "designed for Windows" or not is irrelevant.
I will try that, but my point was that when finder crashes, these software based right click methods don't work. So I can't right click on finder and force it to restart.
I'm not sure what you're doing that causes finder to crash so often--it's only done so maybe 3 or 4 times in the 8 months I've had my MacBook... but I generally don't have a mouse hooked up and don't remember any issues using the right-click menu to restart the finder. There's also Cmd-Option-Esc to bring up the "Force Quit Applications" window, which will let you restart Finder entirely through keyboard control.
There is an important piece that is going to keep me from being able to use it for a while
Subclipse 1.4.0, which works with Subversion 1.5.0 has been released. TortoiseSVN release candidates that are compatible with SVN 1.5 have been out for a while, and the plan is to release TortoiseSVN 1.5.0 this weekend.
Those (along with the SVN commandline client) are probably the most popular clients, so most people won't need to wait "a while".
Ah, I've heard the arguments against Han unification, and don't particularly agree with them... although perhaps I'm described by the, "... the person is thinking of Chinese usage, which is usually much looser than Japanese" in the page you posted (I'm Chinese, but I know a little Japanese).
In the case of hone, my opinion is that if you use a Japanese font, it'll display the Japanese way (little square in the lower-right of the bigger one); if you use a Chinese font, it'll display the Chinese way (little square in the lower-left). An analog with the Roman character set is the "a" that looks like an ellipse with a vertical bar on the right vs. the "a" where the bar curves up over the top of the ellipse. Or the two main styles of writing "g"--they aren't assigned separate Unicode code points.
More serious is that various kanji forms used in given names are absent or changed; this tends to not go down well with people bearing such names.
However, I'm more intrigued by the part about kanji used in given names, which brings me back to my question about if there's a character in the JIS character set that's not in Unicode... page 418 in the section of the Unicode spec I linked to describes Unicode's Han unification rules, and the first rule is the "Source Separation Rule. If two ideographs are distinct in a primary source standard, then they are not unified." JIS X 0208-1990 and JIS X 0212-1990 are both listed as primary sources. They give an example of the ken in kendou (as in the martial art/sport), meaning "sword". There are 6 variants of that kanji in JIS, and they were not unified in Unicode--the 6 variants are in Unicode too. So it was my understanding that due to Unicode's Source Separation rule, if a Japanese person had an unusual kanji variant in his name that was separately encoded in JIS, it was also available in Unicode. Is that not the case?
The "Personal Names" section of the article you linked mentions, "by 1983 [the kanji that could appear in names] was a subset of the JIS X 0208 character set." and goes on to discuss debate about expanding the list. But what I got out of it is that some people who used exotic kanji had problem with not finding their character in the original Japanese encoding standard; while it may still be a problem in Unicode today, it's not a problem Unicode introduced and using, e.g., ISO 2022 JP doesn't solve the problem.
And I think this paragraph agrees with me... it says the subvariants are not in JIS either:
For an example of missing variants, the name 'watanabe' has often been used. There are three main variants of the second character in this name; one new and two older ones (U+908A and U+9089). The original JIS standard included both older ones. However, the older ones each have several subvariants used by various families, which were not in JIS and are therefore, as far as I know, still not in Unicode. These variants (and many other name variants) can be represented by many products sold in Japan designed specially for representing variant kanji, but there is no standard encoding for such products.
since Unicode is actually somewhat broken for the language (not all needed characters are actually defined). Do you have any more details on that? My understanding was that all characters in traditional/legacy Japanese encodings are included in Unicode (with some exceptions, as mentioned in the standard (PDF warning). Do you have an example of a character encoded in, e.g., ISO-2022-JP, that's not in Unicode?
Do you have any fucking idea how many pieces of information per individual the US demands of all incoming flights to the US? Yeah, 12:
Family Name
First Name
Date of Birth
Country of Citizenship
Sex (Male or Female)
Passport Number
Airline and Flight Number (if applicable)
Country Where You Live -- Lawful Permanent Residence
City Where You Boarded (if applicable)
City Where Visa was Issued (if applicable)
Date Issued (Day/Mo/Yr) (if applicable)
Address While in the United States
Seems identical to the info the other countries I've been to require.
And our crazy-ass, grasping, bastard government requires this even about a passenger flying across US airspace, even if the plane does not land in the US.
Sounds like you're referring to the Secure Flight program, which 1) was never fully in effect; 2) has been suspended until at least 2010, and naturally is getting a lot of resistance from Canada and Mexico; and 3) requires that the airlines send TSA the Passenger Name Record information--much less info than what's on the I-94.
While I do think that Secure Flight is pointless and bad, I see absolutely nothing wrong with the info the US requires for people who are actually entering the country. In any case, you should learn more about the things you rant about.
I've had a hmoe computers as long as there has been a home computer market, and the only virus I have ever had was on an Apple IIc. Some clown created a virus that changed the firmware on the read heads of the disk drive. That was from a circulated disk. Apple ][ disk drives didn't have any firmware, much less firmware in the read heads. I don't see how any disk drive could have firmware in the heads. The Disk ][s are extremely dumb drives, to the point that turning the motor on/off and energizing the stepper motor coils to seek is all done under software control by the computer.
Personally, I haven't heard about any comments being addressed in the MSOOXML spec. I know the
issues from the BRM were flagged to be fixed, but when last I heard we were relying on Microsoft's willingness to do the right thing in order to get them fixed.
While I haven't seen a copy of the final standard that got approved, since I'm sure it'll cost $$$$ like just about every other ISO standard, I have seen the corrections MS proposed in reply to the comments raised by the various national standard bodies. And I seriously doubt MS is going to spend the time to write up documentation for that stuff, then go, "Psyche! This isn't going to go into the standard after all!"
The "Proposed Disposition" tab of this page has documentation on these formerly-undocumented/underdocumented elements: autoSpaceLikeWord95, footnoteLayoutLikeWW8, lineWrapLikeWord6, mwSmallCaps, shapeLayoutLikeWW8, suppressTopSpacingWP, truncateFontHeightsLikeWP6, uiCompat97To2003, useWord2002TableStyleRules, useWord97LineBreakRules, wpJustification, and wpSpaceWidth.
Now, the trouble I have here, (and I say this as man who writes software for a living), is that while I see
reference to an algorithm here, I don't see the algorithm specified.
Um, the algorithm is specified in the documentation for the autoSpaceDE and autoSpaceDN elements. What they're trying to say is that those two elements define spacing behavior for the gap between ideographic (i.e., Chinese/Japanese) text and non-ideographic (English, French, Russian, etc.) text. If the autoSpaceLikeWord95 compatibility setting is on, certain non-ideographic characters should be treated as if they were ideographic for the spacing algorithm's purposes, and vice versa.
As everyone on/. likes to say, the OOXML spec is 6000+ pages long. You're not going to get enough detail to implement the spec in a couple of paragraphs. My point was that all the undocumented "do such-and-such like some obsolete version of Word" that everyone points out as an example of how horrible the standard is have since been documented since those objections were raised. I wasn't trying to give you enough information to implement OOXML in a/. post.
For you and prockcore, stuff like (somebody correct me if I am wrong):
FormatLikeWord95
AutospaceLikeWord97
Well, how DOES Word 95 format stuff? And how does Word97 format stuff?... A standard is supposed to eliminate the need for one segment of a market to reverse engineer another segment, by specifying EXACTLY how everything should work, down to the minutest detail (like formatting). The things you mention were problems in the early drafts that were submitted. MS agreed that a detailed spec of exactly what those means is needed, and provided such a spec. So you're complaining about stuff that has been fixed already.
FYI:
2.15.3.6 autoSpaceLikeWord95 (Incorrectly Adjust Text Spacing for Specific Unicode Ranges)
This element specifies adjustments (detailed below) which should be applied to the spacing between adjoining regions of non-ideographic and ideographic text when the autoSpaceDE (Â2.3.1.2) and autoSpaceDN (Â2.3.13) elements have a value of true (or equivalent). This algorithm typically results in the following:
An increase in the inter-character spacing added between non-ideographic and/or number characters and certain full-width characters
No inter-character spacing between non-ideographic and/or number characters and certain half-width characters
Typically, applications apply additional spacing between ideographic and non-ideographic characters/numeric characters when the autoSpaceDE / autoSpaceDN properties are applied. This element, when present with a val attribute value of true (or equivalent), specifies that applications shall apply the following adjustments to this logic:
Characters in the following Unicode ranges should be treated as ideographic, even though those characters are full-width forms of non-ideographic text: U+FF10-U+FF19, U+FF21-U+FF3A, and U+FF41-U+FF5A. [Note: This results in the unnecessary addition of space. end note]
Characters in the following Unicode ranges should be treated as non-ideographic, even though those characters are ideographic: U+FF66-U+FF9F. [Note: This results in the omission of the intended additional space. end note]
[Example: Consider a WordprocessingML document with two paragraphs containing a mix of East Asian and Latin characters:
<w:p> <w:r> <w:t>ab</w:t> </w:r> <w:r> <w:t></w:t> </w:r> <w:r> <w:t></w:t> </w:r> <w:r> <w:t>cd</w:t> </w:r> </w:p> <w:p> <w:r> <w:t>ab</w:t> </w:r> <w:r> <w:t></w:t> </w:r> <w:r> <w:t></w:t> </w:r> <w:r> <w:t>cd</w:t> </w:r> </w:p>
The first paragraph contains characters with Unicode value U+FF66 (). The second paragraph contains characters with Unicode value U+FF12 (). If autoSpaceDE is true , spacing is added in the first paragraph (between the ideographs and the non-ideographic characters), but not in the second (all four characters are not ideographs):
If this compatibility setting is turned on:
<w:compat> <w:autoSpaceLikeWord95/> </w:compat>
Then, although it appears incorrect, applications should not add space in the first paragraph and should apply it in the second: end example]
Yes, exactly, so to say that the LCD only can display 766 colors you have to ignore the fundamental nature of color and human vision. The three colored subpixels correspond to the three color receptors in our eyes. Would say that we can only see red, green, and blue? You can't have it both ways. Either both RGB subpixels and pixel-level dithering only allow the display to display some small number of colors, or they both allow it to display millions of colors. Combining RGB subpixels to form other colors is pixel-level dithering.
I mean take the color brown. There is no "wavelength" for brown. So you must claim that either the color "brown" doesn't exist, or you acknowledge that color is necessarily about a combination of components, and thus the argument that the LCD is "only" displaying shades of red, blue, and green becomes nonsensical. Reddish-orange light (around 600nm) at a low intensity looks brown, but that's beside the point. I have nothing against composite colors. You, however, pick and choose when composites are OK, and when they're not. A red spot of light next to a green spot to make something that looks yellow? No problem--that's how vision works! But a yellow spot next to a slightly different shade of yellow spot to make something that looks like a shade of yellow in between? Evil dithering! It sux0rs!
A pixel with its green subpixel fully on, its blue subpixel fully on, and its red subpixel off is displaying cyan for any meaningful definition of the term. There is no way to "generate" cyan without using a combination of green and blue, so saying that the LCD can't display cyan because it can only display green and blue is laughably foolish. How do you figure there's no way to generate cyan without using a combination of green and blue? Try light with a wavelength of about 490nm.
Nope, despite your attempts, I can still see that you still don't grasp what that guy was saying. His point was that all LCD panels use pixel-level dithering. While it may be sub-optimal to put another level of dithering above that, it certainly doesn't warrant the "OMG horrible!" reaction that some, such as you, display.
You're hilariously wrong. When you get down to it, an LCD panel with 8 bits each of R, G, and B can display these colors:
black (one color)
red at intensities of 1 through 255 (255 colors)
green at intensities of 1 through 255 (255 colors)
blue at intensities of 1 through 255 (255 colors)
for a total of 1 + 255 + 255 + 255 = 766 colors. However, human eyesight blurs the individual red, green, and blue dots together to give the impression of more than 766 colors. And that's what matters--what you actually see, not what's being generated by the display. In the same way, a display that only has 6 bits per channel color resolution, but can use pulse width modulation to quickly flip between two intensities will give the impression of being able to display more intensity levels. Which is the entire point of the guy's post. But good job missing it while simultaneously trying to pretend that you're the smart one.
I'll give you one major downside... no disk platters, no data recovery. Want to undelete some files you accidentally deleted before you overwrite the data sectors? Bzzt... SSHD makes that impossible.
Recovering files before the data sectors are overwritten can be done using software only, and doesn't require access to disk platters. When you delete a file, the blocks that were used by the file are marked as free. To recover the data, just read those blocks back (finding which blocks those are is left as an exercise for the reader).
Now, if you want to undelete some files you accidentally deleted after you've already overwritten the data sectors, then supposedly, with magnetic media, a trace of the previous data is left and can be recovered. I have no idea if there are any techniques that could do the same for a SSHD.
Depends; does the woman they're giving up sex with look like the young one or the old one on Are You Being Served? I, for one, would be delighted to keep an eye on Mrs. Slocombe's pussy.
Slashdot Mirror
Try searching for meowchat instead.
Japanese for "no" is iie (pronounced e-a).
iie is three mora (basically the Japanese equivalent to what syllable would be in English).
So the prize for winning is a $60 hard drive, plus $40? Damn, I don't know why people aren't just jumping all over that!
Also, disassembling the drive is against the rules of the challenge, unless you're a "established data recovery business ... or a National government law enforcement or intelligence agency".
This "challenge" is stupid.
The Coup back in 2006 was to remove corrupt Prime Minister Thaksin Shinawatra who has since been indicted for corruption regarding the abuse of his position to get the tax free sale of his families share of SingTel this amounted to roughly 1.4 Billion US dollars
How is that a problem? According to a law passed during his predecessor's administration (Chuan Leekpai), capital gains from stock sales are tax exempt. Whether the transaction was ethical is a question, but not its legality. The Securities and Exchange Commission investigated and didn't find any wrongdoing: "The investigation concluded that Prime Minister Thaksin Shinawatra and his daughter Pinthongta are clear from all wrongdoing"-- http://www.abc.net.au/news/stories/2006/02/23/1577084.htm. I don't know what "abuse of his position" you're referring to--I could sell stock tax-free too (if I had any, that is), and I'm nobody in particular.
BTW, the transaction in question is his sale of his shares of Shin Corp, the company he founded, not SingTel. They were sold to Temasek Holdings, the parent holding company of SingTel.
You got some of the facts of the situation wrong... there's no anti-monarchy sentiment on either side--the clash is between the rich elite in Bangkok who traditionally held political power (and tended to disenfranchise the rural majority) vs. said rural majority.
Summary: the people elected a Prime Minister who gave a lot of aid to the rural poor (mainly at the expense of the rich elite). He was extremely popular, and was actually elected to a second term (unprecedented in Thai history... Thailand hasn't quite gotten the hang of this "democracy" business and tends to depose their elected officials). Well, the rich folk were getting POed about all their money being taken to help the poor, so they protested, and managed to get the army to stage a coup d'etat. After a period of junta rule, they have elections, and the people vote in the current Prime Minister, a guy who has the same policy as his ousted predecessor. The rich folks are now steaming mad that the majority like someone who'll pay attention to their needs, so they protest again. They're now saying that democracy won't work in Thailand, since the rural hicks aren't smart enough to vote: only 30% of parliament should be elected by the people--the other 70% should be appointed (and of course, the rich elite should be the ones doing the appointing). So far, the rich protesters have temporarily taken over a TV station, blockaded and vandalized airports, and are currently occupying the government house (sort of like the White House). In any other country, if a mob took over government offices, the police would go disperse them, but the Thai government is leery about using force, since past governments have had a bad history of killing anti-government protesters--the police can't even use tear gas. After over a week of anti-government protests, a group of rural pro-government protesters arrived, and they got into a fight, with one guy getting shot and killed (last I heard, it was still unclear which side the guy was on, but most news outlets were saying he was on the pro-government side), and numerous others injured.
FWIW, here are a few articles that give more details: article 1 and article 2
Interesting work of fiction you wrote there. But as with all fiction set in real life locations, it would read better if you had gotten some of the facts correct. As many have replied, "Phuket" is not pronounced "fuck it". U-Tapao AFB is not a short boat ride from Phuket either. They're about 650 km (400 miles) apart as the crow flies, but the main problem with getting from U-Tapao to Phuket by boat is that the Isthmus of Kra is in the way. U-Tapao is on the Gulf of Thailand side, and Phuket is on the Andaman Sea side. Satthahip and Ban Chang are to the north of U-Tapao, BTW. The Thai currency is a "baht", not a "bhat". Etc...
Anyway, work on that and the rest of it, and post another revision. Best of luck!
And yet they have a shelf full of beakers, test tubes and flasks at Fry's
Beakers and test tubes aren't on The List. Neither are flasks in general--only certain (very common) types.
You left out the part of "any item of equipment designed, made, or adapted to manufacture a controlled substance or a controlled substance analogue." This sounds like your standard burglary tools clause, and these are probably not actually illegal in TX on their own.
If intent to manufacture a controlled substance is what makes it illegal, why does TX require a permit to buy/sell/transfer laboratory glassware? And to obtain the permit, you have to allow them to come inspect your home (or wherever you're keeping the glassware) at "any reasonable time".
There are glassware retailers that won't sell to Texans without a permit. For example, this place. Some eBay sellers have the same policy too.
Besides "a filter" is on the list, and it would be laughable to think that everyone who goes to their local big box to buy an AC filter or some cheese cloth is now a criminal.
It actually says "filter funnels", not just any old filter. However, "transformers" are on the restricted list--everyone with any sort of electronic equipment owns dozens of those.
I'm not sure what it would even mean for the hardware to be designed for only one OS. Can you give an example of how a Winmodem is designed only for Windows? In any case, seeing that Winmodems work fine in Linux, a non-Windows OS, whether they're "designed for Windows" or not is irrelevant.
I will try that, but my point was that when finder crashes, these software based right click methods don't work. So I can't right click on finder and force it to restart.
I'm not sure what you're doing that causes finder to crash so often--it's only done so maybe 3 or 4 times in the 8 months I've had my MacBook... but I generally don't have a mouse hooked up and don't remember any issues using the right-click menu to restart the finder. There's also Cmd-Option-Esc to bring up the "Force Quit Applications" window, which will let you restart Finder entirely through keyboard control.
I don't think grep is installed on Windows systems by default.
And I don't think FINDSTR.EXE is installed on Linux by default.
Subclipse 1.4.0, which works with Subversion 1.5.0 has been released. TortoiseSVN release candidates that are compatible with SVN 1.5 have been out for a while, and the plan is to release TortoiseSVN 1.5.0 this weekend.
Those (along with the SVN commandline client) are probably the most popular clients, so most people won't need to wait "a while".
Ah, I've heard the arguments against Han unification, and don't particularly agree with them... although perhaps I'm described by the, "... the person is thinking of Chinese usage, which is usually much looser than Japanese" in the page you posted (I'm Chinese, but I know a little Japanese).
In the case of hone, my opinion is that if you use a Japanese font, it'll display the Japanese way (little square in the lower-right of the bigger one); if you use a Chinese font, it'll display the Chinese way (little square in the lower-left). An analog with the Roman character set is the "a" that looks like an ellipse with a vertical bar on the right vs. the "a" where the bar curves up over the top of the ellipse. Or the two main styles of writing "g"--they aren't assigned separate Unicode code points.
More serious is that various kanji forms used in given names are absent or changed; this tends to not go down well with people bearing such names.However, I'm more intrigued by the part about kanji used in given names, which brings me back to my question about if there's a character in the JIS character set that's not in Unicode... page 418 in the section of the Unicode spec I linked to describes Unicode's Han unification rules, and the first rule is the "Source Separation Rule. If two ideographs are distinct in a primary source standard, then they are not unified." JIS X 0208-1990 and JIS X 0212-1990 are both listed as primary sources. They give an example of the ken in kendou (as in the martial art/sport), meaning "sword". There are 6 variants of that kanji in JIS, and they were not unified in Unicode--the 6 variants are in Unicode too. So it was my understanding that due to Unicode's Source Separation rule, if a Japanese person had an unusual kanji variant in his name that was separately encoded in JIS, it was also available in Unicode. Is that not the case?
The "Personal Names" section of the article you linked mentions, "by 1983 [the kanji that could appear in names] was a subset of the JIS X 0208 character set." and goes on to discuss debate about expanding the list. But what I got out of it is that some people who used exotic kanji had problem with not finding their character in the original Japanese encoding standard; while it may still be a problem in Unicode today, it's not a problem Unicode introduced and using, e.g., ISO 2022 JP doesn't solve the problem.
And I think this paragraph agrees with me... it says the subvariants are not in JIS either:
- Family Name
- First Name
- Date of Birth
- Country of Citizenship
- Sex (Male or Female)
- Passport Number
- Airline and Flight Number (if applicable)
- Country Where You Live -- Lawful Permanent Residence
- City Where You Boarded (if applicable)
- City Where Visa was Issued (if applicable)
- Date Issued (Day/Mo/Yr) (if applicable)
- Address While in the United States
Seems identical to the info the other countries I've been to require. And our crazy-ass, grasping, bastard government requires this even about a passenger flying across US airspace, even if the plane does not land in the US.Sounds like you're referring to the Secure Flight program, which 1) was never fully in effect; 2) has been suspended until at least 2010, and naturally is getting a lot of resistance from Canada and Mexico; and 3) requires that the airlines send TSA the Passenger Name Record information--much less info than what's on the I-94.
While I do think that Secure Flight is pointless and bad, I see absolutely nothing wrong with the info the US requires for people who are actually entering the country. In any case, you should learn more about the things you rant about.
While I haven't seen a copy of the final standard that got approved, since I'm sure it'll cost $$$$ like just about every other ISO standard, I have seen the corrections MS proposed in reply to the comments raised by the various national standard bodies. And I seriously doubt MS is going to spend the time to write up documentation for that stuff, then go, "Psyche! This isn't going to go into the standard after all!"
The "Proposed Disposition" tab of this page has documentation on these formerly-undocumented/underdocumented elements: autoSpaceLikeWord95, footnoteLayoutLikeWW8, lineWrapLikeWord6, mwSmallCaps, shapeLayoutLikeWW8, suppressTopSpacingWP, truncateFontHeightsLikeWP6, uiCompat97To2003, useWord2002TableStyleRules, useWord97LineBreakRules, wpJustification, and wpSpaceWidth.
Um, the algorithm is specified in the documentation for the autoSpaceDE and autoSpaceDN elements. What they're trying to say is that those two elements define spacing behavior for the gap between ideographic (i.e., Chinese/Japanese) text and non-ideographic (English, French, Russian, etc.) text. If the autoSpaceLikeWord95 compatibility setting is on, certain non-ideographic characters should be treated as if they were ideographic for the spacing algorithm's purposes, and vice versa.
As everyone on /. likes to say, the OOXML spec is 6000+ pages long. You're not going to get enough detail to implement the spec in a couple of paragraphs. My point was that all the undocumented "do such-and-such like some obsolete version of Word" that everyone points out as an example of how horrible the standard is have since been documented since those objections were raised. I wasn't trying to give you enough information to implement OOXML in a /. post.
P.S. Here you go. 488nm laser. Monochromatic coherent cyan light. You fail it.
Nope, despite your attempts, I can still see that you still don't grasp what that guy was saying. His point was that all LCD panels use pixel-level dithering. While it may be sub-optimal to put another level of dithering above that, it certainly doesn't warrant the "OMG horrible!" reaction that some, such as you, display.
Sure, you can say it's capable of displaying billions of colors and has a resolution of 1x1 (and that the minimum viewing distance is 100 yards).
- black (one color)
- red at intensities of 1 through 255 (255 colors)
- green at intensities of 1 through 255 (255 colors)
- blue at intensities of 1 through 255 (255 colors)
for a total of 1 + 255 + 255 + 255 = 766 colors. However, human eyesight blurs the individual red, green, and blue dots together to give the impression of more than 766 colors. And that's what matters--what you actually see, not what's being generated by the display. In the same way, a display that only has 6 bits per channel color resolution, but can use pulse width modulation to quickly flip between two intensities will give the impression of being able to display more intensity levels. Which is the entire point of the guy's post. But good job missing it while simultaneously trying to pretend that you're the smart one.Recovering files before the data sectors are overwritten can be done using software only, and doesn't require access to disk platters. When you delete a file, the blocks that were used by the file are marked as free. To recover the data, just read those blocks back (finding which blocks those are is left as an exercise for the reader).
Now, if you want to undelete some files you accidentally deleted after you've already overwritten the data sectors, then supposedly, with magnetic media, a trace of the previous data is left and can be recovered. I have no idea if there are any techniques that could do the same for a SSHD.