Skip to main content
P
ptc-19080751-Visitor
1-Visitor
May 15, 2013
Question

"Attempt to use non-existent character (61527)"

  • May 15, 2013
  • 15 replies
  • 2911 views
Does anyone know where I can find out what character this error message refers to?
Attempt to use non-existent character (61527) in font "Arial"
> - looking for slant=regular, weight=medium (500)
> - no substitute character exists in font "Arial Unicode MS"
Thanks!

Suzanne Napoleon
www.FOSIexpert.com
"WYSIWYG is last-century technology!"

    15 replies

    B
    18-Opal
    bfriesen18-Opal
    18-Opal
    May 15, 2013

    This was what I was told by PTC support for arbortext editor.



    In the error window it will tell you in brackets the number of the offending font (129,0x0081).



    You will use the first number to search for the bad font. This window will also tell you where to locate the bad font. If it says something about filename.style you need to look in the style sheet. If not it should tell you show you a path to the bad file.



    How this procedure works is that you give the character an atribute of "findit", then you search on that attribute. If you do not do this then you will not be able to search for the bad font asthere is nothing to search on.



    Open the document or fosi in Arbortext Editor. At the Arbortext Editor Command: line enter
    $FINDIT=chr(129) and hit the Enter key Now enter (find "$FINDIT") you may not need the quotes.



    Bryon

    P
    ptc-19080751-VisitorAuthor
    1-Visitor
    May 15, 2013
    Unfortunately, the error message was just what I quoted. No path, no file name. Only the five-digit number. I can't find any file that specifies characters that way.

    I am not aware of the FOSI generating any special character. However, the document does include some special characters. I guess I'll check it.

    Thanks!
    Suzanne


    C
    ClayHelberg18-Opal
    18-Opal
    May 15, 2013
    Hi Suzanne--



    That is a "private use" character, as shown in this Unicode Map website:
    D
    DavidS.Taylor1-Visitor
    1-Visitor
    May 15, 2013
    If you can search your document with a hex editor, Unicode 0xF057 would be a three byte character, ef 81 97.

    This has worked for me in the past. Often these characters have been inserted by MS Word for some internal purpose and are transparent in Arbortext until you try to compose the document.

    David

    David S. Taylor

    Project Manager, Structured Information
    Production and Marketing | Building Regulations | NRC Construction
    Building M-23A, Room 114 | 1200 Montreal Road | Ottawa, ON | K1A 0R6
    Telephone: 613-990-2731 | Fax: 613-952-4040
    David.S.Taylor@nrc-cnrc.gc.ca<">mailto:David.S.Taylor@nrc-cnrc.gc.ca>



    N
    naglists1-Visitor
    1-Visitor
    May 15, 2013
    Time to start halving the input.... 😕


    P
    ptc-19080751-VisitorAuthor
    1-Visitor
    May 15, 2013
    Thanks for all the informative replies! Silly me, I took the error message at face value.It never occurred to me I would have to convert the number. So I'm glad I asked. Now the info is in the archives.

    It turns out an off-brand PDF viewer isn't showing fi ligatures. So in the doc, which had come from Word, I tried replacing "fi" with "fi" and that seems to have worked 🙂

    Thanks again!
    Suzanne


    P
    ptc-19080751-VisitorAuthor
    1-Visitor
    May 15, 2013
    Hmmm ... changing fonts made the message come back.



    >----------
    N
    naglists1-Visitor
    1-Visitor
    May 15, 2013
    Unless you've disabled ligatures in Arbortext, it's probably a good idea to
    ensure that you can find find in a PDF. That is, confirm you can search for
    the word "find" and "flower" and words containing whatever the other
    ligatures are.

    fi
    fl

    Are the two I always remember.

    Why? Because there was a time when Arbortext used the ligature in the text
    of a PDF (not just in the "image"), too. When this was true, you couldn't
    do a search on such words because you were looking for f-i-n-d while the
    PDF contained fi-n-d. I do not know if that got fixed or not. We still
    suppress ligatures entirely.


    On Wed, May 15, 2013 at 10:48 AM, Suzanne Napoleon <
    SuzanneNapoleon@fosiexpert.com> wrote:

    > Thanks for all the informative replies! Silly me, I took the error message
    > at face value. It never occurred to me I would have to convert the
    > number. So I'm glad I asked. Now the info is in the archives.
    >
    > It turns out an off-brand PDF viewer isn't showing fi ligatures. So in the
    > doc, which had come from Word, I tried replacing "fi" with "fi" and that
    > seems to have worked 🙂
    >
    > Thanks again!
    > Suzanne
    >
    C
    ClayHelberg18-Opal
    18-Opal
    May 15, 2013
    Maybe there was more than one instance? Or maybe there are other
    ligatures that you didn't replace yet, such as "fl" or "ff" or "ffi" or
    ...



    Clay Helberg

    Senior Consultant



    TerraXML

    1380 Forest Park Circle, Suite 100

    Lafayette, CO 80027
    Show more replies
    Terms & ConditionsCookie settingsAccessibility statement