fonts-bugs August 2010

fonts-bugs@lists.fedoraproject.org

31 participants
295 discussions

by Fedora Koji Build System

python-compositor has broken dependencies in the F-14 tree: On x86_64: python-compositor-0.2b-2.fc14.noarch requires python(abi) = 0:2.6 On i386: python-compositor-0.2b-2.fc14.noarch requires python(abi) = 0:2.6 Please resolve this as soon as possible.

13 years, 9 months

1
0
0 / 0

[Bug 477044] [Tracker] Deploy new font packaging guidelines for Fedora 11

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. https://bugzilla.redhat.com/show_bug.cgi?id=477044 Bug 477044 depends on bug 477054, which changed state. Bug 477054 Summary: [fontconfig] Rebuild against fontpackages-devel depending on fontpackages-filesystem https://bugzilla.redhat.com/show_bug.cgi?id=477054 What |Old Value |New Value ---------------------------------------------------------------------------- Status|CLOSED |ASSIGNED Resolution|WONTFIX | -- 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

1
0
0 / 0

[Bug 29341] Make some fontconfig paths configurable

by bugzilla-daemon＠freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=29341 Nicolas Mailhot <nicolas.mailhot(a)laposte.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fonts-bugs(a)lists.fedoraproj | |ect.org -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

13 years, 9 months

1
0
0 / 0

[Issue 113558] Change Case broken by language tags and/or ligatures

by majukr05＠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 majukr05 changed the following: What |Old value |New value ================================================================================ CC|'fedorafonts' |'fedorafonts,majukr05' -------------------------------------------------------------------------------- --------------------------------------------------------------------- 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

1
0
0 / 0

[Issue 113558] Change Case broken by language tags and/or ligatures

by jurf＠openoffice.org

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113558 ------- Additional comments from jurf(a)openoffice.org Sun Aug 1 04:25:39 +0000 2010 ------- One more comment... After posting this report yesterday, I starting playing with the new user dictionary interface in M85 (the default for new user dictionary files has changed from binary to UTF-8). There are bugs there, too, which may possibly be related to the casing errors. So, please don't treat the following as a separate bug report (it's in the wrong place for that, I know), but instead as a clue to the possible cause of the casing errors. In short, when I add a word to a user dictionary that contains a double-byte character (eg a letter combined with an unusual accent, such as dot underneath), or if the user dictionary already contains such words, things start getting buggy: in some cases, an *incomplete* copy of the last word in the list gets appended to the dictionary; in other cases, the word is not added to the selected dictionary at all, but to another one. Again, I'm not a programmer, but if I were to bet on it, I'd guess there's a possibility that both sets of errors are caused by a bug in a text parsing library used by both the casing and user dictionary routines. Reason for saying this is that all the errors - casing and dictionary - appear to involve miscalculating text bounds. The parallel is particularly compelling when comparing Capitalize Every Word's mangling of text with ligatures (which could be counted as one, two or more characters), to the dictionary parser's mangling of user dictionaries that contain non-compiled characters with combining accents (which could also be counted as one, two or more characters). Has something recently changed in a text parsing component? --------------------------------------------------------------------- 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

1
0
0 / 0

← Newer
1
...
27
28
29
30
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

fonts-bugs August 2010