![]() Earlier versions of Windows won't be able to use these fonts, they were strictly Windows True Types, and with third party software you could use PostScript fonts too. Some of the newer, Open Type fonts may work just fine, without conversion with Windows Vista and above, because Windows started using the Open Type fonts starting with Vista. The PC can't copy the additional parts of the Mac file system on fonts that old. In this case the Mac won't be able to use them, as well as the PC. Second scenario is that they mounted the file share on the Mac, from a PC and copied the fonts over to a Windows server or PC. ![]() The PC will not be able to see these invisible extra parts, that is why they are zero length in file size. In this scenario then any Mac connecting and using those fonts won't have problems with the zero byte length, because they were copied there from the Mac to the Windows server, and all the parts are there, whether it be older fonts with data and resource forks, or PostScript with screen or printer fonts. Mac fonts of any type that were copied to a Windows server or PC and he is connecting from a PC to that Windows server, or is trying to use them locally on that PC. The library that I am looking in is a network fileshare that has a font file with no bytes in it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |