Launchpad has imported 21 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=19128.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2008-12-16T22:44:28+00:00 Freedesktop wrote: Add: <alias binding="same"> <family>ZapfDingbats</family> <accept><family>Dingbats</family></accept> </alias> This fixes bugs with viewing some PDF files that do not include the font... See: https://bugzilla.redhat.com/show_bug.cgi?id=468565 http://bugzilla.gnome.org/show_bug.cgi?id=502664 Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/2 ------------------------------------------------------------------------ On 2008-12-17T03:30:11+00:00 James H. Cloos Jr. wrote: This is an example of the more general issue that <alias>s are matched to patterns' <fontname>s literally, but actual fonts' names are matched with whitespace ignored. Ie, if the font is installed, these: :; fc-match DejaVuSansMono :; fc-match 'DejaVu Sans Mono' give the same result. But to use aliases you need to have all possibilities accounted for in the conf. It is also related to the issue that libs like poppler pass PS names to fontconfig whereas fontconfig caches the full names. (For Type1 fc caches the /FullName, poppler passes the /FontName; for sfnts poppler passes the TT_NAME_ID_PS_NAME, which fc explicitly ignores: #if 0 case TT_NAME_ID_PS_NAME: case TT_NAME_ID_UNIQUE_ID: #endif ) Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/3 ------------------------------------------------------------------------ On 2008-12-17T11:41:09+00:00 Freedesktop wrote: Ah I see. Good point. Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/4 ------------------------------------------------------------------------ On 2008-12-28T13:14:48+00:00 Freedesktop wrote: We prolly need a new comparison operator for the config file that compares ignoring case and blanks. Then we can update all the config files to use that. Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/5 ------------------------------------------------------------------------ On 2009-01-01T12:42:29+00:00 Bugs-freedesktop wrote: (In reply to comment #3) > We prolly need a new comparison operator for the config file that compares > ignoring case and blanks. Then we can update all the config files to use > that. That may be one issue, but isn't necessary going to help with PS-names. e.g. NimbusSansL-Regu is never going to match a full name or family name. PS-names and family names are really quite different. Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/6 ------------------------------------------------------------------------ On 2009-01-01T14:09:34+00:00 Freedesktop wrote: (In reply to comment #4) > (In reply to comment #3) > > We prolly need a new comparison operator for the config file that compares > > ignoring case and blanks. Then we can update all the config files to use > > that. > > That may be one issue, but isn't necessary going to help with PS-names. > e.g. NimbusSansL-Regu is never going to match a full name or family name. > PS-names and family names are really quite different. Right. PS-names are a different issue and that's bug 18095. Retitling again. Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/7 ------------------------------------------------------------------------ On 2009-02-03T13:50:46+00:00 Freedesktop wrote: Note that fc-list also doesn't ignore whitespace when matching. Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/8 ------------------------------------------------------------------------ On 2009-08-05T07:57:22+00:00 Freedesktop wrote: *** Bug 23152 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/9 ------------------------------------------------------------------------ On 2010-02-19T04:01:40+00:00 Eric wrote: The problem with the ZapfDingbats alias is still present in fontconfig-2.8. Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/10 ------------------------------------------------------------------------ On 2010-04-10T18:33:02+00:00 Dirtyepic wrote: If the larger issue of whitespace isn't going to be addressed soon can we add the ZapfDingbats bit in the meantime? Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/11 ------------------------------------------------------------------------ On 2010-04-21T11:06:57+00:00 James H. Cloos Jr. wrote: Does anyone have any comments on the proposed patch I posted to the mailing list a couple of weeks ago (<m3r5mwt1wj....@lugabout.jhcloos.org> and its followup)? Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/12 ------------------------------------------------------------------------ On 2012-03-07T01:23:34+00:00 Akiro wrote: (In reply to comment #10) > Does anyone have any comments on the proposed patch I posted to the mailing > list a couple of weeks ago (<m3r5mwt1wj....@lugabout.jhcloos.org> and its > followup)? I've decided to include a workaround patch for this issue so far because I want to give priority releasing new version since there hasn't seen for awhile. I'll have a look at your patch once new release is out. Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/15 ------------------------------------------------------------------------ On 2012-03-13T02:50:17+00:00 Akiro wrote: (In reply to comment #10) > Does anyone have any comments on the proposed patch I posted to the mailing > list a couple of weeks ago (<m3r5mwt1wj....@lugabout.jhcloos.org> and its > followup)? Well, that might be good start to work on Bug#18095 though, I'm not sure how it helps for this since this is to handle the white spaces in the family name on alias. (In reply to comment #3) > We prolly need a new comparison operator for the config file that compares > ignoring case and blanks. Then we can update all the config files to use > that. I'd vote this idea. we could force using FcStrCmpIgnoreBlanksAndCase() for family but is there any cases one strictly needs to check the white spaces in the string? otherwise can we simply use it for string too? Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/16 ------------------------------------------------------------------------ On 2012-03-30T01:50:43+00:00 Akiro wrote: the proposed fixes for this: http://cgit.freedesktop.org/~tagoh/fontconfig/commit/?h=bz19128 I guess there may be the better operator name though. please test it. hope I'm not missing anything else. thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/17 ------------------------------------------------------------------------ On 2012-04-09T21:08:31+00:00 Akiro wrote: FcStrCmpIgnoreBlanksAndCase() ignores the blanks in any places anyway. so that will says "Co urier" and "C o u r i e r" is same. should we just skips the blanks when the next character is only capitalized? Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/18 ------------------------------------------------------------------------ On 2012-04-10T10:27:44+00:00 Freedesktop wrote: Not really sure. Lets go for less complexity. Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/19 ------------------------------------------------------------------------ On 2012-04-10T18:39:17+00:00 Akiro wrote: Okay. we can fix it later as needed. Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/20 ------------------------------------------------------------------------ On 2012-04-10T19:10:19+00:00 Akiro wrote: I still wonder if "eq_case_blanks" is really better name for operator. there are another idea when I thought of. it is to make the case- sensitivity and ignoring blanks optional. <test name="family" compare="eq" case-sensitivity="false" ignore-blanks="true"> ... </test> the concern is, it's only effective for string. but that may be ok since fontconfig implicitly adjusts the behavior against the operator in even current implementation. e.g. FcOpContains and FcOpListing is equal to FcOpEqual for integer and float. Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/21 ------------------------------------------------------------------------ On 2012-04-10T19:18:49+00:00 Akiro wrote: and it would be capable to add another rule for skip blanks like: <test name="family" ignore-blanks="only_when_capitalized"> not sure if we really want to do that in the future, but maybe good to have scalability in its syntax. another advantage on this idea would be compatibility with the older release. it behaves differently but still can share them. Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/22 ------------------------------------------------------------------------ On 2012-05-08T04:10:39+00:00 Akiro wrote: another try: http://cgit.freedesktop.org/~tagoh/fontconfig/commit/?h=bz19128-2 That looks better now. any volunteers for testing are welcome. Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/23 ------------------------------------------------------------------------ On 2012-05-13T20:11:01+00:00 Akiro wrote: Merged into master. Reply at: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/130687/comments/24 ** Changed in: fontconfig Status: Unknown => Fix Released ** Changed in: fontconfig Importance: Unknown => Medium ** Bug watch added: Red Hat Bugzilla #468565 https://bugzilla.redhat.com/show_bug.cgi?id=468565 ** Bug watch added: GNOME Bug Tracker #502664 https://bugzilla.gnome.org/show_bug.cgi?id=502664 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/130687 Title: fontconfig alias for ZapfDingbats font Status in Fontconfig - Font Configuration Library: Fix Released Status in “fontconfig” package in Ubuntu: Fix Released Status in Debian GNU/Linux: New Bug description: Binary package hint: fontconfig-config fontconfig returns the wrong font for ZapfDingbats. $ fc-match ZapfDingbats DejaVuSans.ttf: "DejaVu Sans" "Book" however it works when looking for Dingbats instead $ fc-match Dingbats d050000l.pfb: "Dingbats" "Regular" Actually I'm not sure whether it should be fixed in every distro or in fontconfig. I already commented it to upstreamer without response: https://bugs.freedesktop.org/show_bug.cgi?id=6478#c12 poppler and consequently evince are affected by this issue, since this font is used in pdf files that contains interactive forms. To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/130687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
