[Bug 843331] New: [ta_IN] Please add glyphs for minority orthographies in Tamil
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=843331
Bug ID: 843331
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, psatpute(a)redhat.com
Assignee: psatpute(a)redhat.com
Summary: [ta_IN] Please add glyphs for minority orthographies
in Tamil
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: samjnaa(a)gmail.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: lohit-tamil-fonts
Product: Fedora
Created attachment 600434
--> https://bugzilla.redhat.com/attachment.cgi?id=600434&action=edit
Glyphs required for minority orthographies in Tamil
While the Tamil script is mainly used for writing Tamil language text, it is
also attested to be used for other language text such as Sanskrit, Saurashtra,
Hindi, Marathi, Telugu and Kannada in the form of transliteration.
For these minority orthography usecases, some characters from script-neutral
blocks are required:
1) The superscript digits ¹²³⁴ would be used for representing the varga
consonants (actually ¹ is only used very rarely). The Unicode chapter on Tamil
script documents this and recommends the characters (0xb9) 0xb2 0xb3 0x2074.
2) Not only the superscript digits but their corresponding subscript digits
₁₂₃₄ (0x2081-0x2084) are also attested as a stylistic variant choice.
3) The modifier letter apostrophe 02BC ʼ is also seen.
4) Further, sometimes the candrabindu is also seen for nasality. Since there is
no Tamil candrabindu character, the generic candrabindu ◌̐ at 0310 can be
used.
5) The visarga is commonly seen but the Tamil visarga code point 0B83 is mapped
to the Tamil special letter aytam ஃ (which has three dots against the visarga's
two dots), so we will have to place the two-dot visarga in the PUA. (Not ideal
I know, but it is unlikely to encode a Tamil-specific two-dot visarga. It is
not possible to use the Devanagari visarga codepoint 0903 since rendering
engines will produce dotted circles as it is not correct to combine Devanagari
codepoints with Tamil codepoints.)
Attestations for these usages and required glyphs are attached. Please add them
with the appropriate script-neutral codepoints shown in the patch TTF so Lohit
Tamil (and Lohit Tamil Classical) is also useful for these minority
orthographies. BTW it would be good font design policy to make the modifier
apostrophe a composite glyph of the regular apostrophe and subscript digits as
composites of superscript digits.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 6 months
[Bug 499790] New: [te_IN][pango]GSUB delete key can't delete the whole char in f10,but works well in rhel5.3
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: [te_IN][pango]GSUB delete key can't delete the whole char in f10,but works well in rhel5.3
https://bugzilla.redhat.com/show_bug.cgi?id=499790
Summary: [te_IN][pango]GSUB delete key can't delete the whole
char in f10,but works well in rhel5.3
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:
GSUB press Delete key to delete the whole char,it can't delete the whole char
in f10,but works well in rhel5.3.
I think it is a regression bug.
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 U+0C15 U+0C4D U+0C15
2.Press Delete key to delete the char
3.
Actual results:
It can't delete the whole char,it will delete part of the char
Expected results:
It will delete the whole char.
Additional info:
All of chars in [te_IN][GSUB] has the same problem.
But in rhel 5.3 they work well.
So I think it is a regression 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.
9 years, 7 months
[Bug 22621] New: RFE: Add font autoinstallation support
by bugzilla-daemon@webkit.org
https://bugs.webkit.org/show_bug.cgi?id=22621
Summary: RFE: Add font autoinstallation support
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: Enhancement
Priority: P2
Component: Text
AssignedTo: webkit-unassigned(a)lists.webkit.org
ReportedBy: nicolas.mailhot(a)laposte.net
CC: fedora-fonts-bugs-list(a)redhat.com
The Linux platform is gaining an on-demand font autoinstallation framework (BSD
and Solaris will probably follow eventually).
http://fedoraproject.org/wiki/Features/AutomaticFontInstallation
Webkit browsers should be plugged into it and use it to request the fonts the
pages they render need. This would have a huge user impact, especially for
pages that have strong i18n constrains.
Unlike proposals such as @font-face and EOT the fonts are sourced from trusted
user-controlled sources, are properly vetted legal-side, use the latest font
versions not old obsolete ones (with bug fixes), and are installed system-wide
where other apps can take advantage of them.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
9 years, 10 months
[Bug 1023977] New: Use fc-cache /usr/share/fonts/<your font directory> instead of /usr/share/fonts
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1023977
Bug ID: 1023977
Summary: Use fc-cache /usr/share/fonts/<your font directory>
instead of /usr/share/fonts
Product: Red Hat Enterprise Linux 7
Version: 7.0
Component: ghostscript-fonts
Assignee: twaugh(a)redhat.com
Reporter: twaugh(a)redhat.com
QA Contact: qe-i18n-bugs(a)redhat.com
CC: fonts-bugs(a)lists.fedoraproject.org,
patrick.noffke(a)gmail.com, tagoh(a)redhat.com,
twaugh(a)redhat.com
Depends On: 1021757
Group: redhat
+++ This bug was initially created as a clone of Bug #1021757 +++
Description of problem:
Running fc-cache with /usr/share/fonts takes too much time and may breaks the
cache for parents when installing multiple font packages or upgrading
fontconfig, especially sometimes happens on the installation say.
As the macro in fontpackages does, please follow it up and use fc-cache
/usr/share/fonts/<your font directory> instead of /usr/share/fonts.
Version-Release number of selected component (if applicable):
ghostscript-fonts-5.50-30.fc19.noarch
How reproducible:
always
Steps to Reproduce:
1.rpm -q --scripts ghostscript-fonts-5.50-30.fc19.noarch
2.
3.
Actual results:
postinstall scriptlet (using /bin/sh):
{
mkfontscale /usr/share/fonts/default/ghostscript
mkfontdir /usr/share/fonts/default/ghostscript
fc-cache /usr/share/fonts
} &> /dev/null || :
postuninstall scriptlet (using /bin/sh):
{
if [ "$1" = "0" ]; then
fc-cache /usr/share/fonts
fi
} &> /dev/null || :
Expected results:
the directory should be /usr/share/fonts/<your font directory> instead
Additional info:
--- Additional comment from Tim Waugh on 2013-10-22 04:51:41 EDT ---
For the postuninstall scriptlet too?
Is there anything planned for the Fedora Project packaging guidelines to make
sure there are no regressions with this?
Does this change look correct?:
diff --git a/ghostscript-fonts.spec b/ghostscript-fonts.spec
index d66fbaa..c2cbc3f 100644
--- a/ghostscript-fonts.spec
+++ b/ghostscript-fonts.spec
@@ -1,7 +1,7 @@
Summary: Fonts for the Ghostscript PostScript interpreter
Name: ghostscript-fonts
Version: 5.50
-Release: 30%{?dist}
+Release: 31%{?dist}
# Contacted Kevin Hartig, who agreed to relicense his fonts under the SIL Open
Font
# License. Hershey fonts are under the "Hershey Font License", which is not
what Fontmap
# says (Fontmap is wrong).
@@ -58,13 +58,13 @@ ln -sf %{fontdir}
$RPM_BUILD_ROOT%{catalogue}/default-ghostscript
{
mkfontscale %{fontdir}
mkfontdir %{fontdir}
- fc-cache %{_datadir}/fonts
+ fc-cache %{fontdir}
} &> /dev/null || :
%postun
{
if [ "$1" = "0" ]; then
- fc-cache %{_datadir}/fonts
+ fc-cache %{fontdir}
fi
} &> /dev/null || :
@@ -80,6 +80,10 @@ rm -rf $RPM_BUILD_ROOT
%ghost %verify(not md5 size mtime) %{fontdir}/fonts.scale
%changelog
+* Tue Oct 22 2013 Tim Waugh <twaugh(a)redhat.com> - 5.50-31
+- Run fc-cache on our font directory, not the entire font collection
+ (bug #1021757).
+
* Wed Feb 13 2013 Fedora Release Engineering <rel-eng(a)lists.fedoraproject.org>
- 5.50-30
- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
--- Additional comment from Nicolas Mailhot on 2013-10-22 05:23:13 EDT ---
(In reply to Tim Waugh from comment #1)
> For the postuninstall scriptlet too?
>
> Is there anything planned for the Fedora Project packaging guidelines to
> make sure there are no regressions with this?
Well, what the packaging guidelines actually say is that you shouldn't install
any font without using fontpackages-devel templates and macros or splitting
fonts per family, which means all font packages have the same implementation
and there is no risk of single-package regression.
I appreciate that ghostscript antedates the consolidation work that went into
current font packaging guidelines, but maybe it's time to align it with them?
Also TEX people have spent many years cleaning up and modernizing gs fonts. It
would be worthwhile to package the tex gyre family and use them as replacement,
dropping all legacy font formats and core font calls. I *think* tex gyre
licensing is finally clean and safe (but you'd need to check with spot)
--- Additional comment from Tim Waugh on 2013-10-22 06:15:13 EDT ---
That's a fair point. :-)
That work might have to be done in step with urw-fonts.
--- Additional comment from Fedora Update System on 2013-10-22 06:27:51 EDT ---
ghostscript-fonts-5.50-32.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/ghostscript-fonts-5.50-32.fc19
--- Additional comment from Fedora Update System on 2013-10-22 06:28:34 EDT ---
ghostscript-fonts-5.50-32.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/ghostscript-fonts-5.50-32.fc20
--- Additional comment from Fedora Update System on 2013-10-22 14:51:18 EDT ---
Package ghostscript-fonts-5.50-32.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing
ghostscript-fonts-5.50-32.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-19682/ghostscript-fon...
then log in and leave karma (feedback).
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1021757
[Bug 1021757] Use fc-cache /usr/share/fonts/<your font directory> instead
of /usr/share/fonts
--
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=IVu6jiD8ho&a=cc_unsubscribe
9 years, 11 months