From Fedora Project Wiki
< Changes
No edit summary |
|||
| (14 intermediate revisions by 2 users not shown) | |||
| Line 35: | Line 35: | ||
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | ||
* Email: tagoh@redhat.com | * Email: tagoh@redhat.com | ||
* Release notes | * Release notes ticket: <s>[https://pagure.io/fedora-docs/release-notes/issue/103 #103]</s> | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | ||
| Line 45: | Line 45: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/28 | Fedora 28 ]] | * Targeted release: <s>[[Releases/28 | Fedora 28 ]] </s> | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
| Line 55: | Line 55: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: < | * Tracker bug: <s>[https://bugzilla.redhat.com/show_bug.cgi?id=1534560 #1534560]</s> | ||
== Detailed Description == | == Detailed Description == | ||
| Line 67: | Line 67: | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
This changes provides better quality | This changes provides better quality of render Korean characters and consistencies in look among typefaces. | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: | ||
** Update packages with proper priority of fontconfig config file (naver-nanum-gothic*fonts and google-cjk-noto-*-kr-fonts) | |||
** Update comps | |||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
| Line 76: | Line 78: | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Release engineering: [https://pagure.io/releng/ | * Release engineering: [https://pagure.io/releng/issue/7225 #7225] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
| Line 110: | Line 112: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* Check if the default font is changed to Noto | |||
** run fc-match for sans, serif, and monospace say | |||
* Check applications, including desktop/toolkit specific and terminals if Japanese characters is properly rendered. | |||
== User Experience == | == User Experience == | ||
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
will see better quality of rendering for Korean characters on applications and on desktops. | |||
== Dependencies == | == Dependencies == | ||
| Line 130: | Line 134: | ||
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? N/A (not a System Wide Change), | * Blocks release? N/A (not a System Wide Change), No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* Blocks product? | * Blocks product? none <!-- Applicable for Changes that blocks specific product release/Fedora.next --> | ||
== Documentation == | == Documentation == | ||
Latest revision as of 08:12, 12 April 2018
Korean Default Fonts to Google Noto
Summary
Changes the default fonts for Korean to Google Noto.
Owner
- Name: Akira TAGOH
- Email: tagoh@redhat.com
- Release notes ticket:
#103
Current status
Detailed Description
Changes the default fonts for Korean to Google Noto. each typefaces will be changed as the following:
- sans-serif
- NanumGothic -> Noto Sans KR
- serif
- (No default for serif) -> Noto Serif KR
- monospace
- (No default for monospace) -> Noto Sans Mono CJK KR
Benefit to Fedora
This changes provides better quality of render Korean characters and consistencies in look among typefaces.
Scope
- Proposal owners:
- Update packages with proper priority of fontconfig config file (naver-nanum-gothic*fonts and google-cjk-noto-*-kr-fonts)
- Update comps
- Other developers: N/A (not a System Wide Change)
- Release engineering: #7225 (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
- Check if the default font is changed to Noto
- run fc-match for sans, serif, and monospace say
- Check applications, including desktop/toolkit specific and terminals if Japanese characters is properly rendered.
User Experience
will see better quality of rendering for Korean characters on applications and on desktops.
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), No
- Blocks product? none
Documentation
N/A (not a System Wide Change)