Where are my Motion Templates?

I have created a title template for a client and tried to install it on her system.
As she does not have Motion installed there was no Motion Templates folder in the Movies folder, so I created one and within that I created a Titles folder into which I copied the folder with my title.

However, even after quitting and restarting FCPX I don't see the title in the browser.

Any suggestions much appreciated!

Add the suffix .localized to the Motion Templates folder. Can’t remember if you need to add it to Titles as well, but add it anyway.

Thank you Tom! Another amazingly swift reply from you that worked!
Any idea why adding .localized is necessary?

I honestly don’t know but it’s something in app not recognizing the folder if it’s not been created by Motion.

This .localized thing is a neat trick that lets the Finder translate the folder names depending on the selected system language - that is how a Spanish or German user will see not "Titles" but "Titulos" or "Titel".
I suppose the requirement that the folders be localized is hardcoded into the application.

Incidentally, I recently found out that localization is handled slightly differently for the Documents, Desktop, Pictures, Music etc folders: instead of the names having .localized extension, the folders contain a specific hidden file whose name is ".localized"

lichinho wrote: This .localized thing is a neat trick that lets the Finder translate the folder names depending on the selected system language - that is how a Spanish or German user will see not "Titles" but "Titulos" or "Titel".
I suppose the requirement that the folders be localized is hardcoded into the application.

Incidentally, I recently found out that localization is handled slightly differently for the Documents, Desktop, Pictures, Music etc folders: instead of the names having .localized extension, the folders contain a specific hidden file whose name is ".localized"

Only half true.
The ".localized" was thought to be only used for application internal things - to localise interfaces.
But as always Apple interprets it's own rules quite relaxed.
The idea was to run different apps on different OS regarding language. I.e. an English app on Japanese system.
In case of the Motion Templates this ".localized" doesn't make too much sense - though I don't know how they are named with Japanese, Chinese and other non Roman OS versions.
A funny "historical" Apple thing: In the first original FCP version most of the internal plugins were commented "Do not localize!" the international versions though included these plugins as localized - that finally led to several bugs.

Anyway if you want to create a Motion Template structure you can down my free X-FX Handler. One click and you have it installed.
BUT:
It will install the template folder within "Application Support" which is the better way if you want to "share" projects with others (this includes yourself on another machine).

Andreas Kiel wrote: …The ".localized" was thought to be only used for application internal things - to localise interfaces.….

… which, btw, would be a nice enhancement for Motion, I know not just me but other plugin makers too would love to see: "language snapshots", allowing to create plugins with localized Interfaces, graphics etc …

Karsten Schlüter wrote: … which, btw, would be a nice enhancement for Motion, I know not just me but other plugin makers too would love to see: "language snapshots", allowing to create plugins with localized Interfaces, graphics etc …

"dot localized" sucks :evil:
My quote as another developer.

If companies like Apple would have a serious way to handle local behaviours it could be nice.
Have you EVER went into the code of your templates to make it easier for other people to interpret values?
I doubt.
With FCP7 I made it with some hundreds of settings of Apple and 3rd party title/text plugins - was and still is a nightmare.
Same with FCPX - took some weeks together with Martin Baker from Digital Heaven to "de.assemble" his own plugin to make it's values available for "a plugin for his plugin".

I could write endless text here but ...
... let me say as long as there is no "de-localize" things suck