Which 5 years is this? IIS has been out over 10 years. It was a player in the server market almost immediately upon release as Netscape's product was expensive and IIS had all sorts of custom windows based features (as well as ease of administration).
That's the wrong setting. You are at too high a level. I'm trying to find out how its embedding fonts. I know what bad bitmaps look like and that was it. Another from experience said it was font embedding: "qtconfig, in the printer tab, i disabled "enable font embedding" A third said to turn off embedding under He said its under system options -> fonts.
So now you've gotten the same advice 3x. I'd say problem solved.
I think people in the arts are pretty good at handling abstract tools. Seeing a statue from a chisel and hunk of rock takes much more vision than seeing how to assemble a LaTeX document. Similarly with classics. Law is super easy to typeset. I really do believe these people could make the switch.
More importantly the discussion was really stuff like LyX, TeXmacs, where the actual TeX can be hidden (mostly).
This was a well reasoned clear response. Get an account, most people generally won't respond to ACs at all.
1) Hardware "drivers" don't have to be pure executables. They can contain library routines that the microsoft "drivers" then call. So Microsoft writes the drivers and they provide hardware specific routines. For an easy example you are familiar with think: --modem init strings under the Hayes standard -- termcap settings
2) As for drivers and the like Microsoft can and should absolutely demand to see source of anything they distribute. IMHO they can avoid these problems by 1) declare themselves to be an OS monopoly for x86 hardware 2) abide by the restrictions in the anti trust laws on monopolies Having a monopoly, its other acts that are illegal for a monopoly
3) As for known buggy hardware. Microsoft could (and should) in the details page of the OS provide information about the hardware which are known issues.
The USPS has internal people that know lots about encryption and servers. Generally though they like partner with companies for their services (i.e. company A buys from company B who buy from the post office) so now worry there. My guess is that people won't pay for verified email.
If you really are talking hundreds of thousands then you are talking a webpress. Which means nothing renders, its all analog data at print time. They are also using imposition software and they are going to be checking proofs.
So my guess is its not the printing that makes any difference its the guy doing the layout for the editing. In other words it could be one copy and it wouldn't matter. That guy may actually work directly in the TeX to layout the whole journal and he wants a consistent feel so no manual layouts (i.e. you have to use your style sheet so he can just redefine). My point is that you shouldn't associate those issues with "mass printing" they have nothing to do with the mass or the printing its "2nd party consolidated layout" or "non professional typesetting" that was the cause of the problem.
IMHO one of the biggest OS/2 made was having their default look good to color blind men (happened between 2.0 final release candidate and 2.0). OS/2 was far and away the nicest looking destkop anyone had: 3d effect on the icons, color coded folders, reasonable dragging, mouse contexts... But the default install was bland and boring. It looked not much better than Windows 3.1 and worse than 95.
Open the.pdf in a text editor..pdf is a forth like language. Search for the text from your document and look for a font setting. You may be getting a very bad bitmap export. I think you have the printer setup wrong rather than a KWord problem (though the setup may be at the KDE level).
I'm reading this and you don't seem like a guy who was around during the days of Ian Murdock founding Debian. I wasn't either but I was around 2 years later.
1) Lizard by Caldera was the first graphical installer for a major distribution. 2) Suse was still in German at that point 3) At the time Debian came out the big distributions were stuff like Yggdrasil not Redhat. 4) Suse vs. Redhat (for the US market) was not until United Linux which was in 2000 and by then everyone had an installer 5) Mandrake's claim to fame was not the installer but the KDE integration by the time of Mandrake RedHat had an installer as well (though IMHO Mandrake's worked better).
I could keep going but I thin I made my point. That this was from a few sentences.
So, these days, if will want to blame someone for instability, you should blame third-party driver developers. They are and will be for a while the big hurdle on stability on any OS.
No. Microsoft has a capability security model built into NT which could easily handle driver issues. The have a great QA department which could refuse to certify bad quality drivers.
-- Its Microsoft which has consistently tried to make sure buggy hardware works "good enough" -- Its Microsoft which has distributed buggy drivers as part of their OS packaging -- Its Microsoft which has built of culture of mediocre software
The x86 platform is exactly the way Microsoft has constructed it to be.
Microsoft does offer those sorts of models. They have subscription services for companies and things like MSDN for developers. MSDN is a great value (would be the equivalent of selling this upgrade for $30). OTOH the subscription model has lowered customer satisfaction like most multi-pricing models do. People get mad about complex pricing schemes.
You have a low number so I figure you are old enough to remember OS/2. OS/2 desktop users who had windows software didn't by in large run OS/2 software. OS/2 was a replacement for Desqview, and often they ran one or two apps (like the multithreaded word processor, or the version of 1-2-3 that could use massive memory like 32 megs).
The Mac user base (at least right now) if filled with Mac snobs who hate windows apps. Hate enough that are often willing to use inferior (from a features perspective), and more costly apps. That's a very different base than the OS/2 base.
I don't know about StuCAD/XSteel but the home platform for AutoCAD used to be AIX. It ran really well on IRIX. It was a very long time before it could run on a PC at all.
And they are quickly and aggressively converting all their internal systems to Linux. Their plan is on schedule. BTW their are shops that converted to all Linux in the late 1990s in a variety of industries. Most (all?) of them were coming from Sun, SCO, not Microsoft so the Linux argument that the problem is one of Windows "addiction" seems borne out by the evidence.
The Lisa's were workstations. A lot more expensive ($10k) and much better. They included stuff like internal hard drives (and for the early models) dual floppies. They ran a different OS though they could emulate the macs.
As far as Amiga dos there are far better systems today that are designed around that hardware. I think you'd be surprised how little those apps actually did if you were to run them and use them for a while.
Slashdot Mirror
Which 5 years is this? IIS has been out over 10 years. It was a player in the server market almost immediately upon release as Netscape's product was expensive and IIS had all sorts of custom windows based features (as well as ease of administration).
They included IE 2.0 as part of Windows 95. And at that point everyone who used the internet (which wasn't many people) still bought netscape.
If you are using a real database look up "materialized views". If you aren't then add this to the list of reasons you should be.
That's the wrong setting. You are at too high a level. I'm trying to find out how its embedding fonts. I know what bad bitmaps look like and that was it.
Another from experience said it was font embedding: "qtconfig, in the printer tab, i disabled "enable font embedding"
A third said to turn off embedding under He said its under system options -> fonts.
So now you've gotten the same advice 3x. I'd say problem solved.
I think people in the arts are pretty good at handling abstract tools. Seeing a statue from a chisel and hunk of rock takes much more vision than seeing how to assemble a LaTeX document. Similarly with classics. Law is super easy to typeset. I really do believe these people could make the switch.
More importantly the discussion was really stuff like LyX, TeXmacs, where the actual TeX can be hidden (mostly).
Dom -
This was a well reasoned clear response. Get an account, most people generally won't respond to ACs at all.
1) Hardware "drivers" don't have to be pure executables. They can contain library routines that the microsoft "drivers" then call. So Microsoft writes the drivers and they provide hardware specific routines. For an easy example you are familiar with think:
--modem init strings under the Hayes standard
-- termcap settings
2) As for drivers and the like Microsoft can and should absolutely demand to see source of anything they distribute. IMHO they can avoid these problems by
1) declare themselves to be an OS monopoly for x86 hardware
2) abide by the restrictions in the anti trust laws on monopolies
Having a monopoly, its other acts that are illegal for a monopoly
3) As for known buggy hardware. Microsoft could (and should) in the details page of the OS provide information about the hardware which are known issues.
The USPS has internal people that know lots about encryption and servers. Generally though they like partner with companies for their services (i.e. company A buys from company B who buy from the post office) so now worry there. My guess is that people won't pay for verified email.
If you really are talking hundreds of thousands then you are talking a webpress. Which means nothing renders, its all analog data at print time. They are also using imposition software and they are going to be checking proofs.
So my guess is its not the printing that makes any difference its the guy doing the layout for the editing. In other words it could be one copy and it wouldn't matter. That guy may actually work directly in the TeX to layout the whole journal and he wants a consistent feel so no manual layouts (i.e. you have to use your style sheet so he can just redefine). My point is that you shouldn't associate those issues with "mass printing" they have nothing to do with the mass or the printing its "2nd party consolidated layout" or "non professional typesetting" that was the cause of the problem.
I can give you think my wife needs that are in Word and not even in OO
Integration with commercial bibliography software
Z99.50 networking integration (automatic pulls from library databases)
For lots of other people its macros and VBA integration.
By humanities I assume he meant social sciences:
They do:
diagrams
different fonts
often different languages
pictures
diagrams
tables
graphs
If its pure humanities work then I guess it depends which one. I'd assume an Art history dissertation is no piece of cake to typeset
How does \overrightarrow instead of \vec hurt mass printing? And what quantities are you talking about in terms of mass?
IMHO one of the biggest OS/2 made was having their default look good to color blind men (happened between 2.0 final release candidate and 2.0). OS/2 was far and away the nicest looking destkop anyone had: 3d effect on the icons, color coded folders, reasonable dragging, mouse contexts... But the default install was bland and boring. It looked not much better than Windows 3.1 and worse than 95.
Open the .pdf in a text editor. .pdf is a forth like language. Search for the text from your document and look for a font setting. You may be getting a very bad bitmap export. I think you have the printer setup wrong rather than a KWord problem (though the setup may be at the KDE level).
There are a dozen very good TeX implementations for Mac.
Except for corporate ownership Corel Linux is still a very user friendly desktop Linux with embedded Windows support, just under a new name.
I'm reading this and you don't seem like a guy who was around during the days of Ian Murdock founding Debian. I wasn't either but I was around 2 years later.
1) Lizard by Caldera was the first graphical installer for a major distribution.
2) Suse was still in German at that point
3) At the time Debian came out the big distributions were stuff like Yggdrasil not Redhat.
4) Suse vs. Redhat (for the US market) was not until United Linux which was in 2000 and by then everyone had an installer
5) Mandrake's claim to fame was not the installer but the KDE integration by the time of Mandrake RedHat had an installer as well (though IMHO Mandrake's worked better).
I could keep going but I thin I made my point. That this was from a few sentences.
Virtual PC gets mentioned a lot in the Wall Street Journal. They must use it there or something but lots of people know about it.
So, these days, if will want to blame someone for instability, you should blame third-party driver developers. They are and will be for a while the big hurdle on stability on any OS.
No. Microsoft has a capability security model built into NT which could easily handle driver issues. The have a great QA department which could refuse to certify bad quality drivers.
-- Its Microsoft which has consistently tried to make sure buggy hardware works "good enough"
-- Its Microsoft which has distributed buggy drivers as part of their OS packaging
-- Its Microsoft which has built of culture of mediocre software
The x86 platform is exactly the way Microsoft has constructed it to be.
Microsoft does offer those sorts of models. They have subscription services for companies and things like MSDN for developers. MSDN is a great value (would be the equivalent of selling this upgrade for $30). OTOH the subscription model has lowered customer satisfaction like most multi-pricing models do. People get mad about complex pricing schemes.
You have a low number so I figure you are old enough to remember OS/2. OS/2 desktop users who had windows software didn't by in large run OS/2 software. OS/2 was a replacement for Desqview, and often they ran one or two apps (like the multithreaded word processor, or the version of 1-2-3 that could use massive memory like 32 megs).
The Mac user base (at least right now) if filled with Mac snobs who hate windows apps. Hate enough that are often willing to use inferior (from a features perspective), and more costly apps. That's a very different base than the OS/2 base.
I don't know about StuCAD/XSteel but the home platform for AutoCAD used to be AIX. It ran really well on IRIX. It was a very long time before it could run on a PC at all.
No, they're discouraging use of Windows by making it inconvenient. That gets the employee to spend some time thinking about how to do XYZ in Linux.
And they are quickly and aggressively converting all their internal systems to Linux. Their plan is on schedule. BTW their are shops that converted to all Linux in the late 1990s in a variety of industries. Most (all?) of them were coming from Sun, SCO, not Microsoft so the Linux argument that the problem is one of Windows "addiction" seems borne out by the evidence.
Well yeah like Peoplesoft, Oracle financials, JD Edwards.... The problem for those guys is Excel Macros not their core apps.
I thought the original mac was the 512kE? With 512kB of RAM? And a whopping 512kB of ROM?
Nope that was the 2nd mac. first mac.
If we don't count the Lisa that is
The Lisa's were workstations. A lot more expensive ($10k) and much better. They included stuff like internal hard drives (and for the early models) dual floppies. They ran a different OS though they could emulate the macs.
As far as Amiga dos there are far better systems today that are designed around that hardware. I think you'd be surprised how little those apps actually did if you were to run them and use them for a while.