i18n-bugs December 2017

i18n-bugs@lists.fedoraproject.org

1 participants
149 discussions

[Fedora-i18n-bugs] [Bug 1084007] Review Request: google-roboto-fonts - Google Roboto fonts
by bugzilla＠redhat.com 29 Dec '17

29 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1084007 --- Comment #8 from Fedora Update System <updates(a)fedoraproject.org> --- google-roboto-fonts-2.138-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-30d4a534b6 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1433628] New: First line of pixels chopped off in Chromium/ Chrome when liberation-fonts built with fontforge > 20150430
by bugzilla＠redhat.com 28 Dec '17

28 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1433628 Bug ID: 1433628 Summary: First line of pixels chopped off in Chromium/Chrome when liberation-fonts built with fontforge > 20150430 Product: Fedora Version: 25 Component: liberation-fonts Assignee: psatpute(a)redhat.com Reporter: chillermillerlong(a)hotmail.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, psatpute(a)redhat.com Description of problem: The current liberation-fonts package is built by fontforge 20160404 and results in the top of the fonts being chopped off in some pages in Chrome/Chromium. For example, with this page: https://www.reddit.com/r/linux/comments/600h4f/wine_24_released/ When built with fontforge 20160404: http://i.imgur.com/kO2H3Hw.png When built with fontforge 20150430: http://i.imgur.com/IQmu5o3.png Notice how the first line of pixels is getting chopped off. Version-Release number of selected component (if applicable): liberation-fonts-common-1.07.4-7.fc24.noarch liberation-mono-fonts-1.07.4-7.fc24.noarch liberation-sans-fonts-1.07.4-7.fc24.noarch liberation-serif-fonts-1.07.4-7.fc24.noarch fontforge-20160404-5.fc25.x86_64 Additional info: I did a git bisect and found that this is the commit in fontforge that introduced the issue. --- [chenxiaolong@cxl-fedora25vm fontforge]$ git bisect bad e870019c2602d50eb00793e979f3e11bcc71d6cf is the first bad commit commit e870019c2602d50eb00793e979f3e11bcc71d6cf Author: Frédéric Wang <fred.wang(a)free.fr> Date: Wed May 13 08:03:13 2015 +0200 Fix read/write of bits USE_TYPO_METRICS and WWS for OS2 version < 4 :040000 040000 7032ea971c1d084ab8a038b4a80d9092e53a8519 eb11e4b5a69718ad94d8dbfc414e7b2a944548d3 M fontforge --- https://github.com/fontforge/fontforge/commit/e870019c2602d50eb00793e979f3e… Is this something that can be fixed without affecting/breaking other fonts? -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Fedora-i18n-bugs] [Bug 1527495] New: fontconfig-2.12.91 is available
by bugzilla＠redhat.com 27 Dec '17

