> 3: Go to Select Input sources 
>   
> Actual results:
> List of input methods associated with Bengali language should appear
> 
> Expected results:
> Input method named "Indian" appears


Actual results:
Input method named "Indian" appears

Expected results:
List of input methods associated with Bengali language should appear

Can you add a screenshot?

Created attachment 748163 [details]
Input sources window shows indian as input sources

Screenshot also list itrans input method because i had installed this input method using g-i-s.Otherwise on a fresh installation g-i-s shows Indian as input source name.

This is a anaconda issue.

I assume "Indian" is the xkb India (in) layout.

I think missing IMEs is just bug 928645.

I am surprised itrans is listed while not inscript.

Parag??

Actually here the original problem is from Anaconda and not at all related to g-i-s. Yesterday I tried to look into this problem and found that anaconda's keyboard spoke class uses pyanaconda's keyboard.py which have all the functions for xkb layout list that uses wrapper for libxklavier.

In summary, Some logic is causing "Marathi" language to be mapped to "Indian" layout. Rest Indic languages uses correct keymaps.

(In reply to comment #5)
> I assume "Indian" is the xkb India (in) layout.

Yes.

> I am surprised itrans is listed while not inscript.

Anish added “itrans” manually (see comment#3).

(In reply to comment #6)
> In summary, Some logic is causing "Marathi" language to be mapped to
> "Indian" layout. Rest Indic languages uses correct keymaps.

Only Marathi?  And Bengali?(In reply to comment #7)

> (In reply to comment #5)
> Anish added “itrans” manually (see comment#3).

Ah right nod thanks - I was struggling to parse "installed".

I am pretty sure that the main IME part of this bug is just a duplicate of bug 928645 - so please test - except RC1 net install seems to backtrace for me currently.

Please file a separate bug against anaconda (or langtable)
if you see issues with the xkb layouts setup.

Jens,
  Finally got fresh f19 Beta TC4 installed. Here is what I did.

1) Used Marathi language in anaconda which picks "Indian" named keymap.
2) Installed Gnome Desktop Environment.
3) g-i-s started in Marathi
4) selected again Marathi language in g-i-s and finished its setup.

Observations on 4th step:- g-i-s when selected Marathi language, input sources step did not show default m17n keymap for Marathi but showed "English" and "Indian" keymaps.

So yes this can be duplicate of bug 928645. 

Now about this bug, using this setup tried to reproduce the bug using steps in comment#0
Choosing "Bengali" language did not show default Bengali m17n keymap (Which is again bug 928645), but it showed "English" and "Indian" which looks ok.

Rui says g-i-s should now setup IMEs (Input Sources) following
https://git.gnome.org/browse/gnome-desktop/tree/libgnome-desktop/default-input-sources.h .

> Choosing "Bengali" language did not show default Bengali m17n keymap (Which
> is again bug 928645), but it showed "English" and "Indian" which looks ok.

Bengali is used in India and Bangladesh, i think showing Indian option is wrong here

> Bengali is used in India and Bangladesh, i think showing Indian option is
> wrong here

The basic name (India) comes from xorg (xkeyboard-config)
and is then tranformed by gnome to Indian I think.
Defaulting to "India" keyboard is correct, but I don't
like the "friendly" change from India -> Indian
(US -> English, etc) - actually I would say again
it is wrong - but that is a separate issue/discussion
that is needed upstream.

I tested new Hindi user and got inscript IME defined by default by g-i-s.

*** This bug has been marked as a duplicate of bug 928645 ***

(In reply to comment #13)
> > Bengali is used in India and Bangladesh, i think showing Indian option is
> > wrong here
> 
> The basic name (India) comes from xorg (xkeyboard-config)
> and is then tranformed by gnome to Indian I think.

You can easily check Indian appears the moment you choose a Indic language where no xkb keymap is available for that language (Note I said language not script) in anaconda.

> Defaulting to "India" keyboard is correct, but I don't
> like the "friendly" change from India -> Indian
> (US -> English, etc) - actually I would say again
> it is wrong - but that is a separate issue/discussion
> that is needed upstream.

Right. This is not a g-i-s issue.

(In reply to comment #13)

> The basic name (India) comes from xorg (xkeyboard-config)
> and is then tranformed by gnome to Indian I think.
> Defaulting to "India" keyboard is correct, but I don't
> like the "friendly" change from India -> Indian
> (US -> English, etc) - actually I would say again
> it is wrong - but that is a separate issue/discussion
> that is needed upstream.

No, “Indian” is already in xkeyboard-config:

$ grep -C 5 Indian /usr/share/X11/xkb/rules/evdev.xml 
    <layout>
      <configItem>
        <name>in</name>
        
        <shortDescription>in</shortDescription>
        <description>Indian</description>
      </configItem>
      <variantList>
        <variant>
          <configItem>
            <name>ben</name>