Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Slightly O.T. (CCaption text import used with FCP)

  • Slightly O.T. (CCaption text import used with FCP)

    Posted by Greg Golden on May 31, 2006 at 4:44 pm

    Anyone using CCaption to close-caption Final Cut video projects? I have it and it works fine except for the way a plain text file imports into the captioning software window. Any use of an apostrophe or quotation marks gives a symbol that looks like a tilde above a vertical bar. This happens throughout the document. I’ve spoken to the MacCaption tech support and they say it shouldn’t do that, and they don’t know what else I can do different to prevent it. I am saving it from Word as a plain text file, just like they recommend. They (MacCaption) are stumped.

    Anybody else have a history of working through this problem?

    All versions of software, OS, etc. are the newest available. My Quad Core is brand new, fully updated. This doesn’t appear to be a hardware issue at all. I can playback the encoded movie and crop it on my timeline and see captions appearing as they are supposed to on a caption-enabled monitor. It’s just that darn symbol that replaces apostrophes and quotation marks.

    Thanks for your insight.

    Greg Golden

    David Bogie replied 19 years, 11 months ago 2 Members · 1 Reply
  • 1 Reply
  • David Bogie

    June 1, 2006 at 2:36 am

    I’m guessing this is font translation/substituion error between you, Microsoft, OS10 and your font of choice.

    Can you find the mystery glyph in the Character Palette? If you can identify the glyph, you can find its unicode; if you can find the unicode, you can compare that against the unicodes for the apostrophe and quote marks you’re trying to use in Word.

    I will say this: open and close and inner and outer quotes, apostrophes, accents, prime marks and tick marks are all different typgrophical glyphs but most people don’t know the differences. You may have Word set to use proper quote marks (substitute smart quotes prefs) but you may not have them in the font you are using. Or your conversion from using smart quotes to plain text may confuse Word, which is an insane program anyway.

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy