i18n-bugs November 2016

i18n-bugs@lists.fedoraproject.org

2 participants
185 discussions

[Fedora-i18n-bugs] [Bug 1035486] New: Text renders fuzzy in Fedora 20
by Red Hat Bugzilla 20 Aug '18

20 Aug '18

https://bugzilla.redhat.com/show_bug.cgi?id=1035486 Bug ID: 1035486 Summary: Text renders fuzzy in Fedora 20 Product: Fedora Version: 20 Component: fontconfig Assignee: tagoh(a)redhat.com Reporter: alexhultman(a)gmail.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 Description of problem: 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. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=3Q3EeLcWVs&a=cc_unsubscribe

2 54

[Fedora-i18n-bugs] [Bug 1176874] New: gcin-2.8.3 is available
by Red Hat Bugzilla 24 Jul '18

24 Jul '18

https://bugzilla.redhat.com/show_bug.cgi?id=1176874 Bug ID: 1176874 Summary: gcin-2.8.3 is available Product: Fedora Version: rawhide Component: gcin Keywords: FutureFeature, Triaged Assignee: i(a)cicku.me Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, i(a)cicku.me Latest upstream release: 2.8.3 Current version/release in Fedora Rawhide: 2.8.2-3.fc22 URL: http://hyperrate.com/gcin-source/ 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 Soon this service will be implemented by a new system: https://release-monitoring.org/ It will require to manage monitored projects via a new web interface. Please make yourself familiar with the new system to ease the transition. -- 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=u18ESfXqvf&a=cc_unsubscribe

2 14

[Fedora-i18n-bugs] [Bug 803646] New: Password is visible on gnome-terminal with English-typing-booster enabled
by Red Hat Bugzilla 23 Jul '18

23 Jul '18

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Password is visible on gnome-terminal with English-typing-booster enabled https://bugzilla.redhat.com/show_bug.cgi?id=803646 Summary: Password is visible on gnome-terminal with English-typing-booster enabled Product: Fedora Version: 17 Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: unspecified Priority: unspecified Component: ibus-european-table AssignedTo: apatil(a)redhat.com ReportedBy: apeter(a)redhat.com QAContact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, apatil(a)redhat.com Classification: Fedora Story Points: --- Type: --- Regression: --- Mount Type: --- Documentation: --- Created attachment 570253 --> https://bugzilla.redhat.com/attachment.cgi?id=570253 Password being displayed on terminal Description of problem: With English-typing-booster enabled on gnome-terminal, while using su- command, password appears in the text. Version-Release number of selected component (if applicable): english-typing-booster-0.0.2-1.fc17 How reproducible: Always Steps to Reproduce: 1. Enable English-typing-booster 2. Go to terminal 3. Try to become root with su- 4. Type your password Actual results: Perform above steps, you can see the password is shown on the screen. Expected results: Password must not be shown. Additional info: -- 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.

2 18

[Fedora-i18n-bugs] [Bug 1388395] New: [abrt] ibus: bus_dbus_impl_name_owner_changed(): ibus-daemon killed by SIGABRT: TAINTED
by Red Hat Bugzilla 23 Jul '18

23 Jul '18

https://bugzilla.redhat.com/show_bug.cgi?id=1388395 Bug ID: 1388395 Summary: [abrt] ibus: bus_dbus_impl_name_owner_changed(): ibus-daemon killed by SIGABRT: TAINTED Product: Fedora Version: rawhide Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: hhan(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com, smaitra(a)redhat.com, tfujiwar(a)redhat.com Description of problem: Version-Release number of selected component: ibus-1.5.14-3.fc26 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/ibus-daemon -r --xim crash_function: bus_dbus_impl_name_owner_changed executable: /usr/bin/ibus-daemon global_pid: 3509 kernel: 4.8.0-0.rc6.git0.1.fc26.x86_64+debug pkg_fingerprint: 812A 6B4B 64DA B85D pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #4 bus_dbus_impl_name_owner_changed at dbusimpl.c:1242 #9 bus_name_service_set_primary_owner at dbusimpl.c:368 #10 bus_dbus_impl_request_name at dbusimpl.c:1076 #11 call_in_idle_cb at gdbusconnection.c:4836 #17 bus_server_run at server.c:143 Potential duplicate: bug 1374611 -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Fedora-i18n-bugs] [Bug 825115] New: [kn_IN] Lohit Kannada glyphs of consonants with vowel signs -II, -EE, -OO and -AI should be optimized
by Red Hat Bugzilla 23 Jul '18

