[go: up one dir, main page]

Menu

#39 Keep input file's extension

trunk
open
nobody
None
1
2013-03-21
2013-03-21
Mahdi
No

In some workflows, my shell script (i.e., the binary) may behave differently based on the type of the input file, which is understood from its extension. However, the "internal file name" is currently statically given by the developer, so the actual extension of the input file is lost.
The feature I request is to have some kind of keyword, or wildcard, that can be used in specifying the "internal name" of a port, and results in copying the original extension of the input file to the Internal name.

For example, I would write the "internal name" as Image.#EXT#, and based on the following input files, it will be changed to:

Input file: MyImage.gif ---> Internal name: Image.gif
Input file: XYZ.jpg ---> Internal name: Image.jpg

Thanks
Mahdi

Discussion


Log in to post a comment.