Media & Folders view is not displaying same filename as Windows File Explorer

[Damit]

I have a file that in Windows Explorer is shown as:
1928-05-15.c.mdts[AB001.P.105-(PS)@1500dpi]{Graduadas de 1928 - Dominicas Americanas}.tif

But in IMatch Media and folders the title does not show anything within the curly brackets:
1928-05-15.c.mdts[AB001.P.105-(PS)@1500dpi].tif

Why is IMatch not displaying what is within the curly brackets?  I am using {File.NameExt} as the variable and when I hover over that variable in the variable selector the pop-up shows the filename as that which is shown in file explorer, so IMatch itself is indicating that the file name should show what is within the curly brackets.

[Mario]

But in IMatch Media and folders the title do

What do you mean by title?
A couple of days ago, another user already explained this problem with your file names to you.

Curly braces are used by IMatch to indicate variables. In your overly complex file name, the

{Graduadas de 1928 - Dominicas Americanas}.

is interpreted as a variable when you use it in another variable like {File.NameExt}, because variables can, and often do so for good reasons, contain embedded variables. Which is what {File.NameExt} does. It parses the part in {} in your file name, and since it is an unknown variable, it is stripped from the result.

Use the noparse variable function to prevent that. Everywhere you will ever use one of your complex file names in IMatch variables. Or, just don't use exotic characters like { and } in file names. There is a reason why programming languages and IMatch use { and } for functionalities, code blocks, variables and suchlike - because { and } are characters usually not used for anything else. Especially not in file names.

[mopperle]

@Damit The fact that one OS allows the usage of special characters in filenames, does not mean that it can be handled by another OS.
So you should really reconsider your naming conventions:
https://www.mtu.edu/umc/services/websites/writing/characters-avoid/

[Mario]

File naming conventions are one of the widely discussed topics among librarians and archivars. Unfortunately, no standard exists.
As @mopperle points out, many universities, large public libraries publish naming conventions. For good reasons.

Including date and time in a standard ISO format like YYYY-MM-DD hh-mm-ss in file names is still common, as users have to deal with software or services which cannot sort files by embedded metadata.

Customer, photographer and project codes are common for pro's.
For technical photography, sometimes technical details like camera serial number must be part of the file name.
This always depends on the recipient and whatever naming convention is applicable.

But all naming standards I know of stick to file names in plain ASCII, without any special characters which may be allowed on on operating system (e.g. Windows) but may cause problems on other operating systems or when synchronized via cloud storage like OneDrive, Dropbox, Google Drive or when uploaded to web sites.

Simple is better. I know quite a number of users regretted their overly complex file naming schema (I wrote to @Damit about that already) and who had to roll back to something simpler. Which is easily doable with IMatch Renamer, but still a nuisance.

The list in the linked web page of @mopperle's post is a good place to start. Other universities and libraries have quite similar exclusion lists and conventions.

You ran twice already in problems in IMatch using variables, because your file names contain embedded variables because you use { and } in your file names. Be prepared to run into more trouble in the future. I would recommend not to use any of these special characters in file names, but as I wrote already, it's your decision. But if you really want to create such complex file names with so many special characters, be prepared to run into trouble. In IMatch or elsewhere.

[Damit]

Thank you for your responses. I am trying to make it simpler. I figured that IMatch was interpreting it as a variable, I just thought you could escape it, I just could not figure out how. I tried using the reg ex escape. 

Thank you, Mario, for pointing the noparse. I know I have read that section at least a dozen times but that one never stuck. And I do see the warning in your emphasis on everywhere.

I used the reference that Mario gave me in his lest reply to another file naming issue and it was not as stringent in its recommendations. I will continue to work on this and I appreciate your input and advice. I have eliminated the " and ' from my system, and I guess I will do the same with @.  That one is not biggie. I will try to figure out a way to isolate the descriptive text without using the curly brackets. I am just testing and hashing out the system as I go to find out issues such as this. Though I don't expect my files to be referenced by any other system other than apple and windows. I am no pro, this is for family archiving.

[JohnZeman]

Just to throw my 2 cents worth in here my file names are very simple as I've mentioned before so the way I see the extra details in the file window is to use the File Window Tip (see attached screen shot).

[axel.hennig]

Hi John, thanks for sharing the File Window Tip screenshot. 

I always wanted to "enhance" this. Now, I've a good template to start with.