Bug 1002380 - U+0A09,U+0A71 sequence collide with each other
Summary: U+0A09,U+0A71 sequence collide with each other
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lohit-punjabi-fonts
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pravin Satpute
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-29 04:33 UTC by Pravin Satpute
Modified: 2013-09-19 02:07 UTC (History)
3 users (show)

Fixed In Version: lohit-punjabi-fonts-2.5.3-3.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-19 02:07:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pravin Satpute 2013-08-29 04:33:54 UTC
Description of problem:
should not collide

Version-Release number of selected component (if applicable):
lohit-punjabi-fonts-2.5.3-1.fc19.noarch

How reproducible:
everytime

Steps to Reproduce:
1. type above sequence in gedit
2.
3.

Actual results:
its merging

Expected results:
should not merge

Additional info:

Comment 1 Fedora Update System 2013-08-30 04:42:33 UTC
lohit-punjabi-fonts-2.5.3-3.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/lohit-punjabi-fonts-2.5.3-3.fc19

Comment 2 Fedora Update System 2013-08-30 22:59:42 UTC
Package lohit-punjabi-fonts-2.5.3-3.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lohit-punjabi-fonts-2.5.3-3.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-15564/lohit-punjabi-fonts-2.5.3-3.fc19
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2013-09-19 02:07:23 UTC
lohit-punjabi-fonts-2.5.3-3.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.