Re: Corrupted Fonts
- From: "Nathan Herring [MSFT]" <nathanh@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 21 Sep 2005 14:08:14 -0700
As far as I can tell, your argument is correct about how to produce a new
build that may fix a problem (assuming the programmer understands the real
reasons underlying the problem).
Unfortunately, it does not account for the vast quantity of testing to make
sure that we're not introducing some other such problem, and even then, we
still produce products for which the full set of in-house testers, in-house
dogfooders, and external beta users do not see a particular bug that an
individual end-user (or set of them) do see. A fix to your problem might
cause problems for some other (possibly overlapping) set of users.
-nh
On 9/21/05 7:14:24 AM, in article
2005092110142437709%loren@hotnospammailcom, "Loren"
<loren@xxxxxxxxxxxxxxxxx> wrote:
> Anyway, once fixed in the high-level source code, the source is
> recompiled. Any change to the source code, from the most superficial
> change to the most major, requires a total recompile, as it does with
> all coding environments. There's nothing so deep that it is beyond
> anyone familiar with the source code. The line of argument you're
> pushing is just a kind of obfuscation that tech geeks like to push on
> every day computer users: make it seem so technical that a fix is
> either impossible or will cost you hundreds of dollars an hour in
> consulting fees.
--
Nathan Herring
MacBU SDE/Development
This posting is provided ³AS IS² with no warranties, and confers no rights.
.
- References:
- Re: Corrupted Fonts
- From: Daiya Mitchell
- Re: Corrupted Fonts
- From: Loren
- Re: Corrupted Fonts
- Prev by Date: Re: Service Release 2 does not fix font problem
- Next by Date: Re: "error accessing the system registry"
- Previous by thread: Re: Corrupted Fonts
- Next by thread: Re: Corrupted Fonts
- Index(es):
Relevant Pages
|
Loading