fontforge has broken dependencies in the epel-5 tree:
On x86_64:
fontforge-20080828-1.1.el5.i386 requires libpython2.4.so.1.0
Please resolve this as soon as possible.
fontforge has broken dependencies in the epel-5 tree:
On x86_64:
fontforge-20080828-1.1.el5.i386 requires libpython2.4.so.1.0
Please resolve this as soon as possible.
https://bugzilla.gnome.org/show_bug.cgi?id=347237
pango | general | unspecified
--- Comment #25 from Behdad Esfahbod <behdad(a)gnome.org> 2014-05-08 18:49:52 UTC ---
Some comments that may help others work around this bug:
==================
I have an idea of how to do this easily in Pango. Give it a try. The
main limitation is that it only works for actual files on the filesystem. But
you may be able to wire it up through ~/.gvfs filenames?
1. FcConfigCreate()
2. FcConfigAppFontAddFile()
3. pango_cairo_font_map_new_for_font_type()
4. Use that PangoFontMap to create your context, etc.
5. Every time you want to use Pango with that context, FcConfigSetCurrent the
above config. Then reset it back to whatever it was before.
This way, Pango will only see that single font.
Misc bugs that would help make this easier in the future:
https://bugs.freedesktop.org/show_bug.cgi?id=78450https://bugs.freedesktop.org/show_bug.cgi?id=78452https://bugs.freedesktop.org/show_bug.cgi?id=64766https://bugzilla.gnome.org/show_bug.cgi?id=547671
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1094015
Parag AN(पराग) <panemade(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fonts-bugs(a)lists.fedoraproj
| |ect.org,
| |i18n-bugs(a)lists.fedoraproje
| |ct.org, panemade(a)gmail.com
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=z9VPqbeA0x&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1081782
--- Comment #8 from Julien Enselme <jujens(a)jujens.eu> ---
(In reply to Paul Flo Williams from comment #6)
> Just a few points:
>
> 1. The FontForge sources for these fonts are available from the Google font
> directory so, according to our packaging policy, these fonts SHOULD be built
> from source.
>
OK, I am building them from source now. Thanks for pointing that out.
> 2. The word "fracture" in the description should be "Fraktur".
>
Corrected.
> 3. Our fonts policy now says that fonts must include correct licensing
> fields in the metadata. In this case, you'll need to correct the metadata
> after building, using the ttname tool.
>
Corrected. However, ttname always exits with status 1 even if the ttf files are
correctly patched. I have the same issue if I just use ttname to display
informations on the fonts. Hence the ugly `|| exit 0` at the end of the ttname
line. Any idea on that?
> 4. The fontconfig file isn't correct. You need to register both fonts with
> the generic name "cursive" using the basic-font-template.conf supplied with
> fontpackages-devel.
Corrected. Thank for your answer.
SPECS:
http://jenselme.perso.centrale-marseille.fr/visible/SPECS/astloch-fonts.spec
SRPMS:
http://jenselme.perso.centrale-marseille.fr/visible/SRPMS/astloch-fonts-1...
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=rDeoiKUTdj&a=cc_unsubscribe
fontforge has broken dependencies in the epel-5 tree:
On x86_64:
fontforge-20080828-1.1.el5.i386 requires libpython2.4.so.1.0
Please resolve this as soon as possible.
fontforge has broken dependencies in the epel-5 tree:
On x86_64:
fontforge-20080828-1.1.el5.i386 requires libpython2.4.so.1.0
Please resolve this as soon as possible.