![]() ![]() One of the problems, beyond those you mentioned, is that the Indian national body responsible for ISCII, although it is a member of ISO, does not send representatives to the ISO 10646 (Universal Character Set) meetings. In the meanwhile, let the keyboard remain a keyboard - a simple reliable mechanism to enter Unicode values, nothing more and nothing less.Īs I mentioned, there has been some discussion of additional Vedic characters in the Unicode mailing list this week. ![]() I would not be surprised to see several of them appear in the future. All the hooks are there, and most applications that are tageting international markets do support IMEs. It may be a good idea to create an IME for Devanagari and other Indian languages. Each IME has many different modes of input (phonetic, alphabetic etc.) and it may be very intelligent in its choice of the final sequence of Unicode characters based on user's input. This functionality is generally attributed to IMEs (Input Method Editors) which are common for many Asian languages. The truth however is that kind of compilcated processing is outside of what is normally called a "keyboard". ![]() the "Desha" keyboard generates the halant automatically after every consonant and makes you "kill" it by typing the vowel A). Krishna's posposal is different from the others I've seen (e.g. I have seen several proposals for "intelligent" keyboards (that is, keyboards that generate a sequence of characters quite defferent from what has been typed, depending on context). I have no hope that these observations will be implemented by MSFT, but am hoping that they stimulate further discussion on keyboard design on this forum. This mapping will be facilitated by using logic (a) and getting rid of most of matra-markers from the keyboard. Since any user of Indian fonts will almost certainly also use English fonts, it will be easy for the user if he can intutively locate non-English chars in iso-sounding locations. While managing this logic, the text shaping engine can create appropriate unicode context to satisfy the unicode standard.ī) It will be easy for users to map the Indian chars to iso-sounding char locations on the (almost) universally used QWERTY keyboard. You can make use halanth as this delinker. So, you have to delink the context by a delinking symbol. #Fontlab studio symbol font free#Rule 2: At times it is necessary to break rule 1, if you want to type a free standing vowel after a consonant. Since short a is already included within the definition of the consonant, this rule does not apply to short a following a consonant. Rule1: Any consonant immediately followed by a vowel results in a vowel-marked consonant form. The matra creation without these sybols can be managed by the following rules: The requirement to have them comes from type-writer days, which is not needed in the computer era. By doing so, you gain lots of slots on the keyboard. Most of these, except Anuswara, Chandrabindu,Visarga, Avgraha can be done away with. My observations on this layout are as follows:Ī) On the keyboard, you don't need the vowel-markers (or matra-symbols). My intention is not to criticise Microsoft or anyone else, but to put forth some ideas for discussion. ![]() I have looked at the keyboard map so kindly referred to me by Abdul, and I am disappointed with the layout. I think any implementation of Devanagari is incomplete unless all the symbols/chars needed for vedic text composition are included. Thanks for all replies you have provided to my 3 questions. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |