Skip navigation
vpmorgan
vpmorgan
Currently Being Moderated

Can't type lowercase "u" or uppercase "C" in FrameMaker 10. Help??

Sep 4, 2012 3:28 PM

I am using Unstructured Frame 10.0.2.419 (as part of TCS 3) on Windows XP. I have been using this system on this computer for 9 months now and have never experienced this issue until today. I've been using Frame on and off since 2000 (since  v. 5.5.6) and have never seen this before anywhere. I'm hoping someone here has seen this behavior before and might have a solution.

 

Really, I'm hoping that I accidentally entered some kind of keystroke combination in Frame that enabled some phantom settings that I can easily disable by entering another magical set of keystrokes or clicking a checkbox somewhere. Or something.

 

This morning when I opened up my recent Frame books that I was working on Friday, I began editing them and soon noticed that the lowercase letter "u" would not appear when I typed it. I began the troubleshooting process:

 

  • Replaced keyboard, thinking it was something to do with the physical key. Nope.
  • Tried typing in other applications - every key types perfectly in all other applications.
  • Tried typing in the "Edit Marker" and "Edit Variables" panes in FrameMaker. The key works just fine there, too.
  • Closed all files and the application, then restarted FrameMaker. Made a wish... the files still behave the same.
  • Since I am on deadline, I decided to wait to Restart my entire computer until later in the day. No success after doing that either.
  • Began using the tedious shortcut of copying and pasting already-existing letter "u"s when I needed them (remember, this key worked on Friday) and soon thereafter discovered that I can type a lowercase "c" but not an uppercase one. Sigh.
  • Opened a book file I haven't worked on in over a month to see if the problem is localized to my specific book or has infected the entire application. Result: It makes no difference what Frame file I open; the behavior persists.
  • Google searched to see if I could find any related problems with solutions posted somewhere. Couldn't.

 

I do realize that "U" and "C" quite possibly have something to do with shortcut keys to Underline and Cut or something, but I have not made any changes to the application, the .ini file, or even assigned any new shortcut keys since leaving work Friday for the holiday weekend. Or even before Friday, for that matter.

 

Any suggestions or help are very much appreciated. I am mystified.

 

Thank you in advance,

Virginia

1148 Views   7 Replies   Latest reply: vpmorgan, Sep 5, 2012 8:39 AM
 
Replies
  • Harpreet seehra
    Currently Being Moderated
    1. Harpreet seehra,
    Sep 4, 2012 3:46 PM   in reply to vpmorgan
    Report

    Go ahead and rename the maker.ini file to makerold.ini making sure the FM 10 is closed and restart FM 10 once renamed and try and type the alphabets now.

     

    In case it does not launch after renaming,just name it back to maker.ini

     

     

    Harpreet

     
    |
    Mark as:
  • Mike Wickham
    Currently Being Moderated
    2. Mike Wickham,
    Sep 4, 2012 5:41 PM   in reply to vpmorgan
    Report

    Did you recently install any "ExtendScripts of the Week?" I recall that

    there were a couple of those that had a bug on initial release that

    wouldn't allow the typing of the lowercase "u". Fixes were released.

    Unfortunately, I can't remember which scripts.

     
    |
    Mark as:
  • vpmorgan
    Currently Being Moderated
    3. vpmorgan,
    Sep 4, 2012 6:27 PM   in reply to Mike Wickham
    Report

    Hi Mike -

     

    Thank you for jogging my memory: last week, I believe I did install an Extend Script of the Week, though I did not try running it yet. (It was one of the ones mentioned in a post in the forums last week.) I went to try and see which one it was/uninstall it, but my work computer has now completely locked up and won't restart. I will have to work with IT to get the computer running in the morning and report back. I will look for a fix for the plug-in. Alternatively, would just uninstalling it work?

     

    Thanks again - Virginia

     
    |
    Mark as:
  • Mike Wickham
    Currently Being Moderated
    4. Mike Wickham,
    Sep 4, 2012 7:52 PM   in reply to vpmorgan
    Report

    Yes, if it's the ExtendScript that is causing the problem, merely

    uninstalling the script will fix things. You can then hunt for the

    repaired version of the script.

     
    |
    Mark as:
  • vpmorgan
    Currently Being Moderated
    5. vpmorgan,
    Sep 5, 2012 7:32 AM   in reply to Mike Wickham
    Report

    Thank you Mike! The IT department got my work laptop up and running this morning, I uninstalled the ExtendScripts (I had an Archive one and a ChangeFormats one - I just took them both out for safe measure). Then, I opened FrameMaker, and voila! I can type normally. Now, to find repaired versions...or ignore those ExtendScripts altogether.

     

    Regards,

     

    Virginia

     
    |
    Mark as:
  • Error7103
    Currently Being Moderated
    6. Error7103,
    Sep 5, 2012 8:20 AM   in reply to vpmorgan
    Report

    > Began using the tedious shortcut of copying and pasting already-existing letter ...

     

    In this tight economy, you may just have to make do with fewer letters.

     

    Another alternative is to set up Variables for letters you can no longer afford:

    Name: letter.C

    Def: \x43

     

    Name: letter.u

    Def: \x75

     

    Typing the Names might be challenging.

     

    You could also use Unicode code points, but then typing the \u arises.

     
    |
    Mark as:
  • vpmorgan
    Currently Being Moderated
    7. vpmorgan,
    Sep 5, 2012 8:39 AM   in reply to Error7103
    Report

    Thank you for the creative suggestions, Error. Mike Wickham successfuly diagnosed the source of my problems: an ExtendScript of the Week that causes this bug. I had downloaded a couple of these last week when someone mentioned their usefulness in the forums (Archive and Create Formats), but had not tried to use them yet. Uninstalling the buggy scripts resolved my issue.

     

    -Virginia

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points