sankarshan said on Mon, Apr 09, 2012 at 06:40:04PM +0530,:
> On Mon, Apr 9, 2012 at 6:36 PM, Mahesh T. Pai <paiva...@yahoo.co.in> wrote:
>
> > This probably explains the fear expressed by some that satisfying this
> > particular
> > requirement will corrupt the Bangla script / Bengali language.
>
> I would request you to provide some links which have led you to the
> above conclusion.
If you are meaning "fear expressed by some ..." part, I am referring to
a mail by Mr. Das. (das at random ink dot com; mail dt. 8 April 2012,
20.07hrs)
Message-ID: <CABWwE-=ugc_ts+ctvtefk-qurqjyuaqmsione03pkvrakeh...@mail.gmail.com>
> Attempting to conflate two distinct character set
> code point ranges
> and thereafter demanding that this new character
> behave in a way that is completely orthogonal to the grammar of the
> language is not the only strange thing in this thread, but the fact
> that even after repeated instances of providing how the script - the
> printed script has evolved starting from Halhead's time, non-native
> speakers of the language on this list keep pondering about it is
> bizarre and curious.
I can understand this part; I repeat, I am not taking any stand here.
I merely point out that there _may_ be a legitimate need for better
clarity on the Bangla standards front _as_far_as_they_apply_to_
_transliteration_of_Sanskrit_ here.
What I do not understand is this phrase used by you:-
> Attempting to conflate two distinct character set
> code point ranges
I strongly suspect that Assamese uses the Bangla script.
(Unicode range 0980 - 09FF). Is not 09F0 and 09F1
part of this _script_ ? Should not the rendering
rules for this script be uniform for a given code
range? Or are rendering rules language dependent?
Or, rephrasing above, I understand that rendering rules are script
specific, not language specific. Please correct me if I am wrong.
As I get it, one of the first questions asked was why the ba-halant
is not rendering. (Swarup's mail on 30 March 12.) I first thought
this was merely a rendering issue; till I re-read Runa's mail; which
(coupled with the void at 09B3-5) points to an inadequacy in the Bangla
script (as defined in the Unicode standard) _for transcribing Sanskrit_.
Now, kindly refer to Runa's mail on 30 March (at 22.38 Hrs).
<quote>
,,,, 'Antastya ba'[1][2] does not have any representation in the Unicode charts
(because its use was discontinued ages ago and your scanned page also mentions
the same),
(snip)
[1] Please do not misrepresent this as 'ba'. There were historically two types
of 'ba' in Bengali (both represented with the same glyph): borgiyo ba i.e.
similar in pronunciation to the hindi ब and antastya ba i.e. similar in
pronunciation to the hindi व .
</quote>
What I gather so far is that
(a) onceupon a time, long, long ago, there was a character, described as
"antastya ba"
(b) Antastya ba is not same thing as the "ba" character currently in use
in Behgali..
(c) Swarup has has a need for antastya ba character _now_
(d) He is trying to create a PUA code for it.
Sanskrit is pretty ugly when it comes to pronounciation - there is zero
tolerance
for mis-pronounciation and mis spelling. Unlike the Bengali way of writing
"bilwa",
Sanskrit will not leave it to user's intelligence to distinguish the two
characters.
Hence, (to me), writers of Sanskrit creating a document in a non-devanagari
script
will introduce / cook up (if you can call it that) glyphs to represent
characters in
devanagari required to write Sanskrit in the alien script. Hence, I can
understand
Swarup's requirement in a sympathetic way.
Now a question to Swarup - if both antastya ba and ba were visually identical,
what is the justification for creating a new code for it now?
And finally, I really see no point in carrying this discussion further till
we get a <name of book> <author> <date of publication> <name of publisher>
details about the source of those scanned pages from Swarup.
--
Mahesh T. Pai ||
It's not the software that's free; it's you.
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
IndLinux-group mailing list
IndLinux-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/indlinux-group
