https://bugzilla.redhat.com/show_bug.cgi?id=2095905
Bug ID: 2095905
Summary: [abrt] ibus-typing-booster: _expat_parse():
langtable.py:912:_expat_parse:xml.parsers.expat.ExpatE
rror: not well-formed (invalid token): line 11583,
column 64
Product: Fedora
Version: 36
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:9a0e6dba4ca5dc3486a02f907d47050684522fb5;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: mfabian(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: anish.developer(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Version-Release number of selected component:
ibus-typing-booster-2.15.27-1.fc36
Additional info:
reporter: libreport-2.17.1
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
cmdline: /usr/bin/python /usr/share/ibus-typing-booster/setup/main.py
crash_function: _expat_parse
exception_type: xml.parsers.expat.ExpatError
executable: /usr/share/ibus-typing-booster/setup/main.py
interpreter: python-unversioned-command-3.10.4-1.fc36.noarch
kernel: 5.17.13-300.fc36.x86_64
runlevel: N 5
type: Python3
uid: 1000
Truncated backtrace:
langtable.py:912:_expat_parse:xml.parsers.expat.ExpatError: not well-formed
(invalid token): line 11583, column 64
Traceback (most recent call last):
File "/usr/share/ibus-typing-booster/setup/main.py", line 87, in <module>
import tabsqlitedb
File "/usr/share/ibus-typing-booster/setup/../engine/tabsqlitedb.py", line
38, in <module>
import itb_util
File "/usr/share/ibus-typing-booster/setup/../engine/itb_util.py", line 89,
in <module>
import langtable # type: ignore
File "/usr/lib/python3.10/site-packages/langtable/__init__.py", line 1, in
<module>
from .langtable import *
File "/usr/lib/python3.10/site-packages/langtable/langtable.py", line 2553,
in <module>
__module_init = __ModuleInitializer()
File "/usr/lib/python3.10/site-packages/langtable/langtable.py", line 2547,
in __init__
_init()
File "/usr/lib/python3.10/site-packages/langtable/langtable.py", line 2539,
in _init
_read_file('territories.xml', TerritoriesContentHandler())
File "/usr/lib/python3.10/site-packages/langtable/langtable.py", line 932, in
_read_file
_expat_parse(file, sax_handler)
File "/usr/lib/python3.10/site-packages/langtable/langtable.py", line 912, in
_expat_parse
parser.ParseFile(file)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 11583,
column 64
Local variables in innermost frame:
file: <gzip on 0x7f2248a50700>
sax_handler: <langtable.langtable.TerritoriesContentHandler object at
0x7f2248a507f0>
parser: <pyexpat.xmlparser object at 0x7f2248a2e9e0>
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2095905
https://bugzilla.redhat.com/show_bug.cgi?id=2096482
Bug ID: 2096482
Summary: translate-toolkit-3.7.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: translate-toolkit
Keywords: FutureFeature, Triaged
Assignee: suanand(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dwayne(a)translate.org.za,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
petersen(a)redhat.com, suanand(a)redhat.com
Target Milestone: ---
Classification: Fedora
Releases retrieved: 3.7.0
Upstream release that is considered latest: 3.7.0
Current version/release in rawhide: 3.6.2-1.fc37
URL: http://toolkit.translatehouse.org/
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/3685/
To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/translate-toolkit
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2096482
https://bugzilla.redhat.com/show_bug.cgi?id=2125153
Bug ID: 2125153
Summary: ibus does not support special Arabic compose sequences
Product: Fedora
Version: 36
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
The following compose sequences do not work in ibus:
$ grep -i arabic.*ligature /usr/share/X11/locale/en_US.UTF-8/Compose
# Arabic Lam-Alef ligatures
<UFEFB> : "لا" # ARABIC LIGATURE LAM WITH ALEF
<UFEF7> : "لأ" # ARABIC LIGATURE LAM WITH ALEF WITH HAMZA ABOVE
<UFEF9> : "لإ" # ARABIC LIGATURE LAM WITH ALEF WITH HAMZA BELOW
<UFEF5> : "لآ" # ARABIC LIGATURE LAM WITH ALEF WITH MADDA ABOVE
They are needed because the Arabic keyboard layout outputs UFEFB on some key:
$ grep -i fefb /usr/share/X11/xkb/symbols/ara
key <AB05> { [ UFEFB, UFEF5,
NoSymbol, NoSymbol ]}; // ﻻ ﻵ
key <AB05> { [ UFEFB, UFEF5,
U06AB, U06AD ]}; // ﻻ ﻵ ګ ڭ
but the UFEFB characters is not what is desired, what one really wants is
U+0644 U+0627. But xkb keyboard layouts can only output one keysym when typing
a key, not two. So compose was used as a hack to work around this limitation of
xkb:
The keyboard produces UFEFB and then the compose support replaces this with
U+0644 U+0627.
This works when the compose support in Xorg is used but not when the compose
support in ibus is used.
How to reproduce:
1) First show that it works when using the Xorg compose support:
Start xterm like this (to disable ibus and use the Xorg compose support):
env XMODIFIERS=@im=none xterm &
Then in the xterm, type
$ echo -n b | iconv -f utf8 -t utf16le | od -x
0000000 0062
0000002
and we see that the b produces U+0062, which is correct.
Switch to the Arabic keyboard
setxkbmap ara
type “arrow up” to get the echo -n b | iconv -f utf8 -t utf16le | od -x line
back, go back to the b with “arrow left”, type b and now one gets:
echo -n لا | iconv -f utf8 -t utf16le | od -x
0000000 0644 0627
0000004
I.e. even though the keyboard surely outputs only U+FEFB, the Compose support
of Xorg transforms this into U+0644 U+0627
2) Now repeat the same test using the compose support in ibus:
Start xterm like this to use the ibus compose support:
env XMODIFIERS=@im=ibus xterm &
Then in the xterm, type
$ echo -n b | iconv -f utf8 -t utf16le | od -x
0000000 0062
0000002
and we see that the b produces U+0062, which is correct.
Switch to the Arabic keyboard
setxkbmap ara
type “arrow up” to get the echo -n b | iconv -f utf8 -t utf16le | od -x line
back, go back to the b with “arrow left”, type b and now one gets:
echo -n ﻻ | iconv -f utf8 -t utf16le | od -x
0000000 fefb
0000002
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2125153
https://bugzilla.redhat.com/show_bug.cgi?id=2131129
Bug ID: 2131129
Summary: emacs-ddskk exists and prevents emacs from running
Product: Fedora
Version: 36
Status: NEW
Component: emacs-common-ddskk
Assignee: dueno(a)redhat.com
Reporter: przemek(a)nist.gov
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: So emacs-common-ddskk seems to work fine, but somehow I
installed the compiled package emacs-ddskk, and it prevents emacs from running.
emacs-ddskk is in fedora repository, but doesn't show up in bugzilla's
component selection; since it appears to be just compiled version of
emacs-common-ddskk, I am opening this report here.
Version-Release number of selected component (if applicable):
emacs-ddskk-16.2-12.fc36.noarch
emacs-common-ddskk-16.2-12.fc36.noarch
How reproducible: every time
Steps to Reproduce:
1. sudo yum install emacs-ddskk
2. emacs
Actual results:
$ emacs
Cannot open load file: No such file or directory, comp
$
Expected results: emacs runs
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2131129