Comment 1 Neil MacLeod (reporter) 2007-03-24 14:30:34 UTC

Media Player in firmware 3.2007.10-7 continues to refer to songs/tracks as
"clips".

Comment 2 Neil MacLeod (reporter) 2007-07-06 17:47:24 UTC

Still not fixed in 4.2007.26-8 :( Songs are still referred to as "clips".

Bug report accepted and forwarded.

This is current implementation and it's according to our specs. Changed to
Enhancemnet and Later. Maybe in future this will be fixed. Quim added to
cc-field.

Comment 5 Neil MacLeod (reporter) 2007-09-09 08:39:22 UTC

If the implementation contains an error because the specification contains a
spelling mistake, would you still defend the specification and tell me the
implementation is correct even though the rest of the world knows it to be
wrong?

The specification uses the wrong term of reference for an audio track - it's
not clip, it's song or track. Look at an Apple iPod, top level menu - "Shuffle
Songs", not "Shuffle Clips". Look at any other media player, and I bet you a
pound to a penny that you will not find a single instance where an audio track
is referred to as a "clip".

The specification is *wrong*. Let's acknowledge this, update the specification
and proceed with correcting the implementation, which can probably be
accomplished in less time than it's taken for us to discuss this bug.

Comment 6 Quim Gil 2007-09-10 07:07:27 UTC

Adding Roope from the UI team. I don't think he has been aware of this bug
report.

Comment 7 Andre Klapper 2008-05-26 16:18:50 UTC

i always disliked "resolved later" bugs.

Comment 8 Neil MacLeod (reporter) 2008-05-26 16:31:42 UTC

Thanks Andre. This uber trivial bug should take only a few minutes to fix, and
would already be fixed if the media player UI wasn't closed code, and I'll be
pretty disheartened if it isn't fixed in Diablo as it would sum up all that is
broken about this process.

Comment 9 Roope Rainisto 2008-05-29 17:38:57 UTC

Hi Neil. 

You're right, we'll fix this bug. Unfortunately it is most likely too late for
Diablo, since fixing this will require small changes to the use of logical
strings and require new translations for all the languages, and Diablo is "just
around the corner".

It's too late because I messed up here. I was added to the bug in September,
but failed to notice this completely. If I would have noticed and reacted there
and then, we would have had the time to fixed this. So I'm sorry. We'll try to
learn from these mistakes.

Comment 10 Neil MacLeod (reporter) 2008-05-29 23:21:28 UTC

Roope - I very much appreciate your candid response! :) I can well understand
you've had your eye on other bigger issues, hopefully once the dust settles the
low hanging fruit can be dealt with in time for the next release post Diablo.
Thanks again for your reply, Neil.

Comment 11 Mikko Nurmi 2008-06-10 10:36:14 UTC

(In reply to comment #9)

> It's too late because I messed up here. I was added to the bug in September,
> but failed to notice this completely. If I would have noticed and reacted there and then, we would have had the time to fixed this. So I'm sorry. We'll try to learn from these mistakes.

As said the fact is that we are not able to fix this for the Diablo release.
Roope, can you confirm that we will fix this with next release? We could then
define this bug as FIXED.

Comment 12 Andre Klapper 2008-06-11 12:31:37 UTC

(well - please only close as fixed when the string change has been committed to
the codebase, just to avoid misunderstandings of the "fixed" resolution.)

setting target milestone.

Comment 13 Roope Rainisto 2008-11-26 10:39:51 UTC

So as I remember the long discussion this will get fixed in Fremantle (although
sorry, I cannot check this for 100% certainty right now).

Comment 14 Quim Gil 2008-11-26 13:02:16 UTC

Fixed in Fremantle. If someone finds any place where a song is called a clip in
Fremantle we could consider it a bug.