[Bug 606217] New: Eccentric glyph for the lowercase Greek gamma letter (=?UTF-8?Q?=CE=B3?=)
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: Eccentric glyph for the lowercase Greek gamma letter (γ)
https://bugzilla.redhat.com/show_bug.cgi?id=606217
Summary: Eccentric glyph for the lowercase Greek gamma letter
(γ)
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: liberation-fonts
AssignedTo: cchance(a)redhat.com
ReportedBy: discon(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, cchance(a)redhat.com,
fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Description of problem:
The liberation fonts have a strange glyph for the lowercase Greek gamma letter
whenever hinting is on. The hinting makes the glyph look similar to the 'y'
letter (the bottom part tends towards left).
This looks weird and is unique on this font family, AFAIK.
--
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.
7 years, 9 months
[Bug 527740] New: [ml_IN] Applying Backspace to a chillu conjunct followed by punctuation/SPACE results in deletion of the chillu also
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: [ml_IN] Applying Backspace to a chillu conjunct followed by punctuation/SPACE results in deletion of the chillu also
https://bugzilla.redhat.com/show_bug.cgi?id=527740
Summary: [ml_IN] Applying Backspace to a chillu conjunct
followed by punctuation/SPACE results in deletion of
the chillu also
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: pango
AssignedTo: besfahbo(a)redhat.com
ReportedBy: apeter(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: eng-i18n-bugs(a)redhat.com, besfahbo(a)redhat.com,
fedora-fonts-bugs-list(a)redhat.com,
smc-discuss(a)googlegroups.com
Classification: Fedora
Target Release: ---
Created an attachment (id=363982)
--> (https://bugzilla.redhat.com/attachment.cgi?id=363982)
Screenshot for chillu conjuncts
Description of problem:
When chillu conjuncts are followed by any punctuation marks like "!", ".", ",",
"'", "?" or SPACE, ie when a word ends with a chillu conjunct, and followed by
a punctuation mark or a SPACE, using Backspace to delete the punctuation mark
or SPACE results in the deletion of chillu conjunct together with the
punctuation mark/SPACE.
Version-Release number of selected component (if applicable):
pango 1.26.0-1.fc12 i686
How reproducible:
Always
Steps to Reproduce:
1. Open gedit
2. type any of chillu conjunct, eg: 0D28, 0D4D, 200D
OR
type a word ending with chillu conjunct, eg: 0D05, 0D35, 0D28, 0D4D, 200D
3. type any punctuation marks like "!", ".", ",", "'", "?" or SPACE
4. Press Backspace
Actual results:
When using Backspace after chillu conjunct followed by punctuation mark or
SPACE, instead of deleting punctuation mark or SPACE only, the chillu conjunct
also gets deleted.
Expected results:
When using Backspace after chillu conjunct followed by punctuation mark or
SPACE, only the punctuation mark/SPACE should get deleted.
Additional info:
1. This does not happen when chillu comes in between a word. eg: നന്മ (0D28,
0D28, 0D4D, 200D, 0D2E)
2. This issue is not present in oowriter and kwrite. When above steps are
reproduced, deletions happens in correct order.
Versions used:
libicu-4.2.1-6.fc12 i686
qt-4.5.2-22.fc12 i686
3. Screenshot attached for chillu conjuncts and eg of words with chillu
--
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.
7 years, 10 months
[Bug 507292] New: [RFE] Allow wildcards/regexps in rpm deps
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: [RFE] Allow wildcards/regexps in rpm deps
https://bugzilla.redhat.com/show_bug.cgi?id=507292
Summary: [RFE] Allow wildcards/regexps in rpm deps
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: rpm
AssignedTo: pmatilai(a)redhat.com
ReportedBy: nicolas.mailhot(a)laposte.net
QAContact: extras-qa(a)fedoraproject.org
CC: pmatilai(a)redhat.com, jnovy(a)redhat.com,
ffesti(a)redhat.com, fedora-fonts-bugs-list(a)redhat.com
Classification: Fedora
(this is mostly a yum-level RFE, but it would be nice if we kept the same
depsolving logic in both apps)
The problem:
Selecting a font is a multi-criterium operation. We need to match on font
family, font style, language support, unicode support, etc. At any time all of
just some of those selection criterii can be provided by the user or
applications.
To have features like font auto-installation work reliably, this matching needs
to extend to the package database
Right now rpm is only allowing to specify atomic provides, so we can have a
font package that
Provides font(dejavusans)
and
Provides
font(:lang=el)
but there is no warranty both those provides are belonging to the same font.
There is no way to distinguish between a package that includes an actual greek
dejavusans and a package that includes a dejavusans greek-less file and another
totally different greek font
To workaround this rpm limitation we've been asking packagers to put font files
belonging to different font families in different packages. However:
1. many still don't
2. it's not technically possible for all font formats, for example the ttc font
format allows mixing of fonts with different characteristics in a single file
The ideal solution:
Ability to have Provides like:
font(comma-separated font name list|comma-separated style list|comma-separated
lang list) (rough mockup that probably needs refining)
And have deps like (dejavu|*|el) work in rpm
(yes a font can declare many different names, be available in many different
styles, cover many different languages)
For ttc files we'd then generate one Provides for each font included in the ttc
bundle
--
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.
8 years, 1 month
[Bug 648350] New: Proper Bold for Lohit Devanagari
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: Proper Bold for Lohit Devanagari
https://bugzilla.redhat.com/show_bug.cgi?id=648350
Summary: Proper Bold for Lohit Devanagari
Product: Fedora
Version: rawhide
Platform: All
OS/Version: All
Status: NEW
Severity: medium
Priority: low
Component: lohit-devanagari-fonts
AssignedTo: psatpute(a)redhat.com
ReportedBy: ujjwol(a)fedoraproject.org
QAContact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
psatpute(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Created attachment 456789
--> https://bugzilla.redhat.com/attachment.cgi?id=456789
Picture showing the bold and regular typeface
Description of problem:
The existing font provided Lohit Devangari only contains the regular version.
It does not contain the bold version. When the computer generates bold using
the regular font, and the results are ugly. The siro-rekha is broken and many
other stuffs are also broken.
Version-Release number of selected component (if applicable):
How reproducible:
Exactly reproducible
Steps to Reproduce:
1.See any hindi/nepali/marathi/sanskrit pages in firefox with bold text
2. type devanagari text in openoffice and bold it
Actual results:
The a broken lohit devanagari font is displayed.
Expected results:
A well maintained bold should be shown.
Additional info:
The typographic value is lost when bold is used though it is still readable.
--
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.
8 years, 4 months
[Bug 770173] New: [abrt] fontforge-20110222-4.fc16: __GI_raise: Process /usr/bin/fontforge was killed by signal 6 (SIGABRT)
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: [abrt] fontforge-20110222-4.fc16: __GI_raise: Process /usr/bin/fontforge was killed by signal 6 (SIGABRT)
https://bugzilla.redhat.com/show_bug.cgi?id=770173
Summary: [abrt] fontforge-20110222-4.fc16: __GI_raise: Process
/usr/bin/fontforge was killed by signal 6 (SIGABRT)
Product: Fedora
Version: 16
Platform: x86_64
OS/Version: Unspecified
Status: NEW
Status Whiteboard: abrt_hash:226d280da458c02dbf836374359e6d45beeb31ad
Severity: unspecified
Priority: unspecified
Component: fontforge
AssignedTo: kevin(a)scrye.com
ReportedBy: quantum.analyst(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: kevin(a)scrye.com, fonts-bugs(a)lists.fedoraproject.org,
paul(a)frixxon.co.uk
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
libreport version: 2.0.8
abrt_version: 2.0.7
backtrace_rating: 4
cmdline: fontforge Lobster.ttf
crash_function: __GI_raise
executable: /usr/bin/fontforge
kernel: 3.1.5-1.fc16.x86_64
pid: 2361
pwd: /home/zero-one/.fonts
reason: Process /usr/bin/fontforge was killed by signal 6 (SIGABRT)
time: Fri 23 Dec 2011 04:57:53 PM EST
uid: 1000
username: zero-one
backtrace: Text file, 53804 bytes
dso_list: Text file, 5454 bytes
maps: Text file, 46458 bytes
build_ids:
:1c6a95451ee19617be5abea3d121f0226d21ddda
:513b62aebf666f00864c6f1ebea4dc82b2bc5012
:3ed9e61c2b7e707ce244816335776afa2ad0307d
:aa733447f84020c94a66814e501a36e248cbb43d
:8b46e30ba91f3a655184141ea81f24005f100891
:e3c88cb9ea428bd61f4064dbd53acae2d396a1ec
:87461d97d0ba0bd94e4d74ff0879190b67b326c5
:6ae19b07608683ea0d76f1406c6d50d5a2793ecc
:d0c6e13f00a20952a72a945c929efb175fd760e3
:ab59942678bcdecb23756804dcd0aac63ccc1669
:30af62b93e2ab7dbaf39c52e346cd52101b4b590
:3d7445fcfec84df0bd46f12e5540d6ab6db2ec9d
:f0d50e3af2dfee021a327fb85a993a2312a98145
:638db099ff5fb986d1a092629d1bb1dca5be4904
:e5429e0905bedecc534b057783916ba43e06a66e
:44ece411beb2ef1acdb5eb2161666de41cc2f31d
:2ff598542ad79916b2e8d621e1dfe2e03aca9e9f
:8acc43df965b3c0a70dcfad11c0ade056bdb055b
:b502249bcf2a4f465feeb8b9578c80cda6f4103d
:c8a4e40c84c2f52e78c64d31efc0191c565a9049
:0f0c9eed63ed279ceb0aef109eff8bcbb351e4bb
:25b834f4c4dc534708635ff1064e2fe02a366a62
:163b323da65b708418226eb5fa8b057c731d1475
:6ecc3efaedf849a17c30a67fe15b4dacca1bd981
:0911ea7c180d733724f89037b8e8a34e64024aec
:8631fa022a75e4bfbd78f96ad368f88456e39cfe
:c64ae11db2f40081de9a6983295b7e2105556695
:ab93f5a6105938b598a9eb4321bcfb9c244945d5
:48aea888319e1848137073c9cbde54a4c2a731c9
:1d1e7527a6b5fd829fe8c097bea4c62b2d0f2df9
:36c3026b958ed92321d0531a483442a9c5a957e9
:2f884a17559b8d3954348fdf2131980eac9a79f0
:1c2ccaf923ac61efd874e4ca82bf6612f4cb0c31
:b0eabf9093defbfdd0857ea3ed1a4563b743434e
:4c842320387ff7f6f91b7842b223c16518be909f
:e2e67b3ae2579e1667b73ad385f61552931024e9
:9d1209fc79304f03cc839de1c0036c61b48dfff8
:7994f114cf7189e482f2665fae8e351ed8bc05e3
:07470201df55a5254027d05fa4dc509b10f2986a
:d460d68692c1b32346f469e0a9ab3933cf1f3d1c
:dc729005f811417fddf05fe15b27c01257fed480
:e5d7ac2dfe435e205e491f7ce827563859fca4f4
:b7633dbfe4880a163b4059184cb20c37cfaf7521
:3e2404bd469800afd61eda83d0292a2165ef0db0
:c394c720f0727b738128393fbf26ebd355f42498
:54a066b1f8ae391050d51221778b39261283cf51
:930141e14bc90a585553dfbe2c6661806af11f06
:c8e7f118041a9f77e0dd673da11b5653be27b5a2
:c2d49d72ec1a1e68b39c3724693f83f44d80a259
:e02146cbd7b3747790cf4808baa58dc78c2e0042
:b0a2d0b4c09d819887ec7d711c8cf3977a074c4f
:a518a8b1b5c3e80dee813df05e951d205d6ac48c
:d203a42e4c417fbf0c6ab96ce6f7946ec8ac0435
:0949b493f01e0553822be3bd14def9dbe79b804f
comment:
:Just randomly looking around directories in the Open Font dialog.
:Was in /usr/share/fonts, after checking four or five subdirectories, but not
opening anything.
environ:
:XDG_VTNR=1
:XDG_SESSION_ID=2
:HOSTNAME=VeniVidiVici.HOME
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:GPG_AGENT_INFO=/tmp/keyring-zRujzU/gpg:0:1
:TERM=xterm
:SHELL=/bin/bash
:HISTSIZE=1000
:XDG_SESSION_COOKIE=ff831396568380a65b4ba5f100000011-1324693688.856668-425829544
:GJS_DEBUG_OUTPUT=stderr
:WINDOWID=41943045
:GNOME_KEYRING_CONTROL=/tmp/keyring-zRujzU
:QTDIR=/usr/lib64/qt-3.3
:QTINC=/usr/lib64/qt-3.3/include
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:IMSETTINGS_MODULE=none
:USER=zero-one
:LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.tbz=01;31:*.tbz2=01;31:*.bz=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;!
35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=01;36:*.au=01;36:*.flac=01;36:*.mid=01;36:*.midi=01;36:*.mka=01;36:*.mp3=01;36:*.mpc=01;36:*.ogg=01;36:*.ra=01;36:*.wav=01;36:*.axa=01;36:*.oga=01;36:*.spx=01;36:*.xspf=01;36:*.pdf=00;33:*.ps=00;33:*.ps.gz=00;33:*.txt=00;33:*.patch=00;33:*.diff=00;33:*.log=00;33:*.tex=00;33:*.xls=00;33:*.xlsx=00;33:*.ppt=00;33:*.pptx=00;33:*.rtf=00;33:*.doc=00;33:*.docx=00;33:*.odt=00;33:*.ods=00;33:*.odp=00;33:*.xml=00;33:*.epub=00;33:*.abw=00;33:*.html=00;33:*.wpd=00;33:
:SSH_AUTH_SOCK=/tmp/keyring-zRujzU/ssh
:USERNAME=zero-one
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1513,unix/unix:/tmp/.ICE-unix/1513
:PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/zero-one/code/android-sdk-linux_x86/tools:/home/zero-one/code/android-sdk-linux_x86/platform-tools:/home/zero-one/.local/bin:/home/zero-one/code/android-sdk-linux_x86/tools:/home/zero-one/code/android-sdk-linux_x86/platform-tools
:MAIL=/var/spool/mail/zero-one
:DESKTOP_SESSION=gnome
:GSETTINGS_SCHEMA_DIR=/home/zero-one/.local/share/glib-2.0/schemas/
:QT_IM_MODULE=xim
:PWD=/home/zero-one/.fonts
:XMODIFIERS=@im=none
:GNOME_KEYRING_PID=1509
:LANG=en_CA.utf8
:KDE_IS_PRELINKED=1
:MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles
:GDM_LANG=en_CA.utf8
:LOADEDMODULES=
:KDEDIRS=/usr
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:XDG_SEAT=seat0
:HOME=/home/zero-one
:SHLVL=2
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:LOGNAME=zero-one
:QTLIB=/usr/lib64/qt-3.3/lib
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-xNGdIawEwq,guid=63f22d2712ab078eb4f10cdd00000034
:MODULESHOME=/usr/share/Modules
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/zero-one
:MTN_MERGE=meld
:DISPLAY=:0
:COLORTERM=gnome-terminal
:XAUTHORITY=/var/run/gdm/auth-for-zero-one-ayzEyJ/database
:'module=() { eval `/usr/bin/modulecmd bash $*`\n}'
:_=/usr/bin/fontforge
:OLDPWD=/home/zero-one
var_log_messages:
:Dec 22 17:23:34 VeniVidiVici yum[3674]: Installed:
fontforge-20110222-4.fc16.x86_64
:Dec 22 17:29:01 VeniVidiVici kernel: [ 6681.618693] fontforge[3698] trap
divide error ip:7ff290f0fd54 sp:7fffaed127e0 error:0 in
libfontforge.so.1.0.0[7ff290e68000+36f000]
:Dec 22 17:29:02 VeniVidiVici abrt[3711]: Saved core dump of pid 3698
(/usr/bin/fontforge) to /var/spool/abrt/ccpp-2011-12-22-17:29:01-3698 (18186240
bytes)
:Dec 22 17:41:40 VeniVidiVici kernel: [ 7440.652920] fontforge[3790] trap
divide error ip:7fe59e65ed54 sp:7fff990867d0 error:0 in
libfontforge.so.1.0.0[7fe59e5b7000+36f000]
:Dec 22 17:41:41 VeniVidiVici abrt[3815]: Saved core dump of pid 3790
(/usr/bin/fontforge) to /var/spool/abrt/ccpp-2011-12-22-17:41:40-3790 (16412672
bytes)
:Dec 23 16:51:23 VeniVidiVici kernel: [ 1448.061763] fontforge[2317] trap
divide error ip:3b3eca7d54 sp:7fff69f0efd0 error:0 in
libfontforge.so.1.0.0[3b3ec00000+36f000]
:Dec 23 16:51:25 VeniVidiVici abrt[2319]: Saved core dump of pid 2317
(/usr/bin/fontforge) to /var/spool/abrt/ccpp-2011-12-23-16:51:23-2317 (16928768
bytes)
:Dec 23 16:57:55 VeniVidiVici abrt[2367]: Saved core dump of pid 2361
(/usr/bin/fontforge) to /var/spool/abrt/ccpp-2011-12-23-16:57:53-2361 (28041216
bytes)
--
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.
8 years, 5 months
[Bug 1016989] New: [ml_IN] non-standard sequence sequence for stacked chillu-N and RRA in Lohit Malayalam font should be removed
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1016989
Bug ID: 1016989
Summary: [ml_IN] non-standard sequence sequence for stacked
chillu-N and RRA in Lohit Malayalam font should be
removed
Product: Fedora
Version: rawhide
Component: lohit-malayalam-fonts
Assignee: psatpute(a)redhat.com
Reporter: samjnaa(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, psatpute(a)redhat.com
This is related to bug #1016984 which I reported just now.
As per TUS 6.2 chapter 9.9 p 321 (p 351 of PDF) the correct sequence to get the
display of stacked chillu-N on top of RRA in Malayalam is: CHILLU N + VIRAMA +
RRA. That is: ൻ്റ = 0d7b 0d4d 0d31. However, currently Lohit Malayalam font
does not support this sequence. In bug #1016984 I have requested to add it.
Apart from that, note that currently the sequence being used to display stacked
chillu-N on top of RRA in Lohit font is ന്റ = 0d28 0d4d 0d31. This is
non-standard. It is inadvisable to retain this sequence as having two
canonically non-equivalent sequences display the same is a security issue of
confusability.
My request from the POV of being standard-compliant would be to remove this
sequence.
However I am sure (based on personal email communication) there will be
objection from people such as Santosh Thottingal since they do not agree with
the standard on this matter. They maintain that NA + VIRAMA + RRA is the
correct sequence to get this display.
I have told them that if they disagree with the standard then they should
discuss the matter on the Unicode and try to make the Unicode Technical
Committee accept their view. Otherwise such sequences will just be
standards-non-compliant and the existing diversified situation will only be
aggravated.
Certainly the current standard-prescribed sequence should be included to be
standards compliant. For that I have already filed the separate bug. For 100%
compliance the old non-standard should be removed. To track that I am filing
this bug now.
In the face of community objection, it is up to the project maintainer to
decide about this.
Version-Release number of selected component (if applicable):
2.5.4
--
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=ALH5tjahY0&a=cc_unsubscribe
8 years, 6 months
[Bug 985343] New: After telugu input .(full stop) is rendering as square box in lokalize editor
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=985343
Bug ID: 985343
Summary: After telugu input .(full stop) is rendering as square
box in lokalize editor
Product: Fedora
Version: 19
Component: lohit-telugu-fonts
Severity: unspecified
Priority: unspecified
Assignee: psatpute(a)redhat.com
Reporter: kkrothap(a)redhat.com
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 774715
--> https://bugzilla.redhat.com/attachment.cgi?id=774715&action=edit
Example screen shot regarding the problem.
Description of problem:
While using lokalize as translation editor, after telugu input if i type .(full
stop) it is rendering as square box.
Version-Release number of selected component (if applicable):
lohit-telugu-fonts-2.5.3-2.fc19.noarch
kdesdk-lokalize-4.10.5-1.fc19.x86_64
How reproducible:
Every time
Steps to Reproduce:
1.Open lokalize.
2.Input some telugu text.
3.Type . after telugu text.
Actual results:
. rendering as square box
Expected results:
Should render as it should be.
Additional info:
Working fine with pothana font.
--
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=ptT4KXOL2o&a=cc_unsubscribe
8 years, 7 months
[Bug 477387] New: Please convert to new font packaging guidelines
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: Please convert to new font packaging guidelines
https://bugzilla.redhat.com/show_bug.cgi?id=477387
Summary: Please convert to new font packaging guidelines
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: fonts-hebrew-fancy
AssignedTo: danken(a)cs.technion.ac.il
ReportedBy: nicolas.mailhot(a)laposte.net
QAContact: extras-qa(a)fedoraproject.org
CC: danken(a)cs.technion.ac.il,
fedora-fonts-bugs-list(a)redhat.com
Classification: Fedora
This bug has been filed because we've detected your package includes one or
several font files:
repoquery -C --repoid=rawhide -f '*.ttf' -f '*.otf' -f '*.pfb'
-f '*.pfa' --qf='%{SOURCERPM}\n' |sed -e
's+-[0-9.-]*\.fc[123456789]\(.*\)src.rpm++g'|sort|uniq
Unfortunately the script
does not detect symlinks to other packages, so if that's your case, you can
close this bug report now.
Otherwise, you should know that:
- Fedora guidelines
demand the packaging of fonts in a separate package or subpackage:
http://fedoraproject.org/wiki/Packaging/Guidelines#Avoid_bundling_of_font...
- our font packaging guidelines recently changed, and every package that ships
fonts must be adapted to the new templates available in the fontpackages-devel
package.
http://fedoraproject.org/wiki/PackagingDrafts/Fonts_packaging_automation_...
http://fedoraproject.org/wiki/Fedora_fonts_policy_package
http://fedoraproject.org/wiki/Simple_fonts_spec_template
http://fedoraproject.org/wiki/Fonts_spec_template_for_multiple_fonts
Please make
your package conform to the current guidelines in rawhide.
If your package is not
principaly a font package, depending on a separate font package or subpackage
is the prefered solution. If your application does not use fontconfig you can
always package symlinks to the files provided by the font package and installed
in the correct fontconfig directories.
It is preferred to make a font package or
subpackage per font family, though it is not currently a hard guidelines
requirement (it may become before Fedora 11 is released). The definition of a
font family is given on
http://fedoraproject.org/wiki/Fonts_spec_template_notes/font-family
The new
templates should make the creation of font subpackages easy and safe.
The
following packages have already been converted and can serve as examples: -
andika-fonts - apanov-heuristica-fonts - bitstream-vera-fonts - charis-fonts -
dejavu-fonts - ecolier-court-fonts - edrip-fonts - gfs-ambrosia-fonts -
gfs-artemisia-fonts - gfs-baskerville-fonts - gfs-bodoni-classic-fonts -
gfs-bodoni-fonts - gfs-complutum-fonts - gfs-didot-classic-fonts -
gfs-didot-fonts - gfs-eustace-fonts - gfs-fleischman-fonts - gfs-garaldus-fonts
- gfs-gazis-fonts - gfs-jackson-fonts - gfs-neohellenic-fonts -
gfs-nicefore-fonts - gfs-olga-fonts - gfs-porson-fonts - gfs-solomos-fonts -
gfs-theokritos-fonts - stix-fonts - yanone-kaffeesatz-fonts
If you have any remaining
questions about the new guidelines please ask them on fedora-fonts-list at
redhat.com
--
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.
8 years, 8 months
[Bug 984230] New: Broken aliasing on small sizes since version 2.00
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=984230
Bug ID: 984230
Summary: Broken aliasing on small sizes since version 2.00
Product: Fedora
Version: 18
Component: liberation-fonts
Severity: medium
Priority: unspecified
Assignee: psatpute(a)redhat.com
Reporter: gitne(a)excite.co.jp
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, psatpute(a)redhat.com
The pixel aliasing of glyphs, especially vertical lines/parts is broken since
version 2.00 on Windows (renderer). This applies to all Liberation Font types
when ClearType is off, i.e. with gray-scale anti-aliasing only. Version 2.00
has incurred aliasing for all font sizes. Version 2.00.1 fixed this by
disabling anti-aliasing for sizes < 14pt. Yet, vertical lines/parts and some
transitions from curves to lines are still rendered incorrectly or with
artifacts.
This may also apply to Fedora GNOME desktops, but it has been observed on
Windows first.
Although, I am not a font design specialist, I suppose that this problem exists
because version 2.00 is based on Google Crosscore fonts and hinting information
for small font sizes is missing.
This is a show stopper for software rendering Libration Fonts on pixel based
digital displays. Software packages like LibréOffice are also negatively
affected by this issue (although on displays only). Please resolve this issue
or revert verion 2.00 and later to beta status.
How to reproduce:
Windows XP/2003
Compare Liberation Fonts version 1.07 to version 2.00.1 for small font sizes <
14pt.
Windows Vista and later
Disable ClearType
Compare Liberation Fonts version 1.07 to version 2.00.1 for small font sizes <
14pt. Version 1.07 has been correctly hinted, hence is perfectly pixel aligned.
--
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=lAiO50lKoF&a=cc_unsubscribe
8 years, 9 months