Extension talk:Narayam/archive

I, didn't find typing tools (script) in Nepali. Would you manage from this-Bhawani Gautam 01:50, 12 June 2011 (UTC)
 * Done --Junaidpv 19:00, 22 July 2011 (UTC)

Changes for Nepali Extension in Inscript
Hello everyone, Thanks for the nice extension. There are few changes in Nepali though. The "V" in Nepali should be "भ" instead of "व". People write investment as इन्भेष्टमेन्ट rather than इन्वेष्टमेन्ट so they expect "भ" sound for "V". The keyboard implemented there is more like a standard keyboard that is used in Nepali. It would be really nice if you could incorporate the keyboard layout that is listed here here.

It would be nice if we could have "a traditional" keyboard and a "romanized" keyboard. The romanized keyboard is more or less already available except that the V needs to be changed. The website has both the keyboards listed as "romanized" and the "traditional" keyboard. Most people used to use the traditional keyboard in the past. The younger generation like the "romanized" because its easy to write in English and they don't have to learn the Nepali keyboard which they call it the traditional keyboard layout. Inscript is used in India whereas "Traditional" used to be used in Nepal.

Thanks.
 * Rajesh Pandey
 * --RajeshPandey 17:51, 20 August 2011 (UTC)


 * So, you says 'v' should be mapped to 'भ' but the website you pointed out also mapped to 'व'! What should be the name when I add your 'traditional' keyboard to Narayam, like we say 'InScript'?


 * Please also give feedback if any. Thanks --Junaidpv 20:19, 12 September 2011 (UTC)
 * Hi, The keyboard layout should be called as : Nepali Traditional Keyboard Layout and Nepali Romanized Keyboard Layout.
 * 'v' should be 'भ' but I don't want to argue about it. That's okay if we could have Nepali Traditional Keyboard Layout. I have enabled 'भ' for 'v' in Nepali Wikipedia. Its a typo and officially people write इनभेष्टमेन्ट for Investment For example this is the website of an investment bank and भिषा is Visa. Example:  where they talk about Visa and Mastercards. So v is pronounced as 'भ' in Nepali. Virus is भाइरस and Violet is भायोलेट। व is W in Nepali and they make a clear distinction between 'v' and 'w' while pronouncing. 'v' is pronounced by biting or touching the lips and forcing the air out, w is not. W is pronounced by releasing air while the mouth is round. Thanks --RajeshPandey 20:37, 12 September 2011 (UTC)


 * OK, I have updated romanized version according to Nepali wikipedia: r96943. The update will be effective within one day on translatewiki.net, you can test it there.
 * Can you give the link that will be useful for me to create traditional layout? I think this site can be used also. --Junaidpv 06:51, 13 September 2011 (UTC)
 * Traditional Screenshot
 * Traditional
 * Software Download link for Traditional Keyboard
 * Nepali Sabdakosh You can also click on "किवोर्ड देखाउ" button for both traditional and Romanized. There are buttons on ट्रेडिसनल and रोमनाइज्ड on that page. You will have to play around the keyboard for a while. Or I can send you some screenshots if you want.
 * A lot of images will come in google image search Click to Search for Nepali traditional keyboard layout--RajeshPandey 10:03, 14 September 2011 (UTC)

Enable by Default for everyone
For my site, i wished to enable Narayam for hindi for everyone, including those whose language is set to hindi. Unfortunately, this is not an option so far, but i changed the following to get the effect:::

in Narayam.hooks.php replace >> $userlangCode = $wgLang->getCode; << with >> $userlangCode = 'hi'; <<

Hope this becomes a option in the next release.


 * A configuration option, $wgNarayamAlwaysLoadForLanguages, has been added for this purpose.
 * You can put this line to LocalSettings.php to always load Hindi typing schemes. --Junaidpv 17:24, 8 October 2011 (UTC)

-- did not realize there is no transliteration for hindi yet? or is there one i can use? Thanks!!!

Hindi Transliteration
Hi,

Is there a Hindi transliteration in the works/available? Thanks!!

Amharic language available?
Hello there, can someone develop or show us how to make up the scheme to develop transliteration for Amharic language?
 * Do you get any clue by reading Extension:Narayam? Or should we develop one for you? If you have any other tools that can be used for this purpose please let us know. --Junaidpv 06:47, 8 October 2011 (UTC)
 * Fast response, I saw the description but I didn't understand it. If its not too much to ask, it'd be great to see how it works and I will troubleshoot for you on any improvement can be done. Here is a website that has an amharic input settings Amharic Input Amharic Input 2, I'm not sure how else i can help.
 * Thanks for the link. I will take the first link as model for implementation. Once I developed it, I will inform you. You can test it then. You can email me if you want. Also I am available at IRC channel (irc.freenode.net) #mediawiki and my IRC nick name is Junaidpv. --Junaidpv 07:04, 8 October 2011 (UTC)

