After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 477784 - Show license of the font in font viewer
Show license of the font in font viewer
Status: RESOLVED DUPLICATE of bug 407605
Product: gnome-control-center
Classification: Core
Component: [obsolete] fonts:///
git master
Other All
: Normal enhancement
: ---
Assigned To: James Henstridge
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-17 14:44 UTC by Praveen A
Modified: 2007-09-17 18:48 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement

Attachments
Add license field to gnome font viewer (1.21 KB, patch)
2007-09-17 15:23 UTC, Praveen A 		none Details | Review
screenshot (208.17 KB, image/png)
2007-09-17 15:25 UTC, Praveen A 		  Details

Description Praveen A 2007-09-17 14:44:23 UTC 
Current the font viewer does not show License information along with Copyright information. It is important that users know what license the font is under in order to decide whether it is a free font, can they embed the font in their document ...?
Comment 1 Praveen A 2007-09-17 15:23:35 UTC 
Created attachment 95737 [details] [review]
Add license field to gnome font viewer

It adds a field to show license of the font along with other information. It is important improvement I think, as there has been lot of discussions recently about "freeness" of some GPLed fonts since it has the license information only in License field.
Comment 2 Praveen A 2007-09-17 15:25:11 UTC 
Created attachment 95738 [details]
screenshot

a screenshot of the font viewer after adding the new field
Comment 3 Jens Granseuer 2007-09-17 18:48:46 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 407605 ***