MHonArc v2.5.2 -->
ubl message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: Re: [ubl] UBL brochure
Hi,
With respect to the 'bin' suffix on files stored on the server,
yes I see the same behaviour with all types of files (.xml, .zip, etc).
For example, the JoineryOrderInstance1.xml file that Marion sent
(http://lists.oasis-open.org/archives/ubl-lcsc/200302/msg00051.html)
is stored as 'bin00008.bin' on the server. In those cases, to view
it from the list server what I do is save it to disk using the name
and suffix I know it should have (evident by the link name in the
message) and then open it from disk without any problem using the
appropriate application as it is configured on my system. However,
I have no problem directly viewing the same attachment if I click
on the corresponding mail message from within my mail reader, as
opposed to trying to read it from the list server. (This assumes
you to be on that particular list so you are also getting the
messages in your mailbox.)
I thought it might be a list server configuration issue, but I see
that, for instance, in some cases the list server has stored .zip
files correctly, but in other instances has also stored them as .bin.
So perhaps it's a list server bug?
I think this is a separate problem from the first one you describe
of opening OO files, but maybe not.
-Anne
"Burcham, Bill" wrote:
>
> I don't know if others are in the same boat, but I for one have trouble
> opening OpenOffice docs. I'm running 1.0.2 on Windows 2000 and I get
> unrecoverable application error on this document and others I've tried to
> open recently (e.g. the context methodology document from Gutentag).
>
> While we're on the subject, it is often the case that attachments to archive
> messages (like the one Jon cites below) are stored with a ".bin" suffix on
> the archive server (e.g.
> http://lists.oasis-open.org/archives/ubl-msc/200302/bin00000.bin is the
> ".swx" document in the message cited). My client software doesn't look at
> mime type or anything else -- it uses the file suffix to determine the
> application for viewing. This meant I had to manually select the
> application to view that document -- groveling around my system for the
> appropriate executable (only to then receive a UAE for my troubles).
>
>