[Bug 812207] New: La (=?UTF-8?Q?=E0=A4=B2?=) and Sha (=?UTF-8?Q?=E0=A4=B6?=) half shape required modifications
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: La (ल) and Sha (श) half shape required modifications
https://bugzilla.redhat.com/show_bug.cgi?id=812207
Summary: La (ल) and Sha (श) half shape required modifications
Product: Fedora
Version: 17
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: lohit-marathi-fonts
AssignedTo: psatpute(a)redhat.com
ReportedBy: psatpute(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
psatpute(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Story Points: ---
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Created attachment 577228
--> https://bugzilla.redhat.com/attachment.cgi?id=577228
pdf explaining problem
Description of problem:
Mail from Sushant Devlekar, Half La (ल) and Sha (श) shape required
modifications as done by Base shape of La (ल) and Sha (श)
Version-Release number of selected component (if applicable):
lohit-marathi-fonts-2.5.1-1
How reproducible:
everytime
Steps to Reproduce:
1. Type ल्ल and श्क
2.
3.
Actual results:
half shape of sha and la not matching with full shape of la and sha
Expected results:
both full and half shape should match.
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.
8 years, 11 months
[Bug 981475] New: Improper glyph names in Lohit fonts
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=981475
Bug ID: 981475
Summary: Improper glyph names in Lohit fonts
Product: Fedora
Version: rawhide
Component: lohit-fonts
Severity: unspecified
Priority: unspecified
Assignee: extras-orphan(a)fedoraproject.org
Reporter: khaledhosny(a)eglug.org
QA Contact: extras-qa(a)fedoraproject.org
CC: extras-orphan(a)fedoraproject.org,
fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pnemade(a)redhat.com,
psatpute(a)redhat.com
For purposes of text extraction from PDF files, glyphs should be named in
accordance with Adobe Glyph Naming convention
(http://www.adobe.com/devnet/opentype/archives/glyph.html). Most glyphs in
Lohit fonts follow this convention properly, but some do not. I did not do an
extensive review, but I noticed several occurances of glyph names like:
u0919_u094D.half_u0915_u094D.half.half
Which is wrong, since step 1 of the mapping algorithm in the above link will
drop the part of glyph name after the first occurence of a peroid, so only
u0919_u094D will remain which is assume is not what is wanted here. A proper
name would then be:
u0919_u094D_u0915_u094D.half.half.half
or something like that (the part after the peroid is completely ignored, so it
can be anything).
--
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=5cwcY7yhhr&a=cc_unsubscribe
9 years, 1 month
[Bug 882267] New: Warning about /etc/fonts/conf.d/50-user.conf
by Red Hat Bugzilla
Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=882267
Bug ID: 882267
Summary: Warning about /etc/fonts/conf.d/50-user.conf
Product: Fedora
Version: 18
Component: fontconfig
Severity: unspecified
Priority: unspecified
Reporter: mefoster(a)gmail.com
Description of problem:
Running appes such as gvim under KDE results in a warning to STDERR like this:
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading
configurations from ~/.fonts.conf is deprecated.
Version-Release number of selected component (if applicable):
fontconfig-2.10.2-1.fc18.x86_64
How reproducible:
Every time
Steps to Reproduce:
1. Run "gvim"
Actual results:
Warning
Expected results:
No warning
Additional info:
I don't know if it's relevant that I use KDE as a desktop environment and that
this error comes up with gvim, but that's where I specifically noticed it.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 2 months
[Bug 842568] New: Bad spacing in Liberation Mono with BCI-hinting
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=842568
Bug ID: 842568
QA Contact: extras-qa(a)fedoraproject.org
Severity: unspecified
Version: rawhide
Priority: unspecified
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, psatpute(a)redhat.com
Assignee: psatpute(a)redhat.com
Summary: Bad spacing in Liberation Mono with BCI-hinting
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: xously(a)gmail.com
Type: Bug
Documentation: ---
Hardware: x86_64
Mount Type: ---
Status: NEW
Component: liberation-fonts
Product: Fedora
Created attachment 599962
--> https://bugzilla.redhat.com/attachment.cgi?id=599962&action=edit
Spacing of "s"
Description of problem:
Applies to Liberation Mono with BCI-hinting.
"s" is too far to the right or left, depending on the font size. E.g. "users"
looks like "user s" at size 11. (See first attachment for font sizes 8-16.)
"ow" is merging in bold font, at least at size 11. E.g. in "downloads". (See
second attachment.)
Version-Release number of selected component:
2.00.0
How reproducible:
Always with this ".fonts.conf":
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<match target="font">
<edit name="antialias" mode="assign">
<bool>true</bool>
</edit>
</match>
<match target="font">
<edit name="hinting" mode="assign">
<bool>true</bool>
</edit>
</match>
<match target="font">
<edit name="hintstyle" mode="assign">
<const>hintfull</const>
</edit>
</match>
<match target="font">
<edit name="rgba" mode="assign">
<const>rgb</const>
</edit>
</match>
<match target="font">
<edit mode="assign" name="lcdfilter">
<const>lcddefault</const>
</edit>
</match>
</fontconfig>
With auto-hinting enabled instead, these problems do not occur:
<match target="pattern" name="family">
<test name="family" qual="any">
<string>Liberation Mono</string>
</test>
<edit name="autohint" mode="assign">
<bool>true</bool>
</edit>
</match>
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 2 months
[Bug 522648] New: glyphs cut-off below "baseline" in firefox
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: glyphs cut-off below "baseline" in firefox
https://bugzilla.redhat.com/show_bug.cgi?id=522648
Summary: glyphs cut-off below "baseline" in firefox
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Keywords: Regression
Severity: medium
Priority: low
Component: ipa-gothic-fonts
AssignedTo: tagoh(a)redhat.com
ReportedBy: petersen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fedora-fonts-bugs-list(a)redhat.com
Classification: Fedora
Target Release: ---
Description of problem:
With ipa fonts being used for Japanese desktop,
it seems the bottom of letters with parts under
the Latin "baseline" tend to get cut-off in
textboxes in Firefox.
How reproducible:
every time
Steps to Reproduce:
1. Login to rawhide Japanese gnome desktop
2. Run firefox and type "abcdefghijklmnopqrstuvwxyz" into awesome bar.
3. sudo yum install vlgothic-fonts
4. repeat (2)
Actual results:
2. Bottom of letters 'g', 'j', 'p', 'q', 'y' are clipped
4. Displays fine.
Expected results:
2. All the glyphs to be visible.
--
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.
9 years, 2 months
[Bug 863817] New: Liberation Sans Hebrew needs Redesign (Willing to contribute)
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=863817
Bug ID: 863817
QA Contact: extras-qa(a)fedoraproject.org
Severity: medium
Version: rawhide
Priority: unspecified
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, psatpute(a)redhat.com
Assignee: psatpute(a)redhat.com
Summary: Liberation Sans Hebrew needs Redesign (Willing to
contribute)
Regression: ---
Story Points: ---
Classification: Fedora
OS: All
Reporter: LIJI32(a)gmail.com
Type: Bug
Documentation: ---
Hardware: All
Mount Type: ---
Status: NEW
Component: liberation-fonts
Product: Fedora
Created attachment 623019
--> https://bugzilla.redhat.com/attachment.cgi?id=623019&action=edit
New Hebrew glyphs I designed
The Hebrew version of Liberation Sans currently uses glyphs from Droid Sans
Hebrew. These glyphs have incorrect proportions, weird letter forms and it's
generally unreadable. In addition, it go along with the Latin glyphs nicely.
I've previously solved the same problem with DejaVu Sans Hebrew by redesigning
it and I'd be more than happy to contribute an entirely new Hebrew glyphset for
Liberation Sans.
I included a Work-in-Progess of new Hebrew glyphs designed to match the design
of the Latin Liberation Sans in style, weight and proportions.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 2 months
[Bug 677448] New: incompatibility/inefficiency with bitmap-fangsongti-fonts
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: incompatibility/inefficiency with bitmap-fangsongti-fonts
https://bugzilla.redhat.com/show_bug.cgi?id=677448
Summary: incompatibility/inefficiency with
bitmap-fangsongti-fonts
Product: Fedora
Version: rawhide
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: fontconfig
AssignedTo: behdad(a)fedoraproject.org
ReportedBy: notting(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: behdad(a)fedoraproject.org, pnemade(a)redhat.com,
fonts-bugs(a)lists.fedoraproject.org
Classification: Fedora
Description of problem:
bitmap-fangsongti-fonts causes fontconfig to exercise some very bad codepaths
on upgrades.
Version-Release number of selected component (if applicable):
fontconfig-2.8.0
How reproducible:
100%
Steps to Reproduce:
1. Have bitmap-fangsongti-fonts installed
2. Be running a desktop
3. Do some upgrade that causes '/usr/bin/fc-cache /usr/share/fonts/bitmap' to
run
Actual results:
Most every fontconfig app on the system (kde4d, notification area applets,
gnome-settings-daemon, and others) suddenly start using 100% cpu. The fc-cache
call takes a *very* long time to complete.
Expected results:
Not that.
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.
9 years, 2 months
[Bug 635961] New: [Pango][Cursoring][mr_IN] - Composed Character Deletion is wrong with DELETE Button
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: [Pango][Cursoring][mr_IN] - Composed Character Deletion is wrong with DELETE Button
https://bugzilla.redhat.com/show_bug.cgi?id=635961
Summary: [Pango][Cursoring][mr_IN] - Composed Character
Deletion is wrong with DELETE Button
Product: Fedora
Version: 13
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: pango
AssignedTo: behdad(a)fedoraproject.org
ReportedBy: smaitra(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: behdad(a)fedoraproject.org, aalam(a)redhat.com,
smaitra(a)redhat.com,
fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org
Blocks: 631761,635957
Classification: Fedora
Target Release: ---
Description of problem:
In pango (tested it in gedit and firefox), the deletion with DELETE key, is not
following the rule of deleting entire composed character with a single key
press. It is deleting each of the character in a composed character, one by
one.
Version-Release number of selected component (if applicable):
pango-1.28.0-1.fc13.i686
How reproducible:
Always
Steps to Reproduce:
1. Open gedit or firefox in mr_IN locale
2. Activate ibus with CTRL+SPACE. Select marathi - Inscript
3. Type : kdk (which means consonant KA + Halant + Consonant KA)
4. Position the cursor at the beginning point of the composed character.
5. Now, press DELETE key. (It needs 3 key strokes to delete the whole
character, but it should be done with a single key stroke in fact)
Actual results:
Delete composed character is happening in wrong manner. Actually it is now
following the convention (Rule) of BACKSPACE, when deleting a composed
character comes into picture.
Expected results:
It should delete the whole composed character in one DELETE key stroke when
cursor positions at the start of the composed character.
Additional info:
OS : Fedora 13
Arch : i386
--
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.
9 years, 2 months
[Bug 923346] New: Symbols incorrectly displayed
by Red Hat Bugzilla
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=ILFMitOgOk&a=cc_unsubscribe
9 years, 3 months