Gadgets Support
Will this extension add support for various gadgets used in the WMF wikis which require text input, like HotCat for instance? Or Twinkle? Or will input support for these gadgets require separate scripts? Thanks.--Siddhartha Ghai 14:00, 6 November 2011 (UTC)


 * Yes, it supports gadgets like HotCat. You can verify it at http://translatewiki.net.--Junaidpv 14:12, 6 November 2011 (UTC)


 * What about Twinkle, which uses a jquery dialog with(I think) HTML forms in it? And basically any gadgets that don't use the MW interface(are there others?). Thanks again.--Siddhartha Ghai 22:53, 6 November 2011 (UTC)


 * It works in XFD atleast. Some part of twinkle use Browser's native input box rather than created with JavaScript/HTML, that Narayam can do nothing, so Narayam will be inactive. Narayam is designed to work with all input boxes within HTML of the page. --Junaidpv 03:48, 7 November 2011 (UTC)

Amir's November 2011 Narayam brain dump
Hi,

After the successful trip to India and learning a lot about the Indic scripts, i made more fixes to the Gujarati phonetic Narayam mapping. (Tests and reviews are welcome.)

While doing it i realized that more structure may be needed in developing these keymaps. First, some facts and assumptions (i'm not completely sure which is which):


 * 1) Most scripts of India, as well as many scripts of South-East Asia, Indonesia and Philippines share a very similar structure. The shapes of the letters are different and the characters are encoded separately in Unicode, but the basic ideas of inherent vowels, virama, phonetic order (ka kha ga gha nga etc.), separate characters for initial and medial vowels, unusual behavior of the character that represents the sound of /r/, etc. are similar. (For details see https://en.wikipedia.org/wiki/Brahmic_family_of_alphabets ).
 * 2) The Indian standard InScript keyboard tries to map the keys similarly in all the scripts of India according to this structure.
 * 3) Some of these scripts are used to write several languages - for example, the Devanagari script is used for Hindi, Marathi, Sanskrit and other languages; the Burmese script is used to write Burmese, Mon, Shan and other languages etc.
 * 4) The same script can be used slightly differently in different languages. For example, Devanagari is used differently in Hindi, Marathi, Sanskrit and Nepali. (This happens in many other scripts, too - Cyrillic is used differently in Russian and Ukrainian.)
 * 5) The main problem with the Gujarati keyboard as it was submitted to us was the confusion between Devanagari virama and the Gujarati virama. They have similar appearance and function and probably the creator of the mapping thought that it's the same character.
 * 6) Some of the changes that the Marathi speakers made to the Hindi transliteration keymap to adapt it to their language are probably useful for Hindi, too.
 * 7) A lot of people that write in the languages that use these scripts would probably love to use a phonetic keymap, although i don't know how many exactly.
 * 8) C-DAC, Red Hat and Google have created phonetic typing schemes.

Now, some ideas about what we can do about it. They are very half-baked and possibly silly; it is also quite hard to put them in writing and it would be better to discuss them in person, but i prefer not to wait until the next time it happens.


 * 1) A phonetic keyboard for different language versions of the same script (e.g. Devanagari-Hindi and Devanagari-Marathi) should be based as much as possible on one copy of the code. (Code reuse FTW.)
 * 2) It can be something like an object-oriented approach. For example, there would be a parent Devanagari class that implements the common functionality from which different schemes for different languages inherit (Hindi, Marathi etc.). The same for the Bengali script, from which Bengali and Assamese would inherit, etc. And maybe there can also be a parent Brahmi class from which Devanagari, Bengali, Malayalam etc. would inherit, replacing the needed characters according to Unicode range. Unfortunately, i'm not sure that it would actually be easy to implement in JavaScript.
 * 3) This approach, if at all feasible, can also be useful for completely different script systems - Arabic, Cyrillic, Latin etc.
 * 4) The schemes must be based as much as possible on C-DAC, Red Hat and Google mappings, unless they are really bad. Is it possible at all to get the mappings for C-DAC and Google or is it only possible to reverse-engineer them?
 * 5) I don't have much to say about InScript, because as far as i understand, an InScript mapping is easier to implement than a transliteration mapping, and my feeling is that transliteration mappings are in higher demand, as much as we want to love InScript.

That's it, more or less. Any ideas about this are welcome. --Amir E. Aharoni 23:04, 28 November 2011 (UTC)