[Fedora-i18n-bugs] [Bug 1249335] New: Inconsistent rules for shortcuts between different applications when switching keymaps
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1249335
Bug ID: 1249335
Summary: Inconsistent rules for shortcuts between different
applications when switching keymaps
Product: Fedora
Version: 22
Component: ibus
Severity: medium
Assignee: tfujiwar(a)redhat.com
Reporter: nicolas.brack(a)mail.be
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
I have this bug since a few fedora version. In some applications, the
shortcuts obeys the localized ibus keymap, but other keeps the default keymap
when pressing CTRL. Typical example includes gimp (follows keymap) and
inkscape (ignore keymap). I'm personally using both the us and dvorak keymap,
and this behaviour is pernicious as the key locations are very dissimilar.
Using "setxkbmap" is hard erasure of the keymap, and after that _all_
applications follows the keymap when using the shortcuts. But then ibus
doesn't really work anymore, and it's inconvenient.
Thus a solution could either be that:
*ibus is resilient to "setxkbmap"
*All software are presented with the same keymap, which can be configured to be
the current map.
Software versions:
GNOME Shell 3.16.3
IBus 1.5.10
Xorg 1.17.2
--
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=0xQlpdl2Ss&a=cc_unsubscribe
4 years, 8 months
[Fedora-i18n-bugs] [Bug 507262] New: Separate Japanese font configuration files for ghostscript
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Separate Japanese font configuration files for ghostscript
https://bugzilla.redhat.com/show_bug.cgi?id=507262
Summary: Separate Japanese font configuration files for
ghostscript
Product: Fedora
Version: 11
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: japanese-bitmap-fonts
AssignedTo: tagoh(a)redhat.com
ReportedBy: t.matsuu(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
I'm not sure which component should be assigned for this bug. So I initially
assign this bug to japanese-bitmap-fonts because the files for discussion is
now owned by japanese-bitmap-fonts package.
Description of problem:
Now
/usr/share/ghostscript/conf.d/CIDFnmap.ja
/usr/share/ghostscript/conf.d/FAPIcidfmap.ja
/usr/share/ghostscript/conf.d/cidfmap.ja
are owned by japanese-bitmap-fonts. But they never use fonts which are bundled
in japanese-bitmap-fonts.
Moreover, fonts which are set in the config files are dispersed among some
packages.
So we need to separate ghostscript contig files from japanese-bitmap-fonts and
they should be provided by another package (or included in ghostscript or
ghostscript-fonts package).
I suggest the following idea.
1. Universal
/usr/share/ghostscript/conf.d/{CIDFnmap.ja,FAPIcidfmap.ja,cidfmap.ja} is owned
by new (eg. ghostscript-fonts-japanese), ghostscript, or ghostscript-fonts
package.
2. Each Japanese fonts have their own CIDFnmap.ja, FAPIcidfmap.ja, and
cidfmap.ja files i their common package.
Discussion required:
* fonts priority
* file owner for ghostscript config files
* package structure of IPA fonts are not ready for generate common subpackage
now (bug 507261)
--
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.
4 years, 9 months
[Fedora-i18n-bugs] [Bug 1090631] New: Please set TT_NAME_ID_PREFERRED_FAMILY for Liberation fonts
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1090631
Bug ID: 1090631
Summary: Please set TT_NAME_ID_PREFERRED_FAMILY for Liberation
fonts
Product: Fedora
Version: rawhide
Component: liberation-fonts
Assignee: psatpute(a)redhat.com
Reporter: rhughes(a)redhat.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
Description of problem:
At the moment the TT_NAME_ID_PREFERRED_FAMILY is not set on any of the
Liberation fonts. As I understand it, TT_NAME_ID_PREFERRED_FAMILY is supposed
to be the same for all files in the same high-level family, and this seems to
be what most other fonts do in Linux. For the next release could you please set
the PreferredFamily key to just "Liberation" in all 10 files. This allows
component installers like gnome-software to group the fonts together rather
than showing them as separate entries and should have no other effects.
Thanks,
Richard.
--
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=ZrCMOyiIAn&a=cc_unsubscribe
4 years, 9 months
[Fedora-i18n-bugs] [Bug 1014357] New: U+266B incorrect glyph with extra beam
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1014357
Bug ID: 1014357
Summary: U+266B incorrect glyph with extra beam
Product: Fedora
Version: rawhide
Component: liberation-fonts
Assignee: psatpute(a)redhat.com
Reporter: fabian+redhat(a)greffrath.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
Originally reported as Debian #724839 [1] by Drake Wilson:
"
Using gucharmap 1:3.8.2-2 to view Liberation Serif characters with "Show only
glyphs from this font" enabled, the glyph for U+266B BEAMED EIGHTH NOTES shows
what is clearly beamed sixteenth notes instead; it should have only one beam
rather than two. FontForge confirms this after opening
LiberationSerif-Regular.ttf with SHA-256 =
ea76595ed32ec4bb117fc715e393b4cca3d42cabe53101baec6bbbeb800fa26a.
The glyph for U+266C BEAMED SIXTEENTH NOTES is correct.
"
The bug has been reported against version 2.00.1, ut I have checked with 1.07.3
and it is also present in this version.
Best regards,
Fabian
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724839
--
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=PXTyqCv0jP&a=cc_unsubscribe
4 years, 9 months