[Bug 18725] New: RFE: allow merging of legacy font family names
by bugzilla-daemon@freedesktop.org
http://bugs.freedesktop.org/show_bug.cgi?id=18725
Summary: RFE: allow merging of legacy font family names
Product: fontconfig
Version: 2.6
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: library
AssignedTo: keithp(a)keithp.com
ReportedBy: nicolas.mailhot(a)laposte.net
CC: fedora-fonts-bugs-list(a)redhat.com
Historically font formats only allowed four faces regular, bold, italic, bold
italic. You had to use a separate font family to distribute condensed, heavy
etc variants
This has changed (cf http://blogs.msdn.com/text/attachment/2249036.ashx ) and
modern fonts such as DejaVu include all faces under a single family name.
Applications such as OO.o are being fixed to handle multifaced fonts
Unfortunately there are still many historic fonts in the wild distributed in
several sets of four faces (gs fonts, arial narrow, arial bold, etc). Those
fonts currently appear under different family names in fontconfig-using apps.
This is perturbing to users, since the same faces of historic and modern fonts
are not handled the same way. Microsoft did some sort of magic in uniscribe to
hide this distinction (irrelevant to users).
Please provide a documented config pattern for font distributors that enables
them to declare to fontconfig "font family A and font family B are the same,
please expose all the associated faces under A name to users".
(of course an application asking explicitely for B should still get it, but
users would only see A in font lists)
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
5 years, 8 months
[Bug 18723] New: RFE: fontconfig-level locl patching
by bugzilla-daemon@freedesktop.org
http://bugs.freedesktop.org/show_bug.cgi?id=18723
Summary: RFE: fontconfig-level locl patching
Product: fontconfig
Version: 2.6
Platform: Other
OS/Version: All
Status: NEW
Severity: enhancement
Priority: medium
Component: library
AssignedTo: keithp(a)keithp.com
ReportedBy: nicolas.mailhot(a)laposte.net
CC: fedora-fonts-bugs-list(a)redhat.com
Due to Han unification and other similar stuff parts of some fonts may not be
suitable for all locales.
This is handled by the locl flag in modern opentype fonts.
However there are still many non-opentype fonts in the wild, and it is not
possible to convert them all at once (when the license permits it).
There should be a way in fontconfig for font distributors to patch in via a
config file the locl characteristics of a font.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
5 years, 8 months
[Bug 22338] New: Make fc-query warn about non-WWS compliant fonts
by bugzilla-daemon@freedesktop.org
http://bugs.freedesktop.org/show_bug.cgi?id=22338
Summary: Make fc-query warn about non-WWS compliant fonts
Product: fontconfig
Version: 2.6
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: library
AssignedTo: freedesktop(a)behdad.org
ReportedBy: nicolas.mailhot(a)laposte.net
QAContact: keithp(a)keithp.com
CC: fedora-fonts-bugs-list(a)redhat.com
(it would be nice if there was a fc-query component in fontconfig BTW)
Since MS' WWS naming model makes stuff simpler for application authors, and
will be required in new window code, it would be mighty nice if fc-query warned
in its general report if a font file didn't respect this model.
Respecting the WWS model is declaring fields 21 and 22 or 16 in 17 in ways that
respect WWS (only weight, width and slant in sytles)
This way we can point FLOSS authors to fc-query as linting tools and promote
font naming our apps can handle easily
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
5 years, 8 months
[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 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 733106] New: fonts.alias refer to encodings not listed in fonts.dir
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: fonts.alias refer to encodings not listed in fonts.dir
https://bugzilla.redhat.com/show_bug.cgi?id=733106
Summary: fonts.alias refer to encodings not listed in fonts.dir
Product: Fedora
Version: rawhide
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: sazanami-fonts
AssignedTo: tagoh(a)redhat.com
ReportedBy: viy(a)altlinux.org
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
Story Points: ---
Type: ---
fonts.alias files refer to jisx020*.19??-0 font encodings while fonts.dir does
not list them.
looks like a fonts.scale/fonts.dir generation bug.
/usr/share/X11/fonts/encodings/large/*
encodings should be present during fonts.scale/fonts.dir generation.
sazanami-fonts-0.20040629-15.fc15.src.rpm
--
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.
6 years, 4 months
[Bug 825081] New: Lohit Kannada font does not properly handle vowel signs in consonant clusters
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=825081
Bug ID: 825081
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: Lohit Kannada font does not properly handle vowel
signs in consonant clusters
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
Created attachment 586752
--> https://bugzilla.redhat.com/attachment.cgi?id=586752&action=edit
ODT and PDF for test-case
Description of problem:
This seems to be a resurfacing of bug #223971 but since I saw no way to reopen
that bug (sorry if I'm wrong) I'm reporting this again.
Version-Release number of selected component (if applicable):
2.5.1
How reproducible:
In a word processor, select Lohit Kannada font and input Kannada Unicode
sequences having consonant clusters of the format CCV. I have attached a sample
ODT.
Actual results:
Except in a few cases of "popular" consonant clusters like K.SSA ಕ್ಷ and J.NYA
ಜ್ಞ, the vowel signs are not attached properly.
When the same text is rendered with other fonts (like Tunga of Microsoft even
loaded into Linux's LibreOffice) the sequences are shown properly without
overlaps or malformed glyphs.
Expected results:
The Kannada language uses lots of Sanskrit-based words and hence has many
consonant clusters with two and even three consonants. Also, when English words
are transliterated in Kannada script like ಎಕ್ಸ್ಪ್ಲೋರ್ (explore) etc for
sign-boards etc, even more consonant clusters will occur. In all these cases
Lohit Kannada should be able to gracefully handle such consonant clusters and
not output overlapping or malformed glyphs.
Additional info:
I have attached an ODT and PDF file demonstrating the problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 4 months