Clip timecode in Project

OK Tom - I've cracked it - a learning curve and I share this so hopefully it will help other people in this situation. Yes, you won't see timecode in the mov. file. but - the reality is in a grey area in the middle so to speak. Canon developed a plug-in for FCP7 which found the time of day data from the two files which come out of the Canon 5d - the mov and the thm files - and applied it to the clips once they open in FCP7. This does NOT exist for FCPX. What you have to do is buy Grinder from Magic Bullet - about $50. This effectively does the same as the Canon plug-in for FCP7 - it finds the time of day data from the mov and thm files and adds it (you could also choose continuous timecode if you want - but since I'd already used time of day for my reference point for the translations I had to stick with that.) The way I did it, after reading another post, was to add the time of day code through Grinder (not converting the files in any other way), and then importing into FCPX - and then, yippee!, I can see the original time of day time code in the clips in the event browser - thus enabling me to find the segments with timecode that I've chosen from the Arabic translations. Now when I look in the event browser - I see the clips I originally imported, without time of day code, and above each of these a new clip, suffixed "main" with the timecode. Phew!! It's all a learning curve, but I'm frankly surprised this hasn't come up more often. The thread that finally cracked it was at Creative Cow - here: forums.creativecow.net/thread/344/656
Thanks Tom for your comments - yes, the truth lay somewhere in the middle, shrouded in mystery -but this is a relatively painless work-around for FCPX - though Apple should be aware of it and signal it in my opinion.
Thanks again.

I wonder if the Magic Lantern firmware upgrade will fix this. It's really something Canon should fix in their cameras.

Canon have fixed this issue with there new cameras. Sadly the good ol 5D Mk II has not been changed. Nor has Canon created a plugin that worked like the brilliant EOS E1 plugin for FCP X.

Only solution is to user Grinder, QtChanger or upgrade to the 5D Mk III.