On Sun, 16 Sep 2001 14:08:01 -0400, "Thorsten Froehlich"
<tho### [at] trfde> wrote:

>In article <xOGkO6cycku13Et0ri0kghPLk0kD@4ax.com> , Glen Berry 
><7no### [at] ezwvcom>  wrote:
>
>> If you do this, will you also add support for some of the other
>> POV-related file extensions that were left out originally? For
>> example, I'm thinking of things like *.cat, *.mcr, *.sph, *.tri
>
>None of these are in any way supported by POV-Ray (it just reads text files
>with whatever extension if you tell it to).  If a user decides to use
>different extensions it is simply a problem because some of these are used
>by other programs and POV-Ray cannot detect if they are for POV-Ray or not!
>In general it is a bad idea to create "your own" file extensions because it
>creates all kinds of these problems.
>
>    Thorsten

That sounds fair enough. 

However, I want to point out that 3 of the 4 extensions I gave above
come from the official 3.5 distribution of POV-Ray. Here are the names
of the files:

quartic.cat
teapot.cat
teapot.sph
teapot.tri

I could have also included the following files and their extensions:

teapot.c1
teapot.c2
teapot.c3

All these files are written in plain text, and are meant to be used
with POV-Ray. According to your own philosophy on this subject, should
these files be converted to the ".inc" extension, to set a good
example for the rest of us? Of course, the files themselves might need
a bit of re-formatting. The ".cat" files for example, would probably
need to be converted to commented text, if placed in an "include" or
"POV" file.

Just curious,
Glen

Post a reply to this message