VV font handling issues

[workflow]

We have a problem recovering font files that were backed up by ViceVersa – they come back as zero K. These fonts have always been stored on NTFS partitions – so we are expecting mac data fork / resource fork to be intact

Possibly all of the Postcript type 1 and screen fonts (.scr) are coming back as zero kb (0K), and they cannot be opened by application , futhermore font utility fails to read them - errors complaining that there is missing data?

This is a serious problem for customer.

Q1. Please confirm viceversa font handling / outstanding problems with fonts... How does viceversa handle mac originated data fork / resource forks contained on NTFS server partions? Does VV have a problem with daling with certain types of fonts? Can you list which types are a problem?

Point is that our initial tests showed fonts copied onto a SATA drive via a pc that was then plugged into a mac via usb showed that font data was intact.

Q2. Are there any special settings in ViceVersa for font-handling?

Q3. Has font handling been improved / being improved – customer is using 2.5 but they may have upgraded from 2.0. i.e some of the backup may have been carried out under 2.0

Q4. Some files are coming back with time stamp errors... Mostly fonts but some others types like illustrator does this mean that they will be corrupt? If ViceVersa copied them fine why should there be errors bringing them back?

Q5. I didn't get any search results for font problems on forum or FAQs?

[glenbetts]

We too are experiencing the same problem with Type 1 fonts on NTFS partitions. Is this a known bug and if so is there a time frame for a fix?

[TGRMN Software]

Hello

can you contact support@tgrmn.com please for further analysis.

thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com