https://bugzilla.redhat.com/show_bug.cgi?id=1195541
Bug ID: 1195541
Summary: When switching windows, input to always English.
Product: Fedora
Version: 22
Component: ibus-hangul
Severity: medium
Assignee: dueno(a)redhat.com
Reporter: sangu.fedora(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
pwu(a)redhat.com, shawn.p.huang(a)gmail.com
Description of problem:
When switching windows, input to always English.
Version-Release number of selected component (if applicable):
1.5.0-1.fc22.x86_64
How reproducible:
always
Steps to Reproduce:
1. Start two apps (gedit, gnome-terminal)
2. toggle to hangul (click shift + space or hangul key)
3. switching window (alt + tab)
4. input
Actual results:
english alphabet
Expected results:
Hangul
Additional info:
ibus-1.5.9-10.fc22.x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=aPLIVFwgAa&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1126249
Bug ID: 1126249
Summary: Component Description of mozc in bugzilla should be
self-contained, and shouldn't rely on other
trademarked product name
Product: Fedora
Version: rawhide
Component: mozc
Assignee: tagoh(a)redhat.com
Reporter: yukawa(a)google.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com
Created attachment 923718
--> https://bugzilla.redhat.com/attachment.cgi?id=923718&action=edit
Component Description says Mozc is "Opensourced Google Japanese Input"
Description of problem:
When you select Mozc in bugzilla.redhat.com, the Component Description says it
is "Opensourced Google Japanese Input". However, OSS Mozc and Google Japanese
Input are different products. IANAL, but I feel the description of OSS Mozc
should be self-contained, and shouldn't rely on other trademarked product name.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Go to https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora
2. Type 'Mozc' in Component section
Actual results:
Component Description says it is "Opensourced Google Japanese Input". See the
attached screenshot.
Expected results:
Component Description should be carefully chosen here because OSS Mozc and
Google Japanese Input are different products. One idea is using the same
description of mozc.spec. What do you think?
Additional info:
Current description of mozc.spec looks a bit obsolete because now Android is
also supported in OSS Mozc. It would be nice if the description of mozc.spec
is also updated.
http://pkgs.fedoraproject.org/cgit/mozc.git/tree/mozc.spec?id=6be8b756d0326…
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Am1nP5Oakm&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1117705
Bug ID: 1117705
Summary: Main2.py should renamed to "<IME Name> Preferences"
Product: Fedora
Version: rawhide
Component: ibus-pinyin
Assignee: pwu(a)redhat.com
Reporter: apatil(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, pwu(a)redhat.com,
shawn.p.huang(a)gmail.com
Created attachment 916675
--> https://bugzilla.redhat.com/attachment.cgi?id=916675&action=edit
screen shot
Description of problem:
For UI consistency across all IME's and better user experience, it would be
nice to have "<IME Name> Preferences" instead of Main2.py
Please find screen shot attached.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=N2xErhcY8J&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1084228
Bug ID: 1084228
Summary: Hinting for Liberation Sans inferior at small font
size
Product: Fedora
Version: 20
Component: liberation-fonts
Assignee: psatpute(a)redhat.com
Reporter: Eduard.Braun2(a)gmx.de
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
Created attachment 882473
--> https://bugzilla.redhat.com/attachment.cgi?id=882473&action=edit
testcase with the problematic font charakteristics
Wikipedia recently switched to a predefined CSS font stack for body font so
even Windows users will be served with Liberation Sans if installed (e.g.
because it is distributed with Libre Office).
This made apparent inferior hinting of Liberation Sans with bold weight when
rendered at the specific size of 0.875em (the font size used in MediaWiki's
vector skin).
Most notable "e"s have a very thick lower curve while the upper curve is much
too thin. This also applies for variants like "è é ê ë". Funnily not for "œ æ"
though which is rendered differently.
Also notable is e.g. "s" which has thick upper/lower curves but is thin in the
middle.
A testcase with the described font characteristics set is attached. The
screenshot shows the rendering in Firefox.
The screenshot was created with Firefox 28.0 on Windows 7.
The installed version of the Liberation fonts is 2.00.1
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Msol5goZ6N&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1011371
Bug ID: 1011371
Summary: cloud pinyin feature is missed in ibus
Product: Fedora
Version: rawhide
Component: ibus-libpinyin
Assignee: pwu(a)redhat.com
Reporter: tfujiwar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Now ibus-cloud-pinyin is available:
http://code.google.com/p/ibus-cloud-pinyin/
Actually I'm not sure if the cloud feature is useful for Chinese users so it's
up to you to integrate the feature or will not fix.
Originally someone pointed out that ibus missed that feature.
Maybe it's an idea to release ibus-cloud-pinyin in Fedora while it provides
sogou only and fcitx provides sogou, ime.qq.com, google, baidu.
I was also interested in the cloud for ja but it seems the protocol is closed
in google.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=EXcOrJl2sb&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1169979
Bug ID: 1169979
Summary: Some fonts not in fontconfig cache on Fedora 21 live
images
Product: Fedora
Version: 21
Component: fontconfig
Assignee: tagoh(a)redhat.com
Reporter: awilliam(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com,
tagoh(a)redhat.com
We've spotted an issue with Fedora 21 live images where some installed fonts
appear to be missing from the fontconfig cache in the live environment. An
'fc-cache -f' fixes this. For instance, on the Fedora 21 Final RC2 Workstation
x86_64 live:
[root@localhost liveuser]# fc-list | wc -l
141
[root@localhost liveuser]# fc-cache --force
[root@localhost liveuser]# fc-list | wc -l
159
The specific fonts that are missing on that image are:
/usr/share/fonts/dejavu/DejaVuSansMono-BoldOblique.ttf: DejaVu Sans
Mono:style=Bold Oblique
/usr/share/fonts/dejavu/DejaVuSansMono-Bold.ttf: DejaVu Sans Mono:style=Bold
/usr/share/fonts/dejavu/DejaVuSansMono-Oblique.ttf: DejaVu Sans
Mono:style=Oblique
/usr/share/fonts/dejavu/DejaVuSansMono.ttf: DejaVu Sans Mono:style=Book
/usr/share/fonts/dejavu/DejaVuSerif-BoldItalic.ttf: DejaVu Serif:style=Bold
Italic
/usr/share/fonts/dejavu/DejaVuSerif-Bold.ttf: DejaVu Serif:style=Bold
/usr/share/fonts/dejavu/DejaVuSerifCondensed-BoldItalic.ttf: DejaVu
Serif,DejaVu Serif Condensed:style=Condensed Bold Italic,Bold Italic
/usr/share/fonts/dejavu/DejaVuSerifCondensed.ttf: DejaVu Serif,DejaVu Serif
Condensed:style=Condensed,Book
/usr/share/fonts/dejavu/DejaVuSerif-Italic.ttf: DejaVu Serif:style=Italic
/usr/share/fonts/dejavu/DejaVuSerif.ttf: DejaVu Serif:style=Book
/usr/share/fonts/google-noto/NotoSansTagalog-Regular.ttf: Noto Sans
Tagalog:style=Regular
/usr/share/fonts/google-noto/NotoSansTaiViet-Regular.ttf: Noto Sans Tai
Viet:style=Regular
/usr/share/fonts/liberation/LiberationSerif-BoldItalic.ttf: Liberation
Serif:style=Bold Italic
/usr/share/fonts/liberation/LiberationSerif-Bold.ttf: Liberation
Serif:style=Bold
/usr/share/fonts/liberation/LiberationSerif-Italic.ttf: Liberation
Serif:style=Italic
/usr/share/fonts/liberation/LiberationSerif-Regular.ttf: Liberation
Serif:style=Regular
The log of the compose is here:
https://kojipkgs.fedoraproject.org//work/tasks/5463/8275463/root.log
In comparison, the i686 Workstation live is 'missing' only
/usr/share/fonts/google-noto/NotoSansTaiViet-Regular.ttf: Noto Sans Tai
Viet:style=Regular
its compose log is here:
https://kojipkgs.fedoraproject.org//work/tasks/5460/8275460/root.log
to me, it appears the affected cases are ones where more than one package
contains fonts in the same directory, for packages installed *after* the
fontconfig package. The fontconfig package has an 'fc-cache -f' in its %post,
so any inconsistencies that exist before it's installed get fixed by that.
My first thesis was 'for any given directory, only fonts from the first package
installed after fontconfig will make it to the cache, fonts in the same
directory from subsequently-installed packages won't be added'. But it doesn't
seem to be that simple, because some fonts in /usr/share/fonts/google-noto
*are* added - the first 'noto' package installed is google-noto-sans-lisu-fonts
, and after that several more noto packages are installed. The fonts from
google-noto-sans-mandaic-fonts, google-noto-sans-meeteimayek-fonts , and
google-noto-sans-tai-tham-fonts *do* get added to the cache - but the fonts
from google-noto-sans-tagalog-fonts and google-noto-sans-tai-viet-fonts do
*not* get added. It's quite odd.
This is a fairly bad bug because of its impact on DejaVu Sans Mono: this is the
default monospace font for both Workstation and KDE (and I think the
non-blocking spins too). Its absence from the cache results in them using
Nimbus Mono L as their monospace fonts, which is a pretty crappy font, ugly and
hard to read. The workaround is easy once you know it, but if you don't, you
just think we have a really bad font.
There's an easy big hammer workaround we can use for a quick rebuild of the RC2
lives, if we like:
--- a/fedora-live-base.ks
+++ b/fedora-live-base.ks
@@ -299,6 +299,12 @@ rm -f /core*
# convince readahead not to collect
# FIXME: for systemd
+# forcibly regenerate fontconfig cache (so long as this live image has
+# fontconfig) - see #XXXXXXX
+if [ -x /usr/bin/fc-cache ] ; then
+ fc-cache -f
+fi
+
%end
i.e., just do an fc-cache -f at the end of live generation %post. I've tested
that locally, and it works, the generated Workstation image has 159 fonts in
fc-list (I also generated an image with the exact same config and build host,
but no change to spin-kickstarts, to verify that it reproduced the bug, and it
does).
The real fix should likely be in fc-cache, but the spin-kickstarts workaround
would solve this problem for F21.
I think fc-cache's behaviour must have changed between F20 and F21, as F20
doesn't appear to be affected by this at all, at least not the x86_64 desktop
live. All F21 images I've tested seem to be affected to some extent, though the
exact affected fonts vary depending on the package install order that yum
decided on.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Ex4RiyuuM1&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1154526
Bug ID: 1154526
Summary: fi_FI compose keys not working after installation
Product: Fedora
Version: 21
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: myllynen(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
Description of problem:
After installing F21 Alpha using Finnish for language and keyboard, fi_FI
compose keys are not in use although LC_CTYPE=fi_FI.utf8.
Earlier related bug about this was
https://bugzilla.redhat.com/show_bug.cgi?id=1013651. See especially
https://bugzilla.redhat.com/show_bug.cgi?id=1013651#c13.
The highly unintuitive step mentioned in bug 1013651#c13 is still needed to
make this work, so the question is do we want to enable this by default or make
enabling it a bit more intuitive or at least document this?
Additional info:
The quick test to see whether fi_FI compose keys work is that with
LC_CTYPE=fi_FI.UTF-8 dead_acute + space should produce acute (not apostrophe as
with en_US.UTF-8).
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=C6KjJh8qDv&a=cc_unsubscribe
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [indic] yum showing content in indic languages, those are broken for terminal
https://bugzilla.redhat.com/show_bug.cgi?id=525046
Summary: [indic] yum showing content in indic languages, those
are broken for terminal
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: yum
AssignedTo: skvidal(a)sethdot.org
ReportedBy: aalam(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: james.antill(a)redhat.com, pmatilai(a)redhat.com,
tim.lauridsen(a)googlemail.com, ffesti(a)redhat.com,
maxamillion(a)gmail.com, skvidal(a)sethdot.org,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
while running yum command in Punjabi Desktop (pa_IN) locale, there was some
output, which is broken, failed to read from terminal. When using Group
command,then all things are broken.
Version-Release number of selected component (if applicable):
yum-3.2.24-5.fc12
How reproducible:
100%
Steps to Reproduce:
1. in gnome-terminal set locale as 'export LANG=pa_IN.UTF-8'
2. yum grouplist
3.
Actual results:
output contains Punjabi (pa_IN) language, which is not shown properly
Expected results:
as Indic (all) languages are not render properly on Terminal, so output
should be in English for better use.
Additional info:
1) Other affected locales are *_IN (as_IN,bn_IN,gu_IN,hi_IN,ml_IN,mr_IN...)
2) for GUI front-end (gpk-application) locales are working fine
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [gcin] [Feature request] Please pack the voice data.
https://bugzilla.redhat.com/show_bug.cgi?id=511197
Summary: [gcin] [Feature request] Please pack the voice data.
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: gcin
AssignedTo: candyz0416(a)gmail.com
ReportedBy: dchen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, candyz0416(a)gmail.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
One of nice gcin features is gcin prounces the character you type, thus lower
typo rate. However, the voice data is not packed in fedora.
Version-Release number of selected component (if applicable):
1.4.5-2.fc11
How reproducible:
Always
Steps to Reproduce:
1. Right click on gcin for gcin setup menu.
2. Click on "Default input method & Enable/disable".
3. Enable "Speak as you type".
Actual results:
Due to lack of voice data, this function is not functional.
Expected results:
gcin speaks as you type.
Additional info:
Voice data can be downloaded at:
http://cle.linux.org.tw/trac/wiki/GcinTextToSpeech
How about make a gcin-voice sub-package?
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1182821
Bug ID: 1182821
Summary: unable to invoke function after pressing enter in
search box of evernote.com
Product: Fedora
Version: 21
Component: ibus-chewing
Severity: medium
Assignee: dchen(a)redhat.com
Reporter: dchen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com
Description of problem:
Log in with your evernote account and click the search button on left panel.
Then type some words with ibus-chewing, it would fail to trigger the search
function.
BUT…ibus-anthy did it successfully.
See also https://github.com/definite/ibus-chewing/issues/48
Version-Release number of selected component (if applicable):
ibus-chewing-1.4.14
How reproducible:
Always
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=gPH6iQOV1D&a=cc_unsubscribe