Does anyone have mimemap entries for things like .xlsx and .pptx files? I get all my email sent to my Iyonix which sometimes includes such
attachments. It would be useful if when I moved them to a Windows
machine to open them I did not have to rename them to get the filetype
correct.
-- ------------------------------------------------------------- Rob Hemmings Southport
In article <528da2ba08robn...@rgvk.co.uk>,
Rob Hemmings (news2) <robn...@rgvk.co.uk> wrote:
> Does anyone have mimemap entries for things like .xlsx and
> .pptx files? I get all my email sent to my Iyonix which
> sometimes includes such attachments. It would be useful if
> when I moved them to a Windows machine to open them I did
> not have to rename them to get the filetype correct.
If you do get any suggestions Rob then can you please pass
them to Tim who is maintaining a very useful resource at http://www.timil.com/riscos/mimemap which could replace your existing
!Boot.Resources.!Internet.files.MimeMap
In article <528db7a193n...@ned.uk.invalid>,
NedA <n...@ned.uk.invalid> wrote:
> In article <528da2ba08robn...@rgvk.co.uk>,
> Rob Hemmings (news2) <robn...@rgvk.co.uk> wrote:
> > Does anyone have mimemap entries for things like .xlsx and
> > .pptx files? I get all my email sent to my Iyonix which
> > sometimes includes such attachments. It would be useful if
> > when I moved them to a Windows machine to open them I did
> > not have to rename them to get the filetype correct.
> If you do get any suggestions Rob then can you please pass
> them to Tim who is maintaining a very useful resource at > http://www.timil.com/riscos/mimemap > which could replace your existing
> !Boot.Resources.!Internet.files.MimeMap > Theres notes at the bottom of the page.
Thanks very much for the suggestion, I'm already using Tim's very useful
mimemap file but I'm certainly happy to pass on any suggestions to him.
-- ------------------------------------------------------------- Rob Hemmings Southport
> In article<528db7a193n...@ned.uk.invalid>,
> NedA<n...@ned.uk.invalid> wrote:
>> In article<528da2ba08robn...@rgvk.co.uk>,
>> Rob Hemmings (news2)<robn...@rgvk.co.uk> wrote:
>>> Does anyone have mimemap entries for things like .xlsx and
>>> .pptx files? I get all my email sent to my Iyonix which
>>> sometimes includes such attachments. It would be useful if
>>> when I moved them to a Windows machine to open them I did
>>> not have to rename them to get the filetype correct.
>> If you do get any suggestions Rob then can you please pass
>> them to Tim who is maintaining a very useful resource at
>> http://www.timil.com/riscos/mimemap >> which could replace your existing
>> !Boot.Resources.!Internet.files.MimeMap
>> Theres notes at the bottom of the page.
> Thanks very much for the suggestion, I'm already using Tim's very useful
> mimemap file but I'm certainly happy to pass on any suggestions to him.
In article <4fac0fe8$0$295$14726...@news.sunsite.dk>,
Alex Macfarlane Smith <nos...@archifishal.co.uk> wrote:
> In terms of MIME types:
> .xlsx
> application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
> .xltx
> application/vnd.openxmlformats-officedocument.spreadsheetml.template
> .ppsx
> application/vnd.openxmlformats-officedocument.presentationml.slideshow
> .pptx
> application/vnd.openxmlformats-officedocument.presentationml.presentation
> .docx
> application/vnd.openxmlformats-officedocument.wordprocessingml.document
> .dotx
> application/vnd.openxmlformats-officedocument.wordprocessingml.template
> But I don't know if any of those have officially allocated filetypes on > RISC OS.
I'm not sure there is currently a need to filetype them really.
Although the official label is "openxml" they are actually a bastardised
xml only used by microsoft.
RISC OS has no available converters.
To the OP I would suggest that you tell the senders that you don't have
that version of MS Office. People are used to dealing with others who only
have the older office formats that can't deal with the new formats or
convert them.
In message <528e108f44spam.pl...@btinternet.com>
spampling <spam.pl...@btinternet.com> wrote:
> In article <4fac0fe8$0$295$14726...@news.sunsite.dk>,
> Alex Macfarlane Smith <nos...@archifishal.co.uk> wrote:
>> In terms of MIME types:
>> [...]
>> .docx
>> application/vnd.openxmlformats-officedocument.wordprocessingml.document
>> [...]
>> But I don't know if any of those have officially allocated filetypes on
>> RISC OS.
.docx is MSWordX (&A7E)
> I'm not sure there is currently a need to filetype them really.
> Although the official label is "openxml" they are actually a bastardised
> xml only used by microsoft.
Not sure what you mean by "bastardised". These are publicly documented standardised XML-based file formats.
> RISC OS has no available converters.
Easi/TechWriter 9.0 reads .docx files.
-- Martin
---------------------------------------------------------------------
Martin Wuerthner MW Software http://www.mw-software.com/ RISC OS Software for Design, Printing and Publishing
---------------------------------------------------------------------
> To the OP I would suggest that you tell the senders that you don't have
> that version of MS Office. People are used to dealing with others who only
> have the older office formats that can't deal with the new formats or
> convert them.
A few "People are used to dealing with others who only have the older office
formats"
Fewer are willing to do anything about it.
I've been getting Solicitors letters in my role of Trustee, they insist on
sending them in docx format, I'd expect only a minority of Joe Public would
already have software installed that would read docx, and many would not know
about MS's Word Viewer. I'm paying for this poor service, because of this and other silliness on
their part I do not recommend Meade King.
Chris Evans
-- CJE Micro's / 4D 'RISC OS Specialists'
Telephone: 01903 523222 Fax: 01903 523679
ch...@cjemicros.co.uk http://www.cjemicros.co.uk/ 78 Brighton Road, Worthing, West Sussex, BN11 2EN
The most beautiful thing anyone can wear, is a smile!
<ch...@cjemicros.co.uk> wrote:
> I've been getting Solicitors letters in my role of Trustee, they insist on
> sending them in docx format, I'd expect only a minority of Joe
Public
Seznd a polite letter saying that as they have continually failed to provide communications in a legible format despite this having been brought to their attention...
...further payment will be withheld until such time as the communications become legible.
That might concentrate their minds on the two extra mouse clicks necessary in the "save" dialog(ue) [format, pick a type, ie RTF or Word97].
In article <528da2ba08robn...@rgvk.co.uk>,
Rob Hemmings (news2) <robn...@rgvk.co.uk> wrote:
> Does anyone have mimemap entries for things like .xlsx and .pptx files? > I get all my email sent to my Iyonix which sometimes includes such
> attachments. It would be useful if when I moved them to a Windows
> machine to open them I did not have to rename them to get the filetype
> correct.
In a related point, I'm using Tim Hill's mimemap file which does include
an entry for .docx format files. This seems to enable me to see such
files correctly typed via Lanman98 but when they arrive via Hermes and
Pluto the attachments are typed as text files. Does anyone know why that
is happening?
I think the ones I've noticed are from Hotmail users so is it another Hotmail
failing?
-- ------------------------------------------------------------- Rob Hemmings Southport
In article <528e3594e4robn...@rgvk.co.uk>,
Rob Hemmings (news2) <robn...@rgvk.co.uk> wrote:
> In article <2ce2198e52.mar...@bach.planiverse.com>, Martin Wuerthner
> <spamt...@mw-software.com> wrote:
> <Snip>
> > Easi/TechWriter 9.0 reads .docx files.
> Yes, I have the latest version of Techwriter for that purpose - it is
> very useful.
<spamt...@mw-software.com> wrote:
> In message <528e108f44spam.pl...@btinternet.com> spampling
> <spam.pl...@btinternet.com> wrote:
> > In article <4fac0fe8$0$295$14726...@news.sunsite.dk>, Alex Macfarlane
> > Smith <nos...@archifishal.co.uk> wrote:
> >> In terms of MIME types:
> >> [...] .docx
> >> application/vnd.openxmlformats-officedocument.wordprocessingml.document
> >> [...] But I don't know if any of those have officially allocated
> >> filetypes on RISC OS.
> .docx is MSWordX (&A7E)
> > I'm not sure there is currently a need to filetype them really.
> > Although the official label is "openxml" they are actually a
> > bastardised xml only used by microsoft.
> Not sure what you mean by "bastardised". These are publicly documented
> standardised XML-based file formats.
MS modified them and parts are not fully documented - loads of stories out
there with people complaining about that not so minor detail.
> > RISC OS has no available converters.
> Easi/TechWriter 9.0 reads .docx files.
Nice.
and the converters for the other application outputs?
In message <528e346cecrobn...@rgvk.co.uk>
on 11 May 2012 Rob Hemmings (news2) wrote:
> In a related point, I'm using Tim Hill's mimemap file which does include an
> entry for .docx format files. This seems to enable me to see such files
> correctly typed via Lanman98 but when they arrive via Hermes and Pluto the
> attachments are typed as text files. Does anyone know why that is
> happening?
> I think the ones I've noticed are from Hotmail users so is it another
> Hotmail failing?
It could be a problem at either end. You need to open the raw e-mail and
look at the Content-Type declaration for the attachment. If it's text/plain
then the problem is at the other end. If it's the correct MIME-type for
docx, then the problem is at your end.
In article <80a5968e52.Matt...@sinenomine.freeserve.co.uk>, Matthew
Phillips <spam20...@yahoo.co.uk> wrote:
> In message <528e346cecrobn...@rgvk.co.uk>
> on 11 May 2012 Rob Hemmings (news2) wrote:
> > In a related point, I'm using Tim Hill's mimemap file which does
> > include an entry for .docx format files. This seems to enable me to
> > see such files correctly typed via Lanman98 but when they arrive via
> > Hermes and Pluto the attachments are typed as text files. Does
> > anyone know why that is happening?
> > I think the ones I've noticed are from Hotmail users so is it another
> > Hotmail failing?
> It could be a problem at either end. You need to open the raw e-mail
> and look at the Content-Type declaration for the attachment. If it's
> text/plain then the problem is at the other end. If it's the correct
> MIME-type for docx, then the problem is at your end.
Thanks Matthew. The final part of the header for the email is as below
so I guess that means the problem is with Hotmail. Typical!
> In article <80a5968e52.Matt...@sinenomine.freeserve.co.uk>, Matthew
> Phillips <spam20...@yahoo.co.uk> wrote:
> > In message <528e346cecrobn...@rgvk.co.uk>
> > on 11 May 2012 Rob Hemmings (news2) wrote:
> > > In a related point, I'm using Tim Hill's mimemap file which does
> > > include an entry for .docx format files. This seems to enable me to
> > > see such files correctly typed via Lanman98 but when they arrive via
> > > Hermes and Pluto the attachments are typed as text files. Does
> > > anyone know why that is happening?
> > > I think the ones I've noticed are from Hotmail users so is it another
> > > Hotmail failing?
> > It could be a problem at either end. You need to open the raw e-mail
> > and look at the Content-Type declaration for the attachment. If it's
> > text/plain then the problem is at the other end. If it's the correct
> > MIME-type for docx, then the problem is at your end.
> Thanks Matthew. The final part of the header for the email is as below
> so I guess that means the problem is with Hotmail. Typical!
No, you need to look further down. The structure of the whole message would
typically be as follows:
1. Main headers of e-mail, which end with a blank line (in your example,
after the X-AntiAbuse line. In a message with an attachment one of the main
headers will be a line like:
(the boundary can be anything that is not going to appear in the body of the
message).
2. You would then get the body of the e-mail message, indicated by a line
matching the boundary above, but with two hyphens preceding. The boundary
marker is followed by header lines describing that chunk. In your example,
it is of content type "multipart/alternative". This is usually found with an
email where it has been sent in two formats, for example plain text and HTML. So what you have above is a container within a container: the
multipart/alternative indicates that we have two or more chunks which contain
the same content, and the e-mail client is supposed to display the richest
one it can. There is another boundery marker, for the alternative
formats of the message. Then you get the declaration of the first, with
content type text/plain.
3. Further down you would get any other alternative formats. I would expect
to find a section of text/html containing the message text in HTML.
4. Eventually you would reach the top-level boundary marker again (the one
ending "99d_" in your case) and the first file attachment would be declared. It is the headers immediately after that which are relevant. The
content-type would tell you what MIME type had been declared, and the content
disposition would declare it to be an attachment and possibly give a
filename. Here is an example from a message in my inbox:
------=_NextPart_001_0007_01CD2A3C.67CB6640--
------=_NextPart_000_0006_01CD2A3C.67CB6640
Content-Type: application/msword;
name="News-sheet 6 May 2012.doc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="News-sheet 6 May 2012.doc"
0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAACAAAAjAAAAAAAAAA A
EAAAigAAAAEAAAD+////AAAAAI8AAACNAAAA/////////////////////////////////////// /
/////////////////////////////////////////////////////////////////////////// /
....
Word documents and other binary formats like zip files will usually be
encoded for transfer as base64, which looks like the example above, that is,
lots of lines all the same length containing uooer and lower case letters,
digits, plus and slash.
So if you locate the headers pertaining to the attachment, you will be able
to find out whether the problem is at your end or HotMail's.
> In message <528ea09aecrobn...@rgvk.co.uk>
> on 12 May 2012 Rob Hemmings (news2) wrote:
> > In article <80a5968e52.Matt...@sinenomine.freeserve.co.uk>, Matthew
> > Phillips <spam20...@yahoo.co.uk> wrote:
> > > In message <528e346cecrobn...@rgvk.co.uk>
> > > on 11 May 2012 Rob Hemmings (news2) wrote:
> > > > In a related point, I'm using Tim Hill's mimemap file which does
> > > > include an entry for .docx format files. This seems to enable me
> > > > to see such files correctly typed via Lanman98 but when they
> > > > arrive via Hermes and Pluto the attachments are typed as text
> > > > files. Does anyone know why that is happening?
> > > > I think the ones I've noticed are from Hotmail users so is it
> > > > another Hotmail failing?
> > > It could be a problem at either end. You need to open the raw
> > > e-mail and look at the Content-Type declaration for the attachment.
> > > If it's text/plain then the problem is at the other end. If it's
> > > the correct MIME-type for docx, then the problem is at your end.
<Snip>
> No, you need to look further down. The structure of the whole message
> would typically be as follows:
<Snip - very useful explanation - thanks>
Thanks for that explanation. I've now found the following which I think
does make it look as though the information coming from Hotmail is
correct?
> In message<528e108f44spam.pl...@btinternet.com>
> spampling<spam.pl...@btinternet.com> wrote:
>> I'm not sure there is currently a need to filetype them really.
>> Although the official label is "openxml" they are actually a bastardised
>> xml only used by microsoft.
> Not sure what you mean by "bastardised". These are publicly documented
> standardised XML-based file formats.
Publicly documented; yes, a implementable standard; no.
You can fly a fully loaded 747 through the holes in the 6,000 pages of the specification. Things like a muddle of different date systems bearing no releationship to anything else on the planet, references to proprietary behaviour with tags like footnoteLayoutLikeWW8 or useWord2002TableStyleRules, etc, etc.
In article <jorns0$8c...@dont-email.me>,
druck <n...@druck.org.uk> wrote:
> On 11/05/2012 09:29, Martin Wuerthner wrote:
> > In message<528e108f44spam.pl...@btinternet.com>
> > spampling<spam.pl...@btinternet.com> wrote:
> >> I'm not sure there is currently a need to filetype them really.
> >> Although the official label is "openxml" they are actually a bastardised
> >> xml only used by microsoft.
> > Not sure what you mean by "bastardised". These are publicly documented
> > standardised XML-based file formats.
> Publicly documented; yes, a implementable standard; no.
> You can fly a fully loaded 747 through the holes in the 6,000 pages of > the specification. Things like a muddle of different date systems > bearing no releationship to anything else on the planet, references to > proprietary behaviour with tags like footnoteLayoutLikeWW8 or > useWord2002TableStyleRules, etc, etc.
In article <528f207544robn...@rgvk.co.uk>, Rob Hemmings (news2)
<robn...@rgvk.co.uk> wrote:
> However, Pluto still shows the file as type Text. Can anyone suggest
> what is going wrong and/or should I raise this on the Pluto mailing
> list instead?
Has EW already been 'seen' by the filer and therefore defined the docx
filetype before the email is fetched?
In message <529037a89d...@invalid.org.uk>
Tim Hill <t...@invalid.org.uk> wrote:
> In article <528f207544robn...@rgvk.co.uk>, Rob Hemmings (news2)
> <robn...@rgvk.co.uk> wrote:
>> However, Pluto still shows the file as type Text. Can anyone suggest
>> what is going wrong and/or should I raise this on the Pluto mailing
>> list instead?
> Has EW already been 'seen' by the filer and therefore defined the docx
> filetype before the email is fetched?
That should not make any difference. The MimeMap contains the mapping from the MIME type to the RISC OS type. This mechanism does not rely on the application defining the type.
Maybe Pluto does not like long MIME type names? The one for .docx has 71 characters, far more than any other in my MimeMap.
-- Martin
---------------------------------------------------------------------
Martin Wuerthner MW Software http://www.mw-software.com/ RISC OS Software for Design, Printing and Publishing
---------------------------------------------------------------------
> That should not make any difference. The MimeMap contains the mapping
> from the MIME type to the RISC OS type. This mechanism does not rely
> on the application defining the type.
I was grasping at straws.
> Maybe Pluto does not like long MIME type names? The one for .docx has
> 71 characters, far more than any other in my MimeMap.
That wouldn't surprise me, given its other hard-wired limitations.
In article <52903a49a4...@invalid.org.uk>,
Tim Hill <t...@invalid.org.uk> wrote:
> In article <34ba399052.mar...@bach.planiverse.com>, Martin Wuerthner
> <spamt...@mw-software.com> wrote:
> [Snip]
> > That should not make any difference. The MimeMap contains the mapping
> > from the MIME type to the RISC OS type. This mechanism does not rely
> > on the application defining the type.
> I was grasping at straws.
> > Maybe Pluto does not like long MIME type names? The one for .docx has
> > 71 characters, far more than any other in my MimeMap.
> That wouldn't surprise me, given its other hard-wired limitations.
Interesting - that could well be the problem although I have just noticed
that there is a difference in attachments received using your (Tim's)
mimemap compared with the one that I had before! With my previous one
the .docx attachments are shown as with a file type of Data but with your
mimemap they are shown with a type of Text. This seems rather strange!
-- ------------------------------------------------------------- Rob Hemmings Southport
In article <5291fa16afrobn...@rgvk.co.uk>,
Rob Hemmings (news2) <robn...@rgvk.co.uk> wrote:
> Interesting - that could well be the problem although I have just noticed
> that there is a difference in attachments received using your (Tim's)
> mimemap compared with the one that I had before! With my previous one
> the .docx attachments are shown as with a file type of Data but with your
> mimemap they are shown with a type of Text. This seems rather strange!
Hmmm, I'm sure the last time I recieved a .docx it showed up correctly and
double-clicking on the attachment loaded Techwriter and displayed it.
However, I don't currently have one to try, since the church office were
persuaded to send out all notices etc as .pdf
In article <5292368d2fSpam...@argonet.co.uk>, Stuart
<Spam...@argonet.co.uk> wrote:
> In article <5291fa16afrobn...@rgvk.co.uk>, Rob Hemmings (news2)
> <robn...@rgvk.co.uk> wrote:
> > Interesting - that could well be the problem although I have just
> > noticed that there is a difference in attachments received using
> > your (Tim's) mimemap compared with the one that I had before! With
> > my previous one the .docx attachments are shown as with a file type
> > of Data but with your mimemap they are shown with a type of Text. > > This seems rather strange!
> Hmmm, I'm sure the last time I received a .docx it showed up
> correctly and double-clicking on the attachment loaded Techwriter and
> displayed it.
On my RISC PC .docx documents show up as "data".
If I double click on them I get a "message from Pluto" saying: "Can't
run this filetype". (This is even with the Techwriter icon on the
iconbar.)
If I drag it from the e-mail on to the TechWriter icon I get the
"Message from Techwriter": "Could not open file because: TechWriter
cannot open this type of file."
If I drag it to the RAM Disc and double click on it I get an error
message saying "An application that loads a file of this type has not
been found by the Filer. Open an application display containing the
required application and try again."
However, if I drag it from the RAM Disc on to the TechWriter icon, it
opens up and I can read it.
> In article <52903a49a4...@invalid.org.uk>,
> Tim Hill <t...@invalid.org.uk> wrote:
>> In article <34ba399052.mar...@bach.planiverse.com>, Martin Wuerthner
>> <spamt...@mw-software.com> wrote:
>> [Snip]
>>> That should not make any difference. The MimeMap contains the mapping
>>> from the MIME type to the RISC OS type. This mechanism does not rely
>>> on the application defining the type.
>> I was grasping at straws.
>>> Maybe Pluto does not like long MIME type names? The one for .docx has
>>> 71 characters, far more than any other in my MimeMap.
>> That wouldn't surprise me, given its other hard-wired limitations.
> Interesting - that could well be the problem although I have just noticed
> that there is a difference in attachments received using your (Tim's)
> mimemap compared with the one that I had before! With my previous one
> the .docx attachments are shown as with a file type of Data but with your
> mimemap they are shown with a type of Text. This seems rather strange!
Not at all. It all boils down to how unknown Mime types are mapped.
The original MimeMap maps all unknown types to Data.
Tim Hill's MimeMap maps all unknown type to Text.
So, that confirms that the type of the given files is not found in your MimeMap. That is exactly what you would expect happen if Pluto truncated the Mime type to a fixed length.
-- Martin
---------------------------------------------------------------------
Martin Wuerthner MW Software http://www.mw-software.com/ RISC OS Software for Design, Printing and Publishing
---------------------------------------------------------------------
