Hi, >>> Additionally, on Solaris 9 and 10 with OOo 2.0.3, artificial bold and/or >>> italic rendering system works improperly. Specifying bold and/or italic >>> typeface on Japanese characters results in finding other ethnic font >>> files. See issue 67167, issue 67197, and issue 65173. >> Then these are bugs again that should not be hidden by manual >> font-overrides.
Herbert Duerr wrote: > Yup. I'll look into these issues. How is the issue 67167 going? Anything can I help you, e.g. preparing an image of VMWare for reproduction? May I escalate the issue 67167 as a showstopper to the release process of 2.0.4? Users of Solaris with Japanese environment cannot use any predefined style with Bold and/or Italic typeface. E.g. Once a user apply a style Heading 1 to a text, the text disappears or is rendered with an inappropriate font. Tracing system calls with "truss -t open -p process_id_of_soffice.bin" reveals that applying bold and/or italic typeface results in finding another font file as Western system does. However, Japanese font sets have only normal typefaces. I.e no bold, italic, bold-italic, font file is provided because of its tremendous number of characters. Apparently, there is something that can be considered. The Artificial bold and/or italic rendering system for ethnic fonts have been introduced in the OOo 2.0. All Asian UNIX users had been waiting for the useful, demanded rendering system. I really appreciate you and the gsl team for the efforts of introducing the artificial rendering system. Best Regards, Tora --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
