Every file on Mac OS, as well as containing the data or code, can also contain a mini- database for text, pictures, menus etc. This is known as the resource fork. This allows you to localise a properly-written program using the resource forks without recompiling: you just need to change the contents of the resource fork. 4D, available in many languages, makes extensive use of this facility.
To implement equivalent features on Windows, each 4D file has a corresponding resource file, with an extension such as .RSR and .4DR. But when a file is moved from Mac OS to Windows, there is no standard way to represent the resource fork. This is why 4D created 4D Transporter to turn the resource fork into a separate file. If this was not done, once a 4D file was copied to Windows, it would already have lost its resource fork. Therefore, there is no way to implement Transporter on Windows.
Every Mac OS file can have both a resource fork and a data fork, as if it contained two files. The resource fork is not recognised by a PC. The 4D Transporter application "splits" any Mac OS file into two separate files, or recombines two such PC files into a single Mac OS file.
You must use 4D Transporter on the Mac OS to convert all 4D files in either direction.
International |
Company | Contact
4D | Site Map | Privacy
Policy | © 4D UK 1995-2008 | Change font size: [A]
[A]
[A]
| 