On Thu, Jun 04, 2020 at 01:42:51AM -0600, Anthony J. Bentley wrote: > Hi, > > On Sat, May 30, 2020 at 2:16 PM Marc Espie <es...@nerim.net> wrote: > > On Sat, May 30, 2020 at 01:00:17PM -0600, Anthony J. Bentley wrote: > > > Matthieu Herrb writes: > > > > This github issue does pretty much explain what's going on: > > > > https://github.com/googlefonts/Inconsolata/issues/42 : > > > > > > I see nothing as extreme as the screenshots in that link in my xterm. > > > But the new font is certainly wider than the previous one. > > > > > > So we should keep the old font, probably. > > > > > > Should we import the old one as inconsolata-old? > > > Or revert + set EPOCH, and import the new one as inconsolata-new? > > > The latter would avoid breaking people's setups. > > > > Later scheme would be less disturbing > > Attached is a revert of inconsolata-font and a tarball of the current > state of the port as inconsolata-new. > > I marked them with @conflict for two reasons: inconsolata-new will > conflict with the current version of inconsolata-font, and it seems > problematic to have different versions of the same font with the same > family name installed at the same time. > > ok?
Hi, works for me. Thanks. -- Matthieu Herrb
