To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=18285
------- Additional comments from [EMAIL PROTECTED] Thu Oct 6 04:24:36 -0700 2005 ------- Ok, this is a small patch comparing to Firefly's previous numerous patches for OOo 1.1.x. So I think this is reasonable, and actually practical enough to ask for a reviewer now. Somebody has compiled OOo 2.0.0 with this patch and it is working okay. But first, on the JCA license stuff. -> npower: I have talked to Mr. Firefly on MSN, and he said he's okay with the JCA agreement. With the permission of his employer he will sign it to allow his patches to go upstream if it is to be accepted. So I think it is the right time to ask for a reviewer on this patch. If you can help him on the cws matter it will be great. About the patch: Please bare with me over the long explanation of this patch. I am contemplating to add this explanation as comment in the patch itself, but I suppose an open explanation here is essential. 1. Scope of influence: This patch will affect Linux, Mac OSX X11 version users of OpenOffice.org (although OOo 2.0 is under overhaul for Mac OSX). I am not sure about the Solaris version, because the apply of this patch depends on the version of freetype OpenOffice.org is using. Is OOo Solaris version using freetype or STSF (http://stsf.sourceforge.net/) to render screen font in OOo? I am not sure. 2. Patch dependence: this patch depends on freetype 2.1.10 In June 2005, freetype 2.1.10 was released. This was the first official version to display artificial bold style for true type font under Linux (see more from my previous comment). The effect of this patch would not be complete if freetype is not upgraded to this version accordingly - so somebody who works on integrating freetype with OpenOffice.org Linux version should pay notice to it. 3. To fully understand this patch you have to understand a bit more about font technology. Embedded Bitmap: In late 2004/early 2005, Mr. Firefly has released a new Chinese font called AR PL New Sung (refer as 'New Sung') under open source license: http://www.study-area.org/apt/firefly-font/fireflysung-1.3.0.tar.gz Before New Sung was released, many Chinese Linux users would simply grab the MingLiu / Simsun font from Windows and use it under Linux, since normal CJK font is simply too blurry and unclear under Linux. With attachment 30175, you can see that the New Sung font offers significantly sharper glyph when comparing to normal CJK font like AR PL Ming2tiL Big5. So how can this be done? Basically New Sung is now comprised of two sets of fonts: the original Vector glyph from AR PL Ming2tiL, and the newly added Embedded Bitmap font for point 11-16. There will be no difference in printing output, but when displaying on screen, font glyph with size 11,12,13,14,15,16 will be replaced by the sharper Bitmap font embedded. As a result, the new patch created by Firefly will need to take this into account because Bitmap font cannot be italicized (and hence needs to revert back to vector when italicized). Embedded bitmap is also why MingLiu/Simsun were preferred by Chinese Linux users despite possible licensing agreement issues (which could mean legal problems). The New Sung font has officially removed any legal risk. Hence embedded bitmap deserves the same attention as other normal TTF should have. It should be noted that OpenOffice.org 1.x also recognizes embedded bitmap glyph internally. Okay, this is long enough in one post, I'll try to start explaining what the patch does in the next comment. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
