NOC-Control Center: If you create elements into Service Map view whose label font is Meiryo type,

From CCUI
1.Log on CUI and create an Management group with member All repositories/Master
2.Right click over Master Management group and create an Service Map View
   - Drag and drop many elements: server view, event view, specific elements
like IIs SQL and so on
3. For each embedded element into Service Map view right click and select
properties and change Label Font 
   - Label Font= Meiryo  or Meiryo UI
   - Icon size=16x16
4. Go to NOC server and select the respective Service Map vie 
   - you will see all elements displayed with respective label font
5. Go to Dashboard server and drag and drog Navigation and Layout portlets
6. Select the service map view from Navigation portlet and verify that elements
are displayed into Layout portlet
   - Verify all elements are showed with respective label font
   - But only elements are showed without label font

Control Center allows users to specify any font that happens to be installed on
the CCUI server.  This means that any and every font that can be installed on
windows may be used in a service map view.  

On the other hand, each browser handles fonts in its own way.  W3C standards
allow  a web page to specify a series of fonts, in order of preference that the
browser is supposed to iterate through until it finds a font that it knows how
to render. IE8 clearly has a bug here, which was apparently fixed in IE9.

Calling this an IE bug is obviously not a valid thing to tell a customer.  If
we had a field situation where a customer hasd service maps that used fonts
that were not rendering correctly on their user's browsers, we have a solution:

In translating an SMV into SVG, our control center solution uses the file
NOC/database/netiq/ControlCenterSMVFonts.xml to translate control center fonts
into a font-stack.  The entry in that file for Meiryo is    
   <entry key="Meiryo">'%font%', sans-serif</entry>
Which renders a font stack of "'Meiryo',sans-serif".  (sans-serif is one of a
few universal fonts defined by W3C that all browsers must understand.)  I have
verified that this is working correctly.  But if the browser is behaving
incorrectly, users may change this file, to something like:
   <entry key="Meiryo">sans-serif</entry>
which would work around the IE bug.