This discussion is locked
Close
Q: Altered Font Spacing Crippling for Designers
first
Previous
Page
4
of 9
last
Next
-
Sep 21, 2009 1:36 PMby Frozo,Well, for what it's worth, I have been monitoring this thread, not the other one. I wouldnt have seen his post otherwise and Im sure there are others like me. If it gets more people to chime in about the bug, then it can NEVER be a bad thing (even if they are already aware of it). Bug lists have priorities, and the more people affected, the higher it is on their list. Being that this is affecting an entire INDUSTRY of graphic designers, I think a little persistence is called for.
I suggest everyone click on that list and add their voice. -
Sep 21, 2009 5:18 PMby MiguelSousa,Well, just hearing from a 3rd party that they know about the issue doesn't seem to be enough, since the number of users that are not at ease keeps growing. Therefore, users should log their problems in the form of bugs, as that's the best channel to Apple's engineers. -
Sep 21, 2009 6:58 PMby MiguelSousa,Has an Apple employee actually posted on this (or the other) thread confirming that? I didn't see any.
The thing is, these forums are mainly for users to help other users. In this case, no one besides Apple's engineers can help solve the problem. Engineers don't act on forum posts, they act on bugs. And bugs get prioritized according to several factors, which include gravity and occurrence. Just because one or two people logged a bug regarding this issue doesn't mean it will get addressed appropriately. All users that reported a problem on this (or the other) thread should log a corresponding bug. -
Sep 22, 2009 6:12 AMby Kurt Lang,Has an Apple employee actually posted on this (or the other) thread confirming that?
Very rarely will an Apple employee post in the forums, but that doesn't mean they don't read them.Just because one or two people logged a bug regarding this issue doesn't mean it will get addressed appropriately.
And where did you come up with that theory? A bug only needs to be reported once. If you use the Bug Reporter system, they go directly to the engineers. They've never failed to respond.
So once again - yes, they know about the font leading issue and are working on it. This was a direct response to me from an Apple engineer on my bug report. I have no reason to think they're lying.All users that reported a problem on this (or the other) thread should log a corresponding bug.
Again, not necessary. A flood of complaints works to convey urgency when a company is still unaware of an issue. It does nothing when it's already being addressed. -
Sep 22, 2009 6:12 AMby Mattspin,We're seeing this in Adobe Flash. Certain fonts (some postscript fonts so far...TheMix is the one that's really causing us trouble) have shifted in our layout and complete messed our files us. The same files still display just fine under Leopard. The OS just seems to display them differently. Very frustrating. -
Sep 22, 2009 11:05 AMby MiguelSousa,Very rarely will an Apple employee post in the forums, but that doesn't mean they don't read them.
Likewise it doesn't mean that they do read them. Perhaps this is one of those rare occasions where they need to come out.And where did you come up with that theory?
It's not a theory, it's a fact. I work for a software company (Adobe) and I'm aware of how these things are processed.A bug only needs to be reported once.
What makes you so sure that the bug you reported when fixed will take care of everyone's problems?If you use the Bug Reporter system, they go directly to the engineers. They've never failed to respond.
I believe that.So once again - yes, they know about the font leading issue and are working on it. This was a direct response to me from an Apple engineer on my bug report. I have no reason to think they're lying.
I'll take your word on that.Again, not necessary. A flood of complaints works to convey urgency when a company is still unaware of an issue. It does nothing when it's already being addressed.
Again, what guarantees can you give that the bug you logged when fixed will take care of everyone's problems? Have you been able to reproduce all the issues reported in this and the other thread on your machine? Have you included those reports on your bug's description? -
Sep 22, 2009 11:17 AMby Kurt Lang,Likewise it doesn't mean that they do read them.
True enough. Especially on a site this large. But the Level 4 and 5 members have brought these threads to the attention of the hosts (we have direct access to talk to them). They then bounce our concerns up the chain of command. I also included links to these threads in the bug report I submitted.I work for a software company (Adobe) and I'm aware of how these things are processed.
One company's policy or procedures is not a 100% reflection of how all of them work.What makes you so sure that the bug you reported when fixed will take care of everyone's problems?
A fair answer is to that is, what makes you think it won't? We'll find out with the next point update if anything has been done to address the issue. Until then, we're just arguing amongst ourselves, which does nothing to change the situation. If it's still not fixed in 10.6.2, then people who rely on accurate font rendering should definitely raise a stink. More so than they are now.Again, what guarantees can you give that the bug you logged when fixed will take care of everyone's problems? Have you been able to reproduce all the issues reported in this and the other thread on your machine? Have you included those reports on your bug's description?
I can't guarantee anything. I said that Apple has told me they're aware of it and are working on it. Yes, I have been able to reproduce the same problems. Yes, I included those issues in my bug report. -
Sep 22, 2009 1:36 PMby MiguelSousa,A fair answer is to that is, what makes you think it won't? We'll find out with the next point update if anything has been done to address the issue. Until then, we're just arguing amongst ourselves, which does nothing to change the situation. If it's still not fixed in 10.6.2, then people who rely on accurate font rendering should definitely raise a stink. More so than they are now.
To me that's not a fair answer, and it's probably not a fair answer to a lot of other users as well. People are being affected by this problem as of now. Why wait until after 10.6.2? Right, there's no point on arguing because your argument just doesn't make sense.I can't guarantee anything.
Then please stop saying that people don't need to submit their own bugs. -
Sep 22, 2009 2:53 PMby Kurt Lang,To me that's not a fair answer, and it's probably not a fair answer to a lot of other users as well.
How is it not fair? Your question was conjecture, as was my answer. Neither had any merit.People are being affected by this problem as of now. Why wait until after 10.6.2?
And just how do you expect it to be fixed before that? I've never know Apple to fix ONE problem at a time. If they do anything to fix this, it won't be until 10.6.2 is released.Right, there's no point on arguing because your argument just doesn't make sense.
And yours does? Here's the real answer, which has been noted by various users in numerous posts in the Snow Leopard forums. If you're using your Mac to make a living, why in the world did you jump on a new operating system with no easy way to go back to Leopard? If you didn't take the precautions to fall back, you've no one to blame but yourself.Then please stop saying that people don't need to submit their own bugs.
Once again. It will do NO GOOD to keep reporting the SAME bug over and over. Report it if you somehow think it will speed things up. It's not like I or anyone can stop you. But you will be wasting your time. -
Sep 22, 2009 3:25 PMby MiguelSousa,How is it not fair? Your question was conjecture, as was my answer. Neither had any merit.
...
And just how do you expect it to be fixed before that? I've never know Apple to fix ONE problem at a time. If they do anything to fix this, it won't be until 10.6.2 is released.
...
And yours does?
Look, I was mainly reacting to your idea of "let's wait for 10.6.2 and see if everything got fixed; if it's not, then let's make noise about it, again; this time around we should make the real noise". I mean, why not do everything now and get over it? Unless this is a game for you...Once again. It will do NO GOOD to keep reporting the SAME bug over and over. Report it if you somehow think it will speed things up. It's not like I or anyone can stop you. But you will be wasting your time.
My point is, it doesn't seem to be ONE single problem because people are reporting different things, so there's no SAME.
Anyways, I think I've made my points clear enough already, so I'll excuse myself. -
Sep 23, 2009 5:59 AMby Kurt Lang,Look, I was mainly reacting to your idea of "let's wait for 10.6.2 and see if everything got fixed;
Ah, now I see your point. I agree whole heartedly that it would be great if Apple would address the problem as soon as possible. Ahead of everything else if necessary. It's just that I can be almost absolutely certain we won't see any possible fix until 10.6.2 is released. That's just the way Apple has always done things, at least from my experience the last 12 years or so. I've seen seen a fix for only one OS issue at a time.
