[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 year, 4 months
[Bug 2045414] New: gettext: FTBFS in Fedora rawhide/f36
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2045414
Bug ID: 2045414
Summary: gettext: FTBFS in Fedora rawhide/f36
Product: Fedora
Version: rawhide
Status: NEW
Component: gettext
Assignee: suanand(a)redhat.com
Reporter: releng(a)fedoraproject.org
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,
petersen(a)redhat.com, praiskup(a)redhat.com,
suanand(a)redhat.com
Blocks: 1992484 (F36FTBFS)
Target Milestone: ---
Classification: Fedora
gettext failed to build from source in Fedora rawhide/f36
https://koji.fedoraproject.org/koji/taskinfo?taskID=81771851
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
Please fix gettext at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
gettext will be orphaned. Before branching of Fedora 37,
gettext will be retired, if it still fails to build.
For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai...
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1992484
[Bug 1992484] Fedora 36 FTBFS Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2045414
1 year, 4 months
[Fedora-i18n-bugs] [Bug 1751061] New: Compose doesn’t work when using ibus
by bugzilla＠redhat.com
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 year, 4 months
[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 year, 4 months
[Bug 2026124] New: add pkg-config file
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2026124
Bug ID: 2026124
Summary: add pkg-config file
Product: Fedora
Version: 35
Status: NEW
Component: libunistring
Severity: medium
Assignee: p(a)draigbrady.com
Reporter: drepper(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
jim(a)meyering.net, p(a)draigbrady.com,
redhat-bugzilla(a)linuxnetz.de
Target Milestone: ---
Classification: Fedora
Description of problem:
To simplify the use of the library and checking in tools like rpm and cmake it
would be beneficial to have a pkg-config file in the -devel package
Version-Release number of selected component (if applicable):
libunistring-0.9.10-14
How reproducible:
always
Steps to Reproduce:
1.cat /usr/lib64/pkgconfig/libunistring.pc
2.
3.
Actual results:
no such file
Expected results:
Perhaps something like this:
prefix=/usr
exec_prefix=/usr
includedir=/usr/include
libdir=/usr/lib64
Name: GNU libunistring
Description: GNU libunistring library implementing Unicode string types in
three flavours
URL: https://www.gnu.org/software/libunistring/
Version: 0.9.10
Cflags: -I${includedir}
Libs: -L${libdir} -lunistring
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2026124
1 year, 4 months
[Bug 2036458] New: Lohit Punjabi font does not implement all unicode
specs
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2036458
Bug ID: 2036458
Summary: Lohit Punjabi font does not implement all unicode
specs
Product: Fedora
Version: 35
Status: NEW
Component: Fonts
Assignee: i18n-bugs(a)lists.fedoraproject.org
Reporter: plehal(a)lehal.net
QA Contact: fonts-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Created attachment 1848544
--> https://bugzilla.redhat.com/attachment.cgi?id=1848544&action=edit
unicode spec.
Description of problem:
Lohit Punjabi Font does not recognize some subjoined consonants which should be
recognized per Unicode specs and are recognised by other fonts from other
vendors.
Version-Release number of selected component (if applicable):
All
How reproducible:
Always
Steps to Reproduce:
1. Try to type subjoined consonants with characters ਕ,ਗ,ਚ,ਤ,ਥ,ਟ,ਠ,ਦ,ਧ,ਨ
2. It shows as ਪ੍ਕ , ਪ੍ਗ, ਪ੍ਚ......instead of these letters showing properly at
the bottom of preceding character.
Actual results:ਪ੍ਕ , ਪ੍ਗ, ਪ੍ਚ.
Expected results: letters showing properly at the bottom of preceding
character.
Additional info: Related Unicode document attached. Raavi and Ravi font from
Microsoft render it correctly.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2036458
1 year, 4 months
[Fedora-i18n-bugs] [Bug 1954716] New: Fonts not used correctly
by bugzilla＠redhat.com
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 year, 4 months
[Bug 2069725] New: Missing support for Georgian uppercase characters
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2069725
Bug ID: 2069725
Summary: Missing support for Georgian uppercase characters
Product: Fedora
Version: 35
Hardware: All
OS: Linux
Status: NEW
Component: Fonts
Assignee: i18n-bugs(a)lists.fedoraproject.org
Reporter: alan.g12r(a)outlook.com
QA Contact: fonts-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Created attachment 1869049
--> https://bugzilla.redhat.com/attachment.cgi?id=1869049&action=edit
Fedora 35 Missing Georgian characters
Description of problem:
Georgian uppercase letters are shown as squares
How reproducible:
always
Steps to Reproduce:
1.add Georgian keyboard layout
2.open text editor
3.type Georgian letters and make them uppercase
Actual results:
all characters are shown as replacement boxes
Expected results:
readable text
Additional info:
Georgian uppercase characters were introduced in Unicode 11 (2018), but there's
no font supporting these glyphs in Fedora.
Google Noto fonts include these characters. Noto Georgian fonts are also used
as default in Arch-based distributions and Android.
Please add Google-Noto-Georgian, that provide full support for Georgian script.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2069725
1 year, 4 months
[Bug 1981500] New: [f34] some snaps are having font display issues
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1981500
Bug ID: 1981500
Summary: [f34] some snaps are having font display issues
Product: Fedora
Version: 34
OS: Linux
Status: NEW
Component: fontconfig
Severity: medium
Assignee: tagoh(a)redhat.com
Reporter: dvd(a)redhat.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, 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:
Installing some snaps like codium are having font issues in dialog windows.
This has been widely discussed upstream [1]
Tried multiple workarounds and none of them are working:
~~~
sudo rm /var/cache/fontconfig/*
rm ~/.cache/fontconfig/*
rm -f ~/snap/codium/current/.cache/
fc-cache -r -v
snap run --shell codium
fc-cache -r -v
exit
~~~
I also tried this with VScodium running
Arch wiki [a] suspects it's an issue caused by fontconfig>=2.13.91
Version-Release number of selected component (if applicable):
fontconfig-2.13.93-6.fc34.x86_64
snapd-selinux-2.51-1.fc34.noarch
snap-confine-2.51-1.fc34.x86_64
snapd-2.51-1.fc34.x86_64
How reproducible:
All the time
Steps to Reproduce:
1. snap install codium
2. Open Folder dialog or any kind of dialog
Actual results:
All the text is square instead of readable characters
Expected results:
We should be able to read the text.
Additional info:
[a] https://wiki.archlinux.org/title/Talk:Snap
[1]
~~~
https://forum.snapcraft.io/t/snapped-app-not-loading-fonts-on-fedora-and-...
https://forum.inkdrop.app/t/snap-with-no-visible-letters-in-system-dialog...
https://wiki.archlinux.org/title/Talk:Snap
https://githubmemory.com/repo/snapcrafters/codium/issues/6
https://github.com/VSCodium/vscodium/issues/426
~~~
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year, 4 months
[Bug 2102608] New: CVE-2022-33068 VUL-0: CVE-2022-33068: harfbuzz:
integer overflow in the component hb-ot-shape-fallback.cc
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2102608
Bug ID: 2102608
Summary: CVE-2022-33068 VUL-0: CVE-2022-33068: harfbuzz:
integer overflow in the component
hb-ot-shape-fallback.cc
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: mrehak(a)redhat.com
CC: caswilli(a)redhat.com, dffrench(a)redhat.com,
eng-i18n-bugs(a)redhat.com, erik-fedora(a)vanpienbroek.nl,
gzaronik(a)redhat.com,
i18n-bugs(a)lists.fedoraproject.org,
jburrell(a)redhat.com, jwong(a)redhat.com,
kaycoth(a)redhat.com, klember(a)redhat.com,
kshier(a)redhat.com, manisandro(a)gmail.com,
moceap(a)hotmail.com, ngough(a)redhat.com,
pnemade(a)redhat.com, psatpute(a)redhat.com,
rgodfrey(a)redhat.com, rh-spice-bugs(a)redhat.com,
tuxator(a)o2.pl
Target Milestone: ---
Classification: Other
An integer overflow in the component hb-ot-shape-fallback.cc allows attackers
to cause a Denial of Service (DoS) via unspecified vectors.
Reference:
https://github.com/harfbuzz/harfbuzz/issues/3557
https://github.com/harfbuzz/harfbuzz/commit/62e803b36173fd096d7ad460dd1d1...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2102608
1 year, 4 months