Posted: Fri Jun 25, 2004 7:16 am Post subject: file type detection
Hi all,
will there be any file type detection within OpenOffice 1.1.* working on MacOSX?
I was glad to find out that bothe OO1.12/X11 and NO/J 0.82 installed easily.
However, I tried to open some old Word document. OO1.12 just crashed, NO opend it as ASCII (although it was told to open as matching Word document).
I was annoyed that I had to copy the files from CD to disk just in order to add a ".doc" - otherwise both applications refused to list it when filtering on Word documents.
Will this limitation remain (getting rid of resource fork informations) or is it planned that OO will accept other info than the file ending?
Posted: Fri Jun 25, 2004 11:56 am Post subject: Re: file type detection
Martin Trautmann wrote:
However, I tried to open some old Word document. OO1.12 just crashed, NO opend it as ASCII (although it was told to open as matching Word document).
The MS Office filters only go back to v6.0, so if your "old Word document" was an older Word format, the current OOo Office filters don't support it.
Martin Trautmann wrote:
I was annoyed that I had to copy the files from CD to disk just in order to add a ".doc" - otherwise both applications refused to list it when filtering on Word documents.
Work-arounds for this (assuming a supported Office version) are 1) don't filter by document type in the OOo open/save boxes, 2) open the file by drag-drop on Neo/J or Start OpenOffice.org, or 3) Control-click on the document and use the Open With contextual menu to open the document (one-time only) in Neo/J or with Start OpenOffice.org*, or 4) tell the Finder to use Neo/J or Start OpenOffice.org* as the default application to open files with creators WDBN (some apps mistyped Word docs recieved from external sources with this older type), W6BN, W8BN.
* Currently, Start OpenOffice.org does not explicitly declare the Office filetypes as documents it can open, so it will not show up by default in the menus for these two options (Neo/J will), but you can select it via the "Other..." option. (Terry, if you read this, are there any plans to add explict creator code declarations in your Info.plist?)
Martin Trautmann wrote:
Will this limitation remain (getting rid of resource fork informations) or is it planned that OO will accept other info than the file ending?
It's not technically a resource-fork issue at all, though file type/creator codes and resource forks are both a function of the HFS (Plus) filesystem.
Apple's guidelines declare that an app should write out a document with all possible identifying information (type/creator, extension):
System Overview: Preparing Software for Mac OS X wrote:
When your application saves a document file, Apple recommends that it associate the proper filename extension with it, as well as any defined type and creator codes. [...] [Y]our application should always apply all valid forms of document typing, including extensions, when it saves its documents.
System Overview: Preparing Software for Mac OS X
The Mac OS X Filesystem: Filename Extensions wrote:
In addition to filename extensions, applications should also set a file type and optionally a creator type for any files they create.
The Mac OS X Filesystem: Filename Extensions
I can't speak for the guys who spend all of their free nights and weekends programming OOo for Mac, but one would hope that the future Aqua OOo would follow Apple guidelines and support metadata; however, I imagine that this is very complex, at the least, to add to the X11 product...
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum