Bug 2095025 - Enhance Persian Font Support
Summary: Enhance Persian Font Support
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Hedayat Vatankhah
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F37Changes
TreeView+ depends on / blocked
 
Reported: 2022-06-08 19:58 UTC by Ben Cotton
Modified: 2023-01-06 22:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 16:25:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ben Cotton 2022-06-08 19:58:55 UTC
This is a tracking bug for Change: Enhance Persian Font Support
For more details, see: https://fedoraproject.org/wiki/Changes/EnhancePersianFontSupport

This change aims to provide a consistent experience for those who use Fedora in Persian or write or read Persian text in Fedora.

If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.

Comment 1 Ben Cotton 2022-08-09 16:02:52 UTC
Today we reached the Code Complete (Testable) milestone on the F37 schedule: https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html

At this time, all F37 Changes should be complete enough to be testable. You can indicate this by setting this tracker to the MODIFIED status. If the Change is 100% code complete, you can set the tracker to ON_QA. If you need to defer this Change to F38, please NEEDINFO me.

Changes that have not reached at least the MODIFIED status will be given to FESCo for evaluation of contingency plans.

Comment 2 Ben Cotton 2022-08-10 16:37:11 UTC
The steps listed in the Scope section (https://fedoraproject.org/wiki/Changes/EnhancePersianFontSupport#Scope) appear to be complete, so I am assuming it is at least testable. Setting to MODIFIED. Please set to ON_QA if it is fully complete or back to ASSIGNED if it's not yet testable.

Comment 3 Hedayat Vatankhah 2022-08-10 21:30:27 UTC
Thanks! I prefer for it to remain in MODIFIED state for the time being, needs some final testing.

Comment 4 Ben Cotton 2022-08-23 19:21:11 UTC
Today we reached the Code Complete (100% complete) milestone on the F37 schedule: https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html

At this time, all F37 Changes should be 100% complete. You can indicate this by setting this tracker to the ON_QA status. If you need to defer this Change to F38 please NEEDINFO me.

Note that we are entering the Beta freeze. Additional package changes to complete this Change will need an approved blocker or freeze exception. See https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process for more information.

Changes that have not reached the ON_QA status will be given to FESCo for evaluation of contingency plans.

Comment 5 Ben Cotton 2022-11-15 16:25:03 UTC
F37 was released today, so I am closing this tracker. If this Change was not completed, please notify me ASAP.

Comment 6 bugzilla.redhat.com@mno.pw 2023-01-06 17:41:10 UTC
I'm not sure if this is the culprit, but since upgrading the last time my terminal is really, really ugly. What can I do to get the previous settings?

Comment 7 Hedayat Vatankhah 2023-01-06 22:57:58 UTC
Check Vazirmatn font to see if your terminal is using it. Although, it is NOT a monospace font and hence it should not affect your terminal. Also, what is your locale? Do you use Arabic/Persian letters? This font doesn't affect other scripts.

Anyway, it's very unlikely that your problem has anything to do with this change, and nobody else have reported such a problem.


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