Bug 1430589 - Version 2.000 is available
Summary: Version 2.000 is available
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: levien-inconsolata-fonts
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1441023
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-09 02:33 UTC by Rastus Vernon
Modified: 2018-11-30 23:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 23:37:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rastus Vernon 2017-03-09 02:33:31 UTC
There is a newer version of the Inconsolata fonts available in the Google Fonts repository[1], which is the official upstream according to Raph Levien's website.[2]

[1]: https://github.com/google/fonts/tree/master/ofl/inconsolata
[2]: http://www.levien.com/type/myfonts/inconsolata.html

Comment 1 Kevin Fenzi 2017-03-12 00:44:01 UTC
Sadly this version does not come with sfd source... 

but I can look at just packaging the ttfs possibly.

Comment 2 Rastus Vernon 2017-03-12 07:47:01 UTC
The source is a Glyphs file.[1] It can be compiled with fontmake[2], which might or might not be more complicated than it's worth. (My guess is that it would be.)

[1]: https://github.com/cyrealtype/Inconsolata
[2]: https://github.com/googlei18n/fontmake

Comment 3 Jan Kurik 2017-08-15 09:27:57 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 4 Marek Suchánek 2018-02-24 15:42:15 UTC
I'd love to see Inconsolata updated in Fedora.

The currently packaged version (1.01) only includes the regular ("medium") weight, whereas version 2 added a bold version. So it's not just a meaningless version-number bump: the change in readability of bold text in pretty significant.

Considering I have no experience building fonts from source, is there a way I could help? What's the status of the bug?

Comment 5 Rastus Vernon 2018-04-06 01:34:02 UTC
The font is developed with the proprietary Glyphs application. The source files can be built to OTFs with the non-proprietary library fontmake and potentially autohinted with ttfautohint or psautohint (for use in Fedora this does not much matter because freetype already does it on its own and upstream says default autohinting options are sufficient). I'm guessing from the policy[1] that it is preferable to build them in Fedora instead of packaging the font files that upstream publishes on GitHub.[2] There's a review request for fontmake.

Of course Kevin could decide to do something different. This is just my suggestion.

[1]: https://fedoraproject.org/wiki/Packaging:FontsPolicy#Building_from_sources

[2]: https://github.com/googlefonts/Inconsolata/tree/master/fonts

Comment 6 Jan Pokorný [poki] 2018-06-11 12:28:12 UTC
I'd like to point out an issue with the recent 2.012-1.fc29 update
in Rawhide.  So far, I've been using Inconsolata in urxvt256c-ml,
launched with "-fn xft:inconsolata:pixelsize=15" parameters.  Sadly,
after the update, the requested font size is not taken into account,
the size of about 10 is being used for terminal rendering, which makes
is really unconvenient for me -- playing with the requested size has
no effect whatsoever.

In this sense, it's a regression, although it may be just some sort
of software/font formats incompatibility.  If that's the case, perhaps
the alternative would be to package both 1.x and 2.x versions in
parallel, leveraging package review exception for such cases, perhaps?

Comment 7 Jan Pokorný [poki] 2018-06-11 13:19:33 UTC
re [comment 6]:

Sorry, PEBKAC, I didn't run full config reinitialization that was needed
for my test changes wrt. font size to be indeed taken into account.
The only part of the regression is then that original pixel size of 15
is now rendered at the same proportion when set to 17.

Comment 8 Kevin Fenzi 2018-06-19 00:23:59 UTC
Huh. I am not seeing a size difference here really. Can you try gnome-terminal and a few other terminals and see if you see it in all of them? or just urxvt?

Comment 9 Jan Pokorný [poki] 2018-11-01 17:36:11 UTC
re [comment 8]:

Hmm, I've now realized it could be related to [bug 1225873].

Comment 10 Ben Cotton 2018-11-27 13:41:33 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Ben Cotton 2018-11-30 23:37:26 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.