February 2019 - i18n-bugs - Fedora Mailing-Lists

[Fedora-i18n-bugs] [Bug 1415322] Wrong character displayed in UKai fonts for "zhi" (2nd tone) (character meaning "directly"), but not in ming fonts.

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1415322 --- Comment #11 from Peng Wu <pwu(a)redhat.com> --- It seems the upstream project is not active now. Maybe you could send an email to ask arne at ubuntu dot com about current status of the project. -- You are receiving this mail because: You are on the CC list for the bug.

5 years, 2 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1470673] [abrt] ibus: parse_compose_value(): ibus-engine-simple killed by signal 6

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1470673 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed In Version|ibus-1.5.19-16.fc29 |ibus-1.5.19-16.fc29 | |ibus-1.5.19-10.fc28 --- Comment #27 from Fedora Update System <updates(a)fedoraproject.org> --- ibus-1.5.19-10.fc28 has been pushed to the Fedora 28 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.

5 years, 2 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1470673] [abrt] ibus: parse_compose_value(): ibus-engine-simple killed by signal 6

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1470673 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Fixed In Version| |ibus-1.5.19-16.fc29 Resolution|--- |ERRATA Last Closed|2018-03-22 06:22:55 |2019-02-14 01:57:59 --- Comment #26 from Fedora Update System <updates(a)fedoraproject.org> --- ibus-1.5.19-16.fc29 has been pushed to the Fedora 29 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.

5 years, 2 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1415322] Wrong character displayed in UKai fonts for "zhi" (2nd tone) (character meaning "directly"), but not in ming fonts.

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1415322 --- Comment #10 from Bill <mattison.computer(a)yahoo.com> --- Today (Feb. 13), I tried to find out the status of this bug and bug 315606 in the cjkunifonts-Bugs (a part of alioth.debian.org). Bug 315606 was submitted as advised in comment #6 above. I was unable to find the cjkunifonts-Bugs web page. I took the problem to the Fedora users list for advice. Matthew Miller (Fedora Project Leader) suggested that I follow up here. See "https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o..." for that thread. I believe that the strategy of having "the problem fixed in the font itself, not as a one-off patch. That makes sense -- that way it gets fixed for everyone in the world, not just Fedora." is the correct one. But Matthew, like me, also could not find cjkunifonts-Bugs bug 315606. How do we get the font itself properly fixed? Is there something more that I should do? -- You are receiving this mail because: You are on the CC list for the bug.

5 years, 2 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1405539] Changing the default keyboard layout changes also disk decryption in plymouth, but only after next kernel update (initramfs rebuild), long afterwards

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1405539 Hans de Goede <hdegoede(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hdegoede(a)redhat.com --- Comment #50 from Hans de Goede <hdegoede(a)redhat.com> --- So this is somewhat related to bug 1059485 where I just added the following comment: "I'm not convinced regenerating the initrd is a good idea, we do kernel-updates often enough that users will pick-up the new plymouth soon enough and if the new plymouth contains some bug breaking the boot, then regenerating the initrd means we've just broken the users system in a way which is quite hard to recover from." This is different though, because we are not changing plymouth at the same time, except if the user has also installed a plymouth updated and not rebooted since ... I think we may need some way to boot a backup initrd and maybe then we can consider regenerating the initrd. Hmm, thinking more about this, plymouth uses the console keymap for input, and the initrd by default has all keymaps, so all that is necessary is updating the kernel commandline, which controls the keymap in the initrd I think, or at least it should ... With the upcoming BLS support for F30, the kernel options are coming from the grubenv, so updating them is much easier (does not require regenerating grub.cfg). But I wonder if the kernel commandline approach works, since things starting to work after the next kernel update suggests that somehow the keymap does get coded inside the initrd ? Either way I'm tempted to call this "not a bug" from the plymouth pov, since plymouth just uses / consumes the installed console keymap for keyboard input, even when the display is graphical. -- You are receiving this mail because: You are on the CC list for the bug.

5 years, 2 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1637760] [abrt] ibus: type_check_is_value_type_U(): ibus-x11 killed by SIGSEGV

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1637760 erichanif <erichanif(a)free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erichanif(a)free.fr --- Comment #20 from erichanif <erichanif(a)free.fr> --- *** Bug 1676837 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

