March 2022 - i18n-bugs - Fedora Mailing-Lists

[Bug 1946871] fc-match ":postscriptname=LiberationSans" returns LiberationSansNarrow

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1946871 --- Comment #7 from Fedora Update System <updates(a)fedoraproject.org> --- FEDORA-2022-1b9895f2c2 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1b9895f2c2 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1946871

2 years, 1 month

1
0
0 / 0

[Bug 1946871] fc-match ":postscriptname=LiberationSans" returns LiberationSansNarrow

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1946871 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|POST |MODIFIED --- Comment #6 from Fedora Update System <updates(a)fedoraproject.org> --- FEDORA-2022-b00e17ca83 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b00e17ca83 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1946871

2 years, 1 month

1
0
0 / 0

[Bug 2059806] New: harfbuzz-4.0.0 is available

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2059806 Bug ID: 2059806 Summary: harfbuzz-4.0.0 is available Product: Fedora Version: rawhide Status: NEW Component: harfbuzz Keywords: FutureFeature, Triaged Assignee: pnemade(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, klember(a)redhat.com, moceap(a)hotmail.com, pnemade(a)redhat.com, psatpute(a)redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 4.0.0 Current version/release in rawhide: 3.4.0-1.fc37 URL: https://harfbuzz.github.io/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/1299/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2059806

2 years, 1 month

1
4
0 / 0

[Bug 2059772] New: Please branch and build google-roboto-slab-fonts in epel8 and epel9

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2059772 Bug ID: 2059772 Summary: Please branch and build google-roboto-slab-fonts in epel8 and epel9 Product: Fedora EPEL Version: epel9 Status: NEW Component: google-roboto-slab-fonts Assignee: pnemade(a)redhat.com Reporter: dcavalca(a)fb.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com Target Milestone: --- Classification: Fedora Please branch and build google-roboto-slab-fonts in epel8 and epel9. If you do not wish to maintain google-roboto-slab-fonts in epel8 and epel9, or do not think you will be able to do this in a timely manner, the EPEL Packagers SIG would be happy to be a co-maintainer of the package; please add the epel-packagers-sig group through https://src.fedoraproject.org/rpms/google-roboto-slab-fonts/addgroup and grant it commit access, or collaborator access on epel* branches. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2059772

2 years, 1 month

1
3
0 / 0

[Bug 2016613] When running anaconda on Wayland with two keyboard layouts configured, hitting any modifier key with the second layout selected switches to the first layout

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2016613 --- Comment #51 from Michael Catanzaro <mcatanza(a)redhat.com> --- (In reply to Jiri Konecny from comment #50) > Honestly, as I briefly described we are looking on a way how to get Anaconda > out of the Live environment completely (not killing Live images nor having > it separate from the installation ISO). However, I still need to discuss > some more pieces. If this will be the thing, the Initial Setup on the Live > media will not be important to Anaconda. However, let's move this discussion > to the proper place when I'll collect all the required information. We were actually discussing this quite recently in #workstation:fedoraproject.org. I think a *separate* live session that only runs anaconda would be a good idea. You probably still have to run under GNOME, though; otherwise, you'd need to reimplement too many features provided by the top bar. We particularly do not want to lose the battery status or accessibility features that are currently only available in the live installer. > To answer your question, Anaconda is using localed to store the > configuration right now, it shouldn't be too problematic to extend that also > to read the default from that. Thanks. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2016613

2 years, 1 month

1
0
0 / 0

[Bug 2016613] When running anaconda on Wayland with two keyboard layouts configured, hitting any modifier key with the second layout selected switches to the first layout

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2016613 --- Comment #50 from Jiri Konecny <jkonecny(a)redhat.com> --- Hi, ok, in that case, I'll finish my keyboard configuration split on Live and fix this soon. I also think that the correct approach here is to disable it for the whole Wayland so Gnome and KDE. To Michael: Honestly, as I briefly described we are looking on a way how to get Anaconda out of the Live environment completely (not killing Live images nor having it separate from the installation ISO). However, I still need to discuss some more pieces. If this will be the thing, the Initial Setup on the Live media will not be important to Anaconda. However, let's move this discussion to the proper place when I'll collect all the required information. To answer your question, Anaconda is using localed to store the configuration right now, it shouldn't be too problematic to extend that also to read the default from that. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2016613

2 years, 1 month

1
0
0 / 0

[Bug 2035178] suggestion: move langpacks to a firefox-langpacks subpackage

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2035178 Parag Nemade <pnemade(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |i18n-bugs(a)lists.fedoraproje | |ct.org -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2035178

2 years, 1 month

1
0
0 / 0

[Bug 2016613] When running anaconda on Wayland with two keyboard layouts configured, hitting any modifier key with the second layout selected switches to the first layout

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2016613 --- Comment #49 from Michael Catanzaro <mcatanza(a)redhat.com> --- (In reply to Jiri Konecny from comment #47) > One is to disconnect keyboard control between Live system and Anaconda. So > Anaconda will handle after installation keyboard configuration and Live will > handle current Live. I'm OK with anaconda not respecting user-specific (desktop-specific) keyboard layout changes made in the live system. It seems like a practical approach to sidestep this problem. I hope anaconda will default to the keyboard layout declared by localed so that initial setup tools that run before anaconda can pass config along to anaconda. For Workstation, we will most likely suppress the keyboard layout spoke entirely, and if it doesn't pick up keyboard layout config via localed, we'll have a problem. At least localed is only one system-wide configuration with a stable API, nothing desktop-specific or user-specific. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2016613

2 years, 1 month

1
0
0 / 0

[Bug 2016613] When running anaconda on Wayland with two keyboard layouts configured, hitting any modifier key with the second layout selected switches to the first layout

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2016613 --- Comment #48 from Adam Williamson <awilliam(a)redhat.com> --- I slightly prefer #1, but I agree it's still not exactly a great result. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2016613

2 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs March 2022