Idea: User-defined file types

George
Administrator

Posts: 4,056

Idea: User-defined file types May 18, 2020 12:33:20 GMT -5

Quote

Post by George on May 18, 2020 12:33:20 GMT -5

Robert: I'm a bit confused (what else is new?). Since we can create profiles with any name we like (UTF8, UTF16BE, whatever) and set these profiles up to whatever is needed to process a peculiar file type, we have the ability right now to override the normally assigned Profile name by specifying the special Profile on the command line via .profname, or on the FM line command by just entering .profname as the line command.

This allows for special SOURCE values, special EOL, RECFM, IMACRO, etc. etc.

What doesn't the current Profile provide that you are looking for?

George

George
Administrator

Posts: 4,056

Idea: User-defined file types May 19, 2020 11:56:29 GMT -5

Quote

Post by George on May 19, 2020 11:56:29 GMT -5

File reading is already cluttered, it does the check for which EOL characters are actually used regardless of what the Profile says, it looks for BOM markers to force UTF translation. Throw in all the different RECFMs it handles, the AUTONL support, etc. and it gets real ugly.

So what you're asking for now is to throw even more clutter in there to dynamically evaluate the beginning of the file data to look for more alternatives. That, for sure, is a "maybe someday" - if I live so long.

George

George Administrator Posts: 4,056	Idea: User-defined file types May 20, 2020 8:31:55 GMT -5 Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by George on May 20, 2020 8:31:55 GMT -5 I've used TrID a few times in the past, don't have it installed anymore, mainly because I've simply no need for it. George

Idea: User-defined file types

Post by George on May 18, 2020 12:33:20 GMT -5

Post by George on May 19, 2020 11:56:29 GMT -5

Post by George on May 20, 2020 8:31:55 GMT -5