This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 733106

Summary: fonts.alias refer to encodings not listed in fonts.dir
Product: [Fedora] Fedora Reporter: Igor Vlasenko <viy>
Component: ttmkfdirAssignee: Pravin Satpute <psatpute>
Status: ASSIGNED --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: fonts-bugs, i18n-bugs, psatpute, tagoh
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sazanami-fonts-0.20040629-16.fc17 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:34:13 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Igor Vlasenko 2011-08-24 15:11:11 EDT
fonts.alias files refer to jisx020*.19??-0 font encodings while fonts.dir does not list them.
looks like a fonts.scale/fonts.dir generation bug.
/usr/share/X11/fonts/encodings/large/*
encodings should be present during fonts.scale/fonts.dir generation.

sazanami-fonts-0.20040629-15.fc15.src.rpm
Comment 1 Akira TAGOH 2011-08-25 03:38:55 EDT
Fixed in sazanami-fonts-0.20040629-16.fc17.
Comment 2 Igor Vlasenko 2011-08-26 11:46:18 EDT
> Fixed in sazanami-fonts-0.20040629-16.fc17.
Not yet. fonts.alias mentions jisx0208.1983-0 and jisx0201.1976-0 encodings, while 
fonts.dir use jisx0208.1983-0 and jisx0201.1990-0 encodings.
Replace s,jisx0201.1976-0,jisx0201.1990-0,g in fonts.alias to fix the bug completely.
Comment 3 Akira TAGOH 2011-08-29 03:38:38 EDT
Well, that is generated by ttmkfdir. reassigning to ttmkfdir then.
Comment 4 Pravin Satpute 2011-08-31 06:32:51 EDT
just checked sazanami-gothic.ttf

is it really supports JIS_X_0201?

http://en.wikipedia.org/wiki/JIS_X_0201 "7-bit and 8-bit coded character sets for information interchange" 

Just checked it by editing in fontforge, it shows me different characters than JIS_X_0201 at location 0xA1, 0xA2. (chart is available at http://en.wikipedia.org/wiki/JIS_X_0201)
Comment 5 Akira TAGOH 2011-08-31 07:29:01 EDT
the character code like 0xA1 and 0xA2 isn't something mapped onto Unicode, but on JIS X 0201. and this is a character sets but not an encoding, those code doesn't necessarily matches to other encoding such as SJIS and EUC-JP.
Comment 6 Fedora End Of Life 2013-04-03 15:41:15 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Comment 7 Fedora End Of Life 2015-01-09 16:52:17 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 8 Pravin Satpute 2015-01-14 04:32:36 EST
moving to F20.
Comment 9 Fedora End Of Life 2015-05-29 04:39:56 EDT
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 10 Fedora End Of Life 2015-06-29 20:34:13 EDT
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 11 Fedora End Of Life 2016-11-24 05:33:54 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.