indic-computing-standards Mailing List for The Indic-Computing Project (Page 2)
Status: Alpha
Brought to you by:
jkoshy
Menu
▾
▴
indic-computing-standards — Discussing standards governing information processing in Indian languages
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(7) |
Feb
(16) |
Mar
(20) |
Apr
(52) |
May
(8) |
Jun
|
Jul
(35) |
Aug
(20) |
Sep
(2) |
Oct
(4) |
Nov
(16) |
Dec
(1) |
| 2003 |
Jan
(9) |
Feb
(1) |
Mar
(1) |
Apr
|
May
(9) |
Jun
(6) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2004 |
Jan
(4) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
(1) |
Nov
(5) |
Dec
(1) |
| 2008 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <pra...@ya...> - 2003-06-08 09:30:56
|
A good no. of Glossaries & previously done translations are available here: http://kannada.sourceforge.net You need nudi font for the kgp glossary & opentype font for the gnome glossary. -pramod. ________________________________________________________________________ Missed your favourite TV serial last night? Try the new, Yahoo! TV. visit http://in.tv.yahoo.com |
|
From: <tbd...@se...> - 2003-06-07 07:10:38
|
Dear change makers=2E=2E :) We are looking for appropriate terms and phrases for the commonly used computer related phrases, in Kannada=2E If you know of any available phrase maps, or have lists you use, please help by publishing or making it avaiable to others/us=2E=20 For example, what is an understandable, acceptable "translation" (phrase to use in Kannada) for these: download file upload file post a message send a message respond remark or comment view domain category category tree community path browse search search criteria logical operators keywords user id sign in log in sign out log out cancel register password log sitemap accesslevel help editor owner author comma separated values database=20 table field template terms and conditions open source indic=20 website webpage internet world wide web files attachments MB GB Mhz GHz etc=2E=2E thanks for any pointers and converging discussions :) d=2E dinesh@servelots=2Ecom +91 80 6762963=20 -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web=2Ecom/ =2E |
|
From: Dr. U.B. P. <pav...@vi...> - 2003-06-07 03:18:57
|
<?xml version="1.0" ?><html> <head> <title></title> </head> <body> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">From VOLT Discussion group (http://groups.msn.com/MicrosoftVOLTuserscommunity/)</span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">-Pavanaja</span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">-----------------------</span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">From Paul Nelson, Microsoft Typography:</span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">I have completed some minor adjustments to the USP10 to correct Bengali functionality and will be sending it to people to beta test as soon as I finish verifying some conjunct forms for the Vrinda font. </span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">If anyone is interested in participating with a private beta of Bengali, please send mail to me directly. </span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">Please note that the behavior set out in Unicode 4.0 defines a requirement to get the reph form by typing: Ra + halant + ZWJ as the first part of the cluster. </span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">Paul</span></font></p> <div align="left"><font face="Times New Roman" size="3"><span style="font-size:12pt">-----------------------------------------------------</span></font></div> <div align="left"><font face="Times New Roman" size="3"><span style="font-size:12pt">Dr. U.B. Pavanaja</span></font></div> <div align="left"><font face="Times New Roman" size="3"><span style="font-size:12pt">Editor, Vishva Kannada</span></font></div> <div align="left"><font face="Times New Roman" size="3"><span style="font-size:12pt">World's first Internet magazine in Kannada</span></font></div> <div align="left"><font face="Times New Roman" size="3"><span style="font-size:12pt">http://www.vishvakannada.com/</span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Times New Roman" size="3"><span style="font-size:12pt">Note: I don't worry about pselling mixtakes</span></font></div> <div align="left"></div> </body> </html> |
|
From: <a_j...@ya...> - 2003-06-02 02:04:10
|
Dear -standards folk, I've put up a tentative list of the information about Indic scripts and languages that we are proposing to document in the Handbook. These lists need review. They can be found at: http://indic-computing.sourceforge.net/handbook/scriptinformation.html and http://indic-computing.sourceforge.net/handbook/languageinformation.html Your comments on these lists are solicited. Is this much information sufficient for developers? Did we miss something? The handbook projects page gives some background information about the development of the Handbook: http://indic-computing.sourceforge.net/projects/handbook.html ===== Joseph Koshy, FreeBSD Developer, http://people.freebsd.org/~jkoshy/ Founder/Manager/Programmer/Peon, The Indic-Computing Project http://indic-computing.sf.net ________________________________________________________________________ Missed your favourite TV serial last night? Try the new, Yahoo! TV. visit http://in.tv.yahoo.com |
|
From: Dr. U.B. P. <pav...@vi...> - 2003-05-31 16:49:13
|
Malayalees, pl take a look. -Pavanaja ------- Forwarded message follows ------- From: "U B Pavanaja" <pav...@ho...> To: pav...@vi... BCC to: Subject: Fwd: Malayalam in Uniscribe Date sent: Sat, 31 May 2003 16:15:25 +0000 >From: "Paul Nelson \(TYPOGRAPHY\)" >To: , >Subject: Malayalam in Uniscribe >Date: Wed, 28 May 2003 06:04:08 -0700 >Dear Ajayalal and Pavanaja, > >I am preparing to begin looking at the Malayalam support in Unscribe so >we can ship a system update later this year. > >Can you please help me understand any issues/deficiencies for Malayalam >text handling that currently exist in Uniscribe? I would like to make >these adjustments and provide an updated copy of USP10.DLL for you to >test. > >If there are any others who should participate in a beta program for >Malayalam, can you please let me know their names and e-mail addresses? > >Regards, > >Paul Reconnect with old pals. Relive the happy times With just one click. ------- End of forwarded message ------------------------------- ----------------------------- Dr. U.B. Pavanaja Editor, Vishva Kannada World's first Internet magazine in Kannada http://www.vishvakannada.com/ Note: I don't worry about pselling mixtakes |
|
From: Bharateeya-OpenOffice <bha...@nc...> - 2003-05-19 08:41:59
|
Hi, OO.o 1.1 Beta (644) incorporates some major changes in implementation, and includes a generalized framework for CTL-based languages like Hindi and Thai. The BharateeyaOO.o version that we have developed, (taken from the 641 source tag), has support only for Indian languages in general. OO.o 1.1 Beta (note: implementations are still in beta stage, and are being perfected for Beta2 and stable releases) provides good initial support for Indian CTL and locales; however, a stable release with complete support is our lookout. We are also testing some extended features like dictionary, Indian language templates and helpcontent, and you will be able to see these incorporated soon. We are planning to release BharateeyaOO.o ,*OO.o 1.1 Beta* and newer stable build localizations soon, specifically on Linux. These will be made available, not only on our site, but also on OO.o mirrors. The urls will be specified on our hi.openoffice.org -> download page. Best Regards, BharateeyaOO.o Team <http://hi.openoffice.org> <http://www.ncb.ernet.in/bharateeyaoo> ----------------------------------------------------------------------- Bhupesh Koli <bh...@op...> Shikha G Pillai <sh...@op...> ----------------------------------------------------------------------- On Mon, 19 May 2003, Guntupalli Karunakar wrote: > On Mon, 19 May 2003 13:36:14 +0530 (IST) > Bharateeya-OpenOffice <bha...@nc...> wrote: > > > Hello All, > > > > (We were going to formally announce the news today..., but well > > information goes around faster than we thought :-) Prakash Advani > > has already announced for us, thank you.) > > > > The Indian Flag flies high on OpenOffice.org!!! > > ----------------------------------------------- > > > > We have started the first Indian Native Language Project on > > OpenOffice.org - http://hi.openoffice.org/ which brings OO.o to > > Indian users in Hindi. This will be the official site for our work, > > through which we hope to represent and coordinate the Indian > > linguistic communities on OpenOffice.org. The site has mailing > > lists, members and issue tracking, which can be used to tackle > > Indian language support problems in OO.o, as well as other language > > issues. The site is just in its initial phase... there will be lots > > more to come soon. > > > > We hope that this will mark a new beginning in the field of > > indic-computing as well as Indian language representation in OO.o, > > and we look forward to some comments and/or feedback. > > > > Is there a Linux version of BharateeyaOO out? How different is it from > OOO 1.1 beta announced to have Hindi support. > > Regards, > Karunakar > > -- > "The best way to cheer yourself up is to try to > cheer somebody else up." -Mark Twain > > --------------------------- > * Indian Linux project * > * http://www.indlinux.org * > --------------------------- > |
|
From: Guntupalli K. <kar...@fr...> - 2003-05-19 08:09:02
|
On Mon, 19 May 2003 13:36:14 +0530 (IST) Bharateeya-OpenOffice <bha...@nc...> wrote: > Hello All, > > (We were going to formally announce the news today..., but well > information goes around faster than we thought :-) Prakash Advani > has already announced for us, thank you.) > > The Indian Flag flies high on OpenOffice.org!!! > ----------------------------------------------- > > We have started the first Indian Native Language Project on > OpenOffice.org - http://hi.openoffice.org/ which brings OO.o to > Indian users in Hindi. This will be the official site for our work, > through which we hope to represent and coordinate the Indian > linguistic communities on OpenOffice.org. The site has mailing > lists, members and issue tracking, which can be used to tackle > Indian language support problems in OO.o, as well as other language > issues. The site is just in its initial phase... there will be lots > more to come soon. > > We hope that this will mark a new beginning in the field of > indic-computing as well as Indian language representation in OO.o, > and we look forward to some comments and/or feedback. > Is there a Linux version of BharateeyaOO out? How different is it from OOO 1.1 beta announced to have Hindi support. Regards, Karunakar -- "The best way to cheer yourself up is to try to cheer somebody else up." -Mark Twain --------------------------- * Indian Linux project * * http://www.indlinux.org * --------------------------- |
|
From: Bharateeya-OpenOffice <bha...@nc...> - 2003-05-19 07:56:02
|
Hello All,
(We were going to formally announce the news today..., but well
information goes around faster than we thought :-) Prakash Advani has
already announced for us, thank you.)
The Indian Flag flies high on OpenOffice.org!!!
-----------------------------------------------
We have started the first Indian Native Language Project on
OpenOffice.org - http://hi.openoffice.org/ which brings OO.o to Indian
users in Hindi. This will be the official site for our work, through which
we hope to represent and coordinate the Indian linguistic communities on
OpenOffice.org. The site has mailing lists, members and issue tracking,
which can be used to tackle Indian language support problems in OO.o, as well
as other language issues. The site is just in its initial phase... there will
be lots more to come soon.
We hope that this will mark a new beginning in the field of
indic-computing as well as Indian language representation in OO.o, and we
look forward to some comments and/or feedback.
So, see you at hi.openoffice.org! :-)
Best Regards
BharateeyaOO.o (& now hi.openoffice.org too!) Team
<http://hi.openoffice.org/>
<http://www.ncb.ernet.in/bharateeyaoo>
----------------------------------------------------------------
Bhupesh Koli <bh...@op...>
Shikha G Pillai <sh...@op...>
----------------------------------------------------------------
|
|
From: Jyotirmoy S. <jyo...@ya...> - 2003-05-13 13:10:53
|
--- Keyur Shroff <keyur_shroff@ya...> wrote: >There are converters which convert ISCII codes to ISFOC >codes; though such converters are not publicly >available. Hi, I'm new to this mailing list! There's one such converter publicly available that I wrote when I was a student in IITK. It's available in the download page of: http://www.cse.iitk.ac.in/users/isciig The name of the converter is "libiscii". Jyotirmoy __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com |
|
From: Keyur S. <key...@ya...> - 2003-05-06 08:43:15
|
--- Alok Kumar <al...@ya...> wrote: > Hi, > What is ISFOC? > Is it a font encoding standard, or a script rendering engine, or > "something > else"? To what extent can it be and has it been used for standardization > of font and/or character encodings as the case may be? ISFOC stands for Indian Script FOnt Codes. Yes, it is proprietary font coding standard used by C-DAC. In ISFOC there is a separate glyph layout scheme for each of the Indic scripts. In such a scheme, a "character" shape may be composed of one or more glyphs. For example, there may be two separate glyphs, e.g., Half-Kha and a vertical bar to represent full form of letter "Kha". There are converters which convert ISCII codes to ISFOC codes; though such converters are not publicly available. However few people tried to write such converters by looking at the layout of ISFOC encoded font. As you can predict, font coding standards doesn't pose much problem for printing, shaping, etc. But on the other hand you can't expect "rich" (rich in features) typography with such font based coding scheme. Also, you can't perform operations like searching, sorting, efficiently with such font based coding scheme. The best way to use such font based standard is to use them as an intermediate layer. Higher level can still operate on character codes and such font based codes at the lower level can come into picture only at the time of rendering. AFAIK, the ISFOC standard was taken as a base for newly proposed glyph-based coding standard for Indic scripts (See Vishwabharat@TDIL issues). Emacs-Unicode has implemented Indic support based on ISFOC standard by writing Unicode->ISFOC conversion rules. Visit http://www.m17n.org/emacs-indian/index.html - Keyur __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com |
|
From: <al...@ya...> - 2003-05-06 08:22:22
|
Hi, What is ISFOC? Is it a font encoding standard, or a script rendering engine, or "something else"? To what extent can it be and has it been used for standardization of font and/or character encodings as the case may be? Here's some information I tried to collect, it confused me more than before ~~ I'm sure the gurus here would be able to derive what it is via this information. http://www.cdacindia.com/html/gist/standard/isfoc.asp <snip> character-slice(glyph) coding standards to ensure good appearance and aesthetics for which Indian scripts are famous for. Unlike ISCII, these code charts are different for each script and are represented in 8-bits only. They are suitable for all GUI environments requiring bit-map fonts, Type-1 fonts or True Type fonts. </snip> I understand that ISFOC is a font encoding standard? If yes, does anyone have the "code charts" for this 8 bit font encoding standard? Surprisingly, they are not available at the official site. If it is not a font encoding standard, what is it? This page doesn't even mention the full form of ISFOC(if it has any). http://www.studio-systems.com/broadfeatures/JulyAug2001/CDAC/29.htm <snip> Converters are components that are needed to supply the rendering engine with the display codes (ISFOC) from the storage codes (ISCII) and vice versa. Converters are language specific mapping tables along with algorithms to generate display strings for the output device. </snip> implies that ISCII, being a character encoding, needs ISFOC for rendering. http://www.lingua-uk.com/cdac.htm gives the full form(Indian Script Font Code) though I'm not very sure it is correct, since it hasn't come from an official source. <snip> # ISFOC Script Manager makes it possible to harness the strength of MS-Windows or Macintosh based powerful packages like Corel Draw , Quark Xpress , 3D Studio , MS-Excel , Power Point, Page Maker, MS-Word etc. # To ensure appealing usage of Indian Scripts, CDAC has ushered in the "ISFOC" (Indian Script Font Code) standard that do justice to the nature of script while conforming to the normal requirements . </snip> seems to imply that ISFOC is a "something" that is used to display indic fonts on win*. http://www.cfilt.iitb.ac.in/resourcepage/ has a "Download Monollingual ISFOC to Billingual ISFOC Converter" link. http://mail.gnome.org/archives/gtk-i18n-list/2000-November/msg00020.html says that it is a "it doesn't count as a standard unless it is freely redistributable." meaning, it is supposed to be a standard of some sort, but nobody really *knows* what that standard is. ===== Contribute to http://indic-computing.sourceforge.net +91-80-653-8200 http://groups.yahoo.com/group/linux-bangalore-hindi/ Can't see Hindi? http://geocities.com/alkuma/seehindi.html http://9211.blogspot.com Set View->Encoding->UTF-8 à¤à¤ªà¤à¥ सà¥à¤à¤¾à¤µ शà¥à¤à¥à¤°à¤¤à¤¾ सॠतà¤à¥ सà¥à¤µà¥à¤à¤¾à¤° हà¥à¤à¤à¥ à¤à¥ à¤à¤¬ à¤à¤ª à¤à¤¨à¥à¤¹à¥à¤ लाà¤à¥ à¤à¤°à¤¨à¥ à¤à¤¾ बà¥à¤¡à¤¼à¤¾ à¤à¥ सà¥à¤µà¤¯à¤ à¤à¤ ायà¥à¤à¤à¥à¥¤ ________________________________________________________________________ Missed your favourite TV serial last night? Try the new, Yahoo! TV. visit http://in.tv.yahoo.com |
|
From: Guntupalli K. <kar...@fr...> - 2003-05-05 11:11:12
|
On Mon, 5 May 2003 11:49:39 +0100 (BST) Alok Kumar <al...@ya...> wrote: > Hi, > Does anybody know the progress on ISO-8859-12 ? > The only information I could get was at > http://czyborra.com/charsets/iso8859.html#Future and I'm not sure > how recent it is. No progress on this, ISO is probably waiting for us to give it something. Anyways having a registered charset for Indic would be good for applications. One issue is ISO-8859 standards are kind of bilingual - with 0 - 127 forming ascii plane & above for another language. ISCII could be accomodated as ISO-8859-12 , but issue comes with ATR language codes, meaining apart from knowing that current charset is iso-8859-12, the application has to know what language to use for current text, it will have to keep a constant look for any ATR codes coming in. Having a registered iso-8859-12 would mean , those against unicode (& utf-8) can use 8 bit encoding scheme for content, & we can have iconv routines to convert from 8 bit to Unicode & vice versa. Font based encodings are bad but ISCII & Unicode are good. Regards, Karunakar -- "Twenty years from now you will be more disappointed by the things that you didn't do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbour. Catch the trade winds in your sails. Explore. Dream.Discover." - Mark Twain --------------------------- * Indian Linux project * * http://www.indlinux.org * --------------------------- |
|
From: <al...@ya...> - 2003-05-05 10:49:50
|
Hi, Does anybody know the progress on ISO-8859-12 ? The only information I could get was at http://czyborra.com/charsets/iso8859.html#Future and I'm not sure how recent it is. Alok ===== Contribute to http://indic-computing.sourceforge.net +91-80-653-8200 http://groups.yahoo.com/group/linux-bangalore-hindi/ Can't see Hindi? http://geocities.com/alkuma/seehindi.html http://9211.blogspot.com Set View->Encoding->UTF-8 à¤à¤ªà¤à¥ सà¥à¤à¤¾à¤µ शà¥à¤à¥à¤°à¤¤à¤¾ सॠतà¤à¥ सà¥à¤µà¥à¤à¤¾à¤° हà¥à¤à¤à¥ à¤à¥ à¤à¤¬ à¤à¤ª à¤à¤¨à¥à¤¹à¥à¤ लाà¤à¥ à¤à¤°à¤¨à¥ à¤à¤¾ बà¥à¤¡à¤¼à¤¾ à¤à¥ सà¥à¤µà¤¯à¤ à¤à¤ ायà¥à¤à¤à¥à¥¤ ________________________________________________________________________ Missed your favourite TV serial last night? Try the new, Yahoo! TV. visit http://in.tv.yahoo.com |
|
From: Guntupalli K. <kar...@fr...> - 2003-03-12 15:17:32
|
Hi, Some patents related to handling Opentype. Maybe we should debate on these, how they affect free s/w or opensource. Also if there is any relevance to Indic. Font feature file processing - Adobe Systems http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&u=/netahtml/search-adv.htm&r=1&p=1&f=G&l=50&d=ptxt&S1=Opentype&OS=Opentype&RS=Opentype Methods and apparatus that process a front-end editable text file--a feature file--that specifies features for a font, and in particular to an OpenType.TM. font. The specified features are parsed and stored in the font as font data. The feature file contains simple logic statements for the specification of various typographical features, such as layout features, expressed in a high-level feature definition language. The feature file may contain override values for fields in font tables. The feature file can be processed in combination with an existing font file to establish an enhanced font file. Using and accessing information from fonts in multiple formats - Sun Microsystems http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&u=/netahtml/search-adv.htm&r=3&p=1&f=G&l=50&d=ptxt&S1=Opentype&OS=Opentype&RS=Opentype Laying out a paragraph by defining all the characters as a single text run by substituting, and then positioning the glyphs - Microsoft http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&u=/netahtml/search-adv.htm&r=4&p=1&f=G&l=50&d=ptxt&S1=Opentype&OS=Opentype&RS=Opentype Laying out a paragraph using a layout services library. An entire paragraph is defined as a single text run. The text run is laid out by substituting glyphs for the characters of the text run and then positioning the glyphs. After the text run is laid out, the length of the text run is compared to the line length. If the length of the text run exceeds the line length, then the text run is divided into a parent text run and a child text run. If justification is enabled, then the parent text run is justified. If a child text run is created, then the length of the child text run is compared to the line length. If the length of the child text run exceeds the line length, then the process is repeated until the length of the last child text run does not exceed the line length. A layout services library provides text processing functions which support the paragraph layout and the justification. Method for rendering glyphs using a layout services library - Microsoft http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&u=/netahtml/search-adv.htm&r=5&p=1&f=G&l=50&d=ptxt&S1=Opentype&OS=Opentype&RS=Opentype Rendering glyphs using a layout services library. A layout services library provides a set of text-processing functions for use by a client program. The text-processing functions access font information stored in the font tables insulating the client program from the details of the font table formats. The layout services library may be used to identify glyph variants and to position glyphs along a base line for a run of text. To identify glyph variants, the layout services library scans the run of text to identify the locations of characters having alternative glyph forms. The layout services library creates a list of feature parameter structures, each of which contains a count of the number of glyph alternates that apply for each identified character. The client program assembles a list of identical characters which have different parameters and presents a list of all glyph variants to the user who chooses one of the alternatives. To position glyphs, the layout services library assembles data that describes the advance of a virtual pen point from glyph to glyph along the base line, an X-placement value, and a Y-placement value. The X-placement value and the Y-placement value are used to position the glyph with respect to the virtual pen point on the base line. Regards, Karunakar -- Hating people is like burning down your house to get rid of a rat - Anon --------------------------- * Indian Linux project * * http://www.indlinux.org * --------------------------- |
|
From: Vijay P. S. A. <vi...@ek...> - 2003-02-22 11:43:39
|
Hi! There are a few updates after the last announcement on the OTF workshop to share with the community. We had been trying our bit to resolve some of the problems, concerns, issues raised by the members in the list, which are definitely correct, understandable and required action. There had been an off-line debate on the topics and some issues got resolved as well as some support has came about, hence this announcement. It has also been recommended by some of members that all debates on workshop issues should be done on lists only. So here it is for all the member for open debate as well as there is strong appeal to the members particularly those who wish to develop open source tools for development of OTF, hence developers of tools and applications and other those who suggest alternate standards as against limitations of Unicode for Indian languages as discussed in Indic-Computing workshop Sept 2002 and again many time in the Indic-mailing lists. This debate has been suggested to be only limited to "users" list so that it does not clutter "devel" & "standards" list. However for this time it is being posted on all lists, so that all members who are interested should join in users list (if they are already not subscribed there). Some of the major issues that had been raised by members are: 1) Why OTF, open standards Vs Proprietary tools for development, simply the debate "How open is OTF" 2) Unicode/OTF - How relevant for Indian languages, concerns and alternatives 3) Registration Fee issue 4) Travel support & Honorarium for speakers 5) Sponsorship At sponsorship front we have some good news to share, we have received some sponsorship that would help us now to offer some concessions to the participants. SARAI, New Delhi (thanks to Ravikant) has agreed to cover the cost of travel of the speakers upto a total of 25,000 Rs (III AC, Train only, might not cover all speakers, hence limitations, those who can afford should please afford). Although we are still waiting for confirmation from CHIPS, who have agreed to sponsor logistics and food, but we can well assume that the same might come, as has been assured by Aman Grewal (thanks to him) [if it does not alternative would be suggested #] ANNOUNCEMENTS: In view of the new developments and the concerns of the members we are happy to announce: 1) To change the name of workshop to "Indic-Font workshop" and include in the workshop agenda the issues raised by Koshy, Hemamurthy, Nagarajan & others and have a debate on relevance of OTF for Indian languages and alternatives. Then the workshop would functionally focus on OTF related issues and at the same time bring up other issues and alternatives as well. Incase there are not enough people to volunteer to take up the relevant topics such as open-source rendering technologies like Graphite, how Omega handles typesetting of complex scripts and make a presentation on the same in the workshop, (Once confirmed these sessions could be added in the existing agenda), then this would be an opentype only workshop (then the existing agenda would stand). The existing topics besides OTF that are already part of agenda are: a. Sunil Abraham, Mahiti, Bangalore, would arrange for an IPR (cyber laws) lawyer Lawrence Liang, who would discuss the issue of OTF openness after understanding the Adobe & Microsoft agreement on release of the fonts. b. Development of Otf from Ttf (Akruti) & other fonts experiences: Karunakar, Nagarjuna, Ravi Pande, Raj Kumar, Sayamindu??? c. Open/free software tools for Otf development: M Arun ????? Suggested Topics: VOLUNTEER, SPEAKERS & SESSION LEADERS NEEDED, also suggest additional topics relevant here a. Alternate standards best for Indian languages, RKK ??? - Hemamurthy b. Generic transliteration rules framework for Indian languages (input sequence & in context with display rendering)/Nagarajan c. Open-source rendering technologies like Graphite d. How Omega handles typesetting of complex scripts e. Nepal case study; Nepali Font Standardisation Project: Amar Gurung??? f. Any more ????????? We need a volunteer here to coordinate the open source sessions along with OTF sessions which Dr. Pavanaja is coordinating. 2) We are dropping the Registration Fee (as announced earlier) and would have a nominal registration fee of say 200.00 Rs. which could be submitted by participants at the time of registration. The amount collected thus would be for logistics/CD/reading material etc 3) Its is agreed that Speakers would voluntarily share there experiences, they shall not be provided any Honorarium, in view of concern raised by members. 4) All participants would have to travel at there own cost. # We would request (if CHIPS support do not come) all participants to pay for there food and mattress/pillow rent (if they are staying in hostels). Those who are making there own staying arrangements, it is fine. We shall arrange for the food in mess on confirmation and participants can directly pay. Lastly we hope that members would come up to volunteer for the sessions, if it is needed that workshop dates be extended from the present, to accommodate some of the open source topics (after confirmation of speakers), it could also be done. Till then the present agenda and dates would hold. We have already started getting applications from participants, those who are yet to submit can please write to me at <vi...@ek...>. We are also in process of putting up an online form for application, which shall be announced shortly. We hope to move ahead with this workshop towards regional language focused workshops soon, we would request all members to keep thinking of them also. regards vijay -- Vijay Pratap Singh Aditya ekgaon technologies email: vi...@ek... website: http://www.ekgaon.com Revised workshop Agenda: --------------------------------- --------------------------------- Indic-Computing Consortium announces ------------------------------------- First National Indic-Font Workshop Date: 28th to 30th March 2003 Venue: PESIT, Bangalore Sponsors: PESIT, Bangalore Vishwa Kannada, Bangalore DeepRoot Linux Pvt. Ltd, Bangalore Chattisgarh Infotech Promotion Society, Raipur Sarai, New Delhi Indlinux.org, Mumbai ekgaon technologies pvt. ltd, Madurai Indic-Computing Consortium: The Indic-Computing Consortium is an initiative of software developers, businesses and academic institutions to help evolve appropriate standards, resources and technologies for the Indic-Computing community. The Indic-Computing Consortium is designed as a national-level participatory organisation that serves as a common forum for discussion, information exchange and advocacy on behalf of all parties interested in the development of Indian Language Computing. The consortium aims to make true access of computing possible for Indian people by enabling support in local language. A framework is being built for creation of a hierarchy of participatory consortia, which would facilitate broad regional and local participation in the standardization and development process from a variety of stakeholders with differing areas of expertise and specialization. It is aimed that these consortia be participatory and inclusive to properly represent the viewpoint of local developers, users and other stakeholders. In step two, Indic-Computing Consortium would encourage & support formation of state-level consortia for each regional language, which could include participants from the following key member groups: - Developers: Software developers and managers developing local-language tools - Technologists: Academics and other experts in encoding and representation issues - Users / Practioners: Government agencies, publishers, NGOs and other major users of local-language software - Linguistic Groups: Academics and other experts of the linguistic features of a language and it's script Working closely with the State Government, this state-level consortium would serve as the representative body for deciding standards and other technical decisions for computing in a given regional language. The major roles to be carried out by the state-level consortium would be as follows: - Discuss various technical, linguistic and practical issues related to computing in the regional language - Serve as a capacity-building and educational resource for small regional software developers and users - Publish documents, tools & other materials helpful for local-language computing and development - Represent the regional language at National consortium meetings - Represent the regional language at International Standardization consortiums and proceedings such as Unicode and ISO In September 2002 Indic-Computing organised its first National workshop, which aimed at finding the various problems faced by the developer communities and issues related to standardization, technical support, policy and tools. To know more about the consortium, workshops and other initiatives, visit us at http://www.indic-computing.sourceforge.net The workshop: One of the working groups formed at the first Indic-Computing workshop was for development of OTF & issues related to language standardization and representation in international consortium. One of the action point and agenda for the group was to Hold OTF training workshop for developing major Indian language OTF fonts . Dr. U B Pavanaja took upon to hold and coordinate this workshop and Mr. Abhas Abhinav proposed to coordinate for logistics & sponsorship, Mr. G. Nagarjuna proposed to help coordinate with Akruti for making available fonts to be used for develop OTF. This group succeeded in its tasks making this workshop possible, Akruti released some free fonts to be used for conversion to OTF, which were taken up by some of the language groups (for more details on the language groups and the major issues being dealt by it please go through the proceedings of first workshop at our website) Some of the major concerns raised by the language community were: i. Developing good look fonts ii. Development of open source tools for rendering and hinting of OTF fonts (currently OTF development uses proprietary tools) iii. Finding font developers for all Indian languages and coordinating the group iv. Making available fonts to be converted to OTF This workshop seeks to address some of these issues and others enclosed in the workshop program as under. This is the first national workshop on the subject, while it shall focus on OTF, but it shall equally share concerns of open standards community and would have talks, demos and training sessions of open source tools, as well as various alternative technologies for Indian fonts. We propose to take up more regional language font workshops in future to give focused attention to each language, these workshops would be held all across India in different parts and would hold training programs and technology demonstration. We invite volunteers who would take upon to hold these workshops and provide coordination & logistics support. The Indic-Computing Consortium would provide necessary technical support and capacity building to these regional groups. Why OpenType? OpenType is an extension to TrueType, and uses Unicode as standard for character encoding. It also provides additional tables for defining rich set of mappings between characters and glyphs. It also provides for a having a large glyph set and even glyph varaints. All the features provided by OpenType format can be made use by having a application independent, preferable system level library with a api interface usable by applications. For Indic script processing OpenType tables like GSUB (glyph substitution) and GPOS (glyph positioning) gives font designer to define his rules on what conjuncts or combinations could be made available. Application programmer is relieved of the burden of knowing all the linguistic part. Also OpenType sort of makes the concept of glyph standard or font encoding standard redundant, again giving font vendors freedom to follow their own glyph sets and not really affecting the application. To summarize OpenType provides lot of benefits to Indic computing and also renders redundant some issues faced in Indic computing. There has been an ongoing debate on whether OTF is right for Indian Languages. The debate is relevant and contextual also. One of the perspectives penned by G Karunakar in support of OpenType is here for participants to explore. However the debate goes on and we invite all to participate in it on the Indic-computing mailing list. Please go through the attachment why_otf.txt for more on OTF fonts. Who can participate & pre-requisites: " Any developer/company/organization having interest in language technology and interested to learn development of OTF, understanding of Unicode, various technologies for Indian languages and related issues. " Pre-requites " Understand how to make a font " Knowledge of Unicode " Have a font that it/he/she can use for lab time " A willingness to keep trying until it/he/she understands " To get comprehensive information on pre-requisites mentioned above please go through the following links " Creating and supporting OpenType fonts for Indic scripts http://www.microsoft.com/typography/otfntdev/indicot/default.htm " Building OTF http://www.microsoft.com/typography/otfntdev/intro.htm " Details about VOLT http://www.microsoft.com/typography/developers/volt/default.htm " Unicode FAQ about Indic http://www.unicode.org/faq/indic.html " Unicode code charts http://www.unicode.org/charts/ (More links would be added subsequently on various development work on open source font technologies) How to participate: i. The workshop is by registration only, last date of registration in 20th March 2003 ii. Participants interested to participate in the workshop should send there applications to Vijay Pratap Singh Aditya <vi...@ek...>. Shortly an online applicatiion form would also be made available. iii. Application format " Name " Organisation " Communication Address " Whether participating in individual capacity or representing your organization " In either case please write in 200 words your interests and what do you expect from the workshop " If there are more then one participant from your organization/group please provide the numbers and communication address only. iv. The registration fee of Rs. 200.00 is to be paid in cash by the participants on the first day. v. Participants please note that all registered members would get, literature, CD with important font development softwares, lodging and boarding for three days (also dinner for the night before the workshop starts). Contacts: Participants are advised to contact the following for there queries: Dr. U B Pavanaja: <pav...@vi...> Technical clarification, sessions of the workshops, required preparation, fonts etc Mr. Abhas Abinav: <ab...@de...> Logistics, Lodging & Boarding, Venue etc Mr. Vijay Pratap Singh Aditya: <vi...@ek...> Workshop registration application, coordination, any other issue not covered above Instructions for Participants: 1) The participants are advised to go through the pre-requisites and equip themselves with necessary knowledge on font & Unicode standard. 2) The staying arrangements are from the evening before the day of start of the workshop. Dinner would be provided for the night also, for all participants reaching before 9.00 PM only. 3) The lodging & boarding provided by PESIT is in hostels & mess, and is modest by all means. Participants who wish to opt out of this arrangement can make there own staying arrangements. Please notify the same to us, also it is expected that the lunch would be taken by all the participants irrespective of there place of stay at mess only as there is not much time available in between the session. 4) The staying arrangement in the hostel is till 3rd day evening, it is expected that the participants would vacate the rooms by evening. 5) PESIT is at outskirts of Bangalore, participants are expected to make there own arrangements for local travel, as nothing could be provided by the organizers. Venue & how to reach: PESIT (PES Institute of Technology) 100 Feet Ring Road, Banashankri IIIrd Stage, (Off. Mysore Road) Bangalore Phone: (080) 672 0007 For participants arriving at Airport, take a prepaid taxi to the above address, the place is known to the prepaid stand. Directions from Airport: Airport Road--->Domlur signal--->Inner ring road--->Koramangala- -->BTM Layout--->Banneraghatta Road--->100 Feet (outer) ring road--->PESIT on 100 Feet (outer) Ring Road For participants arriving at Railway station & Bus station, best is to take a prepaid taxi to the above address, the place is known to the prepaid stand. A Bus is also available Directions from Railway Station: Station--->Chamrajpate--->Ashram--->Hanumant Nagar--->Hosakerehalli --->PESIT 100 Feet Ring Road Workshop program: (to be revised after confirmation of more speakers) ------------------------- Day-1: 09:00 - 09:45 Registration 09:45 - 10:15 Welcome & Inauguration J Koshy / Director PESIT 10:15 - 10:45 Overview - Pavanaja 10:45 - 11:00 Tea break 11:00 - 11:30 Planning glyph repertoire - Pavanaja 11:30 - 13:00 Introduction to Indian scripts, Character set, tools & Glyph Design & current trends in fonts- Ravi Pande 13:00 - 14:00 Lunch break 14:00 - 15:00 Testing glyphs, Generating Fonts, Font format - Ravi Pande 15:00 - 15:15 Tea break 15:15 - 17.15 Lab: Define glyphs and fill out repertoire 17.15 - Tea & informal interaction Day-2: 09:30 - 10:15 Encoding - J Koshy 10:15 - 10:45 Introduction to OTF - Pavanaja 10:45 - 11:00 Tea break 11:00 - 11:30 Open Type Tables - Pavanaja 11:30 - 13:00 Introduction to VOLT - Pavanaja 13:00 - 14:00 Lunch break 14:00 Lab: Open type tables Day-3: 09:30 - 10:15 Testing - Pavanaja 10:15 - 10:45 Hinting Pavanaja 10:45 - 11:00 Tea break 11:00 - 11:30 Digitally signing the font - Pavanaja 11:30 - 13:00 Fonts on Linux - Karunakar 13:00 - 14:00 Lunch break 14:00 Lab: Open type tables Special presentations proposed: a. Sunil Abraham, Mahiti, Bangalore, would arrange for an IPR (cyber laws) lawyer Lawrence Liang, who would discuss the issue of OTF openness after understanding the Adobe & Microsoft agreement on release of the fonts. b. Development of Otf from Ttf (Akruti) & other fonts experiences: Karunakar, Nagarjuna, Ravi Pande, Raj Kumar, Sayamindu??? c. Open/free software tools for Otf development: M Arun ????? |
|
From: Keyur S. <key...@ya...> - 2003-01-23 05:20:57
|
--- Andy White <And...@bt...> wrote: > If problems in Indic Unicode handling are not brought up on the Unicode > list, members of the Unicode consortium may never learn about them and > they may never be sorted. > > I have searched the Unicode list and it seems that Keyur Shroff has > *never* posted to any messages to it. For me it doesn't matter who explained the corrections first as far as my name is there ;-). Seriously, if Andy is very concious about his name then let me clarify that Andy originally suggested the corrections (in what is wrong with Indic Unicode-FAQ) and I tried to put it in other words because few people couldn't understand what Andy meant :) Andy, for your information, I posted a message to Yahoogroups! which is an archive of Unicode list. You can see my message at http://groups.yahoo.com/group/unicode/message/16352 I thought both the orginal Unicode list and this archive is same and message posted to this archive is also included in Unicode list. Somehow I started receving two messages from Unicode list. One from the original and the other from this egroup archive. So I unsubscribed from original Unicode list and I am still a member of Unicode group at Yahoo. If message posted to egroup archive are not received on Unicode list then I don't know where in the world my message was lost :) Also, I apologize for use of word "foreigner". I really meant "non-native" speaker. Regards, Keyur __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com |
|
From: <al...@ya...> - 2003-01-22 04:15:25
|
Hi folks, > > These documents are prepared by the foreign people on Unicode > > list. > > No there were not. They were written by me. > If I am foreign, then you are also foreign! ;-) Let's continue to stick to the technical aspects, and also let's keep in mind the global nature of the mailing lists. I'm still very much a newbie here but I do know that it's very easy for discussions to get derailed in this way. Another example from our mailing lists: "The Tamil community should ask unicode to ..." (not verbatim). Most people would understand that this refers to "Tamil computing user groups" rather than people of Tamil ethnicity as a whole, but a casual reader may easily misinterpret it. Similarly, the word "foreign" has different connotations depending on your nationality. I don't know what the nationalities of the two persons in question are (and I don't care) but perhaps "non native speakers" would be a better term? In brief, let's stick to the technical issues. Keyur, Andy and others, thanks for your inputs, waiting to hear more on this. Hope this discussion gives us a good insight into how unicode consortium works. alok ===== Alok Kumar F1, Wireless Monitoring Station Compound, 9th Main, 47th Cross, Jayanagar V Block Bangalore 560076 India +91-80-653-8200 http://groups.yahoo.com/group/linux-bangalore-hindi/ Can't see Hindi? http://geocities.com/alkuma/seehindi.html ________________________________________________________________________ Missed your favourite TV serial last night? Try the new, Yahoo! TV. visit http://in.tv.yahoo.com |
|
From: Andy W. <And...@bt...> - 2003-01-21 16:29:43
|
If problems in Indic Unicode handling are not brought up on the Unicode list, members of the Unicode consortium may never learn about them and they may never be sorted. I have searched the Unicode list and it seems that Keyur Shroff has *never* posted to any messages to it. To post to the Unicode list you have to first subscribe. See http://www.unicode.org/unicode/consortium/distlist.html To send messages to the list please send them to un...@un... All deficiencies regarding Indic Unicode handling, once discussed, should be mentioned on the Unicode list above. Andy > -----Original Message----- > From: ind...@li... > [mailto:ind...@li...] > On Behalf Of Andy White > Sent: 21 January 2003 15:52 > To: 'Keyur Shroff'; 'SayaminduDasgupta' > Cc: ind...@li... > Subject: RE: [Indic-computing-standards] Re: > [Indic-computing-users] Unicode > > > > > Keyur Shroff wrote: > > > > --- Sayamindu Dasgupta <unm...@So...> wrote: > > > > > > Here is a nice resource - primarily related to Bangla though. > > > http://www.exnet.btinternet.co.uk/ > > > > These documents are prepared by the foreign people on Unicode > > list. > > No there were not. They were written by me. > If I am foreign, then you are also foreign! ;-) > > > The FAQ mentioned there is not part of Unicode standard > > bu it is there on Unicode website for the benefit of people. > > I have noticed some ambiguity and wrong information in the > > FAQ. For example, in the FAQ it has been written that > > ISCII: Halant + Halant > > Unicode: Halant + ZWJ > > > > are equivalent, which is wrong. In ISCII, Halant + Halant is > > known as explicit Halant and it produces result similar to > > Halant + ZWNJ in Unicode. So instead of ZWJ, there should be > > ZWNJ. There are other corrections also. I reported this in > > Unicode list but corrections have not be taken place yet. > > I thought that it was me that reported this, but now it seems > that it was you!? > > Andy |
|
From: Andy W. <And...@bt...> - 2003-01-21 15:51:14
|
Keyur Shroff wrote: > > --- Sayamindu Dasgupta <unm...@So...> wrote: > > > > Here is a nice resource - primarily related to Bangla though. > > http://www.exnet.btinternet.co.uk/ > > These documents are prepared by the foreign people on Unicode > list. No there were not. They were written by me. If I am foreign, then you are also foreign! ;-) > The FAQ mentioned there is not part of Unicode standard > bu it is there on Unicode website for the benefit of people. > I have noticed some ambiguity and wrong information in the > FAQ. For example, in the FAQ it has been written that > ISCII: Halant + Halant > Unicode: Halant + ZWJ > > are equivalent, which is wrong. In ISCII, Halant + Halant is > known as explicit Halant and it produces result similar to > Halant + ZWNJ in Unicode. So instead of ZWJ, there should be > ZWNJ. There are other corrections also. I reported this in > Unicode list but corrections have not be taken place yet. I thought that it was me that reported this, but now it seems that it was you!? Andy |
|
From: Keyur S. <key...@ya...> - 2003-01-21 07:55:53
|
--- Karthik Venkatesh <kar...@vs...> wrote: > >Earlier (couple of weeks ago) I visited RKK's site and > realized that they have some misunderstanding about Unicode > standard. > > Keyur, not at all. No one can challenge Prof. Krishnan's knowledge and contribution in Indian languages. We have respect for Prof. Krishnan and we are far behind him in knowledge. Couple of weeks ago I visited the page http://acharya.iitm.ac.in/multi_sys/uni_iscii.html and found that there is lot of talk about ISCII and Unicode mentioning many problems including sorting and transliteration. In fact they are not the problems but Unicode recommends to handle it in different way because it is not possible to provide general sort order for all languages in a given script encoding because sort order for languages in a script may differ. Also, there are many other issues like different ways for representing characters (e.g., decomposed consonant cluster v/s. precomposed ligature). Hence the characters in a given text must be normalized to either precomposed or decomposed character string before performing any operations like sorting and/or searching. > In fact, Prof. Krishnan is writing a monograph to document > the problems of Unicode vis a vis Indian languages. His > focus will be on the limitations of Microsoft's > Unicode-based approach to Indic language issues. If anyone > on this list has specific ideas about what else he should > tackle in this monograph, please write to him at > rk...@ac... > > From my own association with him for the last several > months, I know that he certainly does not reject Unicode > wholesale. However, he is keen that the Indic developer > community become aware of, and address the problem areas. I > am sure his monograph will throw more light on the subject. This is really appreciable. There are very few people like Prof. Kalyan Krishnan in India who possess great knowledge and also take deep interests in promotion of Indian languages. We are looking forward to learn a lot from his inputs. - Keyur __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com |
|
From: Keyur S. <key...@ya...> - 2003-01-21 07:10:26
|
--- Sayamindu Dasgupta <unm...@So...> wrote: > > Here is a nice resource - primarily related to Bangla though. > http://www.exnet.btinternet.co.uk/ These documents are prepared by the foreign people on Unicode list. The FAQ mentioned there is not part of Unicode standard bu it is there on Unicode website for the benefit of people. I have noticed some ambiguity and wrong information in the FAQ. For example, in the FAQ it has been written that ISCII: Halant + Halant Unicode: Halant + ZWJ are equivalent, which is wrong. In ISCII, Halant + Halant is known as explicit Halant and it produces result similar to Halant + ZWNJ in Unicode. So instead of ZWJ, there should be ZWNJ. There are other corrections also. I reported this in Unicode list but corrections have not be taken place yet. There was some interesting discussion going on Bengali script in Unicode list. It was about Khanda-Ta and what people know as 'Zaphola'. Excuse me if I am wrong. I am not Bengali expert :) It seems that there is inadequate representation of Bengali script in Unicode and still there are many issues to resolve. But that is certainly possible in Unicode in one way or the other. - Keyur __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com |
|
From: Keyur S. <key...@ya...> - 2003-01-21 06:37:39
|
--- "ma...@ch..." <ma...@ch...> wrote: > > Analysis > The problems perceived with the Tamil Unicode segment are as follows. > --------------------------------------------------------------------- > > Character Sequence > The primary problem is that the sequence of characters does not match the > traditional Tamil ordering method. This is the reason many Tamil scholars > have requested a reorganization of the Tamil segment. However since some > softwares including the popular Windows 2000 have already implemented > Unicode in its current form, it will not be possible now to change the > Tamil segment entirely. This is one of the common misunderstanding about Unicode. In fact, the Unicode standard DO NOT (and CAN NOT) provide default sort order because sort order is specific to a language and not to any script. For example, sort order for characters in Marathi and Hindi differ even though both the languages fall under the same script 'Devanagari'. One must understand the difference between collation order and encoding order. It is not possible to change the order of characters in Unicode character chart. Also, it is not desirable. Standards are not meant to change very often. Unicode standard has changed character orders only once during its life - when it was decided to go together with ISO 10646 standard. But, at that time the Unicode was in nascent stage. Changing the order of any characters now will create problems for so many applications, not only MS platform. For detailed explanation, you are requested to read the following paper: http://www.microsoft.com/middleeast/msdn/Indic_collation-DC.pdf > > The actual ordering of characters in unicode based databases happen by > specifying a collation sequence. Unicode has detailed documents on > writing > these collation sequences. A document needs to be prepared in accordance > with Unicode standards for the correct Tamil ordering sequence (tamiz > neTunkaNakku). If it is not ready then Tamil community should come forward and help other people to define correct sorting order for characters. > ------------------------------------------------------------------------- > > Missing Characters > Some characters in Tamil script are missing in Unicode. These are not > native to Tamil language, but are often used in Tamil documents. > Significant among them are, SRI, KSHA and Tamil numeral ZERO. If these characters are really needed in the Tamil script, then they can be added. Inclusion of any character in Unicode chart must go through standard procedure. It includes proposal, justification, evidence, and support from linguists and/or state government. But, if the character is not prime representative of the script and if the characters with the similar semantic has already been defined elsewhere in the Unicode, then it is recommeded to reuse the character instead of duplicating. However, there are some exceptions. Popularity of a particular encoding is also considered sometimes. Unicode could have been designed in a better way with some unified approach for encoding but in order to maintain compatibility with all popular encodings and other existing standards, it was decided to reuse those standards in Unicode. > > While zero is not used in the original Tamil number system, it is often > used in present day documents while writing numbers in Tamil numerals > using > international number system. It is noted [1] that Mauritius currency uses > Tamil numberals with zero in their currencies. This character should be > added at U+0BE6. > > KSHA and SRI are grantha characters not native to Tamil language. However > they are being used in Tamil script for over six centuries [2]. > Devanagari > and many other indian languages consider these characters as ligatures > (combination of several characters). These are considered separate > characters in Tamil, not ligatures. Thus including these characters in > Tamil Unicode range makes good sense and will eliminate complex ligature > handling for Tamil. (Possible locations: KSHA = U+0BBA; SRI = U+0BF3). With experience we have learnt that complexity of ligatures can be handled easily in either application or font. To give unique codepoint to all ligatures is not considered a good idea when there are alternatives available. If you encode each ligature separately then in fact you are at lost of beautiful canonical structures which is unique property of Indic scripts. > > Another character often requested in Tamil Unicode range is OM. > Devanagari > and Gujarati ranges in Unicode have a separate character for OM at U+0950 > and U+0ADO. If there is a consensus on adding this character, it can be > added at U+0BD0. > > There have been some suggestions for including Rupee sign, and Tamil > fraction symbols in Unicode. These characters are not in popular use. > These may need to be considered only when they come into use. If there is consensus for inclusion of these characters in Tamil script, then proposal can be submitted to Unicode. > ----------------------------------------------------------------------- > > Incorrect Characters > Tamil Unicode range has a character for TAMIL SIGN ANUSVARA at U+0B82. > This > character does not exist in native Tamil script. Its existence in grantha > script needs to be examined. This character is sometimes mistaken for > Tamil > oRRu which is at location U+0BCD (TAMIL SIGN VIRAMA). It would be better > if this character is deprecated from Unicode standard. Since characters in Unicode standard can not be removed once they are defined, their use can be deprecated. > > The character TAMIL SIGN VISARGA (Aytam) at U+0B83 is incorrectly > classified as a modifier in Unicode while it is considered as a character > in Tamil script. This error needs to be corrected. The glyph that > represents this character should be changed to remove the character place > holder (dotted circle). AFAIK this change has been made in Unicode version 3.1. - Keyur __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com |
|
From: <kut...@ya...> - 2003-01-15 10:36:59
|
http://www.unicode.org/consortium/distlist.html ________________________________________________________________________ Missed your favourite TV serial last night? Try the new, Yahoo! TV. visit http://in.tv.yahoo.com |
|
From: Dr. U.B. P. <pav...@vi...> - 2003-01-03 14:07:21
|
http://www.unicode.org/Public/4.0-Update/ Checkout your languages. -Pavanaja ---------------------------------------------------- - Dr. U.B. Pavanaja Editor, Vishva Kannada World's first Internet magazine in Kannada http://www.vishvakannada.com/ Note: I don't worry about pselling mixtakes |
|
From: Andy W. <And...@bt...> - 2002-12-02 17:32:47
|
Please see my draft proposal for a CBM here: http://www.exnet.btinternet.co.uk/uniprop/proposalform.htm It is proposed to solve current ambiguities and would particularly = effect Malayalam. It also address concerns I have herd from Kanada users. As far as Malayalam implementers is concerned, If this proposal were to = be excepted, all that should need to be done in current apps, would be = to replace all ZWNJs with CBMs Questions: Is the proposal acceptable and is it the way to go? Are there better examples I should be using? Are the examples correct? Can you supply examples in other scripts? Best wishes Andy White |
1 message has been excluded from this view by a project administrator.
