on extension names

[jelaih]

hi! I've got a few questions...

Can't I be able to give/create my own extension name when saving a certain document in writer?

Here is the scenario of what I want to do...

1) I want to create files with extension names ".pre" and ".prm"
2) ".pre" contains hyperlinks that when clicked will bring you to ".prm"
3) ".prm" contains bookmarks

What bothers me is that I can't be able to open ".prm" when I tried to click my hyperlink on ".pre" , it raises an error

Do I have to stick with Ooo's supported extension names or I still have an option to create my own? Thanks a lot
_________________
codebits...

[Cybb20]

As far as I know OO shouldn't really be bothered at all with other extension names, since it does not only do a flat typedetection but also a deep one before opening up a file or stream.
The deep typedetection of the import mechanism analyzes the internal content of the binary/not binary file, thus extensions shouldn't matter that much.
Christian
_________________
- Knowledge is Power -

[DannyB]

The big problem with using your own extensions is that your gui shell (i.e. Windows, KDE, GNOME, etc.) won't know to launch OOo for those documents. This is an unfortunant side effect of using extensions to convey information that should be metadata, ala, the classic Mac OS. Classic Mac didn't care about file extensions, because each file had other metadata (type/creator) that indicated what the document contained, and what application to launch it with.

In most "modern" systems, (Win, Kde, Gnome) the file extension is used to signify what application to launch and what icon to display for that document.

If you don't have any problems with the launching, i.e. double clicking of a document to start OOo, then I believe just as Cybb20 says that OOo won't have any trouble identifying what kind of document it is.
_________________
Want to make OOo Drawings like the colored flower design to the left?