[Bug 503430] New: Incorrect Kerning in some applications
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: Incorrect Kerning in some applications
https://bugzilla.redhat.com/show_bug.cgi?id=503430
Summary: Incorrect Kerning in some applications
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: liberation-fonts
AssignedTo: cchance(a)redhat.com
ReportedBy: grom358_spamkill(a)yahoo.com.au
QAContact: extras-qa(a)fedoraproject.org
CC: cchance(a)redhat.com, fedora-fonts-bugs-list(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Classification: Fedora
Description of problem: The kerning is incorrect in some applications.
How reproducible: Always
Steps to Reproduce:
1. Install the Microsoft Corefonts for comparions (corefonts.sf.net)
2. Load Abiword and type "Test AV fi" on first and second line. Set first line
to Arial and second line to Liberation Sans.
3. Repeat step 2 in Openoffice
Actual results:
The kerning is incorrect in Openoffice
Expected results:
The kerning should match in Openoffice
Additional info:
The same problems occurs when using the Liberation fonts with Apache FOP
(http://xmlgraphics.apache.org/fop/)
--
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.
13 years, 9 months
[Bug 508899] New: Monospace no more
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: Monospace no more
https://bugzilla.redhat.com/show_bug.cgi?id=508899
Summary: Monospace no more
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: liberation-fonts
AssignedTo: cchance(a)redhat.com
ReportedBy: yaneti(a)declera.com
QAContact: extras-qa(a)fedoraproject.org
CC: cchance(a)redhat.com, fedora-fonts-bugs-list(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Classification: Fedora
Created an attachment (id=349951)
--> (https://bugzilla.redhat.com/attachment.cgi?id=349951)
buggy monospace
Description of problem:
The new liberaion-mono font from liberation-fonts-1.05.1.20090630-1.fc12 , no
longer appears monospaced in verious applications (firefox, gedit). Attached a
composite of the new and old monospaced font rendering of the same thing in
gedit.
--
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.
13 years, 9 months
[Issue 113586] Unable to get correct version of OpenSymbol
by tl@openoffice.org
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=113586
------- Additional comments from tl(a)openoffice.org Mon Aug 2 20:10:12 +0000 2010 -------
To avoid misunderstandings: The font itself is compatible! Meaning that all
characters in the old font are still present in the new font. Thus an old office
with Math using the old private use area code points will still work.
But a OOo 3.3 Math with new and correct code points in use (internally and for
import/export) can not properly work with the old font where usually no symbol
was present at the correct code points.
Just to list here as well what we previously considered as possible solutions
without yet choosing one from:
1) Have new name for the new font. Easiest but maybe ugliest solution since we
just fixed problems with the font and it is still compatible with old versions
of the font.
2) The font found in the installation should *always* be used. This will also
solve the issue for sure, but the font may not have been installed system wide
and thus other applications may still use the old version. Whatever implications
that might have. It could also be considered to use this approach for the
OpenSymbol font only in order to not miss new versions of other fonts
that come with the OOo installation.
3) when vcl is determining the path of the font to use it may also retrieve the
version of that font. If the version within the OOo installation is newer that
one should be used. Since we are probably the only provider for updates of the
OpenSymbol font I see no real advantage over using solution 2) here though if
only the OpenSymbol font is in question.
All in all my favorite solution would be 2) since 3) seems to be unnecessarily
complicated and 1) somewhat crude. But since I'm no expert on the matter and
neither do manage distributions probably someone else might be able to shed more
light on this.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
13 years, 9 months
[Issue 113586] Unable to get correct version of OpenSymbol
by nmailhot@openoffice.org
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=113586
User nmailhot changed the following:
What |Old value |New value
================================================================================
CC|'hdu,is,mru,of' |'fedorafonts,hdu,is,mru,of
| |'
--------------------------------------------------------------------------------
------- Additional comments from nmailhot(a)openoffice.org Mon Aug 2 15:28:31 +0000 2010 -------
> Finally we could also hard code, that this one font is always used from
> share/fonts/truetype
This won't fly under Linux. Distributions explicitely move opensymbol in a
standard place instead of having it lost deep inside the OO.o tree
http://koji.fedoraproject.org/koji/rpminfo?rpmID=2100031
Also, under Linux (still) fontconfig will always use the most recent version of
any given font (as in: font metadata), regardless of where it is installed
Though it's a good idea to rename the font if it has changed so much old
documents referencing the previous version will break if fed the new one
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
13 years, 9 months
[Issue 113558] Change Case broken by language tags and/or ligatures
by es@openoffice.org
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=113558
User es changed the following:
What |Old value |New value
================================================================================
Status|UNCONFIRMED |RESOLVED
--------------------------------------------------------------------------------
Resolution| |INVALID
--------------------------------------------------------------------------------
------- Additional comments from es(a)openoffice.org Mon Aug 2 13:57:08 +0000 2010 -------
This issue is "as is" invalid because it deals with different problems in one
same report.
I split it in issue 113584 and issue 113587.
Feel free to file a separate task for the dictionary problem after have checked
that there is no duplicate for this.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
13 years, 9 months
[lcdf-typetools/f14/master] * Mon Aug 02 2010 Parag Nemade <pnemade AT redhat.com> - 2.83-1 - Update to next upstream release 2.
by Parag Nemade
commit 8d6806dbcba96632d952fae01655c9026ce68f8a
Author: Parag Nemade <pnemade(a)redhat.com>
Date: Mon Aug 2 15:49:11 2010 +0530
* Mon Aug 02 2010 Parag Nemade <pnemade AT redhat.com> - 2.83-1
- Update to next upstream release 2.83
lcdf-typetools.spec | 13 ++++---------
sources | 2 +-
2 files changed, 5 insertions(+), 10 deletions(-)
---
diff --git a/lcdf-typetools.spec b/lcdf-typetools.spec
index 9b5f793..9bf1ef5 100644
--- a/lcdf-typetools.spec
+++ b/lcdf-typetools.spec
@@ -1,13 +1,11 @@
Name: lcdf-typetools
-Version: 2.80
+Version: 2.83
Release: 1%{?dist}
Summary: Tools for manipulating OpenType fonts
Group: User Interface/X
License: GPLv2+
URL: http://www.lcdf.org
Source0: http://www.lcdf.org/type/%{name}-%{version}.tar.gz
-BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX)
-
BuildRequires: kpathsea-devel
%description
@@ -26,12 +24,8 @@ make CFLAGS="%{optflags}" %{?_smp_mflags}
%install
-rm -rf %{buildroot}
make install DESTDIR=%{buildroot} INSTALL="install -p"
-%clean
-rm -rf %{buildroot}
-
%files
%defattr(-,root,root,-)
@@ -51,6 +45,9 @@ rm -rf %{buildroot}
%{_datadir}/lcdf-typetools
%changelog
+* Mon Aug 02 2010 Parag Nemade <pnemade AT redhat.com> - 2.83-1
+- Update to next upstream release 2.83
+
* Wed Dec 02 2009 Parag Nemade <pnemade AT redhat.com>- 2.80-1
- Update to next upstream release 2.80
@@ -62,5 +59,3 @@ rm -rf %{buildroot}
* Thu May 21 2009 Parag Nemade <pnemade AT redhat.com>- 2.78-1
- Initial specfile for Fedora
-
-
diff --git a/sources b/sources
index 5ceafb4..22ee00b 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-2c2d78e8acf7c7cab9e7da6ed4ea87d3 lcdf-typetools-2.80.tar.gz
+e5526d4d05a50c12de0184a25ff0294c lcdf-typetools-2.83.tar.gz
13 years, 9 months