क्या आप के साथ कभी ये हुआ है?
- आपने दूसरे प्रांत के व्यक्ति से बात करते समय कोई अर्थ के लिये उचित इंग्लिश/हिन्दी शब्द याद नही आने पर ये कहा है 'हम तो इसे ये कहेते है' और जवाब में उसने कहा हो 'मेरी भाषा में भी यही शब्द प्रयोग होता है'.
- आप भारत के ऐसे राज्य में हो जहां की भाषा आप के लिए 'काले अक्षर भेंस बराबर' हो, आसपास के लोग क्या बोल रहे है कुछ समझ नही पा रहे हो पर उसी भाषा में जब आकाशवाणी समाचार सुनते हो तो बहोत मात्रा में उसे समझ पाये हो?
- आपने कभी अन्य भारतीय भाषा के कोइ नये शब्द को प्रथम बार सुनने पर भी उसका अर्थ सहज ही जान लिया हो?
तो आप ने भारतवर्ष के कितने ही दूर के व्यक्तिओं के बिच की स्वाभाविक निकटता को अनुभव किया है.
बहुश्रुता देवनागरी यही निकटता को अनावृत्त करने की दिशा में एक प्रयास है.
बहुश्रुता देवनागरी एक font है जो भारत की अन्य भाषा को देवनागरी लिपि में दिखायेगा. जैसे, यह tweet जो बंगाली में है पर बहुश्रुता के उपयोग से देवनागरी में पढ़ा जा सकता है.
अगर आप बंगाली बिलकुल नहीं जानते है तो क्या आपने कल्पना की थी के आप इस tweet के इतने सारे शब्द समझ पायेंगे?
ऐसे ही ये
सब भाषाएँ इतनी सरल न भी लगे तो जो अन्य भाषा सिखने का प्रयास कर रहा है उसके लिये यह देवनागरी में निरूपण लाभदायी हो सकता है ऐसी मेरी आशा है.
और हां, आप सरलता से अन्य लिपि में लिख भी सकते है. बस गूगल इनपुट टूल्स में भाषा चुनिए और लिखिये - वह दिखेगा देवनागरी में पर लिखा जायेगा चुनी हुई भाषा में. जैसे मैंने बहुश्रुता के twitter account के profile header में भारत लिखा है.
अन्य लिपि को देवनागरी में परिवर्तित करते समय कुछ त्रुटियां रहेती है जो इस समय दूर नहीं हो सकती। जैसे की कुछ लिपिओं की ह्रस्व इ की मात्रा आगे दिखाना संभव नहीं है तो उनके लिए वो पीछे ही दिखायी गयी है हलाकि उसे दीर्घ इ से अलग दिखाया गया है।
बहुश्रुता देवनागरी के कुछ अन्य उदाहरण आप यहां देख सकते है।
https://twitter.com/bahushrutaFonts/status/1195621927835987968
-----------------------------------
बहुश्रुता का उपयोग कैसे करें?(for desktop, chrome/IE)
-----------------------------------
-----------------------------------
- यहाँ से ttf फाइल डाउनलोड करे:
- font download (right click -> save link as) और install करें
- in chrome -> settings -> appearance -> select bahushruta devanagari for standard and sans serif
- For internet explorer, go to Tools, Internet options, Fonts on General Tab.
If you are updating to newer version,
Close all instances of browser (or remove Bahushruta from fonts settings) before installing new file.
if newer version is installed while older still in use (browser open), change will take effect only after computer restart.
और जानकारी या प्रश्न के लिये https://twitter.com/bahushrutaFonts/ पे जा सकते है।
How I happened to do this?
- For internet explorer, go to Tools, Internet options, Fonts on General Tab.
If you are updating to newer version,
Close all instances of browser (or remove Bahushruta from fonts settings) before installing new file.
if newer version is installed while older still in use (browser open), change will take effect only after computer restart.
और जानकारी या प्रश्न के लिये https://twitter.com/bahushrutaFonts/ पे जा सकते है।
How I happened to do this?
its here. https://ekakinchan.blogspot.com/2019/10/bahushruta-devanagari.html
----------------------------------------
Notes for technically oriented people or for those who want to understand better how lipi barrier can be removed more effectively.
Note 1: Easier / less resistance step may be
Its kind of tragic that to read our scripts interchangeably, we need to make such efforts when it could be done very easily if reading one script in another was not BLOCKED. yes, you read it right. what is needed is removal of block and not additional feature per se. (okay, strictly in technical sense, it cannot be proved a block, but its still more like it).
Let me explain.
Fonts work like this.
i) They take in ISO codes,
ii) apply rules of script display (decide if matra comes before, after, above, below etc),
iii) apply symbols assigned to ISO codes
iv) apply rules to customise / manipulate actual display based on sequence of ISO codes. (say, if क् is followed by श र or क respectively, display will be क्ष क्र क्क.)
and display.
Now a font developer has control over iii) and iv) only. and ii) is pre-specified (at OS level?) and font developer's choice is restricted. It automatically assumes which rules can be allowed based on ISO block, and restricts its assumption to only one set of rules. i.e. you can ask for application of devanagari script rule only on devanagari ISO block. Only if such restriction is lifted and if we can ask for devanagari script rule to be applied on say Malayalam, Gujarati or Bengali ISO block, most of the work (and all of the unsolvable problems) go away.
Note 2: Unifying ISO blocks - seeing varnas for what they are - uchharan and not as language units.
Probably in most non Indic languages people dont speak what they read which messes up things quite a lot. But for us, Language is association between शब्द and अर्थ while lipi is association between वर्ण / वर्ण शृङ्खला and written symbol. Which means that अ, ਅ, અ, অ, ଅ, അ, ಅ, అ all are symbols for same varn in different lipi and it has NOTHING to do with language (in current ISO system, they all are different entities). Now, because what symbol to use is anyway supplied from font file, role of ISO code is only to convey वर्ण शृङ्खला. We therefore actually need only ONE BLOCK of ISO codes ACROSS all Indic languages. Display lipi can be decided by input user's intended lipi (default) or reader's preferred lipi (override).
This would conceptually and practically simplify things greatly and also do away with a whole lot of ISO codes and would greatly reduced work for everyone. Though I am not hopeful of we having such a simple solution - for, we are not आत्मनिर्भर in any technical aspect..
----------------------------------------
Notes for technically oriented people or for those who want to understand better how lipi barrier can be removed more effectively.
Note 1: Easier / less resistance step may be
Its kind of tragic that to read our scripts interchangeably, we need to make such efforts when it could be done very easily if reading one script in another was not BLOCKED. yes, you read it right. what is needed is removal of block and not additional feature per se. (okay, strictly in technical sense, it cannot be proved a block, but its still more like it).
Let me explain.
Fonts work like this.
i) They take in ISO codes,
ii) apply rules of script display (decide if matra comes before, after, above, below etc),
iii) apply symbols assigned to ISO codes
iv) apply rules to customise / manipulate actual display based on sequence of ISO codes. (say, if क् is followed by श र or क respectively, display will be क्ष क्र क्क.)
and display.
Now a font developer has control over iii) and iv) only. and ii) is pre-specified (at OS level?) and font developer's choice is restricted. It automatically assumes which rules can be allowed based on ISO block, and restricts its assumption to only one set of rules. i.e. you can ask for application of devanagari script rule only on devanagari ISO block. Only if such restriction is lifted and if we can ask for devanagari script rule to be applied on say Malayalam, Gujarati or Bengali ISO block, most of the work (and all of the unsolvable problems) go away.
Note 2: Unifying ISO blocks - seeing varnas for what they are - uchharan and not as language units.
Probably in most non Indic languages people dont speak what they read which messes up things quite a lot. But for us, Language is association between शब्द and अर्थ while lipi is association between वर्ण / वर्ण शृङ्खला and written symbol. Which means that अ, ਅ, અ, অ, ଅ, അ, ಅ, అ all are symbols for same varn in different lipi and it has NOTHING to do with language (in current ISO system, they all are different entities). Now, because what symbol to use is anyway supplied from font file, role of ISO code is only to convey वर्ण शृङ्खला. We therefore actually need only ONE BLOCK of ISO codes ACROSS all Indic languages. Display lipi can be decided by input user's intended lipi (default) or reader's preferred lipi (override).
This would conceptually and practically simplify things greatly and also do away with a whole lot of ISO codes and would greatly reduced work for everyone. Though I am not hopeful of we having such a simple solution - for, we are not आत्मनिर्भर in any technical aspect..



