Ticket #23756 (closed defect: fixed)
Double dagger (‡) replaces "fi" in cairo/pango/gtk2 +quartz+no_x11
| Reported by: | zwaldowski@… | Owned by: | ryandesign@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.8.2 |
| Keywords: | Cc: | nox@…, wyatt@…, toreador@…, glazered@… | |
| Port: | cairo pango gtk2 |
Description
This is a really strange problem that doesn't immediately lean itself to being pinned on a certain port: apps that run on +no_x11+quartz variants of Cairo, Pango, and GTK replace the "fi" character immediately when typed (or shown) with the UTF-8 double dagger symbol (‡). This is not a 64-bit/32-bit issue, as I have personally identified this same issue with the binary beta release of Banshee (http://download.banshee-project.org/banshee/banshee-1-1.5.3.macosx.intel.dmg).
The issue occurs in all text-based forms and effects the characters shown in any combination (for example, any dialog that reads "Loading files..." appears like "Loading ‡les".
The issue did not appear the last time I had a compile of this same toolset, approximately in December.
Attachments
Change History
Changed 3 years ago by zwaldowski@…
- Attachment Screen shot 2010-02-17 at 5.09.39 PM.png added
comment:1 Changed 3 years ago by jmr@…
- Cc nox@… added
- Owner changed from macports-tickets@… to ryandesign@…
- Port set to cairo pango gtk2
Please remember to cc the maintainers.
comment:2 Changed 3 years ago by ryandesign@…
I'm sorry to hear that. It certainly sounds like a bug but unfortunately I don't know what piece of software the bug is in either. The one thing I'm fairly sure of, though, is that it's not a bug in MacPorts, especially since you've seen the issue in a software package released separately from MacPorts. So you should probably begin reporting the bug to the developers of cairo, pango, gtk, or other software you think may be relevant, until you find the right one.
comment:3 Changed 3 years ago by zwaldowski@…
I agree; I'll report upstream tomorrow when I get around to it. It might still be a MacPorts issue, though, at least in terms of OS X integration. My citation of Banshee was just to prove that it's not an 10.6 64-bit issue; the Banshee Tech Preview for OS X is (at least, according to their bug tracker) built partially using MacPorts.
comment:6 follow-up: ↓ 7 Changed 3 years ago by glazered@…
I thought I was going insane trying to find this problem... FWIW, I believe it started for me when I built Gimp with the no_X11 quartz variant
CC me please!
comment:7 in reply to: ↑ 6 Changed 3 years ago by ryandesign@…
- Cc glazered@… added
Replying to glazered@…:
CC me please!
I have Cc'd you, but for future reference, you Cc yourself by clicking the "CcMe!" button at the top of the ticket.
comment:8 Changed 3 years ago by ro@…
I had this too.
Patched the Portfile to use Pango 1.28.1, as per ticket #20924 (https://trac.macports.org/attachment/ticket/20924/patch-pango-1.28.1-introspection.diff) and reinstalled Pango + dependents. This fixed things for me.
A screenshot exhibiting the issue within the GTK+ file dialog