[Fedora-i18n-bugs] [Bug 1850832] New: The Gujarati & Hindi itrans methods are not able to type sentences correctly.
by bugzilla＠redhat.com
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 week, 3 days
[Fedora-i18n-bugs] [Bug 1733869] New: gettext: Getting errors in double free with msgfmt command.
by bugzilla＠redhat.com
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 month
[Fedora-i18n-bugs] [Bug 1757760] New: Hiragana to English conversion with F10 key adds unwanted letters
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1757760
Bug ID: 1757760
Summary: Hiragana to English conversion with F10 key adds
unwanted letters
Product: Fedora
Version: rawhide
Status: NEW
Component: ibus-kkc
Assignee: dueno(a)redhat.com
Reporter: ykatabam(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Description of problem:
When we enter an English word with consecutive double letters (e.g. assembly)
in Hiragana mode and use F10 to convert into English, the double letters
becomes the triple letters in some cases (e.g. asssembly).
This happens irregularly, but tends to happen more often for longer words.
Here are some examples:
communication becomes commmunication
bugzilla becomes bugzilla
Pittsburgh becomes Pitttsburgh
FYI, auto-correct is disabled, as auto-correct changes the input when it's not
a dictionary word so it doesn't allow us to convert into English properly in
hiragana mode.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 months, 3 weeks
[Fedora-i18n-bugs] [Bug 1847347] New: gnome-terminal and xfce4-terminal get surrounding text from previous application
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1847347
Bug ID: 1847347
Summary: gnome-terminal and xfce4-terminal get surrounding text
from previous application
Product: Fedora
Version: 32
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 made the following screenshots and video by testing on Gnome-Xorg, but the
problem occurs on Gnome-Wayland as well.
How to reproduce (see also attached screenshots and video):
- To show what happens with the surrounding text, I first opened the
setup tool of ibus-typing-booster and set the debug level in the
options tab to 3.
When the debug level is high, the auxiliary text above the candidate
list shows what context has been obtained by using surrounding text
(if surrounding text is available, if it is not available like when
using xterm, the context is just remembered from what was typed
last).
- I opened 3 windows: gedit, firefox, and gnome-terminal.
- I focus on gedit and type "a b c d e"
On top of the candidate list one can see: "Context: b c d"
This is because when the letter "e" was typed, ibus-typing-booster
got the surrounding text at the cursor position and parsed the last
3 tokens left of the cursor out of the result. And these
last 3 tokens left of the cursor are "b c d".
- Now I focus on firefox and type "f g h i j"
On top of the candidate list one can see: "Context: g h i"
I.e. the correct context "g h i" to the left of the just typed "j"
(which is still in preedit) has been found using surrounding text.
- Now I focus on gnome-terminal and type "k l m"
On top of the candidate list one can see: "Context h i j"
This comes from the surrounding text left of the cursor in
*firefox*, *not* from gnome-terminal.
Although gnome-terminal reports that surrounding text is supported, i.e.
self.client_capabilities & IBus.Capabilite.SURROUNDING_TEXT
is True (see the code to get the context at:
https://github.com/mike-fabian/ibus-typing-booster/blob/master/engine/hun...
)
gnome-terminal does not really seem to support surrounding text.
The surrounding text comes from the previous client which really supported
surrounding text.
If the previous client was firefox, one still gets the surrounding text from
firefox while typing in gnome-terminal.
Same with gedit, if the previous client before focussing on gnome-terminal
was gedit, one still gets the surrounding text from gedit while typing in
gnome-terminal.
- The same problem occurs when using xfce4-terminal instead of gnome-terminal.
- When using xterm, the problem does *not* occur because when using xterm
self.client_capabilities & IBus.Capabilite.SURROUNDING_TEXT
is False and then the get_context() immediately returns and the context
remembered from the last text typed is used as a fallback.
--
You are receiving this mail because:
You are on the CC list for the bug.
4 months
[Fedora-i18n-bugs] [Bug 1787124] New: [abrt] ibus-mozc: __fdelt_chk(): ibus-engine-mozc killed by SIGABRT
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1787124
Bug ID: 1787124
Summary: [abrt] ibus-mozc: __fdelt_chk(): ibus-engine-mozc
killed by SIGABRT
Product: Fedora
Version: 31
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:d88e523ce263f66e445a1a6f6cd666d77fad9e05;VAR
IANT_ID=matecompiz;
Component: mozc
Assignee: tagoh(a)redhat.com
Reporter: ryutaroh2006(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
robinlee.sysu(a)gmail.com, tagoh(a)redhat.com,
tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I don't know how or why ibuz-engine-mozc was killed by SIGABRT...
Version-Release number of selected component:
ibus-mozc-2.23.2815.102-8.fc31
Additional info:
reporter: libreport-2.11.3
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/dbus\x2d:1.2\x2dcom.redhat.imsettings.slice/dbus-:1.2-com.redhat.imsettings@0.service
cmdline: /usr/libexec/ibus-engine-mozc --ibus
crash_function: __fdelt_chk
executable: /usr/libexec/ibus-engine-mozc
journald_cursor:
s=4479f645f2da4f17afc9f9415d05055f;i=b7c0;b=a6e351a2ff374b38832aa98ebe9457dd;m=7e0bcb9b;t=59afce7bb1367;x=508717657a4cb7e9
kernel: 5.3.16-300.fc31.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (4 frames)
#6 __fdelt_chk at fdelt_chk.c:25
#7 mozc::(anonymous namespace)::IsWriteTimeout at ../../ipc/unix_ipc.cc:108
#8 mozc::(anonymous namespace)::SendMessage at ../../ipc/unix_ipc.cc:157
#9 mozc::IPCClient::Call at ../../ipc/unix_ipc.cc:328
--
You are receiving this mail because:
You are on the CC list for the bug.
4 months, 2 weeks
[Fedora-i18n-bugs] [Bug 1790554] New: Keyboard layout of Kana Kanji wont show up
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1790554
Bug ID: 1790554
Summary: Keyboard layout of Kana Kanji wont show up
Product: Fedora
Version: rawhide
Hardware: x86_64
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: sumukher(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
Description of problem:
The keyboard layout for Kana Kanji Japanese doesnt show up
Version-Release number of selected component (if applicable):
Fedora-Rawhide-20200112.n.0
How reproducible:
Everytime
Steps to Reproduce:
1. Install Fedora-Rawhide-20200112.n.0 WS from live boot
2. Open settings and navigate to Region and Language
3. Add Japanese Kana Kanji in the input source
4. Click the icon looking like an eye button which should open the keyboard
layout
Actual results:
Doesn't show up the keyboard layout
Expected results:
The keyboard layout should show up like it shows up for english
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
4 months, 2 weeks
[Fedora-i18n-bugs] [Bug 1813728] New: Square four dot Unicode character has incorrect glyph
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1813728
Bug ID: 1813728
Summary: Square four dot Unicode character has incorrect glyph
Product: Fedora
Version: 31
Hardware: x86_64
OS: Linux
Status: NEW
Component: pango
Severity: low
Assignee: pwu(a)redhat.com
Reporter: guillaumepoiriermorency(a)gmail.com
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:
The glyph for the Unicode "square four dot" character is incorrect.
Version-Release number of selected component (if applicable):
I think this problem arose when upgrading from Fedora 30 to Fedora 31.
How reproducible:
The simplest way is to start GNOME Characters Map and search for "square four
dot".
--
You are receiving this mail because:
You are on the CC list for the bug.
5 months, 4 weeks
[Fedora-i18n-bugs] [Bug 1809989] New: By default install Noto fonts for Unicode scripts not already covered by default
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1809989
Bug ID: 1809989
Summary: By default install Noto fonts for Unicode scripts not
already covered by default
Product: Fedora
Version: 31
Status: NEW
Component: google-noto-fonts
Assignee: petersen(a)redhat.com
Reporter: hsivonen(a)hsivonen.fi
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,
pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
There is currently movement towards protecting browser users from font
fingerprinting. This means refusing, by default, to load user-installed fonts,
which makes the set of fonts that each OS installs by default even more
important than before.
Firefox bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1582687
W3C CSS WG issue:
https://github.com/w3c/csswg-drafts/issues/4497
Currently, Windows 10, macOS, Android, and Chrome OS provide broader
installed-by-default Unicode coverage than Fedora.
Examples of living scripts that have enough active users to make it to the list
at
https://en.wikipedia.org/wiki/List_of_writing_systems#List_of_writing_scr...
but are not supported by default in Fedora 31 include Javanese, Sundanese,
Batak, Balinese, Mongolian, and New Tai Lue.
Egyptian hieroglyphs is an example of a dead script the Fedora 31 doesn't
support out of the box but Windows 10, macOS, Chrome OS, and Android do.
To remedy this with minimal disk space impact, I suggest the same approach that
Apple took. Apple bundles with macOS those Noto fonts that cover scripts that
were not already covered by the previous installed-by-default set of fonts on
macOS. In the macOS case, the on-disk footprint of the Noto fonts that were
required to take macOS to Android/Chrome OS-competitive Unicode coverage was
only a couple of megabytes. (The fonts are hidden in /Library/Application
Support/Apple/Fonts/Language Support/.) In the case of Fedora, the set of Noto
fonts required to reach the Chrome OS / Android level of script coverage is a
bit larger than in the macOS case but should still be manageable.
Please install, by default, those Noto fonts that provide support for scripts
that are not properly supported by the fonts that Fedora already installs by
default.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 months
[Fedora-i18n-bugs] [Bug 1832351] New: Macintosh keyboard variants not available
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1832351
Bug ID: 1832351
Summary: Macintosh keyboard variants not available
Product: Fedora
Version: 32
Hardware: x86_64
Status: NEW
Component: xkeyboard-config
Severity: medium
Assignee: peter.hutterer(a)redhat.com
Reporter: mthoemme(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, negativo17(a)gmail.com,
peter.hutterer(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I do not have any variants for Macintosh available when trying to change the
keyboard layout via the GUI (Region & Language Settings).
Trying to manually set the keymap in the locale works for the VC keymap, but
not for the X11 Layout. It will set VC keymap to "de-mac" or "de_mac"
respectively, leave the X11 Layout at "de"
localectl set-keymap de-mac
Digging even deeper, the following commands all yield the same errors:
localectl set-x11-keymap de-mac
localectl set-x11-keymap de_mac
localectl set-x11-keymap de macintosh de_mac
All yield: "Failed to set keymap: Specified keymap cannot be compiled, refusing
as invalid."
Version-Release number of selected component (if applicable):
dnf info xkeyboard-config
Last metadata expiration check: 1:03:51 ago on Mi 06 Mai 2020 15:54:00 CEST.
Installed Packages
Name : xkeyboard-config
Version : 2.29
Release : 1.fc32
Architecture : noarch
Size : 5.5 M
Source : xkeyboard-config-2.29-1.fc32.src.rpm
Repository : @System
From repo : anaconda
Summary : X Keyboard Extension configuration data
URL : http://www.freedesktop.org/wiki/Software/XKeyboardConfig
License : MIT
Description : This package contains configuration data used by the X Keyboard
Extension (XKB),
: which allows selection of keyboard layouts when using a
graphical interface.
How reproducible:
Happens consistently. I'm on a fresh Fedora 32 install.
Steps to Reproduce:
1. localectl set-x11-keymap de macintosh de_mac
Actual results:
"Failed to set keymap: Specified keymap cannot be compiled, refusing as
invalid."
Expected results:
Successfully sets the keyboard layout to a Macintosh variant.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
6 months, 1 week