Last modified: 2012-08-22 10:39:36 UTC
follow up to bug 33603 The actual bug probably is Narayam seems to discriminate on English where in I cant see narayam on a wiki whose language is English with interface language as English. This is partly acceptable within WMF wikis where most folks in commons, mediawiki wont want narayam enabled by default, But for a generic multilingual wiki this is a bug. Ideally on mediawiki, commons, meta (and similar non-lang specific WMF wikis) narayam must be enabled with a default "enable input method" preference as false and work even on english interface if someone goes and changes the preference to true. Scenario 1: Set Enable input method as true on preferences on mediawiki/commons while using English interface. Even though the preference is set to true,one doesnt get IMEs visible. Scenario 2: Open Oriya WebFonts Help page (URL), while WebFonts loads on the page, Narayam doesnt load even Enable input method is set to true if am having en as interface language. Should Narayam also detect page's lang attribute and load the related IME's?
(In reply to comment #0) > Scenario 1: Set Enable input method as true on preferences on mediawiki/commons > while using English interface. Even though the preference is set to true,one > doesnt get IMEs visible. This is because English does not have any input methods in Narayam. > Scenario 2: Open Oriya WebFonts Help page (URL), while WebFonts loads on the > page, Narayam doesnt load even Enable input method is set to true if am having > en as interface language. Should Narayam also detect page's lang attribute and > load the related IME's? For the help page, to edit it, you need to use the edit link, that takes you to an edit page where edit area disabled and link to Translate extension. There is no need of Input tool in or in these pages. While using Translate page, you need the tool, but since interface language and content language is English , you are not getting it. I think this is an accepted workflow. If we are going to detect lang tags in a page, and load IMEs for them, it is going to be a big list. Not all of them will be even editable elements. We do detect lang attribute of text areas and load input tools in Multi lingual wiki like WMF Incubator. You won't see input tool in a page, but you will see the tool in edit page, if the content we are editing is tagged with a lang attribute we support. Have a try. With the current UI, I don't think this is a bug. But may be an input to the design spec of Universal language selector. And if you think this is something we need to mention in the user documentation of Translate extension or Narayam webfonts, please help at https://www.mediawiki.org/wiki/Help:Extension:Narayam or https://www.mediawiki.org/wiki/Help:Extension:Translate Thanks
(In reply to comment #1) > (In reply to comment #0) > > Scenario 1: Set Enable input method as true on preferences on mediawiki/commons > > while using English interface. Even though the preference is set to true,one > > doesnt get IMEs visible. > > This is because English does not have any input methods in Narayam. There is some inconsistency here. Going by the same logic, Tamil wiki must have only Tamil IME option in Narayam. The point of Narayam being enabled is not just to type on the particular language(or so I was told), but on all languages supported by narayam. Am not saying Narayam must default on English language wiki's (while it does it (and have to) on language wikis). But when one goes ahead and enables narayam in the user preference on a English language wiki without English interface, Narayam must come up.
>English language wiki without English interface must be read as English language wiki with English interface
Updated summary to reflect feature request. On hold whole developing the universal language selector. We don't want the relatively ugly UI element in all languages.
https://www.mediawiki.org/wiki/Extension_talk:Narayam#Enabling_Narayam_.2F_WebFonts Needs discussion there since it covers most cases(to my knowledge) and we could come back here with the solution.
Closing as this will be fixed in ULS and Narayam will be deprecated.