27 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1527495 Bug ID: 1527495 Summary: fontconfig-2.12.91 is available Product: Fedora Version: rawhide Component: fontconfig Keywords: FutureFeature, Triaged Assignee: tagoh(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, alexl(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, john.j5live(a)gmail.com, mbarnes(a)fastmail.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 Latest upstream release: 2.12.91 Current version/release in rawhide: 2.12.6-4.fc28 URL: http://www.fontconfig.org/release/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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/827/ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Fedora-i18n-bugs] [Bug 1526510] New: USE_TYPO_METRICS set in Fedora 2X but not set in RHEL7 or in ttf binary release
by bugzilla＠redhat.com 27 Dec '17

27 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1526510 Bug ID: 1526510 Summary: USE_TYPO_METRICS set in Fedora 2X but not set in RHEL7 or in ttf binary release Product: Fedora Version: 27 Component: liberation-fonts Assignee: psatpute(a)redhat.com Reporter: caolanm(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: alexl(a)redhat.com, caillon+fedoraproject(a)gmail.com, caolanm(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, john.j5live(a)gmail.com, mbarnes(a)fastmail.com, mclasen(a)redhat.com, petersen(a)redhat.com, psatpute(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com External Bug ID: Document Foundation 114434 Created attachment 1368567 --> https://bugzilla.redhat.com/attachment.cgi?id=1368567&action=edit fontforge os/2 metric table on Fedora for Liberation Serif Regular Description of problem: The USE_TYPO_METRICS fsSelection bit (https://www.microsoft.com/typography/otspec/os2.htm#fss) is set in Liberation Serif Regular (probably all of them) under Fedora >= 25 but is *not* set in the RHEL versions or in the binary releases available at http://releases.pagure.org/liberation-fonts/liberation-fonts-ttf-1.07.4.tar… Version-Release number of selected component (if applicable): liberation-fonts-1.07.4-9.fc27 How reproducible: 100% Steps to Reproduce: 1. (In Fedora) fontforge LiberationSerif-Regular.ttf 2. element->font info->os/2->metrics 3. Example "Really use typo metrics" Actual results: its on Expected results: its off Additional info: If I rebuild the fedora rawhide package on fedora I get the bit set, if I rebuild under RHEL7 I get the bit set, so the build environment/tools matter in terms of the results I think we want this bit off in fedora to match what we have in RHEL and in the binary releases and what I see in Arimo and Times New Roman (probably best to confirm that independently) This matters in that in recent LibreOffice if that bit is on we use the typo metrics while if its off we use the hhea metrics and for Liberation Serif they are different enough to mangle starmath equations as per the linked bug -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Fedora-i18n-bugs] [Bug 1511239] New: fcitx-unikey-0.2.7 is available
by bugzilla＠redhat.com 27 Dec '17

27 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1511239 Bug ID: 1511239 Summary: fcitx-unikey-0.2.7 is available Product: Fedora Version: rawhide Component: fcitx-unikey Keywords: FutureFeature, Triaged Assignee: liangsuilong(a)gmail.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, liangsuilong(a)gmail.com, robinlee.sysu(a)gmail.com Latest upstream release: 0.2.7 Current version/release in rawhide: 0.2.6-1.fc28 URL: https://fcitx-im.org/wiki/Unikey Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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/8017/ -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1511238] New: fcitx-qt5-1.2.0 is available
by bugzilla＠redhat.com 27 Dec '17

27 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1511238 Bug ID: 1511238 Summary: fcitx-qt5-1.2.0 is available Product: Fedora Version: rawhide Component: fcitx-qt5 Keywords: FutureFeature, Triaged Assignee: robinlee.sysu(a)gmail.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, robinlee.sysu(a)gmail.com Latest upstream release: 1.2.0 Current version/release in rawhide: 1.1.1-2.fc28 URL: https://github.com/fcitx/fcitx-qt5 Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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/6513/ -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1528892] key org.gnome.settings-daemon.plugins.keyboard disappeared in a recent update
by bugzilla＠redhat.com 27 Dec '17

27 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1528892 --- Comment #10 from Akira TAGOH <tagoh(a)redhat.com> --- Hmm, better ask upstream for a way to disable ibus safely like they did that by set false to org.gnome.settings-daemon.plugins.keyboard in the past. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1528892] key org.gnome.settings-daemon.plugins.keyboard disappeared in a recent update
by bugzilla＠redhat.com 26 Dec '17

26 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1528892 --- Comment #9 from Robin Lee <robinlee.sysu(a)gmail.com> --- And gdm failed to start if /etc/xdg/autostart/org.gnome.SettingsDaemon.Keyboard.desktop removed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1528892] key org.gnome.settings-daemon.plugins.keyboard disappeared in a recent update
by bugzilla＠redhat.com 26 Dec '17

26 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1528892 --- Comment #8 from Alick Zhao <alick9188(a)gmail.com> --- (In reply to Akira TAGOH from comment #7) > remove /etc/xdg/autostart/org.gnome.SettingsDaemon.Keyboard.desktop I wonder if we can support an alternative way without root privilege, like the user has their own ~/.config/autostart/org.gnome.SettingsDaemon.Keyboard.desktop where autostart is set to false? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1528892] key org.gnome.settings-daemon.plugins.keyboard disappeared in a recent update
by bugzilla＠redhat.com 26 Dec '17

26 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1528892 Akira TAGOH <tagoh(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tagoh(a)redhat.com) | --- Comment #7 from Akira TAGOH <tagoh(a)redhat.com> --- remove /etc/xdg/autostart/org.gnome.SettingsDaemon.Keyboard.desktop -- You are receiving this mail because: You are on the CC list for the bug.

1 0

← Newer
1
...
7
8
9
10
11
12
13
14
15
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs December 2017