Back

If your email is not recognized and you believe it should be, please contact us.

  • You must be logged in to reply to this topic.Login

Font corrupting when archiving

Return to Member Forum

  • Author
    Posts
    • #113876

      Hi, I’ve just switched from an ancient 2007 Mac to a new one, and have migrated all my programmes etc over. I’m using CS6 still (sorry!). I’ve just archived a document for the first time, and found one in particular has corrupted, whilst all others are ok. I’ve tried saving the working version of my document over the one with the problem, but the same thing happens when I open it. I need to supply completed files to my client, and can’t give them like this! Does anyone have any ideas, please? Thanks :)

    • #113877

      Have you tried saving as IDML file and working with that?

      • #113881

        Sorry, missed the reply option and did it in the wrong place… as I mention, long week!

    • #113879

      Ah, hadn’t thought of that! Long week :) I’ll give it a go!

    • #113880

      Unfortunately it’s exactly the same… original file still fine, but any copies corrupt

    • #113973
      Tim Murray
      Member

      What exactly do you mean by “archive”? Are you simply saving it to a different location other than your usual work area? Dragging the file somewhere, then opening it?

      • #114075

        Packaging, sorry – the client calls it archiving and it’s stuck with me. So no, not dragging, packaging files as usual

    • #114067

      After you Package your files, right click on the folder and Compress (to create a .zip file).

      If the fonts don’t work anymore, you can try using a font management app like Suitcase, or start replacing old fonts with new versions. Look for True Type and OTF fonts, .ttf and .otf extensions.

      • #114076

        Hi, thanks, tried it but still happening. If I don’t package fonts everything is ok. Screen looks fine on original document, and it PDFs fine for printing, only goes wrong when I’ve packaged. I’ve got Fontbook too, and unfortunately it’s a purchased font so I can’t easily replace (although I have reinstalled it from the original files, but still hasn’t solved the problem)

    • #114106
      Tim Murray
      Member

      Is the customer willing to purchase the fonts so that you can leave them out of the package, and then move on with the project so you can diagnose at your leisure? In my work, if something like this happens — and assuming I’m making okay $ on the project — I would just give them a credit on my invoice.

      Also, CS6 was released in 2012. Are you sticking with it because the customer has CS6? Again, in a situation like this, either I tell the customer I’m not working with something that old and forego the project, or I’d drag out my old Mac (which I kept, for real, just in case) and use that. In general, literally all of my software is kept the latest.

      • #114121

        Hi, thanks for getting back to me! Customer has the fonts too, so in theory shouldn’t be a problem, I’m just concerned that I can’t remedy the situation. And I know CS6 is old, unfortunately having just upgraded Mac and spending £800/month on nursery fees for the last few years has stumped any ability to upgrade software too for the time being. And so far it’s literally just one font that’s a problem, unfortunately it’s one of the client’s branding fonts, so can’t get round using it, but have just never come across the problem before. :)

    • #114136

      I think we need to restart your problem. It sounds like you should not use Package and keep the font folder separate. Remember, Package is only going to make a copy of the instances of the font (i.e. Regular and italic), not the entire set.

      I troubleshoot this sort of thing at work all the time, so contact me at email in Profile with specifics and maybe we can wrangle it to the ground!

Viewing 7 reply threads
  • The forum ‘General InDesign Topics (CLOSED)’ is closed to new topics and replies.
Forum Ads