i18n-bugs July 2013

i18n-bugs@lists.fedoraproject.org

1 participants
290 discussions

[Fedora-i18n-bugs] [Bug 923346] New: Symbols incorrectly displayed
by Red Hat Bugzilla 31 Jan '15

31 Jan '15

Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=923346 Bug ID: 923346 Summary: Symbols incorrectly displayed Product: Fedora Version: 18 Component: google-croscore-fonts Severity: high Priority: unspecified Assignee: pnemade(a)redhat.com Reporter: jv+fedora(a)fcelda.cz QA Contact: extras-qa(a)fedoraproject.org CC: andreas.bierfert(a)lowlatency.de, fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, jreznik(a)redhat.com, kevin(a)tigcc.ticalc.org, ltinkl(a)redhat.com, mike(a)cchtml.com, mkasik(a)redhat.com, pnemade(a)redhat.com, rdieter(a)math.unl.edu, richard(a)rsk.demon.co.uk, rnovacek(a)redhat.com, stefan(a)lsd.co.za, than(a)redhat.com, tibbs(a)math.uh.edu Depends On: 901858 I'm seeing the same problem as described in bug #901858 with google-croscore-symbolneu-fonts-1.21.0-4.fc18.noarch package. Removing the package solves the problem and math symbols are displayed correctly. google-croscore-symbolneu-fonts-1.21.0-4.fc18.noarch okular-4.10.1-1.fc18.x86_64 +++ This bug was initially created as a clone of Bug #901858 +++ Created attachment 683157 microchip pdf showing the fault Description of problem: When reading technical pdfs, the wrong symbols are displayed for some math characters. e.g. pi is displayed as not equal, ohms as a vertical bar, and micro (mu) is displayed as infinity. Version-Release number of selected component (if applicable): okular-4.9.5.-1.fc18 How reproducible: Displaying a technical pdf such as http://ww1.microchip.com/downloads/en/AppNotes/00954A.pdf shows the wrong symbols. E.G. In figure 1 - the value for C2 is displayed as 470 (inf) F instead of 470 (mu) F Steps to Reproduce: 1. Display technical pdf 2. 3. Actual results: pi is displayed as not equals ohms as a vertical bar micro(mu) as infinity Expected results: The correct symbols should be displayed Additional info: Evince also has this problem, but emacs displays everything correctly. This happens across a range of pdfs and I think is a serious bug than needs fixing as soon as possible,. It reflects badly on fedora if we cannot display technical specifications properly. --- Additional comment from Kevin Kofler on 2013-01-19 12:47:09 EST --- > Evince also has this problem Reassigning to poppler, which is the common library used by both. What I see is that this PDF does not embed its fonts, which means you get whatever fonts are installed on the system. In this case, Symbol is mapped to wine-symbol-fonts. So I'm not sure whether poppler or the font is doing the wrong thing there. And by the way, the PDF is bad because it uses a font outside of the PostScript standard (Symbol) and doesn't embed it. A portable PDF MUST embed all the non-PostScript fonts it uses. --- Additional comment from Richard Kennedy on 2013-02-28 07:57:45 EST --- Just a quick update. The new embedded pdf reader in Firefox 19 displays these files correctly too. Well, the pdf may not be correct but it was created by adobe software & there are lots of them out in the wild, so we should do something to fix it. Can I change the default font mapping for popper to something else ? If so how do I go about that? --- Additional comment from Kevin Kofler on 2013-02-28 19:00:01 EST --- As I said, it's a bug in either poppler or wine-symbol-fonts (or both). Unfortunately, the poppler maintainer hasn't answered so far. --- Additional comment from Marek Kašík on 2013-03-01 07:05:38 EST --- Hi, this is a bug in wine-symbol-fonts package. The symbol.ttf font has wrong mapping. For additional info see upstream bug http://bugs.winehq.org/show_bug.cgi?id=24099. I'm reassigning this to wine. Regards Marek --- Additional comment from Jason Tibbitts on 2013-03-01 14:45:34 EST --- Wow, it's great news that this the cause is known, because I've been struggling with this for some time. Unfortunately upstream bug report has been there for quite some time with no progress, so I'm not sure what chance we have of getting this fixed. What would break by removing this font? Can it be removed from the dependency list of the wine-fonts metapackage? --- Additional comment from Kevin Kofler on 2013-03-01 17:53:16 EST --- Would that really fix the issue? I don't think the symbols can be properly displayed if the font is entirely missing. I suspect there's no way around fixing the font. --- Additional comment from Richard Kennedy on 2013-03-02 11:50:34 EST --- I've just fixed the font following the steps in the wine bug 24099 and it works. I only run one wine app, ltspice, and it still works after the fix, so it's all looking good. Both firefox & emacs can display these characters properly so they must be using some other font, but I don't know how to find out which one. But if we could find out can we swap the mapping to that? --- Additional comment from Richard Kennedy on 2013-03-02 13:29:50 EST --- Having thought about this some more, I think that is more likely that the bug really is that poppler isn't handling unicode characters properly. I cut & pasted the failing mu character from evince into emacs, and it says it's unicode 0x3BC. So it seems that poppler tries to use the symbol font and 0x3BC is something different in there because it's broken too. emacs and firefox somehow resolve the unicode character correctly and don't end up in the symbol font, but I haven't found out which font they do use. I didn't realise all of this stuff was so involved and complex. At least fixing up the font is a temporary fix. --- Additional comment from Kevin Kofler on 2013-03-02 17:58:39 EST --- Maybe poppler shouldn't be looking up "Symbol" in fontconfig at all, but handle the Symbol font specially? The Window$ Symbol TTF font which WINE's font tries to emulate is a hack which predates Unicode and maps Greek letters and other symbol characters to plain 8-bit characters (0-255). Somebody should probably test what happens when you use the original M$ Symbol.ttf. If it has the same issue, it's not WINE's fault. --- Additional comment from Richard Kennedy on 2013-03-04 12:44:39 EST --- Just a couple of notes :- * The poppler version here is 0.20.2 which was released on Tue July 10, 2012, and the latest is 0.22.1 which contains quite a number of bug fixes. * I've reset my machine to the default state and if I run pdftohtml on this file the correct characters are generated in the html. (pdftohtml is a poppler tool). * Libre Office also can display these files correctly. Is there any way to get poppler to use the opensymobol font to resolve these symbols? AFAICT opensymbol contains all of the correct unicode so might make a good replacement and it's already installed. --- Additional comment from Marek Kašík on 2013-03-05 07:26:52 EST --- Created attachment 705385 blacklist wine font Symbol (In reply to comment #10) > Just a couple of notes :- > > * The poppler version here is 0.20.2 which was released on Tue July 10, > 2012, and > the latest is 0.22.1 which contains quite a number of bug fixes. The poppler-0.22.1 doesn't fix this. > * I've reset my machine to the default state and if I run pdftohtml on this > file > the correct characters are generated in the html. (pdftohtml is a poppler > tool). It generates correct html because the codes for those characters are correct in the pdf. > * Libre Office also can display these files correctly. Do you mean the html or the pdf? Libre Office displays me the same characters as poppler when importing the pdf. > Is there any way to get poppler to use the opensymobol font to resolve these > symbols? AFAICT opensymbol contains all of the correct unicode so might make > a good replacement and it's already installed. Place the attached file to ~/.config/fontconfig/fonts.conf. This will blacklist the font for all applications which use fontconfig (useful when the wine-symbol-fonts is a dependency of a package which you don't want to remove). I've tried to view a file with the character for the micro sign (UTF-8 code 0xC2B5) in notepad which is part of wine-common. After switching the font to "Symbol", it showed me the incorrect symbol. I guess that there is really something wrong with the font. Regards Marek --- Additional comment from Kevin Kofler on 2013-03-05 10:00:50 EST --- The problem is that the Symbol font was designed in a way that the 'm' character is displayed as 'µ', and 'µ' is not mapped to anything. In fact, Symbol was the way to get those special characters in old software which didn't support Unicode. I don't know whether it's possible to fix this issue without breaking that old software when people try to run it under WINE. I hope it's possible, but I'm not sure. The WINE upstream bug report has a proposed fix, but I don't know whether that fix doesn't break the non-Unicode apps. --- Additional comment from Andreas Bierfert on 2013-03-05 14:55:02 EST --- Well as a workaround we could confine wine symbol to wine for now (like with tahoma). This would reduce the problem to wine applications. Before resorting to this I will investigate a bit... -- 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=mExkG0NduF&a=cc_unsubscribe

1 17

[Fedora-i18n-bugs] [Bug 734751] New: RFE: improve UI
by Red Hat Bugzilla 31 Jan '15

31 Jan '15

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: RFE: improve UI https://bugzilla.redhat.com/show_bug.cgi?id=734751 Summary: RFE: improve UI Product: Fedora Version: rawhide Platform: Unspecified OS/Version: Unspecified Status: NEW Keywords: FutureFeature Severity: unspecified Priority: unspecified Component: iok AssignedTo: pnemade(a)redhat.com ReportedBy: tagoh(a)redhat.com QAContact: extras-qa(a)fedoraproject.org CC: pnemade(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Classification: Fedora Story Points: --- Type: --- Description of problem: I have some thoughts on improving UI for iok, particularly for the use case on non-Indic language. 1) Get rid of "English" entry from the language list. That is meaningless to keep it there since "to English" button is available. 2) should keep the same state to the initial state after clicking "to English" button. I think the initial state would be natural. I mean selecting the language from ASCII layout (English mode) since the neutral position is ASCII layout on other IM. however once selecting the language from the list and switch back to English mode with "to English" button, iok masks the language list. one needs to switch with "To <language" button to choose other language from the list. this behavior isn't consistent to the initial state and other IM. there are IM that supports to switch multiple IME regardless of current state though, if you want to provide such features, you should simply stop masking the language list. 3) maybe "to ASCII" is better than "to English"? I like to see the icon to indicate the state of "on" and "off" with the icon though, if you want to keep the string, guess that would be better using "ASCII" instead of "English". 4) selected the language from the list should keeps it default in next time 5) entries in the language list should be translatable Since it's hidden when running iok on any Indic locale, that should appears in the native language on current desktop. that would be helpful for those who wants to learn Indic but running iok on their locale. 6) simplify the language list like the IME list on ibus there are too many entries on the language list. that would be nice to simplify like ibus does. -- 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.

1 4

[Fedora-i18n-bugs] [Bug 926729] New: WritRecogn: Does not support aarch64 in f19 and rawhide
by Red Hat Bugzilla 29 Jan '15

29 Jan '15

Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=926729 Bug ID: 926729 Summary: WritRecogn: Does not support aarch64 in f19 and rawhide Product: Fedora Version: rawhide Component: WritRecogn Severity: unspecified Priority: unspecified Assignee: dchen(a)redhat.com Reporter: dennis(a)ausil.us QA Contact: extras-qa(a)fedoraproject.org CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com Blocks: 922257 (ARM64) Support for the ARM 64 bit CPU architecture (aarch64) was introduced in autoconf 2.69. WritRecogn appears to use an earlier version of autoconf, preventing its being built. This can be fixed in of three ways (In order of preference): 1. Work with upstream to migrate the package to autoconf 2.69. 2. Rerun autoconf or autoreconf in %prep or %build prior to running configure. 3. Apply the patch at http://ausil.fedorapeople.org/aarch64/WritRecogn/WritRecogn-aarch64.patch which updates config.guess and config.sub to recognize aarch64. -- 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=1CXdpd4cMH&a=cc_unsubscribe

1 1

[Fedora-i18n-bugs] [Bug 801374] New: autopoint fails if GREP_OPTIONS contains -n
by Red Hat Bugzilla 18 Jan '15

18 Jan '15

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: autopoint fails if GREP_OPTIONS contains -n https://bugzilla.redhat.com/show_bug.cgi?id=801374 Summary: autopoint fails if GREP_OPTIONS contains -n Product: Fedora Version: 16 Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: unspecified Priority: unspecified Component: gettext AssignedTo: petersen(a)redhat.com ReportedBy: jcholast(a)redhat.com QAContact: extras-qa(a)fedoraproject.org CC: petersen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Classification: Fedora Story Points: --- Type: --- Regression: --- Mount Type: --- Documentation: --- Description of problem: autopoint fails if the GREP_OPTIONS environment variable contains the -n (prefix each line of output with line number) option. This happens because autopoint assumes that grep outputs lines of the source file in an unmodified form, which is not always true. Version-Release number of selected component (if applicable): How reproducible: Always. Steps to Reproduce: 1. cd to a directory with a configure.ac file which contains the AM_GNU_GETTEXT_VERSION macro 2. run "GREP_OPTIONS=-n autopoint --force" Actual results: autopoint: *** Missing version: please specify in configure.ac through a line 'AM_GNU_GETTEXT_VERSION(x.yy.zz)' the gettext version the package is using autopoint: *** Stop. autoreconf: autopoint failed with exit status: 1 Expected results: autopoint succeeds as if the -n grep option was not set. 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.

1 18

[Fedora-i18n-bugs] [Bug 981479] New: [abrt] imsettings-1.6.3-1.fc19: g_variant_iter_next_value: Process /usr/libexec/imsettings-check was killed by signal 11 (SIGSEGV)
by Red Hat Bugzilla 16 Jan '15

16 Jan '15

https://bugzilla.redhat.com/show_bug.cgi?id=981479 Bug ID: 981479 Summary: [abrt] imsettings-1.6.3-1.fc19: g_variant_iter_next_value: Process /usr/libexec/imsettings-check was killed by signal 11 (SIGSEGV) Product: Fedora Version: 19 Component: imsettings Severity: unspecified Priority: unspecified Assignee: tagoh(a)redhat.com Reporter: j.mark.brooks(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Version-Release number of selected component: imsettings-1.6.3-1.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/imsettings-check --check-modulesettings -d crash_function: g_variant_iter_next_value executable: /usr/libexec/imsettings-check kernel: 3.9.8-300.fc19.x86_64 runlevel: N 5 uid: 1000 var_log_messages: Jul 4 17:39:37 localhost abrt[27341]: Saved core dump of pid 27334 (/usr/libexec/imsettings-check) to /var/tmp/abrt/ccpp-2013-07-04-17:39:37-27334 (9330688 bytes) xsession_errors: Truncated backtrace: Thread no. 1 (3 frames) #0 g_variant_iter_next_value at gvariant.c:3032 #1 g_variant_iter_next at gvariant.c:4961 #2 _check_modules at imsettings-check.c:240 -- 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=KUjcTmzYGi&a=cc_unsubscribe

1 3

[Fedora-i18n-bugs] [Bug 586214] New: knm-new-fixed-fonts isn't usable
by Red Hat Bugzilla 15 Jan '15

15 Jan '15

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: knm-new-fixed-fonts isn't usable https://bugzilla.redhat.com/show_bug.cgi?id=586214 Summary: knm-new-fixed-fonts isn't usable Product: Fedora Version: rawhide Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: knm-new-fixed-fonts AssignedTo: tagoh(a)redhat.com ReportedBy: tagoh(a)redhat.com QAContact: extras-qa(a)fedoraproject.org CC: tagoh(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org Classification: Fedora Target Release: --- Description of problem: knm-new-fixed-fonts is capable for Japanese font though, it doesn't have enough glyph coverage for Japanese. Version-Release number of selected component (if applicable): knm-new-fixed-fonts-1.1-11.fc13 How reproducible: always Steps to Reproduce: 1.fc-match -v Fixed|grep -E " lang"|grep ja 2. 3. Actual results: No output Expected results: the lang spec should contains ja. 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.

1 4

[Fedora-i18n-bugs] [Bug 802524] New: [abrt] ibus-chewing-1.3.10-1.fc16: __memmove_ssse3_back: Process /usr/libexec/ibus-engine-chewing was killed by signal 11 (SIGSEGV)
by Red Hat Bugzilla 15 Jan '15

15 Jan '15

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: [abrt] ibus-chewing-1.3.10-1.fc16: __memmove_ssse3_back: Process /usr/libexec/ibus-engine-chewing was killed by signal 11 (SIGSEGV) https://bugzilla.redhat.com/show_bug.cgi?id=802524 Summary: [abrt] ibus-chewing-1.3.10-1.fc16: __memmove_ssse3_back: Process /usr/libexec/ibus-engine-chewing was killed by signal 11 (SIGSEGV) Product: Fedora Version: 16 Platform: x86_64 OS/Version: Unspecified Status: NEW Status Whiteboard: abrt_hash:161b83f9183e7a85517ec5cb9aedaa2e2d97e0a4 Severity: unspecified Priority: unspecified Component: ibus-chewing AssignedTo: dchen(a)redhat.com ReportedBy: scottt.tw(a)gmail.com QAContact: extras-qa(a)fedoraproject.org CC: tfujiwar(a)redhat.com, dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com Classification: Fedora Story Points: --- Type: --- Regression: --- Mount Type: --- Documentation: --- libreport version: 2.0.8 abrt_version: 2.0.7 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-chewing --ibus crash_function: __memmove_ssse3_back executable: /usr/libexec/ibus-engine-chewing kernel: 3.2.6-3.fc16.x86_64 pid: 2050 pwd: /tmp reason: Process /usr/libexec/ibus-engine-chewing was killed by signal 11 (SIGSEGV) time: Tue 13 Mar 2012 02:08:44 AM CST uid: 1000 username: scottt var_log_messages: Mar 13 02:08:45 5220m abrt[18013]: Saved core dump of pid 2050 (/usr/libexec/ibus-engine-chewing) to /var/spool/abrt/ccpp-2012-03-13-02:08:44-2050 (23797760 bytes) xsession_errors: backtrace: Text file, 138913 bytes dso_list: Text file, 7646 bytes maps: Text file, 45737 bytes build_ids: :4d5437cf71ea3e4bac1c445da58ca7897d509d15 :1c6a95451ee19617be5abea3d121f0226d21ddda :dc998e8c1e1dc44c684b9b86e753945a868e134a :aaf7ed41612348bd1141db06cadd428244aa6ea5 :fd8a00c88eb1fd6872e45001f9ed4e5c6172995e :ec72f897bbac2f33aadee57e01b7e01bbed4c534 :07470201df55a5254027d05fa4dc509b10f2986a :aa733447f84020c94a66814e501a36e248cbb43d :78c1ade3665ad67db02654e2e74152270c5852b3 :e3c88cb9ea428bd61f4064dbd53acae2d396a1ec :c11071801b4acea1cb1d7783c72d5f09ccf39764 :5e8c36ca13a4af14fa6b1b45a0dbfb43ed6aed6e :de272a66db7a1b50e62eaf658976bce648412179 :719a85c49c612de86619fed98146f316432aee92 :ab59942678bcdecb23756804dcd0aac63ccc1669 :aaf62304b0fc10611d35b4f56005479d4c58868d :c124e79ca47fee27b34b962e8144fd5ae98f1dae :f0d50e3af2dfee021a327fb85a993a2312a98145 :8b0f0f32d4400b2bf7632c55f013226297f44d17 :e5429e0905bedecc534b057783916ba43e06a66e :49a34982a874d88cf1d02c0da70918e7d10fd222 :36a149d1e2c29890b616402f6bc5e3f69ca2738e :a594ab36356a9b6dc6ecf25a6124463ccbfd0a29 :12ebe599358398f2c1a5294bb2dd387545474b65 :124bfd663f5587288e6e0da8497fb4153469e657 :c8a4e40c84c2f52e78c64d31efc0191c565a9049 :0f0c9eed63ed279ceb0aef109eff8bcbb351e4bb :4953d1f613914126bccceb3cb96386647ffba9df :e2e67b3ae2579e1667b73ad385f61552931024e9 :0911ea7c180d733724f89037b8e8a34e64024aec :ccadad4ec7dab3bb6abc23f9d4cdf53ff01cb235 :58f626f3815dd6adeb4a543bca2472ab98f2953b :56cd5a4b8ecf7f375c95a4fd575895efbe294071 :48aea888319e1848137073c9cbde54a4c2a731c9 :4b4285058f7f6b39b7e7c45df83fd36c6833bfe4 :3ed9e61c2b7e707ce244816335776afa2ad0307d :4a7e68edf2778a9fbd3d4a8fbd3f9d1e7b785fc6 :2639b5594fe4d7897db63ecd1ebb9681438317a8 :4c842320387ff7f6f91b7842b223c16518be909f :6ecc3efaedf849a17c30a67fe15b4dacca1bd981 :1e0de72c7f10f33e0ee489a9a32c4e4f01902580 :9d1209fc79304f03cc839de1c0036c61b48dfff8 :ee2f04900ae1f07517d91eba300ef385fccab1b8 :700c536566e06857d8abfeea98d617c72a122d4a :374add1ead31ccb449779bc7ee7877de3377e5ad :39294193f046cf15442542705526228c60d70a6e :2976a5f82b01d5dedaaefdd41fa7a78b090c75a1 :638db099ff5fb986d1a092629d1bb1dca5be4904 :0fe03f2aa418c7dbfdc2d0d1802a8e86b27d3120 :400444fb368f79b54959b083f449a1497bf71c13 :661bf8d51a632f74853e2c4e005ef1b527c4b74a :8acc43df965b3c0a70dcfad11c0ade056bdb055b :3269336f76283d9cebaa8222e0017c80fd14bdf6 :44ece411beb2ef1acdb5eb2161666de41cc2f31d :e982a67c98e50c7c68039aec0859bc4dfc896270 :7994f114cf7189e482f2665fae8e351ed8bc05e3 :3b50812827b755646178db9447ced77425add5d8 :41785923286ebc820c23b630f1ab810fb24061fc :82cca0d5b06a649072a966dc4f05aded63d736bc :23b6792e3218744316fd495002f40a037c2e0095 :c2d49d72ec1a1e68b39c3724693f83f44d80a259 :2670385f49fb9f120f7cf843f211e3c620da8632 :163b323da65b708418226eb5fa8b057c731d1475 :5cb5f8da286abd58aeab3bd6676e661d52ec2b5d :b0a2d0b4c09d819887ec7d711c8cf3977a074c4f :a518a8b1b5c3e80dee813df05e951d205d6ac48c :be507c791e34415e8f42f0e6030c889b2895cf9a environ: :SHELL=/bin/bash :DBUS_STARTER_ADDRESS=unix:abstract=/tmp/dbus-ocjwUDzuo9,guid=349e930559b6c336193035df0000001a :XDG_SESSION_COOKIE=24990a7dcebf36938cb84a9900000005-1331545525.828385-220611063 :XDG_RUNTIME_DIR=/run/user/scottt :DISPLAY=:0 :DESKTOP_SESSION=gnome :WINDOWPATH=1 :PATH=/usr/local/bin:/usr/bin:/bin :GDMSESSION=gnome :XDG_VTNR=1 :USERNAME=scottt :XDG_SESSION_ID=2 :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-ocjwUDzuo9,guid=349e930559b6c336193035df0000001a :XDG_SEAT=seat0 :XAUTHORITY=/var/run/gdm/auth-for-scottt-yJhxtA/database :USER=scottt :DBUS_STARTER_BUS_TYPE=session :GNOME_KEYRING_PID=1438 :SHLVL=1 :PWD=/home/scottt :GNOME_KEYRING_CONTROL=/tmp/keyring-z4oR01 :LANG=en_US.UTF-8 :_=/usr/bin/dbus-launch :LOGNAME=scottt :HOME=/home/scottt :LC_CTYPE=en_US.UTF-8 :GTK_IM_MODULE=ibus :QT_IM_MODULE=xim :XMODIFIERS=@im=ibus smolt_data: : : :General :================================= :UUID: 7ba1c065-054d-43b7-9546-c5d6405b8e86 :OS: Fedora release 16 (Verne) :Default run level: Unknown :Language: en_US.UTF-8 :Platform: x86_64 :BogoMIPS: 5332.78 :CPU Vendor: GenuineIntel :CPU Model: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz :CPU Stepping: 5 :CPU Family: 6 :CPU Model Num: 37 :Number of CPUs: 4 :CPU Speed: 2667 :System Memory: 7779 :System Swap: 8191 :Vendor: Hewlett-Packard :System: HP ProBook 5220m :Form factor: Notebook :Kernel: 3.2.6-3.fc16.x86_64 :SELinux Enabled: 1 :SELinux Policy: targeted :SELinux Enforce: Enforcing :MythTV Remote: Unknown :MythTV Role: Unknown :MythTV Theme: Unknown :MythTV Plugin: :MythTV Tuner: -1 : : :Devices :================================= :(32902:11539:32902:32902) pci, None, HOST/PCI, Core Processor Reserved :(4332:33128:4156:5181) pci, r8169, ETHERNET, RTL8111/8168B PCI Express Gigabit Ethernet controller :(32902:11521:32902:32902) pci, None, HOST/PCI, Core Processor QuickPath Architecture System Address Decoder :(32902:11537:32902:32902) pci, None, HOST/PCI, Core Processor QPI Physical 0 :(32902:11538:32902:32902) pci, None, HOST/PCI, Core Processor Reserved :(5348:18215:4156:5212) pci, bcma-pci-bridge, NETWORK, BCM4313 802.11b/g/n Wireless LAN Controller :(32902:70:4156:5181) pci, i915, VIDEO, Core Processor Integrated Graphics Controller :(32902:15176:4156:5181) pci, pcieport, PCI/PCI, 5 Series/3400 Series Chipset PCI Express Root Port 4 :(32902:15170:4156:5181) pci, pcieport, PCI/PCI, 5 Series/3400 Series Chipset PCI Express Root Port 1 :(32902:15115:4156:5181) pci, None, PCI/ISA, Mobile 5 Series Chipset LPC Interface Controller :(32902:15154:4156:5181) pci, intel ips, NONE, 5 Series/3400 Series Chipset Thermal Subsystem :(32902:15190:4156:5181) pci, snd_hda_intel, MULTIMEDIA, 5 Series/3400 Series Chipset High Definition Audio :(32902:11536:32902:32902) pci, None, HOST/PCI, Core Processor QPI Link 0 :(32902:9288:4156:5181) pci, None, PCI/PCI, 82801 Mobile PCI Bridge :(32902:11362:32902:32902) pci, None, HOST/PCI, Core Processor QuickPath Architecture Generic Non-core Registers :(32902:15151:4156:5181) pci, ahci, STORAGE, 5 Series/3400 Series Chipset 6 port SATA AHCI Controller :(32902:15164:4156:5181) pci, ehci_hcd, USB, 5 Series/3400 Series Chipset USB2 Enhanced Host Controller :(32902:15156:4156:5181) pci, ehci_hcd, USB, 5 Series/3400 Series Chipset USB2 Enhanced Host Controller :(32902:68:4156:5181) pci, agpgart-intel, HOST/PCI, Core Processor DRAM Controller :(32902:15204:4156:5181) pci, None, SIMPLE, 5 Series/3400 Series Chipset HECI Controller :(32902:15180:4156:5181) pci, pcieport, PCI/PCI, 5 Series/3400 Series Chipset PCI Express Root Port 6 : : :Filesystem Information :================================= :device mtpt type bsize frsize blocks bfree bavail file ffree favail :------------------------------------------------------------------- :/dev/sda4 / ext4 4096 4096 70044651 36313005 35612114 17530880 16227334 16227334 :/dev/sda2 /boot ext4 4096 4096 1045750 935142 882714 262144 261899 261899 : -- 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.

1 11

[Fedora-i18n-bugs] [Bug 487061] New: Japanese fonts changed to less readable after update
by Red Hat Bugzilla 15 Jan '15

15 Jan '15

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Japanese fonts changed to less readable after update https://bugzilla.redhat.com/show_bug.cgi?id=487061 Summary: Japanese fonts changed to less readable after update Product: Fedora Version: 10 Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: vlgothic-fonts AssignedTo: ryo-dairiki(a)users.sourceforge.net ReportedBy: mcmonster(a)o2.pl QAContact: extras-qa(a)fedoraproject.org CC: tagoh(a)redhat.com, ryo-dairiki(a)users.sourceforge.net, fedora-fonts-bugs-list(a)redhat.com, fedora-i18n-bugs(a)redhat.com Estimated Hours: 0.0 Classification: Fedora User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; pl-PL; rv:1.9.0.6) Gecko/2009020410 Fedora/3.0.6-1.fc10 Firefox/3.0.6 I'm using irssi on gnome-terminal (Monospace font), after update Japanese fonts changed, they're now much smaller (compared to latin), harder to read (some ideograms are completely unreadable). It is very annoying, because I use Japanese and sit on Japanese channel a lot. The change occured only in terminal, in gEdit and other applications old fonts are still used for typing (SCIM + Anthy) and displaying. The change didn't affect everyone, some Fedora 10 still got old, simple and readable fonts. Reproducible: Always Steps to Reproduce: Just try displaying any Japanese text. This is the update, that probably changed fonts: Feb 14 02:31:53 Installed: vlgothic-fonts-common-20090204-2.fc10.noarch Feb 14 02:32:39 Installed: vlgothic-fonts-20090204-2.fc10.noarch Feb 14 02:32:42 Installed: vlgothic-p-fonts-20090204-2.fc10.noarch Feb 14 02:33:28 Erased: VLGothic-fonts Feb 14 02:33:30 Erased: VLGothic-fonts-proportional ]# LANG=C yum list vlgothic\* Loaded plugins: refresh-packagekit Installed Packages vlgothic-fonts.noarch 20090204-2.fc10 installed vlgothic-fonts-common.noarch 20090204-2.fc10 installed Available Packages VLGothic-fonts.noarch 20081029-1.fc10 updates VLGothic-fonts-proportional.noarch 20081029-1.fc10 updates vlgothic-p-fonts.noarch 20090204-2.fc10 updates -- 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.

1 15

[Fedora-i18n-bugs] [Bug 875429] New: Lohit Punjabi overlaps when used as WebFonts on Windows
by Red Hat Bugzilla 14 Jan '15

14 Jan '15

https://bugzilla.redhat.com/show_bug.cgi?id=875429 Bug ID: 875429 QA Contact: extras-qa(a)fedoraproject.org Severity: high External Bug URL: https://bugzilla.wikimedia.org/ Version: rawhide 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: Lohit Punjabi overlaps when used as WebFonts on Windows Regression: --- Story Points: --- Classification: Fedora OS: Unspecified Reporter: srik.lak+public(a)gmail.com Type: Bug Documentation: --- Hardware: Unspecified Mount Type: --- Status: NEW Component: lohit-punjabi-fonts Product: Fedora External Bug ID: Wikimedia 40473 Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Open http://srik.me/jquery.webfonts/examples/ on windows machine. 2. Change between Lohit-Punjabi, Saab, Sakal Bharathi to notice the difference in 1999 3. 9 overlaps with existing text causing rendering bug on windows. Actual results: 19 comes for 1999 (in Punjabi). Same goes with digit 8 overlapping with digit 9. Expected results: 1999 should come for 1999 Additional info: Pravin Satpute knows about the issue and this was debugged at Pune Language Summit -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 963648] New: upper bar (shirorekha) rendering is broken for marathi installation
by Red Hat Bugzilla 14 Jan '15

14 Jan '15

Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=963648 Bug ID: 963648 Summary: upper bar (shirorekha) rendering is broken for marathi installation Product: Fedora Version: 19 Component: lohit-devanagari-fonts Severity: unspecified Priority: unspecified Assignee: psatpute(a)redhat.com Reporter: apatil(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, psatpute(a)redhat.com Category: --- Created attachment 748720 --> https://bugzilla.redhat.com/attachment.cgi?id=748720&action=edit screenshot of the problem Description of problem: upper bar (shirorekha rendering) is broken for Marathi installation i have attached screenshot for the issue. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Install F19 with Marathi language 2. Installation screen shows Marathi language Actual results: word "मराठी" is broken Expected results: word "मराठी" should render correctly 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=9bi7MjId7N&a=cc_unsubscribe

1 3

← Newer
1
...
6
7
8
9
10
11
12
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs July 2013