23 Jul '18

https://bugzilla.redhat.com/show_bug.cgi?id=825115 Bug ID: 825115 QA Contact: extras-qa(a)fedoraproject.org Severity: unspecified Version: 16 Priority: unspecified CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, psatpute(a)redhat.com Assignee: psatpute(a)redhat.com Summary: [kn_IN] Lohit Kannada glyphs of consonants with vowel signs -II, -EE, -OO and -AI should be optimized Regression: --- Story Points: --- Classification: Fedora OS: Unspecified Reporter: samjnaa(a)gmail.com Type: Bug Documentation: --- Hardware: Unspecified Mount Type: --- Status: NEW Component: lohit-kannada-fonts Product: Fedora Description of problem: Currently the Lohit Kannada fonts unnecessarily contain separate glyphs for consonants with vowel signs -II, -EE, -OO and -AI. These are merely sequences of other glyphs. In the case of -II, -EE, -OO the glyphs are the same as those of the corresponding short vowels plus a separate glyph 0CD5 Kannada Length Mark ೕ (unlike in Telugu where the length mark ligates with the syllable). Therefore instead of doing substitutions of: CONSONANT + VOWEL_SIGN_II/EE/OO --> CONSONANT_VOWELSIGN_II/EE/OO the optimized way would be to do: CONSONANT + VOWEL_SIGN_II/EE/OO --> CONSONANT_VOWELSIGN_I/E/O LENGTH_MARK If this is done, any changes that are reflected on the CONSONANT_VOWELSIGN_I/E/O glyphs would automatically reflect for the long vowels as well without additional work being needed. For instance, see my recent report of bug 825104. If that bug is fixed for short vowels I, E and O, automatically it would reflect for II, EE and OO also. As for -AI, it is merely sequence of glyph for -E plus 0CD6 Kannada AI Length Mark ೖ. So instead of doing substitutions of: CONSONANT + VOWEL_SIGN_AI --> CONSONANT_VOWELSIGN_AI the optimized way would be to do: CONSONANT + VOWEL_SIGN_AI --> CONSONANT_VOWELSIGN_E AI_LENGTH_MARK with same benefits as above. Further, when handling combinations of: CONSONANT1 + VIRAMA + CONSONANT2 + VOWEL_SIGN_II/EE/OO/AU by separating the length mark as recommended here, the sub-base form of CONSONANT2 can be placed closer to the base CONSONANT1 which is also typographically a desirable factor in a good font. The rules would be: CONSONANT1 + VIRAMA + CONSONANT2 + VOWEL_SIGN_II/EE/OO/AU --> CONSONANT1_VOWEL_SIGN_I/E/O + SUB_BASE_CONSONANT_2 + (AI_)LENGTH_MARK Version-Release number of selected component (if applicable): 2.5.1 How reproducible: Examine the internals of Lohit Kannada font. Actual results: Currently there are separate glyphs for consonants with vowel signs -II, -EE, -OO and -AI unnecessarily. These are merely sequences of other glyphs. Therefore any change effected on the component glyphs has to be re-done here. Expected results: The superfluous glyphs should be removed and the appropriate effect should be achieved by appropriate smartfont rules as indicated above. Additional info: This would also reduce the size of the font. Not an issue on laptops/desktops but nowadays Lohit fonts are finding their way into smaller screens such as smartphones, and it would be good to have a trim font with small footprint. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Fedora-i18n-bugs] [Bug 1382982] New: Fedora iBus typing language detector breaks events call stack of web pages
by Red Hat Bugzilla 19 Jul '18

19 Jul '18

