Thread:Andrewds1021/@comment-45310000-20200414034500/@comment-45310000-20200417011049

1) I was up rather late when I wrote it, so yes, I will go back an do that.

2) What I am talking about is any object in the 'File:' namespace. So what I would like, is given the title of an object in that system, is to find out how wide and tall it is - whether is formatted as landscape where w>h or portrait w<h, and adjust the displayed image width based on this information, so portrait pictures aren't displayed sizes that dwarf the landscape images.  I really just need a binary function for this.

BTW, I made a 'feature' request regarding the image file system which I think got ignored. I think that it is pointless that the 'File:' namespace is typed, I don't think the title of the object should be required to carry a tag indicating the internal image format, because for most purposes, this information is just not important to the end user. But I suppose all that good 'check if the title matches the internal image or video format file extension' code can't go to waste. It already manifested itself in a problem I reported, where YouTube links in the files system cannot be renamed/moved, because the move procedure complains that the name doesn't have the required non-existent file extension.

It got in the way of my automatic first image in article system, which I did a workaround using redirects created within the File: namespace.

3) What I am talking about is that it makes a distinction between Protected Titles, articles/objects that should never be created with that name, and Protected Files, articles/objects that exist and are administratively protected from change. I want to access the former, so I can protect the title "File:Story-Do not create! (character)" from creation, as it would nullify the example displayed in the template's documentation output.  It's not really a big deal, because to get an object in the 'File:' namespace with no extension, you have to explicitly create a new page.  And it is only required for the template demonstration in the documentation, so I'm not sweating it.