The error I get is that when copying text from the Mac environment and pasting into the Windows one the pasted text misses the carriage return and first word at the start of every paragraph from paragraph two onwards. This then means comparison and then typing in the missing words which is incredibly time consuming.
This is a long-standing niggle. Initially I thought it was the particular hosted application but since the bug occurs with many hosted application in the Windows environment, even with NotePad (and not TextMate in the Mac environment) it looks to be an error in the movement of the text from the Mac's clipboard to the hosted Windows one.
Example
I apologise the the technical-sounding nature of the text but this is what I tried to report using the VMWare Technical support under MyVMWare) which steadfastly refuses to let me post any fault whatsoever. simply responding with 'Unable to Complete Your Request' (PLEASE FIX!)
1. The initial text in the Mac application is:
'Introduction
The TRAK metamodel defines the object types (stereotypes) and relationships that can appear within the TRAK architecture viewpoints and therefore TRAK architecture views. In effect it defines the language used to describe the real world in a TRAK architecture description.
As such the metamodel does not need to contain representations of the mechanisms that TRAK itself uses to enforce or manage (which may be through textual requirements) - it only needs to contain elements that can appear in TRAK viewpoints and views. It is deliberately user- rather than specifier-centric. Any metamodel type that does not appear in a TRAK viewpoint represents an overhead. It is important to keep the size of the TRAK metamodel as small as possible.
The purpose of the metamodel is also to constrain and improve consistency..'
2. The resulting pasted text in the Windows application is:
'Introduction
The TRAK metamodel defines the object types (stereotypes) and relationships that can appear within the TRAK architecture viewpoints and therefore TRAK architecture views. In effect it defines the language used to describe the real world in a TRAK architecture description. such the metamodel does not need to contain representations of the mechanisms that TRAK itself uses to enforce or manage (which may be through textual requirements) - it only needs to contain elements that can appear in TRAK viewpoints and views. It is deliberately user- rather than specifier-centric. Any metamodel type that does not appear in a TRAK viewpoint represents an overhead. It is important to keep the size of the TRAK metamodel as small as possible.purpose of the metamodel is also to constrain and improve consistency.'
i.e. the missing text, highlighted in red is:
Introduction
The TRAK metamodel defines the object types (stereotypes) and relationships that can appear within the TRAK architecture viewpoints and therefore TRAK architecture views. In effect it defines the language used to describe the real world in a TRAK architecture description.
As such the metamodel does not need to contain representations of the mechanisms that TRAK itself uses to enforce or manage (which may be through textual requirements) - it only needs to contain elements that can appear in TRAK viewpoints and views. It is deliberately user- rather than specifier-centric. Any metamodel type that does not appear in a TRAK viewpoint represents an overhead. It is important to keep the size of the TRAK metamodel as small as possible.
The purpose of the metamodel is also to constrain and improve consistency..
+ it is missing the carriage associated carriage returns.