https://bugzilla.redhat.com/show_bug.cgi?id=1382982 Bug ID: 1382982 Summary: Fedora iBus typing language detector breaks events call stack of web pages Product: Fedora Version: 24 Component: ibus Severity: urgent Assignee: tfujiwar(a)redhat.com Reporter: danielemi(a)hotmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com, smaitra(a)redhat.com, tfujiwar(a)redhat.com Created attachment 1208438 --> https://bugzilla.redhat.com/attachment.cgi?id=1208438&action=edit html page for test purpose Description of problem: My Fedora box is configured with two typing language between which I can switch, English and Chinese. I'm using Firefox v49 as browser. I'm developing a webpage, a registration form using jQuery on the validation part. The registration form contain 4 input controls with 2 password controls, all validated on the blur event. The form script is kind of complex one using blur, and focus events and a list of functions. The form script completely mess up on the live validation of the fields due to the presence of the two password controls on which only latin alphabet is allowed. The ibus language detector change on the fly when the two password fields received focus causing blur and focus events of different contols to happen in unexpected order. It is like ibus is taking the focus and releasing. I tested both jQuery (all the available methods) and pure javascript with the same result. I had the chance to try other websites using blur and focus events on password fields and are completely mess up too. To finish my job I will unset the Chinese IME. I can't guess what is about application development in the same context. Version-Release number of selected component (if applicable): Fedora 24 4.7.5-200.fc24.x86_64 ibus-1.5.13-3.fc24.x86_64 How reproducible: https://jsfiddle.net/8tqwL7y5 Steps to Reproduce: 1. Settings, Region and Lanaguges, input sources: set English (US) and Chinese (intelligent Pinyin) 2. try the link 3. try the webpage attached Actual results: Blur event doesn't happen or happen just mixed up with other events like other control's Focus events. Expected results: Blur and Focus events get fired in common order on the events call stack -- You are receiving this mail because: You are on the CC list for the bug.

2 18

[Fedora-i18n-bugs] [Bug 1296121] New: XIM: When commiting with a space, it is inserted before a hangul character rather than after it
by Red Hat Bugzilla 11 Jul '18

11 Jul '18

https://bugzilla.redhat.com/show_bug.cgi?id=1296121 Bug ID: 1296121 Summary: XIM: When commiting with a space, it is inserted before a hangul character rather than after it Product: Fedora Version: 23 Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: psabata(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: This appears to be a recurring issue; I recall this was fixed a few times already :) The behavior is similar to #675503. However, only XIM appears to be affected this time; the input works fine in a GTK+v2 application. Version-Release number of selected component (if applicable): ibus-1.5.11-1.fc23.x86_64 ibus-libs-1.5.11-1.fc23.x86_64 ibus-hangul-1.5.0-5.fc23.x86_64 ibus-gtk2-1.5.11-1.fc23.x86_64 How reproducible: Always with XIM. Never with GTK+v2. Steps to Reproduce: 1. Run ibus with XIM ibus-daemon -x 2. Set your environment and run something that uses it, e.g. xterm -- export XMODIFIERS='@im=ibus' xterm 3. Type some hangul and commit with a space, e.g. "하나 둘 셋" (input being "gksk enf tpt ") Actual results: "하 나 둘 셋" Expected results: "하나 둘 셋 " Additional info: -- 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=cxyVQxcKBJ&a=cc_unsubscribe

2 17

[Fedora-i18n-bugs] [Bug 1398181] New: Start at hangul does not work
by Red Hat Bugzilla 03 Jul '18

03 Jul '18

https://bugzilla.redhat.com/show_bug.cgi?id=1398181 Bug ID: 1398181 Summary: Start at hangul does not work Product: Fedora Version: 25 Component: ibus Severity: medium Assignee: tfujiwar(a)redhat.com Reporter: hwhwang7(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com, smaitra(a)redhat.com, tfujiwar(a)redhat.com Description of problem: After the input source 'hangul', I can enable the option 'start at hangul mode'. Even after I enabled it, whenever I switch to hangul, it does not start at hangul mode. Version-Release number of selected component (if applicable): IBus 1.5.14 How reproducible: Always Steps to Reproduce: 1. Add the input source 'hangul' 2. Enable the option 'start at hangul mode'. 3. Switch input mode Actual results: Hangul mode does not start as enabled Expected results: Hangul mode starts as enabled -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Fedora-i18n-bugs] [Bug 1040336] New: [or_IN][libuninum] - Change language name from "Oriya" to "Odia"
by Red Hat Bugzilla 29 Jun '18

29 Jun '18

https://bugzilla.redhat.com/show_bug.cgi?id=1040336 Bug ID: 1040336 Summary: [or_IN][libuninum] - Change language name from "Oriya" to "Odia" Product: Fedora Version: rawhide Component: libuninum Keywords: i18n Severity: low Priority: medium Assignee: terjeros(a)phys.ntnu.no Reporter: smaitra(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, smaitra(a)redhat.com, terjeros(a)phys.ntnu.no Description of problem: Upstream bug reference : https://sourceware.org/bugzilla/show_bug.cgi?id=15601 Preface : As per the Govt of India record, the State name of Orissa has been replaced with Odisha (hopefully I am correct with its spelling) and the language of Odisha State which was Oriya earlier, has been replaced with Odia. Please change the word "Oriya" occurrences to "Odia" in SPEC file. Version-Release number of selected component (if applicable): libuninum-2.7-13.fc20.1 libuninum-2.7-13.fc20.1 How reproducible: N/A Steps to Reproduce:N/A 1. 2. 3. Actual results: Presently the word "Oriya" is mentioned in the SPEC file. Expected results: Please replace the word "Oriya" with the word "Odia" in the SPEC File for all the occurrences. Additional info: References: http://orissamatters.com/2011/11/07/orissa-became-odisha/ http://www.ndtv.com/article/india/parliament-passes-bill-to-change-orissa-s… http://orissa.gov.in/e-magazine/Orissareview/2011/Nov/engpdf/9-17.pdf -- 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=YHitKy2naE&a=cc_unsubscribe

