[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
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.
5 years, 9 months
[Bug 1580458] New: [ta_IN] Error in latest Tamil ttf
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1580458
Bug ID: 1580458
Summary: [ta_IN] Error in latest Tamil ttf
Product: Fedora
Version: rawhide
Component: lohit-tamil-fonts
Severity: high
Assignee: psatpute(a)redhat.com
Reporter: nsesha92(a)yahoo.co.in
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, psatpute(a)redhat.com
Created attachment 1439625
--> https://bugzilla.redhat.com/attachment.cgi?id=1439625&action=edit
Error screen shot jpeg
Description of problem:
Hi,
1. Latest ttf-tar says version 2.91.3, but when installed it shows as 2.91.1
2. Glyph issue with 'ra', 'na' and its i, ii, u, uu .. series.
3. shrii is missing, should be next to kshii per 2.5.3
Screen shot attached.
Wram regards
Seshadri
Version-Release number of selected component (if applicable):
2.91.3 & 2.91.1
How reproducible:
Screen shot attached.
Steps to Reproduce:
1. See in Windows Character Map
2.
3.
Actual results:
Expected results:
Additional info: I am trying my luck with FontForge to correct these errors.
Will try to get back in few days.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 9 months
[Bug 500110] New: [hi_IN][Dependent Vowels]Press backspace key it delete the whole char and letter before it
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: [hi_IN][Dependent Vowels]Press backspace key it delete the whole char and letter before it
https://bugzilla.redhat.com/show_bug.cgi?id=500110
Summary: [hi_IN][Dependent Vowels]Press backspace key it delete
the whole char and letter before it
Product: Fedora
Version: 10
Platform: i386
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: pango
AssignedTo: besfahbo(a)redhat.com
ReportedBy: kxiong(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: besfahbo(a)redhat.com, fedora-fonts-bugs-list(a)redhat.com
Classification: Fedora
Target Release: ---
Description of problem:
In gedit press Backspace key to delete the whole char,it delete both the whole
char and the letter before it
Version-Release number of selected component (if applicable):
pango-devel-1.22.1-1.fc10.i386
pango-1.22.1-1.fc10.i386
pangomm-2.14.0-2.fc10.i386
How reproducible:
always
Steps to Reproduce:
1.In gedit input dabenा
2.Press Backspace key to delete the whole char ा
Actual results:
It delete the whole char and the letter n when pressing the Backspace key.
Expected results:
It should only delete the whole char.
Additional info:
1. U+093E ा
2. U+093F ि
3. U+0940 ी
4. U+0941 ु
5. U+0942 ू
6. U+0943 ृ
7. U+0944 ॄ
8. U+0945 ॅ
9. U+0946 ॆ
10. U+0947 े
11. U+0948 ै
12. U+0949 ॉ
13. U+094B ो
14. U+094C ौ
in Dependent Vowels all have the same problem
--
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.
5 years, 9 months
[Bug 1569943] New:
upgrading from Liberation 1 to 2 in a desktop session can affect rendering
of text
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1569943
Bug ID: 1569943
Summary: upgrading from Liberation 1 to 2 in a desktop session
can affect rendering of text
Product: Fedora
Version: rawhide
Component: liberation-fonts
Assignee: psatpute(a)redhat.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: alexl(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, mbarnes(a)fastmail.com,
mclasen(a)redhat.com, petersen(a)redhat.com,
psatpute(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com
Description of problem:
The Liberation 1 and 2 fonts may be binary incompatible
in the sense that upgrading a live desktop from Liberation 1 to 2
seemed to corrupt some characters for me in Firefox (with Ariel text in
Google Docs for the default unordered list mark symbols).
Version-Release number of selected component (if applicable):
liberation-fonts-2.00.1
Actual results:
'·' -> '>'
'⃝' -> '<'
for example
Expected results:
Not change of glyphs.
Additional info:
I suspect this might be due to caching of the old font's tables in memory.
It would be better if the tables were more compatible I suppose.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 9 months
[Bug 1569848] New: Fontlint gives error with korean font.
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1569848
Bug ID: 1569848
Summary: Fontlint gives error with korean font.
Product: Fedora
Version: 28
Component: fonts-korean
Assignee: extras-orphan(a)fedoraproject.org
Reporter: poyadav(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: extras-orphan(a)fedoraproject.org,
fonts-bugs(a)lists.fedoraproject.org
Description of problem:
When testing for technical/common isssues for Korean font, getting error.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Install Fedora in korean locale
2. Run the command fontlint /usr/share/fonts/naver-nanum/NanumGothic.ttf
Actual results:
Getting below error:
[test@localhost ~]$ fontlint /usr/share/fonts/naver-nanum/NanumGothic.ttf
Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE.
Based on sources from 21:59 UTC 11-Feb-2018-ML-D.
Based on source from git with hash:
Attempt to unget two characters
CHECKING /usr/share/fonts/naver-nanum/NanumGothic.ttf
ERROR 2 Self-intersecting glyph
ERROR 3 Wrong direction
ERROR 5 Missing points at extrema
WARNING 99 Flags in the OS/2 table say the font is non-free
FAIL /usr/share/fonts/naver-nanum/NanumGothic.ttf
Expected results:
There should be no error.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 10 months
[Bug 1332250] New: Incorrect font configuration
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1332250
Bug ID: 1332250
Summary: Incorrect font configuration
Product: Fedora
Version: rawhide
Component: open-sans-fonts
Assignee: pvoborni(a)redhat.com
Reporter: dag.odenhall(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
pvoborni(a)redhat.com
When a website requests Open Sans, Firefox uses Comfortaa. I have both fonts
installed. I don't know if the following is the cause, because the matching
works correctly with fc-match, but I discovered this and it's still wrong, I
think.
The open-sans-fonts package includes this fontconfig rule:
<alias>
<family>Open Sans</family>
<prefer>
<family>sans-serif</family>
</prefer>
</alias>
In my understanding of fontconfig, this is saying "Edit the font family list
for Open Sans and prepend the sans-serif font family" i.e. Open Sans itself is
given *less* priority than all other sans-serif fonts. The
aajohan-comfortaa-fonts package includes this (correct) rule:
<alias>
<family>sans-serif</family>
<prefer>
<family>Comfortaa</family>
</prefer>
</alias>
And so perhaps C being early in the alphabet or perhaps because being the next
fontconfig file in my conf.d (I don't fully understand fontconfig) the combined
effect ends up being "When looking for Open Sans, the first match is sans-serif
which in turn is Comfortaa".
I think the Open Sans rule above should be edited to something closer to the
Comfortaa rule above, like:
<alias>
<family>sans-serif</family>
<prefer>
<family>Open Sans</family>
</prefer>
</alias>
The second rule it contains is also wrong, I think, and not like how any other
fonts are configured:
<alias>
<family>sans-serif</family>
<default>
<family>Open Sans</family>
</default>
</alias>
Should probably also swap the families like so:
<alias>
<family>Open Sans</family>
<default>
<family>sans-serif</family>
</default>
</alias>
This Firefox bug seems relevant but I think this is a bug in the packaged font
configuration and really unrelated to Firefox (I didn't read the whole bug):
https://bugzilla.mozilla.org/show_bug.cgi?id=1245811
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 10 months