Getting Native files from a MAC, I need...

Hi everyone,



I have a question regarding Native Files obtained from MAC users.



I work on a PC and every company/person that gives me native files works on a MAC.



They always ZIP up the packaged InDesign File and send it over. And with every company that gives me files, there is always a _MACOSX folder, ALL EXCEPT FOR ONE!



I have done some research and what I've learned is, when you ZIP up a file on a MAC, an _MACOSX folder is usually created and inserted automatically. The MACOSX folder apparently contains all the ''resource fork'' data for each file inside.



So I take the file they sent and Unzip it, after I unzip the folder and open it up, inside there are 2 more folders, one name _MACOSX and the other is named after the project. Inside the folder named after the project is the usual stuff: link/fonts/.indd docments, etc.... But the problem is, the fonts in the fonts folder are all 0KB, but if I go into the fonts folder that is inside the _MACOSX folder, they all have a file size of 30-60kb.



So here's the thing...It's only the fonts from the _MACOSX folder that I am able to convert and use on my PC....I need that folder because it's impossible to convert a font that is 0kb



Which leads to what I am trying to find out. Why do some MACs always create that separate _MACOSX folder and some do not?????????



The person I am getting it from has no idea what I am talking about and I REALLY NEED to be able to tell him how to create the file so I can convert fonts here



Any help would be greatly appreciated



Thank you very much,
Getting Native files from a MAC, I need...
Normally there is nothing at all in the _MacOSX folder that you would need, so I take it you have a font conversion utility that converts Mac fonts for use on PC. This may or may not be a violation of the license for the fonts (most likely is, since you obviously don't have your own license for a PC version of the same font, which would eliminate the problem except for possible differences from different version numbers).



If you are collaborating with Mac people you should either standardize on OpenType fonts, which are cross-platform compatible, or on Windows flavored TrueType or Type 1 fonts. The former will work when placed in the Mac OS-X fonts folder, and the T1s will work if they are put into one of the private Adobe fonts folders (though they will not be available to non-Adobe applications).



In either case, to do this legally, you will each need to buy your own copies of the fonts in question.



Peter
Getting Native files from a MAC, I need...
you bring up an interesting point. And I have always had a few questions about that.



I thought that's why you package fonts up, so you can give it to the person who needs it, (i.e. printer, other designer). So then, is every person who packages fonts and sends them to someone else breaking the law?



Also it was to my understanding that when you purchase a font, doesn't the cost usually cover 1-5 license users? So wouldn't it be legal to provide the person who needs based on the idea that you are working with them?



Thanks a lot

When you run Package there is a warning (in CS3 and later, unless you've turned it off) regarding copyright and font licensing.



Every font foundry has it's own rules, but few of them allow you to give your font to the service provider unless he also pays for a license, though it is common practice to violate this provision. Using PDF with embedded fonts (and ID will not embed fonts that don't allow it for output, and tell you so, so you can pick a better font) bypasses that issue, but only for output. If you both need editing capability you both need the fonts.



I think you'll find, if you read your license agreement, that those that allow installation on more than one machine restrict use to a single organization (Adobe certainly does). If you work for these other people as an employee and log into their network to do your work from a remote location that might qualify, but an ordinary freelance arrangement would not, in my opinion. This actually has been discussed here before, I think, so you might find more by searching.



Seriously, though, if you plan on a long-term relationship with these people, you all should agree on a font collection to be used and you need to be prepared to invest some money in buying those fonts you don't already have. You may be able to buy just one or two at a time as new jobs come in, rather than forking over lots of money all at once. That's how most of us build our collections. Once you own a font license you can use it anywhere you like, not just for work with that collaboration.



Peter