• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Cocoa Text Handling Crashes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa Text Handling Crashes


  • Subject: Re: Cocoa Text Handling Crashes
  • From: Douglas Davidson <email@hidden>
  • Date: Tue, 7 Jan 2003 12:58:15 -0800

On Monday, January 6, 2003, at 06:38 PM, Andrew Thompson wrote:

In particular, I find its quite easy to get it to die by accidentally asking an NSCell subclass to render an NSAttributedString with only one character. The key problems occur if the character turns out to be mapped to NSNullGlyph in the current font and for some characters whose bounding box is an empty rectangle.

Sounds like a malformed font. Can you determine which fonts this occurs with, where you obtained them, and what characters the font handles improperly?

Douglas Davidson
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Cocoa Text Handling Crashes
      • From: Andrew Thompson <email@hidden>
References: 
 >Cocoa Text Handling Crashes (From: Andrew Thompson <email@hidden>)

  • Prev by Date: Re: Working with 32-bit Unicode (NSString stringWithUTF32String: (const UTF32Char *) bytes needed)
  • Next by Date: problems with loading nib files
  • Previous by thread: Cocoa Text Handling Crashes
  • Next by thread: Re: Cocoa Text Handling Crashes
  • Index(es):
    • Date
    • Thread