Cocoa框架中日文字符打印异常问题求助

Hey David, let's walk through practical, actionable steps to diagnose why characters like 「写」 aren't rendering as expected with most fonts (except HiraginoKaku and HiraginoMaru) in your Cocoa app:

• Verify Unicode Codepoint and Font Glyph Support
  First, confirm the character itself isn't being mangled in your code. Check that your string correctly references the Unicode scalar U+5199 (the codepoint for 「写」) with this quick snippet:

  NSString *targetChar = @"写";
  for (NSUnicodeScalar scalar in targetChar.unicodeScalars) {
      NSLog(@"Character Unicode: U+%04X", scalar.value);
  }
  

  Next, check if the problematic font actually includes a glyph for this character. A return value of 0 from Core Text means the font lacks the glyph, forcing a system fallback that might fail:

  NSFont *problemFont = [NSFont fontWithName:@"AffectedFontName" size:14];
  CTFontRef ctFont = CTFontCreateWithName((__bridge CFStringRef)problemFont.fontName, problemFont.pointSize, NULL);
  CGGlyph glyph = CTFontGetGlyphForCharacter(ctFont, 0x5199);
  NSLog(@"Glyph ID for 写: %u", glyph);
  CFRelease(ctFont);
  

• Inspect the Font Fallback Chain
  Cocoa uses a fallback system to pick alternative fonts when the primary font lacks a glyph. Check which fonts the system is trying to use as fallbacks for your problematic font:

  NSFontDescriptor *fontDescriptor = [NSFontDescriptor fontDescriptorWithName:@"AffectedFontName" size:14];
  NSArray *matchingDescriptors = (__bridge NSArray *)CTFontDescriptorCreateMatchingFontDescriptors((__bridge CTFontDescriptorRef)fontDescriptor, NULL);
  for (NSFontDescriptor *desc in matchingDescriptors) {
      NSLog(@"Fallback font: %@", desc.fontAttributes[NSFontNameAttribute]);
  }
  

  If the fallback list doesn't include a font that supports 「写」, you might need to explicitly add a valid fallback font to your font descriptor using NSFontDescriptorAttributeTraits.

• Check Printing Context Specifics
  Since this issue occurs when printing (not just on-screen), the print context might have unique settings interfering. Verify your print operation uses the correct font and that NSPrintInfo isn't enforcing legacy encoding or unwanted substitution:

  NSPrintInfo *printInfo = [NSPrintInfo sharedPrintInfo];
  printInfo.stringEncoding = NSUTF8StringEncoding; // Ensure UTF-8 is enforced
  // Explicitly set your target font in the print view
  NSTextView *printTextView = [[NSTextView alloc] initWithFrame:NSMakeRect(0,0,600,800)];
  printTextView.string = @"写";
  printTextView.font = [NSFont fontWithName:@"AffectedFontName" size:12];
  

  Test printing the same text in TextEdit with the problematic font—if it fails there too, the issue is likely with the font itself or system print settings, not your code.

• Validate Font File Integrity
  Corrupted or incomplete font files often cause rendering issues. Open the problematic font in Font Book to check for automatic error flags, and test the font on another macOS machine to rule out system-specific corruption.

• Rule Out System Version Compatibility
  Older macOS versions have had known gaps in non-system font support for full Japanese Unicode ranges. Test your app on different macOS releases (if possible) to see if the problem is version-specific. Also ensure you're using modern Cocoa/Core Text APIs instead of deprecated methods (like older NSFontManager calls) that might handle fonts incorrectly.

Start with the first two steps—they'll quickly narrow down whether the issue stems from character encoding, missing font glyphs, or a broken fallback system.

内容的提问来源于stack exchange，提问作者David