[Fedora-i18n-bugs] [Bug 488398] New: /usr/share/ghostscript/conf.d/*.zh_* refers to *.ttf instead of *.ttc
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: /usr/share/ghostscript/conf.d/*.zh_* refers to *.ttf instead of *.ttc
https://bugzilla.redhat.com/show_bug.cgi?id=488398
Summary: /usr/share/ghostscript/conf.d/*.zh_* refers to *.ttf
instead of *.ttc
Product: Fedora
Version: 10
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: cjkunifonts
AssignedTo: cchance(a)redhat.com
ReportedBy: htl10(a)users.sourceforge.net
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, cchance(a)redhat.com,
fedora-fonts-bugs-list(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
/usr/share/ghostscript/conf.d/*map.zh_* refers to *.ttf instead of *.ttc,
causing printing or viewing of cjk pdf without embedded cjk fonts to not work.
Version-Release number of selected component (if applicable):
cjkunifonts-uming-0.2.20080216.1-10.fc10.noarch
cjkunifonts-ukai-0.2.20080216.1-10.fc10.noarch
Additional info:
This seems to be an small oversight of the packager when the unifonts changes
from ttf in 0.1.x to ttc in 0.2.x ?
--
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.
15 years
[Fedora-i18n-bugs] [Bug 500553] New: [Indic] Indic hunspell dictionary not working with kate
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: [Indic] Indic hunspell dictionary not working with kate
https://bugzilla.redhat.com/show_bug.cgi?id=500553
Summary: [Indic] Indic hunspell dictionary not working with
kate
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: enchant
AssignedTo: uwog(a)uwog.net
ReportedBy: pnemade(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: uwog(a)uwog.net, petersen(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Created an attachment (id=343731)
--> (https://bugzilla.redhat.com/attachment.cgi?id=343731)
See default spell checker is not selected to that of locale in which kate is
started.
Description of problem:
When tried to use Marathi hunspell in kate, I saw default spell checker
selected was not Marathi but English(USA)
Version-Release number of selected component (if applicable):
kdesdk-4.2.2-2.fc11.x86_64
kdebase-4.2.2-2.fc11.x86_64
enchant-1.4.2-5.fc11.x86_64
hunspell-mr-20060920-2.fc11.noarch
enchant-1.4.2-5.fc11.i586
How reproducible:
always
Steps to Reproduce:
1.Start KDE in Marathi
2.For easy testing copy text from http://mr.wikipedia.org to kate
3. Apply spell checker
Actual results:
Kate used English locale hunspell dictionary when asked to spell check.
Expected results:
Kate should use default locale hunspell dictionary when asked to spell check.
Additional info:
This bug is present for Indic languages. I just reproduced for mr_IN,
gu_IN,bn_IN,ta_IN languages.
--
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.
15 years
[Fedora-i18n-bugs] [Bug 445621] index*.html files no longer needed?
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.
https://bugzilla.redhat.com/show_bug.cgi?id=445621
Karsten Wade <kwade(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flag|needinfo? |
--- Comment #7 from Karsten Wade <kwade(a)redhat.com> 2009-05-13 01:01:22 EDT ---
Can we come up with a middle ground idea?
Maybe the startpage.xml that is the /usr/share/doc/HTML/index.html currently
could:
* Remove the version specific information (my F10 file says Fedora 9)
* A link to the local release notes
* Mentions that the search bar may not work if the computer is in fact off line
Otherwise, don't bother to add a bunch of overly busy resource links, as we did
in the past. Just those three conceptual changes.
--
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.
15 years
[Fedora-i18n-bugs] [Bug 476459] wqy-zenhei-fonts overrides Japanese desktop (so can't be installed by default in @chinese-support group)
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.
https://bugzilla.redhat.com/show_bug.cgi?id=476459
--- Comment #36 from Akira TAGOH <tagoh(a)redhat.com> 2009-05-12 22:27:01 EDT ---
(In reply to comment #35)
> But you do realize, in the end, there only exists one font order, no matter
> which way you set it. It is impossible for two fonts to be both preferred if
> they are both installed. If you want to control the orders by the presence of
> fonts, you can do exactly the same thing with a centralized conf file. The only
> difference is that a single config file gives you a master fallback list, and
> what you suggested determines this list ad-hoc, which is more difficult to
> predict and debug.
That's the policy to not mess up.
> IMHO, this is impossible. If you set <prefer> or use prepend/prepend_first, you
> ARE affecting other font packages. Indeed, that's how fontconfig works. Again,
> for a given system state, there is only one priority list for each language, no
> matter you set it from a single file, or by a bunch of font-specific files.
Right. I meant language, but not font packages. sorry.
> It's not dependency, it is fallback relationship. If you set priority as A>B>C
> and some of them do not present, fontconfig will pick up the next one with the
> highest priority. I think that's how fontconfig was designed.
At least you should do as long as you expect them to get it working. otherwise
you just leave it to outside your rule.
If you have a dependency in the package, the referred font package owner or
that package owner can realizes any attentions is needed when something is
changed. you can prevent the font naming issue you've faced in wqy-bitmap-fonts
say.
> If you check my old posts, I used to be a supporter to font-specific config
> files, because I know the fonts I maintained are good, but other high priority
> fonts prevent the use of these good one but I have no control (for exp.
> 65-nonlatin). I endured a lot of troubles in order to set my own list. Now I am
> suggesting to get things right from the very beginning, and save time of the
> font maintainers. In you really want to insist, you can still do what you have
> been doing, but having a up-to-date default language-specific font list will
> greatly reduce the amount of work you need to do.
Yes, but what you are suggesting is actually the same thing what fontconfig
does because both are centralized management. why you feel it's comfortable is,
you're about to get an control of it. it's not necessarily a happy solution for
everyone.
--
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.
15 years
[Fedora-i18n-bugs] [Bug 476459] wqy-zenhei-fonts overrides Japanese desktop (so can't be installed by default in @chinese-support group)
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.
https://bugzilla.redhat.com/show_bug.cgi?id=476459
--- Comment #35 from Qianqian Fang <fangqq(a)gmail.com> 2009-05-12 10:43:46 EDT ---
(In reply to comment #34)
> It just works for your desired packages. but not for someone's. that's not a
> neutral solution.
But you do realize, in the end, there only exists one font order, no matter
which way you set it. It is impossible for two fonts to be both preferred if
they are both installed. If you want to control the orders by the presence of
fonts, you can do exactly the same thing with a centralized conf file. The only
difference is that a single config file gives you a master fallback list, and
what you suggested determines this list ad-hoc, which is more difficult to
predict and debug.
> we can suggest the default font in comps. but someone may not
> likes that. the centralized management for the rule would prevents to use the
> preferred font packages for users. I'm afraid you can't maintain/update it
> without painful for you and everyone nor without any notice from the font
> package maintainers.
>
>
> The point I'm saying is:
>
> * Do not make any changes that affects to the other font packages.
> -> this can be solved to apply the rule for the specific language.
IMHO, this is impossible. If you set <prefer> or use prepend/prepend_first, you
ARE affecting other font packages. Indeed, that's how fontconfig works. Again,
for a given system state, there is only one priority list for each language, no
matter you set it from a single file, or by a bunch of font-specific files.
>
> * Do not make any changes that depends on the other font packages. otherwise it
> must has certain dependencies in the package.
It's not dependency, it is fallback relationship. If you set priority as A>B>C
and some of them do not present, fontconfig will pick up the next one with the
highest priority. I think that's how fontconfig was designed.
>
> * Maintaining all of the font packages available on Fedora at the centralized
> fontconfig rule isn't realistic. as fontconfig is capable to read the rule from
> each fonts, maintaining it in each font packages with the certain policy would
> works enough.
If you check my old posts, I used to be a supporter to font-specific config
files, because I know the fonts I maintained are good, but other high priority
fonts prevent the use of these good one but I have no control (for exp.
65-nonlatin). I endured a lot of troubles in order to set my own list. Now I am
suggesting to get things right from the very beginning, and save time of the
font maintainers. In you really want to insist, you can still do what you have
been doing, but having a up-to-date default language-specific font list will
greatly reduce the amount of work you need to do.
>
> Right now some font packages doesn't follow even current policy. we have to
> mass-file a bug for them in F-12.
--
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.
15 years