2 13

[Fedora-i18n-bugs] [Bug 1133127] New: The hotkey for switching to direct input mode should be configurable
by Red Hat Bugzilla 12 Jun '18

12 Jun '18

https://bugzilla.redhat.com/show_bug.cgi?id=1133127 Bug ID: 1133127 Summary: The hotkey for switching to direct input mode should be configurable Product: Fedora Version: 19 Component: ibus-table Assignee: mfabian(a)redhat.com Reporter: stsp(a)list.ru QA Contact: extras-qa(a)fedoraproject.org CC: dchen(a)redhat.com, extras-qa(a)fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, kent.neo(a)gmail.com, me(a)kaio.net, mfabian(a)redhat.com, pwu(a)redhat.com, shawn.p.huang(a)gmail.com, stsp(a)list.ru +++ This bug was initially created as a clone of Bug #1128912 +++ (In reply to Stas Sergeev from comment #23) > I noticed another problem. > When I type, the layout ocasionally changes back > to EN, even though I do not press the modifier combo. > The switcher applet still shows RU, but the typing > becomes latinic. > Presumably this happens after Shift-Space, but again, > not always... So we have another puzzle. I wonder if > you can make a sharp guess or reproduce that... You are switching between table mode ("rusle") and direct input mode (using the underlying keyboard layout directly). The hotkey for this is the left shift key (Without space, just left shift and release it). You can see which mode you are in if you open the input method menu in the gnome panel while rusle is active. Look at the 4 menu entries near the bottom: Direct input (Left Shift) Phrase mode (Ctrl-;) <- quite useless for rusle Direct commit mode (Ctrl-/) <- quite useless for rusle Setup If you hit the left shift key and look again, you see that the topmost of these "property" menus toggles between Direct input (Left Shift) <-> Р (Left Shift) I am not sure what I can do about this now. For Chinese, this is used often as a quick way to toggle between Chinese and English mode (faster than switching between two input sources). That might be the reason why the original developer of ibus-table did choose the left shift key as the hot key for that. The disadvantage is of course that the left shift key can be hit far too easily. In the long run, I want to make the keybindings configurable, then you could set that keybinding to empty. But I have no time for that soon, that is a bit more work. Choosing a different shortcut is not nice to existing users. Disabling that shortcut for non-CJK input methods might also be not so nice. Maybe one wants to quickly toggle between direct input and a non-CJK input method as well. So I am a bit puzzled what to do about this now. Maybe wait until I have time to make the keybindings configurable? --- Additional comment from Stas Sergeev on 2014-08-22 15:32:52 EDT --- > Maybe wait until I have time to make the keybindings configurable? Maybe I have no other option than to agree with this? :) Anyway, another sharp guess, you are right, left shift is the culprit. Thank you. So, should I open a separate report for this or what? --- Additional comment from Stas Sergeev on 2014-08-22 15:34:22 EDT --- (In reply to Mike FABIAN from comment #24) > Created attachment 929759 [details] > 0001-Ignore-Shift-Space-hotkey-to-switch-fullwidth-halfwi.patch > > To fix the problem in comment#21 Patch tested and works. --- Additional comment from Mike FABIAN on 2014-08-22 15:55:18 EDT --- (In reply to Stas Sergeev from comment #26) > > Maybe wait until I have time to make the keybindings configurable? > Maybe I have no other option than to agree with this? :) > Anyway, another sharp guess, you are right, left shift > is the culprit. Thank you. > > So, should I open a separate report for this or what? Yes, I think a separate bug report is helpful so I do not forget this. Maybe, as a temporary workaround, I disable that hotkey for non-CJK and enable it again as soon as the hotkeys are configurable. I really should make the hotkeys configurable ... -- 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=DFaAYcdVbL&a=cc_unsubscribe

2 111

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs November 2016