documentation-packages team mailing list archive

[Launchpad Bug Tracker <1979493@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

I was initially using : 
fonts-beng-extra/impish,impish,now 1.0-7 version and moved to using 
fonts-beng-extra/jammy,jammy,now 3.2.1-1 

I see the difference for my concerned font is as below: 
+* Converted mitra.ttf(0.70) to mitramono.ttf(0.80)


What is expected?
 --> With the older mitra.ttf present in fonts-beng-extra:1.0-7, the output was: 
$ fc-match mitra
MitraMono.ttf: "Mitra" "Regular"

$ fc-match mitramono
mitra.ttf: "Mitra Mono" "Regular"


What happened instead?
--> However with the mitramono.ttf present in fonts-beng-extra:3.2.1-1, I see : 
$fc-match mitra
MitraMono.ttf: "Mitra" "Regular"

$ fc-match mitramono
DejaVuSans.ttf: "DejaVu Sans" "Book" 


Not sure if this mapping is intentional?


More Info: 

$ lsb_release -rd
Description:	Ubuntu 22.04 LTS
Release:	22.04

$ apt-cache policy fonts-beng-extra
fonts-beng-extra:
  Installed: 3.2.1-1
  Candidate: 3.2.1-1
  Version table:
 *** 3.2.1-1 500
        500 http://in.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        500 http://in.archive.ubuntu.com/ubuntu jammy/main i386 Packages
        100 /var/lib/dpkg/status


Thanks!

** Affects: fonts-beng-extra (Ubuntu)
     Importance: Undecided
         Status: New

-- 
fc-match maps font "mitramono" wrong under fonts-beng-extra package
https://bugs.launchpad.net/bugs/1979493
You received this bug notification because you are a member of Documentation Packages, which is subscribed to fonts-beng-extra in Ubuntu.