5 years, 2 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1676290] New: sazanami-fonts: FTBFS in Fedora rawhide/f30

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1676290 Bug ID: 1676290 Summary: sazanami-fonts: FTBFS in Fedora rawhide/f30 Product: Fedora Version: rawhide Status: NEW Component: sazanami-fonts Assignee: tagoh(a)redhat.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com, walter.pete(a)yandex.com Blocks: 1674516 Target Milestone: --- Classification: Fedora sazanami-fonts failed to build from source in Fedora rawhide/f30 https://koji.fedoraproject.org/koji/taskinfo?taskID=32601130 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild Please fix sazanami-fonts 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, sazanami-fonts will be orphaned. Before branching of Fedora 31, sazanami-fonts will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://fedoraproject.org/wiki/Fails_to_build_from_source Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1674516 [Bug 1674516] (F30FTBFS) - Fedora 30 Mass Rebuild FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug.

5 years, 2 months

1
6
0 / 0

[Fedora-i18n-bugs] [Bug 1670078] Incorrect classification of Norwegian keyboard layouts

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1670078 --- Comment #6 from Mike FABIAN <mfabian(a)redhat.com> --- /usr/share/X11/xkb/rules/base.xml contains for Norway: <layout> <configItem> <name>no</name> <shortDescription>no</shortDescription> <description>Norwegian</description> <languageList> <iso639Id>nor</iso639Id> <iso639Id>nob</iso639Id> <iso639Id>nno</iso639Id> </languageList> </configItem> <variantList> <variant> <configItem> <name>nodeadkeys</name> <description>Norwegian (no dead keys)</description> </configItem> ... And for Denmark: <layout> <configItem> <name>dk</name> <shortDescription>da</shortDescription> <description>Danish</description> <languageList> <iso639Id>dan</iso639Id> </languageList> </configItem> <variantList> <variant> <configItem> <name>nodeadkeys</name> <description>Danish (no dead keys)</description> </configItem> ... And /usr/share/xml/iso-codes/iso_639.xml has for "dan": <iso_639_entry iso_639_2B_code="dan" iso_639_2T_code="dan" iso_639_1_code="da" name="Danish" /> So it looks to me that "nno" is used to lookup that name in case of Norway and "dan" is used for Denmark. And the name is looked up in And /usr/share/xml/iso-codes/iso_639.xml. -- You are receiving this mail because: You are on the CC list for the bug.

5 years, 2 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1670078] Incorrect classification of Norwegian keyboard layouts

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1670078 --- Comment #5 from Mike FABIAN <mfabian(a)redhat.com> --- It looks to me that this does not come from langtable. Because: $ grep -B 4 "Norwegian Nynorsk; Nynorsk, Norwegian" /usr/share/xml/iso-codes/* /usr/share/xml/iso-codes/iso_639-2.xml- <iso_639_entry /usr/share/xml/iso-codes/iso_639-2.xml- iso_639_2B_code="nno" /usr/share/xml/iso-codes/iso_639-2.xml- iso_639_2T_code="nno" /usr/share/xml/iso-codes/iso_639-2.xml- iso_639_1_code="nn" /usr/share/xml/iso-codes/iso_639-2.xml: name="Norwegian Nynorsk; Nynorsk, Norwegian" /> -- /usr/share/xml/iso-codes/iso_639.xml- <iso_639_entry /usr/share/xml/iso-codes/iso_639.xml- iso_639_2B_code="nno" /usr/share/xml/iso-codes/iso_639.xml- iso_639_2T_code="nno" /usr/share/xml/iso-codes/iso_639.xml- iso_639_1_code="nn" /usr/share/xml/iso-codes/iso_639.xml: name="Norwegian Nynorsk; Nynorsk, Norwegian" /> I.e. the exact string "Norwegian Nynorsk; Nynorsk, Norwegian" which is seen in your screenshot happens to be in /usr/share/xml/iso-codes/iso_639.xml. But I cannot find that string in the langtable data. langtable does have "Norwegian Nynorsk" as the English name for the language id “nn”: <language> <languageId>nn</languageId> <iso639-1>nn</iso639-1> <iso639-2-t>nno</iso639-2-t> <iso639-2-b>nno</iso639-2-b> <names> ... <name><languageId>en</languageId><trName>Norwegian Nynorsk</trName></name> -- You are receiving this mail because: You are on the CC list for the bug.

5 years, 2 months

1
0
0 / 0

[Fedora-i18n-bugs] [Bug 1670078] Incorrect classification of Norwegian keyboard layouts

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1670078 David Sommerseth <dazo(a)eurephia.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dazo(a)eurephia.org | |) | --- Comment #4 from David Sommerseth <dazo(a)eurephia.org> --- Created attachment 1533988 --> https://bugzilla.redhat.com/attachment.cgi?id=1533988&action=edit Danish keyboard layouts Danish and Norwegian are pretty close in language and even the keyboard layouts have few differences. But this is how the Norwegian one should somewhat look like. Basically, just replace "Danish" with "Norwegian". -- You are receiving this mail because: You are on the CC list for the bug.

5 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs February 2019