IBM Support

HD60337: DRAFTING (INTDRAFT) / WRONG JAPANESE KANJI FONT IS DISPLAYED IN THE ANNOTATION TEXT.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Permanent restriction.

Error description

  • Drafting (IntDraft) / WRONG JAPANESE KANJI
    FONT IS DISPLAYED IN THE ANNOTATION TEXT.
    SCENARIO:
    .
    1. Start CATIA.
    2. Create a new CATDrawing.
    3. Create a new annotation text in this drawing.
    Type "juutenn" and click enter to display the
    Kanji font, and click OK.
    .
    OBSERVAION:
    .
    A wrong Japanese Kanji font is displayed on the
    drawing.
    .
    EXPECTED RESULT:
    .
    A correct Japanese Kanji font should be displayed
    on the drawing.
    .
    

Local fix

Problem summary

  • Drafting (IntDraft) / WRONG JAPANESE KANJI FONT IS DISPLAYED IN
    THE ANNOTATION TEXT.
    Drafting (IntDraft) / WRONG JAPANESE KANJI
    FONT IS DISPLAYED IN THE ANNOTATION TEXT.
    SCENARIO:
    .
    1. Start CATIA.
    2. Create a new CATDrawing.
    3. Create a new annotation text in this drawing.
    Type "juutenn" and click enter to display the
    Kanji font, and click OK.
    .
    OBSERVAION:
    .
    A wrong Japanese Kanji font is displayed on the
    drawing.
    .
    EXPECTED RESULT:
    .
    A correct Japanese Kanji font should be displayed
    on the drawing.
    .
    

Problem conclusion

  • null
    ==========*===========*==========
    THIS PROBLEM IS PERMANENT RESTRICTION IN
    CATIA
    .
    Incident Diagnosis
    Kanji glyph displayed in CATIA with KANJ font is
    other than the expected one.
    .
    Restriction Explanation
    .
    In The Unicode Standard both of these two
    characters are defined with different unicode:
    Expected one is 5861 and wrong one is 586B.
    .
    In fact, these represent same character and have
    exactly the same meaning, there is just different
    way to write it. May be in Japanese language the
    last one (586B) is the only one used.
    If we look at TTF fonts found in the market
    (supporting CJK ideographs), most of them contain
    both of the glyphs with correct unicode.
    One exception is MingLiU (although it is a real
    Japanese font): it has only the glyph shaped like
    5861 with 586B as its unicode.
    In CATIA stroke fonts (SSS4, KANJ, SICH, TRCH)
    all of them propose only one form and with unicode
    586B.
    SICH and TRCH contain the correct form
    (corresponding to 586B) but SSS4 and KANJ
    contain the wrong form (corresponding to 5861), as
    does MingLiU.
    Thus this is a permanent restriction due to
    1) These are two forms of same character
    2) SSS4 and KANJ fonts cannott be modified
    3) Even the market fonts (such as MingLiU) can be
    wrong
    .
    Please refer the following for more info:
    http://www.unicode.org/charts/PDF/U4E00.pdf
    .
    By-Pass
    use another fonts like SICH, TRCH (from CATIA) or
    Arial Unicode.
    .
    .
    

Temporary fix

Comments

APAR Information

  • APAR number

    HD60337

  • Reported component name

    CATIA V5 NT>XP

  • Reported component ID

    569151000

  • Reported release

    517

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-01-02

  • Closed date

    2007-06-08

  • Last modified date

    2007-06-08

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSVJ2K","label":"CATIA V5"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"517","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
08 June 2007