[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.
2 days, 10 hours
[Fedora-i18n-bugs] [Bug 1677534] New: texttopaps OOMs with 4GB text file!
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1677534
Bug ID: 1677534
Summary: texttopaps OOMs with 4GB text file!
Product: Fedora
Version: rawhide
Hardware: x86_64
OS: Linux
Status: NEW
Component: paps
Severity: high
Assignee: tagoh(a)redhat.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: desktop-qa-list(a)redhat.com, eng-i18n-bugs(a)redhat.com,
i18n-bugs(a)lists.fedoraproject.org, rhel(a)vlasiu.net,
tagoh(a)redhat.com
Depends On: 1635160
Target Milestone: ---
Classification: Fedora
(Cloned from a RHEL7 report)
+++ This bug was initially created as a clone of Bug #1635160 +++
Description of problem:
Trying to print with cups a 4Gb text file fail.
texttopaps consume all the memory and is killed bye the system:
[1023082.003989] Out of memory: Kill process xxxx (texttopaps) score 955 or
sacrifice child
[1023082.005120] Killed process xxxx (texttopaps) total-vm:19958848kB,
anon-rss:7531872kB, file-rss:84kB, shmem-rss:0kB
/usr/lib/cups/filter/texttopaps 1 user1 "example" 1 "" sample-4Gb.txt
--- Additional comment from Akira TAGOH on 2018-10-03 11:54:48 SGT ---
Hmm, that log says it all. I don't think OOM is a software bug.
--- Additional comment from GV on 2018-10-03 13:00:48 SGT ---
Of course OOM is not a software bug. Where exactly did I said that?
The problem is texttopaps that allocate memory out of control.
texttopaps should allocate memory, use-it, release-it. Like any sane program.
The issue was not present on RHEL 6. I had printed the same file multiple times
with cups on RHEL6 and it worked just fine (not sure it was texttopaps cups
filter involved). Printing the file does not work on RHEL 7 and it should.
The 4Gb file is a testcase for our application we develop.
--- Additional comment from Jens Petersen on 2018-10-18 17:49:35 SGT ---
I don't think the paps in RHEL7 is significantly different from RHEL6.
As you say it could be due to changes in Cups?
The cups versions in RHEL 6, 7 and Fedora are certainly quite different.
Unless texttopaps really worked in RHEL6 it might make to reassign this to
cups?
--- Additional comment from GV on 2018-10-25 18:29:46 SGT ---
Since the real computer running RHEL 6 was already scrapped, I tried to make a
virtual machine using RHEL 6. Unfortunately, now I also get a crash on RHEL 6
when printing the 4GB file. I can't recall how much memory was in that
computer. The virtual machine had 8Gb of memory allocated.
Still, it does not matter that much.
I think texttopaps have an issue and it should be fixed or at least an
workaround should be available (other than 'don't print a file that large').
I'm afraid this is not a cups issue since I can reproduce the issue running the
texttopaps standalone.
Sincerely,
Gabriel
--- Additional comment from Akira TAGOH on 2018-11-16 17:59:04 SGT ---
paps isn't supposed to work with large files. to support it, most of code needs
to rewritten. this isn't realistic to provide an update for existing products.
for a workaround, you can remove paps package (or simply remove
/usr/share/cups/mime/paps.convs file) to fall back the text filter to texttops
which CUPS originally provides. this should works for this issue and as long as
you don't need the internationalization support for printing.
Hope that helps.
--- Additional comment from GV on 2018-12-07 14:03:33 SGT ---
It helps. Thank you!
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1635160
[Bug 1635160] texttopaps OOMs with 4GB text file!
--
You are receiving this mail because:
You are on the CC list for the bug.
1 month, 1 week
[Fedora-i18n-bugs] [Bug 1836327] New: Hangul text commit and key forward don't preserve order sometimes
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1836327
Bug ID: 1836327
Summary: Hangul text commit and key forward don't preserve
order sometimes
Product: Fedora
Version: 32
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus
Severity: medium
Assignee: tfujiwar(a)redhat.com
Reporter: edward.park0203(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
Description of problem:
Hangul text commit and key forward don't preserve order sometimes
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
2 months, 1 week
[Fedora-i18n-bugs] [Bug 1753295] New: Pango no longer supports bitmap fonts
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1753295
Bug ID: 1753295
Summary: Pango no longer supports bitmap fonts
Product: Fedora
Version: 31
Status: NEW
Component: pango
Assignee: tagoh(a)redhat.com
Reporter: jsbillin(a)umich.edu
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 bitmap fonts, so font packages like
terminus-fonts and ucs-miscfixed-fonts no longer appear in GNOME applications
that use pango, such as Terminal. If you did a dnf system-upgrade from Fedora
30 and were using a bitmap font like Terminus, all your terminals will show the
rectangular placeholders the first time you start a terminal.
Bitmap fonts like terminus and ucs-miscfixed are much easier to read in a
terminal since they are pixel perfect. If Fedora 31 is going to disable
support for bitmap fonts, it needs to be announced and the package maintainers
of those bitmap font packages are going to need to find a way to convert their
fonts.
Version-Release number of selected component (if applicable):
pango-1.44.6-1.fc31.x86_64
How reproducible:
always
Steps to Reproduce:
1. install 'terminus-fonts'
2. Start GNOME terminal
3. Open Terminal Preferences
4. Attempt to change the font to Terminus font
Actual results:
If you upgraded from Fedora 30 and had Terminus fonts as the default font, the
first time you launch Terminal, all the text will be the rectangular
placeholders. If you search for the Terminus font in the preferences, you
won't be able to find it.
Expected results:
Use the Terminus font as usual
Additional info:
It appears that pango switched from using FreeType to HarfBuzz, which only
supports truetype. I rebuilt the Fedora 30 pango package (1.43) for Fedora 31,
downgraded it, and now my terminals are fine showing my bitmap fonts.
--
You are receiving this mail because:
You are on the CC list for the bug.
2 months, 1 week
[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.
2 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.
2 months, 2 weeks
[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.
2 months, 2 weeks
[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.
2 months, 2 weeks
[Fedora-i18n-bugs] [Bug 1830709] New: Invalid metainfo files
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1830709
Bug ID: 1830709
Summary: Invalid metainfo files
Product: Fedora
Version: 32
Status: NEW
Component: google-noto-fonts
Assignee: petersen(a)redhat.com
Reporter: mohd.akram(a)outlook.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,
pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Metainfo files provided by the package are deemed invalid by appstream.
Version-Release number of selected component (if applicable):
20181223-7.fc32
How reproducible:
Always.
Steps to Reproduce:
1. appstreamcli validate
/usr/share/metainfo/google-noto-sans-sinhala-vf.metainfo.xml
Actual results:
E: google-noto-sans-sinhala-vf:~: font-no-font-data
E: google-noto-sans-sinhala-vf:4: cid-is-not-rdns google-noto-sans-sinhala-vf
I: google-noto-sans-sinhala-vf:~: font-description-missing
E: google-noto-sans-sinhala-vf:~: component-summary-missing
E: google-noto-sans-sinhala-vf:~: component-name-missing
E: google-noto-sans-sinhala-vf:~: extends-not-allowed
I: google-noto-sans-sinhala-vf:4: cid-contains-hyphen
google-noto-sans-sinhala-vf
Validation failed: errors: 5, infos: 2
Expected results:
Validation was successful.
--
You are receiving this mail because:
You are on the CC list for the bug.
2 months, 2 weeks
