[Bug 451744] Review Request: root - The CERN analyzer for high to medium energy physics

[bugzilla at redhat.com]

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=451744


Nicolas Mailhot <nicolas.mailhot at laposte.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fedora-fonts-bugs-list at redh
                   |                            |at.com




--- Comment #33 from Nicolas Mailhot <nicolas.mailhot at laposte.net>  2009-06-13 04:31:42 EDT ---
(In reply to comment #0)

> 4) Not an issue, but I will mention it upfront. Upstream includes the MS
> TrueType fonts 

The licensing of those fonts does not comply with our guidelines
http://fedoraproject.org/wiki/Packaging:FontsPolicy#Legal_considerations
We basically require the same freedom to distribute and modify of our fonts
than of our software.

Also, even if they did, we'd ask to locate the font upstream and package it
separately
http://fedoraproject.org/wiki/Packaging:FontsPolicy#Package_layout_for_fonts

Bundling fonts is prohibited. Fonts must be split out cleanly so they can be
installed separately and reused by other packages

Also, when a project relies on default fonts from another OS or Linux
distribution, you have to ask yourself if the look, feel and metrics of those
fonts is required before hunting for the closest substitute. If the software
does not rely on some exact font characteristic, reconfiguring it to use Fedora
default fonts instead is much preferred.

The Liberation fonts are metrically-equivalent to some MS fonts. However they
are *not* our default font, so forcing their use will make your application
stand out in Fedora. Also they have a lot less Unicode coverage than Dejavu
Fonts.

GNU free fonts are not installed at all by default in Fedora and are not
present on liveCDs and other physical distribution media.


http://fedoraproject.org/wiki/Shipping_fonts_in_Fedora_(FAQ)#What_if_my_package_bundles_Bitstream_Vera.2C_Arev.2C_DejaVu_LGC_or_another_Bitstream_Vera_font_derivative.3F
http://fedoraproject.org/wiki/Shipping_fonts_in_Fedora_(FAQ)#What_if_my_package_bundles_FreeSans.2C_Linux_Libertine.2C_Droid_or_Liberation_fonts.3F
A lot of the symbols in symbol.ttf have long been attributed standard unicode
values. If this software properly references those symbols by their unicode
codepoint (and not the old legacy symbol-specific codepoint) any unicode font
with coverage of the associated unicode blocks will work for you (DejaVu
includes most common symbols). If this is not good enough for you, you can look
at openoffice's opensymbol (and open a bug dejavu-side to request the missing
symbol).

Lastly, if you have all those problems, that's probably because this software
does not use fontconfig. Fontconfig has been the default font management stack
for many years on modern Unixes and anything using X. It will locate for you
the most appropriate installed font transparently. Using something else is
broken by design nowadays, and you'll have no end of font-related problems till
the software is switched to use fontconfig (unlike under windows, the font
complement varies from Unix to Unix and release to release, Unix font Unicode
coverage is not and won't ever be exactly the same as windows fonts, etc).

The only correct mid-term solution is getting this software ported to
fontconfig, usually using a higher-level library like pango-cairo. (and if it
manages PDFs is should probably take a look at poppler too)

-- 
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.