[Issue 107831] Deprecated SEAC operator is not supported in PS-OTF
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=107831 --- Additional comments from h...@openoffice.org Tue Dec 22 13:59:17 + 2009 --- I'm not sure whether fontlint already warns about this yet, but the related fontforge project is already aware of the problem as the quick grep over the source shows fontforge/splinesave.c:/* Type2 doesn't allow any seacs */ What is meant here are the Type2 charstrings and these are used in about every PS-OTF-font out there to define the glyph outlines. If fontlint doesn't warn about it yet doing so would be a good idea. - 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 ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Bug 545824] cjkuni-uming bold face not working at 11pt
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=545824 Caolan McNamara caol...@redhat.com changed: What|Removed |Added External Bug ID||OpenOffice.org 107834 External Bug ID|OpenOffice.org 92859| --- Comment #9 from Caolan McNamara caol...@redhat.com 2009-12-22 09:01:29 EDT --- There's no point in tracking things that don't get fixed -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Bug 545824] cjkuni-uming bold face not working at 11pt
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=545824 Caolan McNamara caol...@redhat.com changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #10 from Caolan McNamara caol...@redhat.com 2009-12-22 09:03:57 EDT --- hmm, no point in... wasn't intended for here :-). OOo-specific issue alright, some plausible fixes submitted upstream and checked in locally. Will be in = 3.1.1-19.24 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Issue 107834] sw: at various zoom value s the pseudu-bold/italic disappears in writer
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=107834 User cmc changed the following: What|Old value |New value CC|'hdu' |'fedorafonts,hdu' - 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 ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Issue 107834] sw: at various zoom value s the pseudu-bold/italic disappears in writer
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=107834 User hdu changed the following: What|Old value |New value Assigned to|fme |od OS/Version|Linux |All --- Additional comments from h...@openoffice.org Tue Dec 22 14:25:16 + 2009 --- I agree that the patch against SW makes more sense and is safer. Reassigning to the owner of the patch target code in SW. The other platforms Aqua and Win also do artificial bold and italic so I wouldn't be surprised if it is reproducible there too. - 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 ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Issue 43029] support PS-OpenType/OTF/(S FNT with CFF) fonts for PDF export and printin g
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=43029 --- Additional comments from h...@openoffice.org Tue Dec 22 14:43:26 + 2009 --- See followup issue 107831 for support of the deprecated SEAC operator in PS-OTF Type2 charstrings. Some PS-OTFs still used this obsolete operator for some of their accented characters because they were converted 1:1 from their Type1 ancestors. If there are some important fonts that have not been converted to use valid and non-deprecated charstring operators then adding support for this ancient and very limited feature will be considered. - 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 ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Issue 107831] Deprecated SEAC operator is not supported in PS-OTF
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=107831 --- Additional comments from h...@openoffice.org Tue Dec 22 15:15:58 + 2009 --- Also see http://partners.adobe.com/public/developer/opentype/index_composite.html : In the CFF/Type 2 charstring format, the seac operator is not supported. The priority of this issue depends on the importance of the fonts that have this problem. I do not expect them to be plentyful since if they were important enough to be maintained they would not use illegal operators. Anyway, here is the start of the list: - Yanone Kaffeesatz - older versions of FreeFontPro - 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 ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Issue 107831] Deprecated SEAC operator is not supported in PS-OTF
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=107831 --- Additional comments from h...@openoffice.org Tue Dec 22 15:33:49 + 2009 --- Correction: current versions of Yanone Kaffeesatz use only non-deprecated operators. Thanks Jan! - 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 ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Issue 107831] Deprecated SEAC operator is not supported in PS-OTF
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=107831 --- Additional comments from h...@openoffice.org Tue Dec 22 15:36:24 + 2009 --- - ZapfinoPro is affected (http://www.ntg.nl/pipermail/ntg-context/2009/045689.html) - 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 ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Bug 522187] SWT crash with GTK 2.18 and GNOME accessibility
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=522187 --- Comment #33 from Andrew Overholt overh...@redhat.com 2009-12-22 15:55:20 EDT --- I'm building some updated RPMs with a patch for this issue back-ported from upstream: http://koji.fedoraproject.org/koji/taskinfo?taskID=1887104 If anyone can give those a shot with accessibility enabled and see if there are still crasher bugs, I'd appreciate it. I think bug #547056 is a dupe of this one. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Bug 522187] SWT crash with GTK 2.18 and GNOME accessibility
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=522187 Andrew Overholt overh...@redhat.com changed: What|Removed |Added External Bug ID||Eclipse Project 291128 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Bug 522187] SWT crash with GTK 2.18 and GNOME accessibility
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=522187 --- Comment #34 from Andrew Overholt overh...@redhat.com 2009-12-22 16:56:17 EDT --- Oops, there was an issue with my SRPM. Here's a better koji build: http://koji.fedoraproject.org/koji/taskinfo?taskID=1887224 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Bug 545824] cjkuni-uming bold face not working at 11pt
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=545824 --- Comment #11 from Caius 'kaio' Chance ccha...@redhat.com 2009-12-22 18:48:06 EDT --- (In reply to comment #7) I imagine this is emboldening gone wrong +- embedded bitmaps or sommat I tested both with embedded bitmaps on and off. Same problem was observed. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Bug 549887] SIGSEGV in _pango_cairo_font_private_get_scaled_font in /usr/bin/blueman-manager
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=549887 Dave Malcolm dmalc...@redhat.com changed: What|Removed |Added CC||besfa...@redhat.com, ||fedora-fonts-bugs-l...@redh ||at.com Component|python |pango AssignedTo|dmalc...@redhat.com |besfa...@redhat.com Summary|[abrt] crash detected in|SIGSEGV in |python-2.6.2-2.fc12 |_pango_cairo_font_private_ ||get_scaled_font in ||/usr/bin/blueman-manager Flag||needinfo?(m_run...@yahoo.co ||m) --- Comment #2 from Dave Malcolm dmalc...@redhat.com 2009-12-22 19:06:29 EDT --- Thank you for reporting this bug. If you run the program from a terminal, is an error message printed? What version of blueman and pango do you have installed? Looking at the backtrace, it looks like the problem occurred in the program's single thread in _pango_cairo_font_private_get_scaled_font Reassigning component from python to pango, but could be a blueman issue. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Bug 490830] Nafees Web Naksha should drop Preferred Family name
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=490830 --- Comment #23 from Parag pnem...@redhat.com 2009-12-23 01:19:21 EDT --- any updates here? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
Re: fontconfig config priority
Le jeudi 17 décembre 2009 à 23:06 +0900, Akira TAGOH a écrit : Hi, Hi, I have a question and a suggestion for the fontconfig config priority in the font packaging policy. I'm writing a small script to validate the fontconfig config in packages to not mess up. Wondeful! If you want commit access to fontpackages to have it integrated with our other tools, just ask (if the licensing is OK with you) the goal is to check if the priority is set accurately and the config files are following our templates. it roughly started working. but I'm not quite sure what Latin in LGC really covers. is it similar to what Latin-[1-10] covers? or more strictly applied? LGC roughtly means latin-like alphabetical scripts that are written linearly with few ligatures, and those that exist optional (not indic, not arabic, not cjk…) Also an unofficial requirement for those scripts is to be from regions where people are familiar enough with latin letters not to butcher them when they include them in fonts A more professional description would be welcome :) The suggestion is, about improving the policy to set the priority more strictly. I have two ideas: 1) have variety of the priorities for non-LGC fonts as well like for default, main and low perhaps. even though LGC fonts has a priority for default font, but not for non-LGC fonts. it may messes up their default font if multiple fonts with the same priority such as 65 are installed. this priority things could avoids this issue. it may be something like: 65-69 ... High priority non-LGC fonts 70... Main non-LGC font list 71-64 ... Low priority non-LGC fonts Those ranges are inherited from the fontconfig master file split that occured a few years ago upstream. I'm not so sure that nowadays they are the most appropriate. We've certainly started pushing a lot more fontconfig files that upstream thought at the time, and are hitting many limitations (layout that was supposed to be flexible enough to allow customization, but is not really because of the files that have kept long font lists). If you try to split the non-latin file, for example, you quickly hit prefix starvation. However, that's just MHO. Other people may not share it. But please keep an open mind and do propose another file naming convention if you find a better one. I think that the main requirements would be to 1. clearly define the ranges a local sysadmin, a distro, and fontconfig upstream fallbacks should use 2. try to separate classes of fonts to minimize risks of conflicts (like the current lgc/non lgc split) 3. make locale appear when it is relevant 4. make the font names appear in filenames so people do not need grepping to locate where the rules associated with their font are It is possible in fontconfig to use something longer that the current 2-digit prefixes to order files 2) describes what exactly default, Main and Low priority means. during developing and testing this script, I see some packages is possibly wrongly set the priority to their fontconfig config files, for example, some font is set the priority to 57 that is supposed to be the default font, but not marked as mandatory in comps. so I'd suggest to update comps or change the priority like: - mandatory for higher priority - default for main priority - optional for low priority and update the policy with it as well. I don't think using comps brutally will work : 1. currently we do not have separate comps groups for every fontconfig/css generic, fontconfig and apps really want a separate font stack for each generic (though this could be fixed by splitting the master fonts comps group) 2. sometimes our requirements are a lot more subtle than mandatory/default : dejavu and liberation are both default, but their ordering is not random However I can only applaud trying to improve our fontconfig packaging, and writing qa tests: this is sorely needed, if we want to continue improving Fedora font support. Best regards, -- Nicolas Mailhot signature.asc Description: This is a digitally signed message part ___ Fedora-fonts-list mailing list Fedora-fonts-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-list
