Apparently it doesn't have enough coverage to satisfy hi.orth.  Check hi.orth and check coverage on the font to see why.

(In reply to comment #1)
> Apparently it doesn't have enough coverage to satisfy hi.orth.  Check hi.orth
> and check coverage on the font to see why.
> 

2-line comment
1) I didn't get what this mean? whose issues is this font??
2) I see hi.orth is written with following lines and I can see all those unicode defined in madan.ttf
0905-0914       # Independent vowels
0915-0939       # Consonants
093f-094c       # Dependent vowel signs
094d            # virama

(In reply to comment #2)
> (In reply to comment #1)
> > Apparently it doesn't have enough coverage to satisfy hi.orth.  Check hi.orth
> > and check coverage on the font to see why.
> 
> 2-line comment

Stop this 1), 2) game.


> 1) I didn't get what this mean? whose issues is this font??
> 2) I see hi.orth is written with following lines and I can see all those
> unicode defined in madan.ttf
> 0905-0914       # Independent vowels
> 0915-0939       # Consonants
> 093f-094c       # Dependent vowel signs
> 094d            # virama

How did you check?  Using fontforge, I don't see 090C, 090D, or 090E.

(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > Apparently it doesn't have enough coverage to satisfy hi.orth.  Check hi.orth
> > > and check coverage on the font to see why.
> > 
> > 2-line comment
> 
> Stop this 1), 2) game.

Fine. I thought you have some problem in understanding Indic bug description and you love to see description written in point-wise.
I see you are the only one who can fix fontconfig as well as pango issues in upstream. And if we failed to convince you what fix we want then we may see forever problem with Indic rendering and I don't think we can get any benefit in HarfBuzz project.

> 
> 
> > 1) I didn't get what this mean? whose issues is this font??
> > 2) I see hi.orth is written with following lines and I can see all those
> > unicode defined in madan.ttf
> > 0905-0914       # Independent vowels
> > 0915-0939       # Consonants
> > 093f-094c       # Dependent vowel signs
> > 094d            # virama
> 
> How did you check?  Using fontforge, I don't see 090C, 090D, or 090E.
> 
Yes fontforge. Ok, So my eyes missed these 3 glyphs. I am sorry for that. I will check this with its language community and if needed will report new bug to get ne.orth get fixed.

(In reply to comment #4)

> > Stop this 1), 2) game.
> 
> Fine. I thought you have some problem in understanding Indic bug description
> and you love to see description written in point-wise.

I only brought it up in one particular bug that I failed to understand the problem consistently.


> I see you are the only one who can fix fontconfig as well as pango issues in
> upstream. And if we failed to convince you what fix we want then we may see
> forever problem with Indic rendering and I don't think we can get any benefit
> in HarfBuzz project.

Yes, unfortunately I'm the only one hacking on these.  It doesn't help that my knowledge of Indic is zero.  In the past, I had blindly committed patches coming in from Indic users and Red Hat i18n team.  However, that practice proved to introduce more bugs than it fixed.  For that reason, I'm not committing any Indic patches to Pango anymore until we get a test suite.  That's why the best course of action right now is to make sure the HarfBuzz Indic test suite initiative takes off and create a comprehensive test suite.

> > > 1) I didn't get what this mean? whose issues is this font??
> > > 2) I see hi.orth is written with following lines and I can see all those
> > > unicode defined in madan.ttf
> > > 0905-0914       # Independent vowels
> > > 0915-0939       # Consonants
> > > 093f-094c       # Dependent vowel signs
> > > 094d            # virama
> > 
> > How did you check?  Using fontforge, I don't see 090C, 090D, or 090E.
> > 
> Yes fontforge. Ok, So my eyes missed these 3 glyphs. I am sorry for that. I
> will check this with its language community and if needed will report new bug
> to get ne.orth get fixed.

Thanks.

Behdad,
  I got confirmation from Nepali community that those 3 characters should not be part of ortho file. I also got ods sheet for Nepali character set. and one more reference http://www.panl10n.net/english/Outputs%20Phase%202/CCs/Nepal/MPP/Papers/2007/0702/mpp_reports_pdf/report_character_encoding_constraints_nepali.pdf

I will create new bugzilla entry for this issue. But I got one question here. fc-query failed here because font glyph set and ortho file mismatched( less glyphs in Madan font than ortho file mentioned). But what will happen if font contains more glyphs(reverse scenario what we see for Madan) than any ortho file? I mean ortho contains subset of any font file glyphs. Will that ortho language name will get extracted for that font?

Open a new bug please.

(In reply to comment #7)
> Open a new bug please.
> 

For question I asked that also? so total 2 bugs?

The orth file is the minimum coverage.  If there are more characters/glyphs, that's ok.

(In reply to comment #9)
> The orth file is the minimum coverage.  If there are more characters/glyphs,
> that's ok.
> 

Thanks for your reply. I have reported new bug for fixing ortho file at http://bugs.freedesktop.org/show_bug.cgi?id=24729