i18n-bugs May 2021

i18n-bugs@lists.fedoraproject.org

1 participants
87 discussions

[Fedora-i18n-bugs] [Bug 1779123] New: Pango no longer supports type1 fonts
by bugzilla＠redhat.com 26 Apr '23

26 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=1779123 Bug ID: 1779123 Summary: Pango no longer supports type1 fonts Product: Fedora Version: rawhide Status: NEW Component: pango Assignee: pwu(a)redhat.com Reporter: mjg(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: 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, pwu(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: In pango 1.44, pango dropped support for type1 fonts. Therefore, no application which uses pango for font loading can use type1 fonts any more. Version-Release number of selected component (if applicable): pango-1.44.6-1.fc31.x86_64 (and later) How reproducible: always Steps to Reproduce: 1. Upgrade F31 or rawhide 2. Open any pango-using application 3. Try to use type1 font Actual results: No type1 font is usable Expected results: Type1 font is usable Additional info: bug 1753295 is the same bug for dropped bitmap font support. Over there, workarounds specific for bitmap fonts (conversion to opentype bitmap fonts) are discussed. An attempt to discuss type1 there failed. This bug here is specifically about type1 fonts to discuss ways (or their absence) to deal with pangos dropped type 1 support. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Fedora-i18n-bugs] [Bug 1895482] New: Liberation Fonts Support For Serbian locl Glyphs Incomplete
by bugzilla＠redhat.com 04 Apr '23

04 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=1895482 Bug ID: 1895482 Summary: Liberation Fonts Support For Serbian locl Glyphs Incomplete Product: Fedora Version: rawhide Hardware: x86_64 OS: Linux Status: NEW Component: liberation-fonts Assignee: vishalvijayraghavan(a)gmail.com Reporter: aleslavista(a)outlook.it QA Contact: extras-qa(a)fedoraproject.org CC: caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com, petersen(a)redhat.com, psatpute(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, vishalvijayraghavan(a)gmail.com Target Milestone: --- Classification: Fedora Created attachment 1727218 --> https://bugzilla.redhat.com/attachment.cgi?id=1727218&action=edit Correctly Localized Glyphs Description of problem: Liberation Fonts do NOT provide full support for Serbian localized glyphs. Version-Release number of selected component (if applicable): Liberation-Fonts 2.1-1-1 How reproducible: You need a program that is able to access the font's localized glyphs: usually that's LibreOffice Writer. Steps to Reproduce: 1. Open LibreOffice Writer 2. Type бгдпт, then бгдпт in Italic, бгдпт in Bold and finally бгдпт in Italic Bold with Liberation Serif, and do the same with Liberation Sans 3. Set the language to "Serbian Cyrillic" Actual results: Not all glyphs are correctly localized Expected results: See attachment for correctly localized glyphs Additional info: Liberation Mono has slanted Italic, therefore only the first glyph should be localized: CYRILLIC LETTER SMALL BE. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1767976] New: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT
by bugzilla＠redhat.com 14 Dec '22

14 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1767976 Bug ID: 1767976 Summary: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:b24defc317ee932c47b15b9c24c231f607dad274;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: rauch.christian(a)gmx.de QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-1.5.21-3.fc31 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1001.slice/user@1001.service/gnome-shell-wayland.service cmdline: ibus-daemon --panel disable -r --xim crash_function: bus_dbus_impl_connection_filter_cb executable: /usr/bin/ibus-daemon journald_cursor: s=3ad93f33cf144f27b2bc4f480d8f3f2e;i=4b9e;b=9037b22bbad44adc83ebb6c1be09e1fc;m=1975f869;t=594e3ce75700c;x=34f5463c97ecc8bd kernel: 5.3.5-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001 Potential duplicate: bug 1475710 -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Fedora-i18n-bugs] [Bug 1842034] New: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT
by bugzilla＠redhat.com 14 Dec '22

14 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1842034 Bug ID: 1842034 Summary: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT Product: Fedora Version: 32 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:b24defc317ee932c47b15b9c24c231f607dad274;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: niki.guldbrand(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-1.5.22-7.fc32 Additional info: reporter: libreport-2.13.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-42.slice/session-c1.scope cmdline: ibus-daemon --panel disable -r --xim crash_function: bus_dbus_impl_connection_filter_cb executable: /usr/bin/ibus-daemon journald_cursor: s=f592520f518043e0bf22bcb1059f85fa;i=5f0d;b=e5641f6c2ed84e629455c7ec8e6a1276;m=1c9e25e;t=5a6dbe50f3604;x=b9e38dca02503832 kernel: 5.6.15-300.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 42 Potential duplicate: bug 1475710 -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Fedora-i18n-bugs] [Bug 1931294] New: URL tag is outdated
by bugzilla＠redhat.com 13 Dec '22

13 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1931294 Bug ID: 1931294 Summary: URL tag is outdated Product: Fedora Version: 32 Status: NEW Component: scim-anthy Severity: low Assignee: tagoh(a)redhat.com Reporter: tim(a)tim-landscheidt.de QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora The URL "http://scim-imengine.sourceforge.jp/" used in the URL tag for the binary package scim-anthy is outdated. https://github.com/scim-im/scim-anthy seems to be working. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Fedora-i18n-bugs] [Bug 1926996] New: [abrt] ibus: ibus_bus_connect_async(): ibus-x11 killed by SIGSEGV
by bugzilla＠redhat.com 13 Dec '22

13 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1926996 Bug ID: 1926996 Summary: [abrt] ibus: ibus_bus_connect_async(): ibus-x11 killed by SIGSEGV Product: Fedora Version: rawhide Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:e9e25725fbf5b802310f7153823734fd779117b2;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: ivanbondar(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-1.5.23-4.fc34 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service cmdline: /usr/libexec/ibus-x11 --kill-daemon crash_function: ibus_bus_connect_async executable: /usr/libexec/ibus-x11 journald_cursor: s=aab3f47a17be489baf33710542b2170a;i=f80;b=45370d40ccad4b839c075727799cd0e0;m=25b8493c;t=5baec3f2ba7c1;x=373238aeaa187c3d kernel: 5.11.0-0.rc6.20210204git61556703b610.144.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 ibus_bus_connect_async at /usr/src/debug/ibus-1.5.23-4.fc34.x86_64/src/ibusbus.c:462 #1 _g_cclosure_marshal_VOID__OBJECT_OBJECT_ENUMv at ../gio/gmarshal-internal.c:1380 #2 _g_closure_invoke_va at ../gobject/gclosure.c:873 #5 g_file_monitor_source_dispatch at ../gio/glocalfilemonitor.c:567 #8 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4131 #10 ibus_main at /usr/src/debug/ibus-1.5.23-4.fc34.x86_64/src/ibusshare.c:318 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Fedora-i18n-bugs] [Bug 1850832] New: The Gujarati & Hindi itrans methods are not able to type sentences correctly.
by bugzilla＠redhat.com 13 Dec '22

13 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1850832 Bug ID: 1850832 Summary: The Gujarati & Hindi itrans methods are not able to type sentences correctly. Product: Fedora Version: 32 Hardware: x86_64 OS: Linux Status: NEW Component: ibus-m17n Severity: high Assignee: pnemade(a)redhat.com Reporter: nirmalpathak(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com, pnemade(a)redhat.com, shawn.p.huang(a)gmail.com Target Milestone: --- Classification: Fedora Created attachment 1698739 --> https://bugzilla.redhat.com/attachment.cgi?id=1698739&action=edit Actual result while typing in GEdit using Gujarati and Hindi using itrans(m17n) input method. Description of problem: The Gujarati & Hindi itrans methods are not able to type sentences correctly. When you start typing in Gujarati or Hindi using itrans(m17n) input method, the letters at times are replaced by 'space' or it simply doesn't print. At times, the special characters like "?" are printed before the previously typed/printed character. This happens abruptly but in most cases, once you enter a new line by pressing 'enter' or 'return' key and start new sentence. Version-Release number of selected component (if applicable): m17n-db-1.8.0-9.fc32.noarch ibus-m17n-1.4.2-2.fc32.x86_64 m17n-lib-1.8.0-7.fc32.x86_64 How reproducible: Type in Gujarati or Hindi language using ibus itrans(m17n) method. Steps to Reproduce: 1. Select Gujarati (itrans - m17n) or Hindi (itrans - m17n) method from ibus input method. 2. Start typing multiple sentences in Gujarati or Hindi. 3. Press 'enter' or 'return' key to start a new sentence in a new line. Actual results: - કે મછે? - બરાબ રનથી લખાતું - कै से ?हो - ऐसा क्युं छ परहा है? Expected results: - કેમ છે? - બરાબર નથી લખાતું - कैसे हो? - ऐसा क्युं छप रहा है? Additional info: Please check attached GIF image for actual results. -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Fedora-i18n-bugs] [Bug 1751061] New: Compose doesn’t work when using ibus
by bugzilla＠redhat.com 13 Dec '22

13 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1751061 Bug ID: 1751061 Summary: Compose doesn’t work when using ibus Product: Fedora Version: 31 Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: mfabian(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora I installed Fedora-Everything-netinst-x86_64-31-20190909.n.0.iso in qemu. Ibus version is: ibus-1.5.21-1.fc31.x86_64 I installed the gnome-tweaks package and set the compose key (Multi_key) to “Scroll Lock”. Configured input methods and keyboard layouts (as seen in the gnome panel) are: English (US, euro on 5) en 日本語　　　　　　　 ja 日本語（かな漢字） ja その他（Typing Booster） 🚀 I choose the "English (US, euro on 5)" keyboard layout and try to type into gedit. When pressing <Multi_key> , I see ⎄ i.e. I see U+2384 COMPOSITION SYMBOL as expected. But if I wait about a second, it disappears again. Now I type <Multi_key> <'> fast, not waiting after <Multi_key> I see ⎄' and it disappears again after about a second. <Multi_key> <'> <a> fast and I see: á After waiting for about a second, it turns into á⎄ i.e. U+2384 COMPOSITION SYMBOL is added after the á without pressing any more keys, just by waiting. This U+2384 COMPOSITION SYMBOL stays there, even if I wait more. If I continue to type <'> <a>, I finally get: áá i.e. I have produced this “áá” by typing <Multi_key> <'> <a> <'> <a>. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Fedora-i18n-bugs] [Bug 1733869] New: gettext: Getting errors in double free with msgfmt command.
by bugzilla＠redhat.com 13 Dec '22

13 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1733869 Bug ID: 1733869 Summary: gettext: Getting errors in double free with msgfmt command. Product: Fedora Version: 30 Status: NEW Component: gettext Assignee: panovotn(a)redhat.com Reporter: poyadav(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, jjanco(a)redhat.com, nphilipp(a)redhat.com, panovotn(a)redhat.com, petersen(a)redhat.com, praiskup(a)redhat.com, suanand(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Error in poc, please refer the result section for details. Version-Release number of selected component (if applicable): gettext-0.19.8.1-18.fc30.x86_64 How reproducible: Always Steps to Reproduce: 1. Clone https://github.com/CCCCCrash/POCs.git. 2. Run valgrind msgfmt poc command. 3. Observe the output. Actual results: [poyadav@localhost doublefree]$ valgrind msgfmt poc ==8072== Memcheck, a memory error detector ==8072== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==8072== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==8072== Command: msgfmt poc ==8072== ==8072== Conditional jump or move depends on uninitialised value(s) ==8072== at 0x48D9940: freea (in /usr/lib64/libgettextlib-0.19.8.1.so) ==8072== by 0x487E8EA: po_lex_charset_set (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487E098: po_gram_parse (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487EB9A: ??? (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487A773: catalog_reader_parse (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x10E7C7: ??? (in /usr/bin/msgfmt) ==8072== by 0x10D8EB: ??? (in /usr/bin/msgfmt) ==8072== by 0x4AABF32: (below main) (in /usr/lib64/libc-2.29.so) ==8072== poc:17: duplicate message definition... poc:16: ...this is the location of the first definition poc:18:3: syntax error poc:18: keyword "n" unknown poc:19: end-of-line within string poc:28: duplicate message definition... poc:24: ...this is the location of the first definition poc:35: keyword "msgud_plural" unknown poc:34: missing 'msgstr' section poc:35:13: syntax error poc:40: end-of-line within string poc:46: end-of-line within string poc: warning: Charset missing in header. Message conversion to user's charset will not work. poc:42: duplicate message definition... poc:6: ...this is the location of the first definition poc:46:2: syntax error poc:46: keyword "Ep" unknown poc:47: keyword "C" unknown poc:48: keyword "s" unknown poc:49: keyword "bo" unknown poc:50: keyword "S" unknown poc:50:236: invalid control sequence poc:50:397: invalid control sequence poc:51: end-of-line within string msgfmt: too many errors, aborting ==8072== ==8072== HEAP SUMMARY: ==8072== in use at exit: 59,783 bytes in 123 blocks ==8072== total heap usage: 547 allocs, 424 frees, 99,479 bytes allocated ==8072== ==8072== LEAK SUMMARY: ==8072== definitely lost: 650 bytes in 82 blocks ==8072== indirectly lost: 0 bytes in 0 blocks ==8072== possibly lost: 0 bytes in 0 blocks ==8072== still reachable: 59,133 bytes in 41 blocks ==8072== suppressed: 0 bytes in 0 blocks ==8072== Rerun with --leak-check=full to see details of leaked memory ==8072== ==8072== Use --track-origins=yes to see where uninitialised values come from ==8072== For lists of detected and suppressed errors, rerun with: -s ==8072== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Expected results: No errors. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1954716] New: Fonts not used correctly
by bugzilla＠redhat.com 08 Dec '22

08 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1954716 Bug ID: 1954716 Summary: Fonts not used correctly Product: Fedora Version: rawhide Status: NEW Component: fontconfig Assignee: tagoh(a)redhat.com Reporter: barbarah.duarte(a)fluocomunicacao.com.br 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, 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 Created attachment 1776799 --> https://bugzilla.redhat.com/attachment.cgi?id=1776799&action=edit LibreOffice with all three fonts displayed in regular, italic and bold face. I have installed some company-provided fonts for use in presentations etc.: $ ls /usr/share/fonts/neo-sans-intel/ NeoSansIntel-Italic.ttf NeoSansIntel-MediumItalic.ttf NeoSansIntel-LightItalic.ttf NeoSansIntel-Medium.ttf NeoSansIntel-Light.ttf NeoSansIntel.ttf In LibreOffice I have a choice of three separate fonts: Neo Sans Intel, Neo Sans Intel Medium, and Neo Sans Intel Light. For each of those three, the italic version of the font (from the separate TTF file) is used. I can tell by the tail on the 'f' character. For bold text, however, an 'emboldening' algorithm seems to be used instead of using the appropriate separate font file. In GNOME font selection dialogs, I see just one 'Neo Sans Intel' family, with a choice of 8 styles. I'll ignore the italic versions since those do actually seem to work as expected, so there are four weights listed: - Light (== Neo Sans Intel Light) - Regular (== Neo Sans Intel Medium) - Medium (== Neo Sans Intel Medium) - Bold (== Neo Sans Intel Medium + emboldening algorithm?) I *don't* seem to have an option in GNOME which will just use the straight 'Neo Sans Intel' font. So both seem to be getting it wrong, in different ways. Or perhaps there's something wrong with the fonts themselves? -- You are receiving this mail because: You are on the CC list for the bug.

1 7

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs May 2021