1) Due apparently to time constraints, the multithreading API was not included in Palm OS 5. It is scheduled to be in OS 5.5, which will include a slew of other new stuff too. Remember, a lot of the Palm OS 5 guys worked at Apple and had first-hand knowledge of the ship-date-that-never-came of Apple's Copeland OS. So they were anxious to get something out the door already.
2) Your information about the Treo is wrong. You can use the phone while using another app. In fact, Handspring's ads expressly mention this as a feature of the device. How does it do this without multitasking/threading? The Treo hands phone conversation processing over to another chip, leaving the main processor free for other things.
The task goal is to produce a working two-way prototype from each of four teams by the end of 18-months. The languages that will be translated are English and Godless Terrorist.
Incorrect, and unfair. Many of the "Northern Alliance" spoke Pashto and/or Dari (which is a dialect of Farsi). Uzbekistan let us use their military bases during the invasion of Afghanistan. And several of our allies, both real and on paper, speak Arabic.
This is not a "English vs. Godless Terrorist" issue, as you say. The simple fact is there is a dearth of US military personnel that speak these languages, and we have an urgent need, now more than ever, to communicate with people who speak these languages. We do indeed have to spy on our enemies that speak in these tongues, but we also have to accurately share information and intelligence with our allies.
If you think $220 is pricey, and the HandEra 330 too expensive at $300 (MSRP; it's widely available for less), then there's no way you're going to be able to afford a $499 Sharp Zaurus SL-5500 plus the extra cost of an 802.11 wireless card. Or any of the Pocket PCs for that matter, which can run from the $400 range up through almost $700.
If you want wireless LAN connectivity on the cheap, the HandEra is the cheapest (and one of the best) solutions out there. In addition to a well-designed device, they have great service and support. And frankly, if you don't like the HandEra, your only other option is to spend lots more money.
I use iSilo and iSiloX to grab all kinds of web sites for offline reading. I also use iSilo as a general Palm DOC reader. Sure, it's closed source and not free (<$20), but for my money it's the best doc reader for Palm OS available.
Yuck, the grammar in this message is horrible. I can't believe a VP of a multi-billion dollar corporation sent out a business communique with so many grammar mistakes. Did he not take a business writing class in college (or English in high school, for that matter)? If his grammar were any worse I would expect him to write for Slashdot, not Microsoft.
OK, I'm poking fun, sure, but if I owned a multi-billion dollar software company, I wouldn't want such drivel being sent out with my company's logo on it. My grammar is not perfect, but I'm not writing business correspondence. I'm posting on Slashdot, not publishing a message to employees and business partners to make them feel good about working for my company and supporting our products.
This is great news considering OpenMail was the only serious Unix-based competitor to Microsoft Exchange.
Except of course for Lotus Domino, which thousands of corporations run quite happily on Solaris, Linux, and all IBM servers (AIX, OS/400, OS/390).
I personally hate Domino (and Exchange), but saying that OpenMail is the only serious competitor to Exchange when there are so many Domino and Notes users is incorrect.
Though a little short on info, the US Navy's Fact File on the Sea Shadow is here.
A little off-topic, but the US Navy Fact File site contains info on all kinds of Navy military hardware. If you hear about a ship in the news, like the Enterprise, the Carl Vinson, or the Peleliu, you can find out more information (and links to most of the ships' web sites) there.
Actually, the correct formula for determining whether a Star Trek movie is good or bad was flushed out by Brunching Shuttlecocks in their review of Insurrection. Obviously, it's too long to repost here, but is highly accurate (or at least will at least make you smile).
A couple of years ago, there were 250,000 AS/400s in service. That market isn't growing, but it's probably not contracting, since those customers are a hidebound bunch. I seem to remember that average AS/400/iSeries customers spend $100,000 or more on their machines.
I have no actual sales numbers on System 390/zSeries servers, but I seem to remember most customers spending at least $1 million for each of those.
Between the iSeries and zSeries customers, we're talking about customers who have enough cash to pay extra for support and services. And I know these customers most often pony up extra for IBM support services anyway, so it probably won't be such a big deal for RedHat to get a nice piece of that pie.
Palm has no interest in continuing to develop either BeOS or BeIA. Palm's sole interest at this point putting together an ARM-based Palm OS that can compete with Windows CE, both at the high PocketPC end and at lower mobile phone end. Palm wants BeOS engineers and any Be intellectual property that could be useful to Palm OS; Palm cares nothing for BeOS itself, and have no plans to either develop it or release new versions.
Take a look at the initial Palm press release of the buyout here. BeOS and BeIA are never mentioned. Probably the most succinct quote is from now former CEO "you are the weakest link, goodbye" Carl Yankowski:
The technology and people from Be are highly regarded," said Carl Yankowski, Palm chief executive officer. "We look forward to them joining forces with our own outstanding engineers on future versions of the Palm OS. This move will help us expand the PalmOS platform into broader markets using their multimedia media and Internet expertise.
Again, the engineering team is the focus for Palm; BeOS isn't mentioned.
I admit I'm a bit sad to see BeOS go, as it was an amazing desktop operating system that deserved better than the market gave it. But I don't think the public should hold out hope that Palm will continue to develop BeOS. Palm is in a fight for its life. It bought Be because it needed engineers with expertise in multimedia and Internet applications to fill in Palm OS's large gaps. Palm did not buy Be to expand into an unrelated market segment.
Actually, they don't want BeIA either. Palm's interest is Be's engineering staff and intellectual property to bulk up the multimedia and certain other pieces in ARM-based Palm OS 5.
Re:I'd have a hard time taking this book seriously
on
God's Debris
·
· Score: 1
I disagree about taking a book on philosophy by Charles Schultz seriously. Peanuts often incorporated thoughts about existence, the universe, mankind, and God. Presenting these profound thoughts and musings through the eyes of children made them all the more profound. He had a wonderful ability to present philosophical ideas in a way accessible to the common man. Charles Schultz was a man with a talent we may not see again in this lifetime.
I would not read a book on philosophy written by Stan Lee, but I might read a book where he talks about youth culture, since his work seems to have had such an impact there. I would have no respect for anything written by either OJ Simpson or Tonya Harding unless it was titled Yeah, OK, I Killed Them or Of Course I Told Whathisface to Wack Her Knee, respectively. And even then, I would not actually read them. Schulz is not in the same league as the others.
Why does the department of justice keep insisting that things are dealt with quickly?
I think the short answer is the current Administration never liked the case to begin with, and they're now using the war against terrorism as an excuse to get rid of it. Which, as you point out, is unfortunate, since the DOJ won the case.
Some penalties I'd like to see:
1. Require open standards. No more proprietary protocols or file formats. All have to be published by the time Microsoft releases a product to the public.
2. Divest MSN, and X-Box divisions.
I personally can't agree more strongly with these. M$'s proprietary protocols (and proprietary extensions to otherwise open protocols) are its primary weapons against anyone effectively interoperating with MS-powered servers and clients. If everyone can see how MS protocols operate, there's much less of a chance MS could leverage their domination of the client world into a stranglehold in the server world, especially in the Internet server space. Of course, one could argue MS could just continue to implement its newly-open protocols poorly (ie SMB), thus locking out specification-compatible 3rd party software. And that's where the second provision comes in: If Microsoft did find a way around having completely open protocols, their exploitation of the loophole would still be hindered by their inability to operate an online service. Remember, one of the primary goals of.NET and Hailstorm is to make the lion's share of Internet users do their online business through Microsoft. If Microsoft could not operate an online service, they would be prevented from using.NET protocols and services to force people to use Microsoft products to do business over the Internet.
Yes, Novell realized back in the early 1990s that NetWare on its own could not continue to defend itself from the onslaught of Windows NT. Noorda's answer: buy UNIX from AT&T, and turn out a version of UNIX that could easily integrate into existing NetWare shops as an application server (which NetWare just couldn't do reliably).
The result, UnixWare, flopped horribly.
UnixWare 1.0 demonstrated that Novell didn't know anything about Unix. After a somewhat improved 2.0 release, Novell finally sold it and Unix Systems Labs to SCO.
SCO did their best with UnixWare and OpenServer, but Linux and Windows started eating into their already small market big time. So their solution was to throw in the towel: sell it all to Caldera, including OpenServer, and hope they could do something with it.
Caldera is probably the best thing that as happened to UNIX since it left AT&T. Unlike Novell, Caldera understands what it can do. Unlike SCO, Caldera understands where it needs to go in the future.
Incidentally, though I don't remember the exact order of events, Noorda's interest in *nix on x86 was the reason for his (rather, The Canopy Group's) funding of Caldera in the first place.
Anyone reading the plane English of this license cannot help but see that, very clearly, the end user is required to grant Microsoft any and every right to their ideas, their work, even their patents, just by processing their information through a piece of software which happens to use Passport as an authentication mechanism. This could, in the future, include any document written by Micosoft Word (using passport to authenticate the author or encrypt the file as a new feature, etc.), sent through a Microsoft mail server, or served from a Microsoft Web server.
It was my understanding one of the new "features" of Windows XP was to pass your username/password entered in the initial user logon box to MS Passport-enabled sites to provide seemless logon to M$ services.
This sounds alarmist, but especially considering Microsoft's well-publicized refocus on.NET and so-called "services," they could consider Windows XP merely a "Passport-associated service," thus meaning anything created/residing on your PC would belong to them, and they would have every right to download any data from your PC as they wished.
They wouldn't do that, would they? As much as I hate Microsoft, even I can't believe they'd do something like this. Someone please convince me I'm wrong...
(historical tip: if they were going to, it was more likely to be German than English).
Yeah, and supposedly one of the presidents of the Continental Congress under the Articles of Confederation asked the King of Prussia to step in and become monarch. That one didn't fly, either.
Hmm, now that I think about it, I seriously doubt an inanimate carbon rod would do things like:
sign the Communications Decency Act into law
sign the CDA II act into law
sign COPA into law
So far, sounds like an improvement. OTOH, inanimate carbon rods could still leave stains on blue dresses, but hey, that's not that big of a deal considering all the things an inanimate carbon rod wouldn't do!
Now, if we can only find an inanimate carbon rod that will actually run....
This is to try and stop people minimising their tax liabilities by keeping their savings hidden in overseas banks in countries with strong banking privacy laws - like Luxembourg. Luxembourg makes it quite easy for people in Germany, Holland, Belgium etc to open accounts and move their savings there, therefore avoiding paying tax on interest or capital gains.
Oh well, then by all means, the need to do something! God forbid that someone would dare try to actually keep some money they saved!
On a serious note, though, thanks for the clarification on this. It still seems a bit troubling to me, but insight is always a good thing.
To summarize, most of the EU nations want to trade private citizens' income information (specifically, income from savings accounts). Of course, not only do they want to just trade this info amongst themselves, some of the EU governments want to hammer out agreements with 3rd party nations (read: US and Canada) so they can do the same with them. Frankly, I'm a US citizen, and I don't believe France, Germany, or even Luxembourg should have any access to any of my income information if none of my income was in their country. I really do not think a group so gung-ho about having access to private citizens' (of other countries) personal information is really that concerned with privacy at all!
1) As I think several people have touched on, the problem here isn't the documentation, since Microsoft through MSDN etc. has documented the Word file format. The problem is that the only specifications on how to correctly render the Word documents are the Word rendering engine itself. Without the ability to see the exact logic that Word uses to render certain formatting codes (read: source code), it is impossible to reverse-engineer a 100%-compatible converter/viewer. It is a similar situation to what the Samba team faces: the SMB/CIFS protocols have been documented by Microsoft, but the only implementation of those protocols is Windows NT/2000, so Samba in reality must be coded to re-implement NT, not implement the CIFS specifications. The difference here, of course, is that CIFS apparently has a complete spec that Microsoft simply ignores, rather than the Word situation where they purposefully keep people in the dark on how things should be done.
2) the reason that you can't just watch what the Word rendering engine does and duplicate it is because it's stupid. From my experience working with Word itself and wvWare to convert Word files to HTML, it's obvious that Word just throws odd formatting codes where ever it pleases, and never bothers to clean them up. Often tags to end bold formatting (converted to </b> by wvWare) are just randomly placed in the document, nowhere near where any bolding is supposed to occur. The same goes for font sizing/coloring: Word seems to place odd, irrelevant font codes in places, only to override them with the correct codes a few lines later (often without canceling the first codes). In other words, it's a mess. With the Word source code, one may be able to figure out the (supposed) logic behind the mess; without it, I fear anyone is simply grasping at straws, especially since MS continuously changes to Office keeps everyone guessing about what Word is actually doing underneath it all.
Slashdot Mirror
1) Due apparently to time constraints, the multithreading API was not included in Palm OS 5. It is scheduled to be in OS 5.5, which will include a slew of other new stuff too. Remember, a lot of the Palm OS 5 guys worked at Apple and had first-hand knowledge of the ship-date-that-never-came of Apple's Copeland OS. So they were anxious to get something out the door already.
2) Your information about the Treo is wrong. You can use the phone while using another app. In fact, Handspring's ads expressly mention this as a feature of the device. How does it do this without multitasking/threading? The Treo hands phone conversation processing over to another chip, leaving the main processor free for other things.
The task goal is to produce a working two-way prototype from each of four teams by the end of 18-months. The languages that will be translated are English and Godless Terrorist.
Incorrect, and unfair. Many of the "Northern Alliance" spoke Pashto and/or Dari (which is a dialect of Farsi). Uzbekistan let us use their military bases during the invasion of Afghanistan. And several of our allies, both real and on paper, speak Arabic.
This is not a "English vs. Godless Terrorist" issue, as you say. The simple fact is there is a dearth of US military personnel that speak these languages, and we have an urgent need, now more than ever, to communicate with people who speak these languages. We do indeed have to spy on our enemies that speak in these tongues, but we also have to accurately share information and intelligence with our allies.
If you think $220 is pricey, and the HandEra 330 too expensive at $300 (MSRP; it's widely available for less), then there's no way you're going to be able to afford a $499 Sharp Zaurus SL-5500 plus the extra cost of an 802.11 wireless card. Or any of the Pocket PCs for that matter, which can run from the $400 range up through almost $700.
If you want wireless LAN connectivity on the cheap, the HandEra is the cheapest (and one of the best) solutions out there. In addition to a well-designed device, they have great service and support. And frankly, if you don't like the HandEra, your only other option is to spend lots more money.
Because of a lack of cash flow, my company decided to lay off half of us, then lay off the other half a month later and shut the doors.
Yeah, pay cuts suck, but just be glad you still have a job.
I use iSilo and iSiloX to grab all kinds of web sites for offline reading. I also use iSilo as a general Palm DOC reader. Sure, it's closed source and not free (<$20), but for my money it's the best doc reader for Palm OS available.
Congratulations to you both!
Yuck, the grammar in this message is horrible. I can't believe a VP of a multi-billion dollar corporation sent out a business communique with so many grammar mistakes. Did he not take a business writing class in college (or English in high school, for that matter)? If his grammar were any worse I would expect him to write for Slashdot, not Microsoft.
OK, I'm poking fun, sure, but if I owned a multi-billion dollar software company, I wouldn't want such drivel being sent out with my company's logo on it. My grammar is not perfect, but I'm not writing business correspondence. I'm posting on Slashdot, not publishing a message to employees and business partners to make them feel good about working for my company and supporting our products.
This is great news considering OpenMail was the only serious Unix-based competitor to Microsoft Exchange.
Except of course for Lotus Domino, which thousands of corporations run quite happily on Solaris, Linux, and all IBM servers (AIX, OS/400, OS/390).
I personally hate Domino (and Exchange), but saying that OpenMail is the only serious competitor to Exchange when there are so many Domino and Notes users is incorrect.
Though a little short on info, the US Navy's Fact File on the Sea Shadow is here.
A little off-topic, but the US Navy Fact File site contains info on all kinds of Navy military hardware. If you hear about a ship in the news, like the Enterprise, the Carl Vinson, or the Peleliu, you can find out more information (and links to most of the ships' web sites) there.
Actually, the correct formula for determining whether a Star Trek movie is good or bad was flushed out by Brunching Shuttlecocks in their review of Insurrection. Obviously, it's too long to repost here, but is highly accurate (or at least will at least make you smile).
A couple of years ago, there were 250,000 AS/400s in service. That market isn't growing, but it's probably not contracting, since those customers are a hidebound bunch. I seem to remember that average AS/400/iSeries customers spend $100,000 or more on their machines.
I have no actual sales numbers on System 390/zSeries servers, but I seem to remember most customers spending at least $1 million for each of those.
Between the iSeries and zSeries customers, we're talking about customers who have enough cash to pay extra for support and services. And I know these customers most often pony up extra for IBM support services anyway, so it probably won't be such a big deal for RedHat to get a nice piece of that pie.
For those of us still not comfortable with IBM's new eServer marketspeak, here's a simple conversion chart:
eServer Name == Real Name
iSeries == AS/400
pSeries == RS/6000
xSeries == Netfinity/PC server
zSeries == System/390 mainframe
Take a look at the initial Palm press release of the buyout here. BeOS and BeIA are never mentioned. Probably the most succinct quote is from now former CEO "you are the weakest link, goodbye" Carl Yankowski:
- The technology and people from Be are highly regarded," said Carl Yankowski, Palm chief executive officer. "We look forward to them joining forces with our own outstanding engineers on future versions of the Palm OS. This move will help us expand the PalmOS platform into broader markets using their multimedia media and Internet expertise.
Again, the engineering team is the focus for Palm; BeOS isn't mentioned.I admit I'm a bit sad to see BeOS go, as it was an amazing desktop operating system that deserved better than the market gave it. But I don't think the public should hold out hope that Palm will continue to develop BeOS. Palm is in a fight for its life. It bought Be because it needed engineers with expertise in multimedia and Internet applications to fill in Palm OS's large gaps. Palm did not buy Be to expand into an unrelated market segment.
Actually, they don't want BeIA either. Palm's interest is Be's engineering staff and intellectual property to bulk up the multimedia and certain other pieces in ARM-based Palm OS 5.
I disagree about taking a book on philosophy by Charles Schultz seriously. Peanuts often incorporated thoughts about existence, the universe, mankind, and God. Presenting these profound thoughts and musings through the eyes of children made them all the more profound. He had a wonderful ability to present philosophical ideas in a way accessible to the common man. Charles Schultz was a man with a talent we may not see again in this lifetime.
I would not read a book on philosophy written by Stan Lee, but I might read a book where he talks about youth culture, since his work seems to have had such an impact there. I would have no respect for anything written by either OJ Simpson or Tonya Harding unless it was titled Yeah, OK, I Killed Them or Of Course I Told Whathisface to Wack Her Knee, respectively. And even then, I would not actually read them. Schulz is not in the same league as the others.
Why does the department of justice keep insisting that things are dealt with quickly?
I think the short answer is the current Administration never liked the case to begin with, and they're now using the war against terrorism as an excuse to get rid of it. Which, as you point out, is unfortunate, since the DOJ won the case.
Some penalties I'd like to see:
.NET and Hailstorm is to make the lion's share of Internet users do their online business through Microsoft. If Microsoft could not operate an online service, they would be prevented from using .NET protocols and services to force people to use Microsoft products to do business over the Internet.
1. Require open standards. No more proprietary protocols or file formats. All have to be published by the time Microsoft releases a product to the public.
2. Divest MSN, and X-Box divisions.
I personally can't agree more strongly with these. M$'s proprietary protocols (and proprietary extensions to otherwise open protocols) are its primary weapons against anyone effectively interoperating with MS-powered servers and clients. If everyone can see how MS protocols operate, there's much less of a chance MS could leverage their domination of the client world into a stranglehold in the server world, especially in the Internet server space. Of course, one could argue MS could just continue to implement its newly-open protocols poorly (ie SMB), thus locking out specification-compatible 3rd party software. And that's where the second provision comes in: If Microsoft did find a way around having completely open protocols, their exploitation of the loophole would still be hindered by their inability to operate an online service. Remember, one of the primary goals of
Yes, Novell realized back in the early 1990s that NetWare on its own could not continue to defend itself from the onslaught of Windows NT. Noorda's answer: buy UNIX from AT&T, and turn out a version of UNIX that could easily integrate into existing NetWare shops as an application server (which NetWare just couldn't do reliably).
The result, UnixWare, flopped horribly.
UnixWare 1.0 demonstrated that Novell didn't know anything about Unix. After a somewhat improved 2.0 release, Novell finally sold it and Unix Systems Labs to SCO.
SCO did their best with UnixWare and OpenServer, but Linux and Windows started eating into their already small market big time. So their solution was to throw in the towel: sell it all to Caldera, including OpenServer, and hope they could do something with it.
Caldera is probably the best thing that as happened to UNIX since it left AT&T. Unlike Novell, Caldera understands what it can do. Unlike SCO, Caldera understands where it needs to go in the future.
Incidentally, though I don't remember the exact order of events, Noorda's interest in *nix on x86 was the reason for his (rather, The Canopy Group's) funding of Caldera in the first place.
Anyone reading the plane English of this license cannot help but see that, very clearly, the end user is required to grant Microsoft any and every right to their ideas, their work, even their patents, just by processing their information through a piece of software which happens to use Passport as an authentication mechanism. This could, in the future, include any document written by Micosoft Word (using passport to authenticate the author or encrypt the file as a new feature, etc.), sent through a Microsoft mail server, or served from a Microsoft Web server.
.NET and so-called "services," they could consider Windows XP merely a "Passport-associated service," thus meaning anything created/residing on your PC would belong to them, and they would have every right to download any data from your PC as they wished.
It was my understanding one of the new "features" of Windows XP was to pass your username/password entered in the initial user logon box to MS Passport-enabled sites to provide seemless logon to M$ services.
This sounds alarmist, but especially considering Microsoft's well-publicized refocus on
They wouldn't do that, would they? As much as I hate Microsoft, even I can't believe they'd do something like this. Someone please convince me I'm wrong...
ActiveX...just say NO!
(historical tip: if they were going to, it was more likely to be German than English).
Yeah, and supposedly one of the presidents of the Continental Congress under the Articles of Confederation asked the King of Prussia to step in and become monarch. That one didn't fly, either.
- sign the Communications Decency Act into law
- sign the CDA II act into law
- sign COPA into law
So far, sounds like an improvement. OTOH, inanimate carbon rods could still leave stains on blue dresses, but hey, that's not that big of a deal considering all the things an inanimate carbon rod wouldn't do!Now, if we can only find an inanimate carbon rod that will actually run....
This is to try and stop people minimising their tax liabilities by keeping their savings hidden in overseas banks in countries with strong banking privacy laws - like Luxembourg. Luxembourg makes it quite easy for people in Germany, Holland, Belgium etc to open accounts and move their savings there, therefore avoiding paying tax on interest or capital gains.
Oh well, then by all means, the need to do something! God forbid that someone would dare try to actually keep some money they saved!
On a serious note, though, thanks for the clarification on this. It still seems a bit troubling to me, but insight is always a good thing.
I really have a hard time believing that Europe protects online privacy better than the US, considering what I read on CNN.com yesterday:
u t/
http://www.CNN. com/2000/WORLD/europe/06/19/portugal.eu.summit.re
To summarize, most of the EU nations want to trade private citizens' income information (specifically, income from savings accounts). Of course, not only do they want to just trade this info amongst themselves, some of the EU governments want to hammer out agreements with 3rd party nations (read: US and Canada) so they can do the same with them. Frankly, I'm a US citizen, and I don't believe France, Germany, or even Luxembourg should have any access to any of my income information if none of my income was in their country. I really do not think a group so gung-ho about having access to private citizens' (of other countries) personal information is really that concerned with privacy at all!
I believe there are actually 2 problems here:
1) As I think several people have touched on, the problem here isn't the documentation, since Microsoft through MSDN etc. has documented the Word file format. The problem is that the only specifications on how to correctly render the Word documents are the Word rendering engine itself. Without the ability to see the exact logic that Word uses to render certain formatting codes (read: source code), it is impossible to reverse-engineer a 100%-compatible converter/viewer. It is a similar situation to what the Samba team faces: the SMB/CIFS protocols have been documented by Microsoft, but the only implementation of those protocols is Windows NT/2000, so Samba in reality must be coded to re-implement NT, not implement the CIFS specifications. The difference here, of course, is that CIFS apparently has a complete spec that Microsoft simply ignores, rather than the Word situation where they purposefully keep people in the dark on how things should be done.
2) the reason that you can't just watch what the Word rendering engine does and duplicate it is because it's stupid. From my experience working with Word itself and wvWare to convert Word files to HTML, it's obvious that Word just throws odd formatting codes where ever it pleases, and never bothers to clean them up. Often tags to end bold formatting (converted to </b> by wvWare) are just randomly placed in the document, nowhere near where any bolding is supposed to occur. The same goes for font sizing/coloring: Word seems to place odd, irrelevant font codes in places, only to override them with the correct codes a few lines later (often without canceling the first codes). In other words, it's a mess. With the Word source code, one may be able to figure out the (supposed) logic behind the mess; without it, I fear anyone is simply grasping at straws, especially since MS continuously changes to Office keeps everyone guessing about what Word is actually doing underneath it all.
My US$0.02 of course.