i18n-bugs February 2019

i18n-bugs@lists.fedoraproject.org

1 participants
82 discussions

[Fedora-i18n-bugs] [Bug 1094779] No Cyrillic Italic Glyphs for Sans, Sans Narrow and Mono
by bugzilla＠redhat.com 25 Feb '19

25 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1094779 --- Comment #9 from Pravin Satpute <psatpute(a)redhat.com> --- [1] Commit : https://github.com/liberationfonts/liberation-1.7-fonts/commit/b72da688058b… * This bug has been fixed long time back, we were only waiting for upstream release. * This bug was fixed in Liberation 1.7, Since we are providing Liberation 1.7 through copr, we can provide Copr link here and close this bug. * I am not sure state of this bug for Liberation 2 (cant find commit log), Vishal need to cross check commit log [1] and see, if those thing still present in Liberation 2. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1249335] Inconsistent rules for shortcuts between different applications when switching keymaps
by bugzilla＠redhat.com 25 Feb '19

25 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1249335 --- Comment #10 from Jens Petersen <petersen(a)redhat.com> --- I think better to report this upstream against individual applications. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1094779] No Cyrillic Italic Glyphs for Sans, Sans Narrow and Mono
by bugzilla＠redhat.com 25 Feb '19

25 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1094779 --- Comment #8 from Jens Petersen <petersen(a)redhat.com> --- Actually I am not even clear on what the bug report/request is? Is it to remove partial coverage provided by italic Cyrillic glyphs or is it to add those glyphs?? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1094779] No Cyrillic Italic Glyphs for Sans, Sans Narrow and Mono
by bugzilla＠redhat.com 25 Feb '19

25 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1094779 --- Comment #7 from Jens Petersen <petersen(a)redhat.com> --- I don't really understand the status here (In reply to Pravin Satpute from comment #1) > I have now removed Serbian localized glypsh from Sans, Mono and SansNarrow > > Commit id for same: > https://git.fedorahosted.org/cgit/liberation-fonts.git/commit/?h=liberation- > fonts-1_07_3&id=b72da688058b451a9aef8baf0fc1d4ddc49060e5 Couldn't find this commit in github... So this issue still exists in Liberation 1 and 2? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1677056] default out of the box font rendering is virtually unreadable
by bugzilla＠redhat.com 25 Feb '19

25 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1677056 --- Comment #14 from Kalev Lember <klember(a)redhat.com> --- Thanks, fixed in https://src.fedoraproject.org/rpms/gsettings-desktop-schemas/c/5078dfad9559… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1648825] Split and update smc-fonts to match upstream release
by bugzilla＠redhat.com 25 Feb '19

25 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1648825 --- Comment #8 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- If you can build from sources please do so. That's the only way to make sure our font building infra is sane and we will be able to use it the day someone needs a fix in the font files and upstream is busy somewhere else. (and that also makes sure Fedora is something upstream can rely on should it need to). DejaVu for example builds fine from source in Fedora, that's the result of a cooperation between us and the font project to fix the required Makefile parts. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1677056] default out of the box font rendering is virtually unreadable
by bugzilla＠redhat.com 25 Feb '19

25 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1677056 --- Comment #13 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- Please never require font packages by name, it can change over time, use the fonts() autoprovides computed by fontconfig at package build time -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1677056] default out of the box font rendering is virtually unreadable
by bugzilla＠redhat.com 24 Feb '19

24 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1677056 Chris Murphy <bugzilla(a)colorremedies.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lruzicka(a)redhat.com --- Comment #12 from Chris Murphy <bugzilla(a)colorremedies.com> --- *** Bug 1678683 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1648825] Split and update smc-fonts to match upstream release
by bugzilla＠redhat.com 23 Feb '19

23 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1648825 --- Comment #7 from Rajeesh <rajeeshknambiar(a)gmail.com> --- (In reply to vishal vijayraghavan from comment #5) > https://src.fedoraproject.org/rpms/smc-anjalioldlipi-fonts > https://src.fedoraproject.org/rpms/smc-dyuthi-fonts > https://src.fedoraproject.org/rpms/smc-meera-fonts > https://src.fedoraproject.org/rpms/smc-rachana-fonts > https://src.fedoraproject.org/rpms/smc-raghumalayalamsans-fonts > https://src.fedoraproject.org/rpms/smc-suruma-fonts Just a thought. The font packaging guidelines say we SHOULD build from source if possible [1]. Any particular reason not to follow that? (The upstream Makefile is not very well suited for Fedora, but I can engage with upstream if anything could be improved). [1] https://docs.fedoraproject.org/en-US/packaging-guidelines/FontsPolicy/#_bui… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1679619] New: Undefined symbol in libfontconfig prevents any graphical activity (booting also).
by bugzilla＠redhat.com 22 Feb '19

22 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1679619 Bug ID: 1679619 Summary: Undefined symbol in libfontconfig prevents any graphical activity (booting also). Product: Fedora Version: 29 Hardware: x86_64 OS: Linux Status: NEW Component: fontconfig Severity: urgent Assignee: tagoh(a)redhat.com Reporter: artu72(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, john.j5live(a)gmail.com, mclasen(a)redhat.com, pnemade(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: While booting the system, gdm-wayland-session complains undefined symbol FT_Done_MM_Var in libfontconfig, the same behaviour occurs issuing a startx from a textual console in a system started without graphical level. Version-Release number of selected component (if applicable): fontconfig-2.13.1-3.fc29.x86_64.rpm How reproducible: Always. Steps to Reproduce: 1. Boot the system with default settings. 2. 3. Actual results: Booting hangs on a blank screen with a steady cursor. Expected results: Plymouth screen with fedora logo, then a X session. Additional info: I am providing journal and boot logs links on fedora paste: https://paste.fedoraproject.org/paste/oWkRwE6zFksSwcw4RDPFSA -- You are receiving this mail because: You are on the CC list for the bug.

1 3

← Newer
1
2
3
4
5
6
7
8
9
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs February 2019