When saving the tiff form, you can remove one letter f

[xanuzz]

When saving the .tiff form, you can remove one letter f 

Many wide-format printing devices do not support .tiff
I rename each file every time, I remove one letter f
.tif is saved through coral Drow and Photoshop

[PaoloT]

But only as an option, please!

 

[GarryP]

Simply removing the extra “F” (either manually or via an option) from the file extension might cause problems and/or confusion later in the production process because TIFF (two “F”s) files aren’t exactly the same thing as TIF (one “F”) files.

See here: https://proshotmediagroup.com/photography/tiff-vs-tif/

Quote (with my emphasis): “To sum it up, TIFF and TIF are both standard file formats for digital imaging programs that allow you to store and share your images better. Although they may seem similar at first glance, they have distinct differences such as their compression levels, compatibility with different programs, and the advantages and disadvantages of each format when comparing them side by side. Knowing what the difference between TIFF and TIF are makes converting image formats much easier so that you can get the most out of your images without losing any image quality. Whether you need to optimize an image for a website or print advertisement, understanding the pros and cons of both formats helps make sure that you’re using the correct one.”

I’m not an expert in this area but I think this difference would need to be taken into account if any change were to be made.

[fde101]

1 hour ago, GarryP said:

TIFF (two “F”s) files aren’t exactly the same thing as TIF (one “F”) files.

This is hogwash.

As was discussed in a previous thread on the subject (this one is a duplicate), the TIFF file format standard calls for its files to be named with a .TIF extension on platforms that use file extensions to represent the file type, but many applications ignore this advice and use .TIFF instead.  

The .TIF and .TIFF extensions are both used for EXACTLY the same file format.

The TIFF standard offers a number of compression and storage formats which can be used interchangeably, regardless of file extension.  One application might save files with the .TIF extension and use one compression format by default (or as its only option), while another might use .TIFF and a different compression format, but they are both TIFF files.

Some of the compression formats are more suitable for one type of image (such as black and white scans of business forms) while others are more suitable for other types of images (such as photographs).

TIFF files can also be uncompressed.

[NotMyFault]

If in doubt just refer to the original and still valid documents from the inventor (Aldus, now Adobe).

https://www.itu.int/itudoc/itu-t/com16/tiff-fx/docs/tiff6.pdf
 

[GarryP]

Like I said, I’m not an expert in this area, but I was simply pointing out that this request might not be as simple as it might seem at first as there are some differences of opinion about it with different people saying different things.

Some people, who seem to know more about it than I do, say that they are exactly the same and others, who also seem to know more about it than I do, say that there are differences.

Even if there are no actual differences between the formats, some people may think that there are and they might have a problem with any changes to the functionality.

I’m sure that the Serif developers will know much better about this than I do so I can happily leave it for others to deal with.

If it is as simple as it seems then I have no problem with that.

[wonderings]

I have never run into this with our RIP's. but then 99.99% of files we push through are all saved as PDF. 

[PROdult]

TIFF and TIF are exactly the same, but they serve as a prime example of how humans and complexity are incompatible - how humans create complexity that is fundamentally at odds with their own inability to grasp it.

TIFF is the actual name, but it was (in DOS and Windows) reduced to TIF due to the uniquely primitive DOS and its three-letter file extension limitation. This principle was then carried over into Windows and, unfortunately, into the future inside people’s minds. It’s sad that the little ‘F’ still causes trouble.

I assume that Serif is following macOS conventions, while Adobe is overriding it out of consideration for their customers. That consideration is necessary if macOS users are forced to save files as TIF due to client demands or compatibility with other software in their workflow.

This makes it difficult to turn into a global setting - some users likely need to choose per file, depending on workflow requirements. Personally, I prefer not to be forced into something as if I were a child, which Adobe and others have allowed through their overrides.

[NotMyFault]

The filename extension was limited to 3 characters in DOS / FAT filesystem before long filename extensions ) were added much later in 1994. Other OS never had such limitations. TIFF dates 2 years earlier, 1992 and had to consider 3 character extension - but maybe assumed DOS was a less relevant platform than Unix or Mac.

The „correct“ extension was .tiff, but for DOS and early Windows versions it hat to be shortened to .tiff. Unrelated to the filename, the internal structures and data inside the file are 100% identical.

As we now have shared filesystems like NAS and cloud synced folders it does not matter (for the data inside) which extension you are using. 
For historical reasons some Apps prefer one over the other, and Affinity is inconsistent as it may allow tif in one UI and tiff in another.

https://en.wikipedia.org/wiki/Long_filename

 

[xanuzz]

ok why then does Photoshop also save the .tif format

 

[xanuzz]

The program CorelDraw also saves in .tif format

Edited Tuesday at 03:43 PM by xanuzz

[NotMyFault]

The apps can use what they want, .tif or .tiff or .TIF or .TIFF are all valid. Ideally they should allow the user to choose a global preference (use .tif, use .tiff, use same as source file, ….) for export and allow both .tiff and .tif for import/open (and ignore case).

[PROdult]

This isn’t about a format but simply a naming convention. My guess is that Adobe has adapted to reality - specifically, the reality of its customers, where files are constantly exchanged between creatives, clients, print shops, and web developers across multiple systems. And since the actual file name is completely irrelevant, they likely chose TIF as the model that would cause the least problems in production environments. Brand value increases when customers aren’t struggling with pointless issues, and support teams receive fewer inquiries. Win.

I want to wholeheartedly criticize and shake my head at companies that fail to build in real-world adaptability, forcing customers to deal with both scenarios on their own. Not understanding the reality around them is a fundamental mistake. In this case, making an exception to system standards is simply the right approach.

You have to be able to connect theory with reality.

[fde101]

3 hours ago, NotMyFault said:

The „correct“ extension was .tiff,

Not correct.

Look at the page from the specification you yourself posted a screenshot of: the standard for the file format specifically said that "UNIX" should use .TIF, not .TIFF - this was to keep the naming compatible across platforms.

The Mac file type code of "TIFF" was not referring to a file extension.  The Mac at that time (prior to OS X) was using an additional property of the file, not part of its name, to track the type, and that code was always exactly four characters long, thus "TIFF" being appropriate.  An extension would have needed to be added when moving the file to some other platform.

[NotMyFault]

1 hour ago, fde101 said:

the standard for the file format specifically said that "UNIX" should use .TIF, not .TIFF - this was to keep the naming compatible across platforms.

Yes, but only based on the filesystem restrictions at that time (1992), about 2 years before Microsoft introduced LFN support in 1994 with Windows NT 3.51.

And only to ease interoperability at that time. 
To be precise: it says „recommended“, thus allowing other extensions.
 

Don’t forget: TIFF is more a container format, many other RAW formats are technically TIFF containers with some Camera brand specific content.

All the arguments have been exchanged, I will step out this thread for good.

[PaoloT]

11 hours ago, NotMyFault said:

If in doubt just refer to the original and still valid documents

Who wouldn't want to be compatible with computers running MS-DOS? 😁

 

[PaoloT]

6 hours ago, fde101 said:

The Mac file type code of "TIFF" was not referring to a file extension.

Version 6.0 of the TIFF specs allow for the ".tiff" extension. Someone had bought a Mac at the office!

 

[xanuzz]

Это должно быть исправлено тем, с кем следует связаться.