Re: Missing MIMEMAP entries
"David J. Ruck" <druck@...> said:
> On 17/03/2015 11:10, Richard Mellish wrote:
>> I'm starting a thread here on this list because I've often seen the
>> same thing in other contexts than email attachments, though I've never
>> established exactly when it happens and when it doesn't.
>>
>> I have a file on the Windows side, I do SOMETHING with it on the RISC
>> OS side, and it acquires the additional comma-extension, which of
>> course prevents even the relevant local Windows application from
>> understanding it.
> I assume you are talking about editing a file using Virtual Acorn,
> rather than email the file between a PC and RISC OS.
It has indeed been with VirtualRPC that I have had this trouble,
normally accessing the files with HostFS. But it seemed to happen
without my obviously opening the file at all, let alone editing it.
I'm really not sure what actions caused it, but I think copying (using
the RISC OS filer) may have been one of them and renaming using Nick
Roberts's !Rename application may have been another.
I haven't (yet) observed it with my ARMX6, using LanMan98, but I have
only had the new machine for a few weeks.
> For Virtual Acorn, you need to make sure that its file type mappings
> include all the types of file you want to handle from both machines.
> Then file will appear on RISC OS as name/ext and it will have the
> correct file type.
Indeed, and I did set up mappings for some frequently-encountered
types such as .xlsx. But other types come up occasionally and it's a
nuisance to have to add them to the mappings.
> For emailing you need the MIMEMAP file set up, so the correct RISC OS
> file type is set when receiving files, and it wont change the name when
> sending files. You also need to name the file name/ext so that a PC will
> get the right file name and recognise it from its extension.
Richard
______________________________________________________________________
This message was sent via the messenger-l mailing list
To unsubscribe, mail messenger-l+unsubscribe@...
|