[Fedora-i18n-bugs] [Bug 476871] GDM uses wrong keyboard layout after switching back
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=476871
--- Comment #13 from fujiwara <tfujiwar(a)redhat.com> 2009-10-05 21:10:26 EDT ---
(In reply to comment #12)
> You don't want to always send GDM_KEYBOARD_LAYOUT because then the users choice
> from within the session (from gnome-keyboard-properties) would get ignored.
Is it the implementation for gnome-settings-daemon instead of GDM?
My concern is that GDM cannot get the current user's layout without gconfd but
if GDM calls user's gconfd to check the user's layout, it would be possible
double gconfd, one is from GDM and another is from gnome-session.
If GDM always send GDM_KEYBOARD_LAYOUT, gnome-settings-daemon could implement
if it uses the enviroment or get the value from gconf value.
--
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.
14 years, 6 months
[Fedora-i18n-bugs] [Bug 526633] Review Request: gargi-fonts - A Devanagari font
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=526633
Ankur Sinha <sanjay.ankur(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flag|needinfo?(sanjay.ankur@gmai |
|l.com) |
--- Comment #7 from Ankur Sinha <sanjay.ankur(a)gmail.com> 2009-10-05 09:11:41 EDT ---
(In reply to comment #3)
> Anyway, thanks a lot for adding a new font package in the review pipe
>
> Appart from the CSS classification I can't really help you with, here is some
> review:
>
> 1. non LGC font ⇒ please use a priority ≥ 65 as per fontconfig-priorities.txt
>
I'll check up the prio for the lohit font and fix this..
> 3. Licensing should be GPLv2+
Fixed. Will upload a new build in a day max.
>
> 4. (non blocking) please ask upstream to add the standard FSF GPL font
> exception to their licensing
Contacted upstream, no response yet :(
>
> 5. (non blocking) description could use some meat
I copied whatever I got from the font homepage. There's no readme etc to get
more from.
> Anyway, this package is mostly fine, except for the classification problem.
>
> NEEDINFO till this is resolved
(In reply to comment #6)
> Ankur, please use Sans as classification and I'll approve the package (if you
> fixed the other bits. Also, please make sure your fontconfig prio is > Lohit
> Devanagari so Lohit stays the default
Okay, ill fix up the fontconfig. I cant do much about some of the other bits
(stated above)
regards,
Ankur
--
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.
14 years, 6 months
[Fedora-i18n-bugs] [Bug 526633] Review Request: gargi-fonts - A Devanagari font
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=526633
--- Comment #5 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> 2009-10-05 07:13:19 EDT ---
(In reply to comment #4)
> (In reply to comment #3)
> > 2. please ask the lohit people what they think about this font. IMHO it is
> > highly likely one of the lohit fonts shares a common ancestry with gargi (and
> > in that case they should at least cross-alias each other)
>
> while comparing lohit devanagari script fonts (marathi, hindi, konkani, nepali,
> sindhi and kashmiri)
>
> There are little bit differences in lohit and Gargi
> i.e Gargi fonts shape are little more Bold compare to lohit,
> space of gargi is more than lohit
> there are also little bit differences in characters shape
Ok, that means that they probably were not forked from a common root after all,
so no need to cross-alias
> but overall as said above yes, they share common style(Sans) and ancestry.
>
> between how corss-alias will work?
cross-alias is when package B tells fontconfig : if app asks for font A, and it
is not present, use my font B instead (and the reverse in package A). We do it
for DejaVuLGC/DejaVu for example. But this kind of aliasing is only worth it
when fonts are very close in style or metrics, typically when two projects took
the same origin font and froked it in different ways
--
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.
14 years, 6 months
[Fedora-i18n-bugs] [Bug 526633] Review Request: gargi-fonts - A Devanagari font
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=526633
--- Comment #4 from Pravin Satpute <psatpute(a)redhat.com> 2009-10-05 06:55:16 EDT ---
(In reply to comment #3)
> 2. please ask the lohit people what they think about this font. IMHO it is
> highly likely one of the lohit fonts shares a common ancestry with gargi (and
> in that case they should at least cross-alias each other)
while comparing lohit devanagari script fonts (marathi, hindi, konkani, nepali,
sindhi and kashmiri)
There are little bit differences in lohit and Gargi
i.e Gargi fonts shape are little more Bold compare to lohit,
space of gargi is more than lohit
there are also little bit differences in characters shape
but overall as said above yes, they share common style(Sans) and ancestry.
between how corss-alias will work?
--
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.
14 years, 6 months
[Fedora-i18n-bugs] [Bug 504270] New: [Fonts-Indic][te_IN] - GSUB shape with SSA and HA are wrong.
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: [Fonts-Indic][te_IN] - GSUB shape with SSA and HA are wrong.
https://bugzilla.redhat.com/show_bug.cgi?id=504270
Summary: [Fonts-Indic][te_IN] - GSUB shape with SSA and HA are
wrong.
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: fonts-indic
AssignedTo: rbhalera(a)redhat.com
ReportedBy: smaitra(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: smaitra(a)redhat.com, rbhalera(a)redhat.com,
fedora-fonts-bugs-list(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
GSUB shape with SSA (0C37) and HA (0C39) is showing wrong in the font.
Its positioning for the lower part of the composed character, should be
below-right aligned which is now aligned as below-middle.
As of now The Image that is given to our Internal web page, is hand drawn and
partly wrong also. But, the lower part alignment is Perfect there which is
showing right-aligned.
These specific Combinations are given below :
68. U+0C24 U+0C4D U+0C37 త్ష TA + HALANT + SSA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
70. U+0C24 U+0C4D U+0C39 త్హ TA + HALANT + HA => In image main character must
be corrected as in font and in font the position of sub character(which is at
the bottom) should be corrected as in image.
103. U+0C28 U+0C4D U+0C37 న్ష NA + HALANT + SSA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
105. U+0C28 U+0C4D U+0C39 న్హ NA + HALANT + HA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
140. U+0C2E U+0C4D U+0C39 మ్హ MA + HALANT + HA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
175. U+0C2F U+0C4D U+0C39 య్హ YA + HALANT + HA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
208. U+0C30 U+0C4D U+0C37 ర్ష RA + HALANT + SSA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
210. U+0C30 U+0C4D U+0C39 ర్హ RA + HALANT + HA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
243. U+0C32 U+0C4D U+0C37 ల్ష LA + HALANT + SSA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
245. U+0C32 U+0C4D U+0C39 ల్హ LA + HALANT + HA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
278. U+0C35 U+0C4D U+0C37 వ్ష VA + HALANT + SSA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
280. U+0C35 U+0C4D U+0C39 వ్హ VA + HALANT + HA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
Version-Release number of selected component (if applicable):
lohit-telugu-fonts-2.3.8-1.fc11
How reproducible:
Always
Steps to Reproduce:
1. Start system with FC11 or Latest
2. Change the ibus with RAWCODE
3. Open Gedit
4. Type the combination's Unicode as given above.
5. Observe the lower part of the composed character.
Actual results:
Its showing below-middle alignment.
Expected results:
It should be below-right alignment.
Additional info:
--
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.
14 years, 6 months