https://bugzilla.redhat.com/show_bug.cgi?id=1762455
fujiwara <tfujiwar(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CLOSED |MODIFIED
Resolution|ERRATA |---
Keywords| |Reopened
--- Comment #16 from fujiwara <tfujiwar(a)redhat.com> ---
Reopening the bug to follow the maintainer's suggestion since F31 glib2 is not
avalable yet.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1762455
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ON_QA |CLOSED
Fixed In Version| |glib2-2.60.7-2.fc30
Resolution|--- |ERRATA
Last Closed| |2019-11-17 01:13:39
--- Comment #15 from Fedora Update System <updates(a)fedoraproject.org> ---
glib2-2.60.7-2.fc30 has been pushed to the Fedora 30 stable repository. If
problems still persist, please make note of it in this bug report.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1762455
--- Comment #14 from Stefan Haan <stefanhaan08(a)gmail.com> ---
Updating to glib2-2.60.7-2.fc30.x86_64 fixed my input problems with anki and
telegram-desktop :)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1762455
--- Comment #13 from fujiwara <tfujiwar(a)redhat.com> ---
(In reply to Michael Catanzaro from comment #11)
> Due to scheduling, we decided to wait a few days for glib 2.62.3 before
> preparing a F31 update. Please make sure to reopen this bug if bodhi closes
> it if the F30 update lands before the F31 update is ready.
OK, I understood what you meant. Thank you for fixing F30 too.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1762455
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|MODIFIED |ON_QA
--- Comment #12 from Fedora Update System <updates(a)fedoraproject.org> ---
glib2-2.60.7-2.fc30 has been pushed to the Fedora 30 testing repository. If
problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2019-9ff4e37cb3
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1619530
--- Comment #20 from Alan <alan.g12r(a)outlook.com> ---
(In reply to Vendula Poncova from comment #16)
> When I install bpg-dejavu-sans-fonts in Live OS, the issue seems to be fixed
> (see the attachment F32 Live Screenshot). Could someone confirm that this is
> the expected output? If yes, we need to make sure that the font is installed
> in the boot.iso (handled by lorax) and Live images (handled by
> spin-kickstarts). Anaconda doesn't install any fonts.
The text on the right top corner (Fedora's installation) is correctly shown in
Georgian, as long as it's all caps. But the word "Georgian" in the language
menu is inaccurate, because titlecasing is not expected in modern Georgian.
(In reply to Mike FABIAN from comment #9)
> So anaconda should make an exception for Georgian not to automatically
> capitalize the first letter.
Yes, automatic capitalization just should not be applied to Georgian text. A
localizer can decide, whether or not to use uppercase for emphasis.
> (In reply to Jens Petersen from comment #6)
> > It is surprising then that neither bpg-sans-fonts or
> > google-noto-sans-georgian-fonts cover the glyph(s).
>
> There is a work around for Noto fonts:
> https://github.com/googlefonts/noto-fonts/issues/1261
> Here you can get bpg-fonts that support Mtavruli:
> https://bpgfonts.wordpress.com/2018/09/07/gnu-gpl-license-grant-to-linux-
> distributors/
Now Google Noto fonts also include Mtavruli characters (updated 2 months ago):
https://github.com/googlefonts/noto-fonts/tree/master/hinted/NotoSansGeorgi…
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1762455
Michael Catanzaro <mcatanzaro(a)gnome.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mcatanzaro(a)gnome.org
Flags|needinfo?(mclasen(a)redhat.co |
|m) |
--- Comment #11 from Michael Catanzaro <mcatanzaro(a)gnome.org> ---
Due to scheduling, we decided to wait a few days for glib 2.62.3 before
preparing a F31 update. Please make sure to reopen this bug if bodhi closes it
if the F30 update lands before the F31 update is ready.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1762455
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |MODIFIED
--- Comment #10 from Fedora Update System <updates(a)fedoraproject.org> ---
FEDORA-2019-9ff4e37cb3 has been submitted as an update to Fedora 30.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-9ff4e37cb3
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1762455
Christian Krause <chkr(a)plauener.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(mclasen(a)redhat.co
| |m)
--- Comment #9 from Christian Krause <chkr(a)plauener.de> ---
@glib2 maintainers:
Please can you have a look at this issue?
Are you interested in a merge request to backport the mentioned upstream bug
fix?
It looks like that other distributions backported the changes:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941018
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1090631
--- Comment #9 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
TT_NAME_ID_FONT_FAMILY (Name ID 16) is actually quite problematic, it was not
defined strictly enough to be useful for apps.
The correct way to group fonts is to use Name ID 21, and fallback to Name ID 16
if it is not present. Though Name ID 21 may be absent either because 16 already
has the value 21 would have, or because 16 is completely broken but not yet
fixed via 21.
Distinguishing between those two cases requires setting bit 8 of the
fsSelection correctly (and reading this bit app-side)
https://docs.microsoft.com/en-us/typography/opentype/spec/name
In any case keying "Liberation" is *definitely* broken from a OpenType WWS PoW,
so using it in Liberation files *requires* setting Name ID 21 to fix it.
If fail to see the point of introducing known-broken naming at the 16 layer,
just to get the benefit to fix it at the 21 layer. Just use WWS-conformant
naming at 16 and 17 directly.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1619530
--- Comment #19 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
Yes, sure, it’s bigger than a font or Anaconda, it’s how Georgian is expected
to behave, and how it got standardised
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1619530
--- Comment #18 from Jiri Konecny <jkonecny(a)redhat.com> ---
(In reply to Nicolas Mailhot from comment #17)
> (In reply to Jiri Konecny from comment #14)
> > The question is if we should use other fonts which would work or to change
> > Anaconda code. Honestly the first variant seems like a less hacky to me...
>
> The first option is a short-term workaround. The way Georgian has been
> standardized Unicode-side is not expected to change. So if anaconda does not
> handle it properly, the issue will come back in a few releases when the
> Fedora font set gets updated.
Don't you think that this problem is bigger than Anaconda? Anaconda is just one
of the projects but all the projects supporting Georgian may experience the
same issue. I don't think it's reasonable to fix one case instead of fixing the
root cause here.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1619530
--- Comment #17 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
(In reply to Jiri Konecny from comment #14)
> The question is if we should use other fonts which would work or to change
> Anaconda code. Honestly the first variant seems like a less hacky to me...
The first option is a short-term workaround. The way Georgian has been
standardized Unicode-side is not expected to change. So if anaconda does not
handle it properly, the issue will come back in a few releases when the Fedora
font set gets updated.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1619530
--- Comment #16 from Vendula Poncova <vponcova(a)redhat.com> ---
When I install bpg-dejavu-sans-fonts in Live OS, the issue seems to be fixed
(see the attachment F32 Live Screenshot). Could someone confirm that this is
the expected output? If yes, we need to make sure that the font is installed in
the boot.iso (handled by lorax) and Live images (handled by spin-kickstarts).
Anaconda doesn't install any fonts.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1619530
--- Comment #14 from Jiri Konecny <jkonecny(a)redhat.com> ---
The question is if we should use other fonts which would work or to change
Anaconda code. Honestly the first variant seems like a less hacky to me...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1619530
--- Comment #13 from Mike FABIAN <mfabian(a)redhat.com> ---
So it looks like we need something like this:
$ git diff
diff --git a/pyanaconda/localization.py b/pyanaconda/localization.py
index 59a58d51f..e642cb5db 100644
--- a/pyanaconda/localization.py
+++ b/pyanaconda/localization.py
@@ -335,6 +335,8 @@ def get_native_name(locale):
territoryIdQuery=parts.get("territory",
""),
scriptIdQuery=parts.get("script", ""))
+ if parts["language"].startswith("ka"):
+ return name
return upcase_first_letter(name)
def get_available_translations(localedir=None):
lines 1-13/13 (END)
which looks crazy, but what else could one do?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1619530
--- Comment #12 from Mike FABIAN <mfabian(a)redhat.com> ---
(In reply to Jens Petersen from comment #10)
> (In reply to Mike FABIAN from comment #9)
> > So anaconda should make an exception for Georgian not to automatically
> > capitalize the first letter.
>
> Shouldn't that be handled elsewhere?
I guess this code does it:
https://github.com/rhinstaller/anaconda/blob/master/pyanaconda/localization…
def get_native_name(locale):
"""
Function returning native name for the given locale.
:param locale: locale to return native name for
:type locale: str
:return: english name for the locale or empty string if unknown
:rtype: st
:raise InvalidLocaleSpec: if an invalid locale is given (see LANGCODE_RE)
"""
parts = parse_langcode(locale)
if "language" not in parts:
raise InvalidLocaleSpec("'%s' is not a valid locale" % locale)
name = langtable.language_name(languageId=parts["language"],
territoryId=parts.get("territory", ""),
scriptId=parts.get("script", ""),
languageIdQuery=parts["language"],
territoryIdQuery=parts.get("territory", ""),
scriptIdQuery=parts.get("script", ""))
return upcase_first_letter(name)
So it upper cases the first letter of the language name. For almost all
languages, this is what we want if the name appears isolated in a list, it is
sort of like at the start of a sentence then. For languages which don’t have
uppercase letters (like Japanese for example), the uppercasing changes nothing.
Georgian seems special in that uppercase letters are available, but apparently
they are not supposed to be used in title case.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1658187
fujiwara <tfujiwar(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |POST
--- Comment #3 from fujiwara <tfujiwar(a)redhat.com> ---
One process is running in the background to manage copy & paste in Wayland,
another one is invoked by `ibus emoji` command.
So the later process exists until the user type Esc key.
But this issue explains the process is persistent even if Esc key is typed and
I fixed it in upstream.
https://github.com/ibus/ibus/commit/26a8105b7003953e56bf04426ee89a93482a45c5
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1761556
Bug ID: 1761556
Summary: fntsample missing dependency on perl-libintl-perl
Product: Fedora
Version: 29
Hardware: x86_64
Status: NEW
Component: fntsample
Severity: low
Assignee: pnemade(a)redhat.com
Reporter: nepeta(a)msu.edu
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com,
psatpute(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The pdfoutline tool included with fntsample requires Perl module
Locale::TextDomain (packaged in perl-libintl-perl), but the fntsample package
doesn't specify it as a dependency.
Version-Release number of selected component (if applicable):
fntsample-5.2-2.fc29
How reproducible:
always
Steps to reproduce:
1. Without perl-libintl-perl installed, install the fntsample package.
2. Run pdfoutline.
Actual results:
Application reported an error: "Can't locate Locale/TextDomain.pm in @INC (you
may need to install the Locale::TextDomain module) [...] at /bin/pdfoutline
line 36."
Expected results:
Usage instructions.
Additional info:
Installing perl-libintl-perl causes the application to work as expected.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1657030
Peter Hatina <peter(a)hatina.eu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |NEXTRELEASE
Flags|needinfo?(peter(a)hatina.eu) |
Last Closed| |2019-11-07 06:09:47
--- Comment #8 from Peter Hatina <peter(a)hatina.eu> ---
Upgrading to KDE Plasma 5.17 seems to fix this. Closing.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1619530
Tom "spot" Callaway <tcallawa(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #11 from Tom "spot" Callaway <tcallawa(a)redhat.com> ---
bpg-fonts-20120413-14.fc32 just built in rawhide, it includes the newer bpg
versions of DejaVu indicated in Comment #8.
If I need to also build this for stable branches, please let me know.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1619530
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(mfabian(a)redhat.co |
|m) |
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1619530
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fonts-bugs(a)lists.fedoraproj
| |ect.org,
| |tcallawa(a)redhat.com
Component|anaconda |bpg-fonts
Assignee|anaconda-maint-list@redhat. |tcallawa(a)redhat.com
|com |
Flags| |needinfo?(mfabian(a)redhat.co
| |m)
--- Comment #10 from Jens Petersen <petersen(a)redhat.com> ---
(In reply to Mike FABIAN from comment #9)
> So anaconda should make an exception for Georgian not to automatically
> capitalize the first letter.
Shouldn't that be handled elsewhere?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1708013
Bug ID: 1708013
Summary: gettext-0.20 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: gettext
Keywords: FutureFeature, Triaged
Assignee: panovotn(a)redhat.com
Reporter: upstream-release-monitoring(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,
panovotn(a)redhat.com, petersen(a)redhat.com,
praiskup(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 0.20
Current version/release in rawhide: 0.19.8.1-18.fc30
URL: http://www.gnu.org/software/gettext/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/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/898/
--
You are receiving this mail because:
You are on the CC list for the bug.