[GRASS5] Indic support in GRASS GIS with Indix2

GRASS GIS GRASS GIS developer
1

HI all,
my first post. I hope I am posting this is right list.
this is for your comments. If it sounds ok, can some 2-3MB code of Indix2 (indic Shaping Engine) be included in grass code to claim something like “GRASS GIS supports 11 Indian Scripts” ?

Bye

---------- Forwarded message ----------
From: SWAPNIL HAJARE <dreamil1000a@yahoo.com>
Date: Dec 1, 2005 4:17 PM
Subject: Indic support in GRASS GIS with Indix2
To: indlinux-group@lists.sourceforge.net
Cc: dreamil@gmail.com

Hi everybody,
greetings.

GRASS (http://www.grass.itc.it) is a powerful desktop
GIS application. we have been working on it for some
time.The current version GRASS ( 6.0.1) has support for
Unicode but doesn’t support OpenType fonts. So things
like labels on maps could not be shown in Indian
scripts. As a workaround we used tryutype display-only
font setu-dev
( http://www.janabhaaratii.org.in/janabhaaratii/page_gen.php?lang=en&body=/setu-doc/setu.html).

After attending the Indix2
(http://ncst.ernet.in/projects/indix/ ) developer
workshop at NCST, I started working on adding support
for Indic scripts in GRASS using Indix2 client
libraries (not sure if this is correct terminology -
but it can be compared in functionality with
Pango/Qt).I have achieved some success in this as I
have managed to get display Unicode UTF-8 text on maps
using “d.text.freetype” utility of GRASS
( http://grass.itc.it/grass60/manuals/html60_user/d.text.freetype.html).
What I have done basically is modified the
d.text.freetype code to check if the text to be
displayed falls under Indic scripts range and if it
does, use Indix2 routines to convert the logical
sequence of characters to visual sequence of glyphs to
be displayed directly by X. Please see snapshot of the
same at
http://203.199.16.202/grass_indix2_20051201.png
showing text in
Devanagari,gujarati,Gurumukhi,Bangla,Kannada,Tamil,Telugu,Malayalam
and Oriya. In the snapshot, the right side gedit
window shows the script which draws these labels in
GRASS.

The fonts used in snapshot are Saral series fonts
developed by Indix2 team.Many thanks to Vinod Kumar
and Sandeep Rao of Indix2 team for their valuable
guidence.
There are lot many things to be cleaned up in the code
and once it gets into some respectable form I am going
to submit this patch to the GRASS team.
Your comments/feedback awaited.
Thanks,

Swapnil K Hajare
Technical Coordinator,
janabhaaratii ( www.janabhaaratii.org.in)
CDAC Mumbai (formerly NCST)
home: http://www.janabhaaratii.org.in/portal/Members/swapnil/
blog: http://dreamil.blogspot.com

Enjoy this Diwali with Y! India Click here http://in.promos.yahoo.com/fabmall/index.html

–
Swapnil Hajare

2

Hello all,

Sorry for a much belated response.
Indian Language support for GRASS (For GUI and
in the map lables) will be highly benificiary.

A discussion on a better GUI for GRASS is already
going on. I think it may end up with using GTK or
QT as toolkit. Both GTK and QT has indian language
support.
So this work may become irrelevent, according to the
future plans of the GUI team. So we may need to switch
to pango/Qt

On 12/8/05, Swapnil Hajare <dreamil@gmail.com> wrote:

HI all,
   my first post. I hope I am posting this is right list.
   this is for your comments. If it sounds ok, can some 2-3MB code of Indix2
(indic Shaping Engine) be included in grass code to claim something like
"GRASS GIS supports 11 Indian Scripts" ?

--
Change the rules, or the rules will change you
     ---------Kumaranasan

3

hi,
greetings.
not sure if the new GTK gui will solve our problem. Does the new GUI means GRASS monitors will use pango for rendering? I guess they will use the same monitor. And by the time they come up with new GUI, should we wait for them to finish and then start our localised GIS work ? My feeling is this should be seen as a patch for indic support (similar to d.text.freetype used for CJK). correct me if I am wrong.
I am also not sure how many indic scripts are supported well by Pango/QT and what is the quality of rendering for all these scripts. If this solution can provide a better rendering solution, it has every right to be accepted as a good alternative to Pango/Qt.

bye

On 12/19/05, Sajith VK <sajithvk@gmail.com> wrote:

Hello all,

Sorry for a much belated response.
Indian Language support for GRASS (For GUI and
in the map lables) will be highly benificiary.

A discussion on a better GUI for GRASS is already
going on. I think it may end up with using GTK or
QT as toolkit. Both GTK and QT has indian language
support.
So this work may become irrelevent, according to the
future plans of the GUI team. So we may need to switch
to pango/Qt

On 12/8/05, Swapnil Hajare < dreamil@gmail.com> wrote:

HI all,
my first post. I hope I am posting this is right list.
this is for your comments. If it sounds ok, can some 2-3MB code of Indix2
(indic Shaping Engine) be included in grass code to claim something like
“GRASS GIS supports 11 Indian Scripts” ?

–
Change the rules, or the rules will change you
---------Kumaranasan

–
Swapnil Hajare

4

I would suggest translating QGIS as a start. I think is the easiest and most
promising way.
pc

At 07:43, lunedì 19 dicembre 2005, Swapnil Hajare has probably written:

hi,
greetings.
  not sure if the new GTK gui will solve our problem. Does the new GUI
means GRASS monitors will use pango for rendering? I guess they will use

...
--
Paolo Cavallini
email+jabber: cavallini@faunalia.it
www.faunalia.it
Piazza Garibaldi 5 - 56025 Pontedera (PI), Italy Tel: (+39)348-3801953

5

Hello,

I too dont know whether GUI team will keep the existing monitor in the "next
generation GUI". I think the road map for next GUI is not yet ready. So for the
time being, your work seems to be highly beneficial.

Can some one working on the GUI give their comments?

On 12/19/05, Swapnil Hajare <dreamil@gmail.com> wrote:

hi,
greetings.
  not sure if the new GTK gui will solve our problem. Does the new GUI means
GRASS monitors will use pango for rendering? I guess they will use the same
monitor. And by the time they come up with new GUI, should we wait for them
to finish and then start our localised GIS work ? My feeling is this should
be seen as a patch for indic support (similar to d.text.freetype used for
CJK). correct me if I am wrong.
  I am also not sure how many indic scripts are supported well by Pango/QT
and what is the quality of rendering for all these scripts. If this solution
can provide a better rendering solution, it has every right to be accepted
as a good alternative to Pango/Qt.

bye

--
Change the rules, or the rules will change you
     ---------Kumaranasan

6

Hi,

I have added Hindi support to GRASS by adding two .po files.
After installing
kde-i18n-hi-3.4.2-10mdk
locales-hi-2.3.5-1mdk
on my Mandriva box, I can even see the characters. With
d.font.freetype it should be possible to print them on the monitor
such as for Japanese and Chinese. Screenshots asap...

I fetched the KDE Hindi file and autotranslated the GRASS
messages, some hundred fuzzy translations resulted. Since
my Hindi is a bit rusty, I would leave the verification to
native speakers.

You can grab the wto hindi files from here

http://grass.itc.it/devel/i18n.php
-> Download current .po files from CVS
    -> grasslibs_hi.po
    -> grassmods_hi.po

Please send updates to these files regularly, in order to
stay in sync.

If needed, I can add other languages are well.

Cheers

Markus

On Mon, Dec 19, 2005 at 07:43:53AM +0100, Swapnil Hajare wrote:

hi,
greetings.
  not sure if the new GTK gui will solve our problem. Does the new GUI means
GRASS monitors will use pango for rendering? I guess they will use the same
monitor. And by the time they come up with new GUI, should we wait for them
to finish and then start our localised GIS work ? My feeling is this should
be seen as a patch for indic support (similar to d.text.freetype used for
CJK). correct me if I am wrong.
  I am also not sure how many indic scripts are supported well by Pango/QT
and what is the quality of rendering for all these scripts. If this solution
can provide a better rendering solution, it has every right to be accepted
as a good alternative to Pango/Qt.

bye

On 12/19/05, Sajith VK <sajithvk@gmail.com> wrote:
>
> Hello all,
>
> Sorry for a much belated response.
> Indian Language support for GRASS (For GUI and
> in the map lables) will be highly benificiary.
>
> A discussion on a better GUI for GRASS is already
> going on. I think it may end up with using GTK or
> QT as toolkit. Both GTK and QT has indian language
> support.
> So this work may become irrelevent, according to the
> future plans of the GUI team. So we may need to switch
> to pango/Qt
>
> On 12/8/05, Swapnil Hajare <dreamil@gmail.com> wrote:
> > HI all,
> > my first post. I hope I am posting this is right list.
> > this is for your comments. If it sounds ok, can some 2-3MB code of
> Indix2
> > (indic Shaping Engine) be included in grass code to claim something like
> > "GRASS GIS supports 11 Indian Scripts" ?
> >
> --
> Change the rules, or the rules will change you
> ---------Kumaranasan
>

--
Swapnil Hajare

--
Markus Neteler <neteler itc it> http://mpa.itc.it
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy

7

Paolo, all,

the Hindi translation of GRASS should be pretty straightforward
now (see my other mail). Those messages will be also available
in QGIS through the GRASS-QGIS interface.

Markus

On Mon, Dec 19, 2005 at 07:57:51AM +0100, Paolo Cavallini wrote:

I would suggest translating QGIS as a start. I think is the easiest and most
promising way.
pc

At 07:43, lunedì 19 dicembre 2005, Swapnil Hajare has probably written:
> hi,
> greetings.
> not sure if the new GTK gui will solve our problem. Does the new GUI
> means GRASS monitors will use pango for rendering? I guess they will use
...
--
Paolo Cavallini
email+jabber: cavallini@faunalia.it
www.faunalia.it
Piazza Garibaldi 5 - 56025 Pontedera (PI), Italy Tel: (+39)348-3801953

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

--
Markus Neteler <neteler itc it> http://mpa.itc.it
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy

8

Hi again,

an update for support of Indian languages:

- we now have messages files in Hindi available (still to be
  translated)
- we can out-of-the-box generate Hindi (or other) scripts
  in the GRASS monitor using TTF fonts, see screenshot at
  http://grass.itc.it/devel/i18n.php
  -> example for Hindi
     http://grass.itc.it/images/grass61_hindi_hi.jpg

Note that this is a proof of concept example in Spearfish,
done with:

#extraction of phrase in Hindi:
head -37 locale/po/grassmods_hi.po | tail -1 > /tmp/hindi
echo "599505|4921010|`cat /tmp/hindi | cut -d'"' -f2 `" | v.in.ascii out=hindi

d.rast elevation.dem
v.db.select hindi
d.vect hindi icon=basic/circle
d.font.freetype font=/usr/share/fonts/hi/lohit_hi.ttf
d.vect hindi disp=attr attr=str_1 lsize=40 lcol=blue

Works :slight_smile:

Cheers

Markus

On Tue, Dec 20, 2005 at 10:38:44PM +0100, Markus Neteler wrote:

Hi,

I have added Hindi support to GRASS by adding two .po files.
After installing
kde-i18n-hi-3.4.2-10mdk
locales-hi-2.3.5-1mdk
on my Mandriva box, I can even see the characters. With
d.font.freetype it should be possible to print them on the monitor
such as for Japanese and Chinese. Screenshots asap...

I fetched the KDE Hindi file and autotranslated the GRASS
messages, some hundred fuzzy translations resulted. Since
my Hindi is a bit rusty, I would leave the verification to
native speakers.

You can grab the wto hindi files from here

http://grass.itc.it/devel/i18n.php
-> Download current .po files from CVS
    -> grasslibs_hi.po
    -> grassmods_hi.po

Please send updates to these files regularly, in order to
stay in sync.

If needed, I can add other languages are well.

Cheers

Markus

On Mon, Dec 19, 2005 at 07:43:53AM +0100, Swapnil Hajare wrote:
> hi,
> greetings.
> not sure if the new GTK gui will solve our problem. Does the new GUI means
> GRASS monitors will use pango for rendering? I guess they will use the same
> monitor. And by the time they come up with new GUI, should we wait for them
> to finish and then start our localised GIS work ? My feeling is this should
> be seen as a patch for indic support (similar to d.text.freetype used for
> CJK). correct me if I am wrong.
> I am also not sure how many indic scripts are supported well by Pango/QT
> and what is the quality of rendering for all these scripts. If this solution
> can provide a better rendering solution, it has every right to be accepted
> as a good alternative to Pango/Qt.
>
> bye
>
> On 12/19/05, Sajith VK <sajithvk@gmail.com> wrote:
> >
> > Hello all,
> >
> > Sorry for a much belated response.
> > Indian Language support for GRASS (For GUI and
> > in the map lables) will be highly benificiary.
> >
> > A discussion on a better GUI for GRASS is already
> > going on. I think it may end up with using GTK or
> > QT as toolkit. Both GTK and QT has indian language
> > support.
> > So this work may become irrelevent, according to the
> > future plans of the GUI team. So we may need to switch
> > to pango/Qt
> >
> > On 12/8/05, Swapnil Hajare <dreamil@gmail.com> wrote:
> > > HI all,
> > > my first post. I hope I am posting this is right list.
> > > this is for your comments. If it sounds ok, can some 2-3MB code of
> > Indix2
> > > (indic Shaping Engine) be included in grass code to claim something like
> > > "GRASS GIS supports 11 Indian Scripts" ?
> > >
> > --
> > Change the rules, or the rules will change you
> > ---------Kumaranasan
> >
>
>
>
> --
> Swapnil Hajare

--
Markus Neteler <neteler itc it> http://mpa.itc.it
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy

9

---------- Forwarded message ----------
From: Swapnil Hajare <dreamil@gmail.com>
Date: Jan 5, 2006 3:02 PM
Subject: Re: Hindi support in GRASS 6.1 - was Re: [GRASS5] Fwd: Indic support in GRASS GIS with Indix2
To: Sajith VK <sajithvk@gmail.com>, grass developers list <grass5@grass.itc.it>, GRASS user list <grasslist@baylor.edu>

Hi,
sorry for such a late response.
I downloaded the CVS version of GRASS GIS and compiled it on my debian sarge machine. I then used the commands given by you to create a sample vector and displayed it on monitor. For the example that you have in your snapshot, it works fine. But then I realised that you have displayed a string in devanagari/hindi which does not require any processing on font side. i.e. the text is displayed just similar to english text
using juxtapositioning of glyphs. So I tried with some conjunct text which requires some positioning/replacement rules to be used from the opentype font, it couldnot display properly. See the snapshot for details (snapshot uploaded on http://203.199.16.202/grass_cvs_comparison.png ). The left monitor show the GRASS CVS version as downloaded on 2006-01-05 and compiled as-it-is. The right monitor shows output of d.tect.freetype compiled with Indix2 libraries. The right monitor show properly rendered text while the left monitor show text in form of juxtapositioned glyphs. I knew that because of freetype library GRASS will be able to use opentype fonts but I also knew that it doesn’t have any rendering engine like pango/qt/indix2 to render complex text in indic scripts correctly.

We had tried this same thing in past without any rendering engine and failed. That is why I had filed this bug (http://intevation.de/rt/webrt?serial_num=3189 ). I must apologise for not following it up properly.

regards

On 12/22/05, Markus Neteler <neteler@itc.it > wrote:

Hi again,

an update for support of Indian languages:

Note that this is a proof of concept example in Spearfish,
done with:

#extraction of phrase in Hindi:
head -37 locale/po/grassmods_hi.po | tail -1 > /tmp/hindi
echo "599505|4921010|cat /tmp/hindi | cut -d'"' -f2 " | v.in.ascii out=hindi

d.rast elevation.dem
v.db.select hindi
d.vect hindi icon=basic/circle
d.font.freetype font=/usr/share/fonts/hi/lohit_hi.ttf
d.vect hindi disp=attr attr=str_1 lsize=40 lcol=blue

Works :slight_smile:

Cheers

Markus

On Tue, Dec 20, 2005 at 10:38:44PM +0100, Markus Neteler wrote:

Hi,

I have added Hindi support to GRASS by adding two .po files.
After installing
kde-i18n-hi-3.4.2-10mdk
locales-hi-2.3.5-1mdk
on my Mandriva box, I can even see the characters. With
d.font.freetype it should be possible to print them on the monitor
such as for Japanese and Chinese. Screenshots asap…

I fetched the KDE Hindi file and autotranslated the GRASS
messages, some hundred fuzzy translations resulted. Since
my Hindi is a bit rusty, I would leave the verification to
native speakers.

You can grab the wto hindi files from here

http://grass.itc.it/devel/i18n.php
→ Download current .po files from CVS
→ grasslibs_hi.po
→ grassmods_hi.po

Please send updates to these files regularly, in order to
stay in sync.

If needed, I can add other languages are well.

Cheers

Markus

On Mon, Dec 19, 2005 at 07:43:53AM +0100, Swapnil Hajare wrote:

hi,
greetings.
not sure if the new GTK gui will solve our problem. Does the new GUI means
GRASS monitors will use pango for rendering? I guess they will use the same
monitor. And by the time they come up with new GUI, should we wait for them
to finish and then start our localised GIS work ? My feeling is this should
be seen as a patch for indic support (similar to d.text.freetype used for
CJK). correct me if I am wrong.
I am also not sure how many indic scripts are supported well by Pango/QT
and what is the quality of rendering for all these scripts. If this solution
can provide a better rendering solution, it has every right to be accepted
as a good alternative to Pango/Qt.

bye

On 12/19/05, Sajith VK <sajithvk@gmail.com> wrote:

Hello all,

Sorry for a much belated response.
Indian Language support for GRASS (For GUI and
in the map lables) will be highly benificiary.

A discussion on a better GUI for GRASS is already
going on. I think it may end up with using GTK or
QT as toolkit. Both GTK and QT has indian language
support.
So this work may become irrelevent, according to the
future plans of the GUI team. So we may need to switch
to pango/Qt

On 12/8/05, Swapnil Hajare < dreamil@gmail.com > wrote:

HI all,
my first post. I hope I am posting this is right list.
this is for your comments. If it sounds ok, can some 2-3MB code of
Indix2
(indic Shaping Engine) be included in grass code to claim something like
“GRASS GIS supports 11 Indian Scripts” ?

–
Change the rules, or the rules will change you
---------Kumaranasan

–
Swapnil Hajare

–
Markus Neteler http://mpa.itc.it
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy

–
Swapnil Hajare

–
Swapnil Hajare

10

Hi Swapnil Hajare,

can you send the necessary changes as CVS diffs? It is explained
in the GRASS 6.1-CVS SUBMITTING file in the main source directory
how to generate it properly.

Then we can better see what needs to be changed.

thanks

Markus

On Thu, Jan 12, 2006 at 04:32:55PM +0530, Swapnil Hajare wrote:

---------- Forwarded message ----------
From: Swapnil Hajare <dreamil@gmail.com>
Date: Jan 5, 2006 3:02 PM
Subject: Re: Hindi support in GRASS 6.1 - was Re: [GRASS5] Fwd: Indic
support in GRASS GIS with Indix2
To: Sajith VK <sajithvk@gmail.com>, grass developers list <
grass5@grass.itc.it>, GRASS user list <grasslist@baylor.edu>

Hi,
  sorry for such a late response.
  I downloaded the CVS version of GRASS GIS and compiled it on my debian
sarge machine. I then used the commands given by you to create a sample
vector and displayed it on monitor. For the example that you have in your
snapshot, it works fine. But then I realised that you have displayed a
string in devanagari/hindi which does not require any processing on font
side. i.e. the text is displayed just similar to english text
using juxtapositioning of glyphs. So I tried with some conjunct text which
requires some positioning/replacement rules to be used from the opentype
font, it couldnot display properly. See the snapshot for details (snapshot
uploaded on http://203.199.16.202/grass_cvs_comparison.png ). The left
monitor show the GRASS CVS version as downloaded on 2006-01-05 and compiled
as-it-is. The right monitor shows output of d.tect.freetype compiled with
Indix2 libraries. The right monitor show properly rendered text while the
left monitor show text in form of juxtapositioned glyphs. I knew that
because of freetype library GRASS will be able to use opentype fonts but I
also knew that it doesn't have any rendering engine like pango/qt/indix2 to
render complex text in indic scripts correctly.

We had tried this same thing in past without any rendering engine and
failed. That is why I had filed this bug (
http://intevation.de/rt/webrt?serial_num=3189 ). I must apologise for not
following it up properly.

regards

On 12/22/05, Markus Neteler <neteler@itc.it> wrote:
>
> Hi again,
>
> an update for support of Indian languages:
>
> - we now have messages files in Hindi available (still to be
> translated)
> - we can out-of-the-box generate Hindi (or other) scripts
> in the GRASS monitor using TTF fonts, see screenshot at
> http://grass.itc.it/devel/i18n.php
> -> example for Hindi
> http://grass.itc.it/images/grass61_hindi_hi.jpg
>
> Note that this is a proof of concept example in Spearfish,
> done with:
>
> #extraction of phrase in Hindi:
> head -37 locale/po/grassmods_hi.po | tail -1 > /tmp/hindi
> echo "599505|4921010|`cat /tmp/hindi | cut -d'"' -f2 `" | v.in.asciiout=hindi
>
> d.rast elevation.dem
> v.db.select hindi
> d.vect hindi icon=basic/circle
> d.font.freetype font=/usr/share/fonts/hi/lohit_hi.ttf
> d.vect hindi disp=attr attr=str_1 lsize=40 lcol=blue
>
> Works :slight_smile:
>
> Cheers
>
> Markus
>
> On Tue, Dec 20, 2005 at 10:38:44PM +0100, Markus Neteler wrote:
> > Hi,
> >
> > I have added Hindi support to GRASS by adding two .po files.
> > After installing
> > kde-i18n-hi-3.4.2-10mdk
> > locales-hi-2.3.5-1mdk
> > on my Mandriva box, I can even see the characters. With
> > d.font.freetype it should be possible to print them on the monitor
> > such as for Japanese and Chinese. Screenshots asap...
> >
> > I fetched the KDE Hindi file and autotranslated the GRASS
> > messages, some hundred fuzzy translations resulted. Since
> > my Hindi is a bit rusty, I would leave the verification to
> > native speakers.
> >
> > You can grab the wto hindi files from here
> >
> > http://grass.itc.it/devel/i18n.php
> > -> Download current .po files from CVS
> > -> grasslibs_hi.po
> > -> grassmods_hi.po
> >
> > Please send updates to these files regularly, in order to
> > stay in sync.
> >
> > If needed, I can add other languages are well.
> >
> > Cheers
> >
> > Markus
> >
> > On Mon, Dec 19, 2005 at 07:43:53AM +0100, Swapnil Hajare wrote:
> > > hi,
> > > greetings.
> > > not sure if the new GTK gui will solve our problem. Does the new GUI
> means
> > > GRASS monitors will use pango for rendering? I guess they will use the
> same
> > > monitor. And by the time they come up with new GUI, should we wait for
> them
> > > to finish and then start our localised GIS work ? My feeling is this
> should
> > > be seen as a patch for indic support (similar to d.text.freetype used
> for
> > > CJK). correct me if I am wrong.
> > > I am also not sure how many indic scripts are supported well by
> Pango/QT
> > > and what is the quality of rendering for all these scripts. If this
> solution
> > > can provide a better rendering solution, it has every right to be
> accepted
> > > as a good alternative to Pango/Qt.
> > >
> > > bye
> > >
> > > On 12/19/05, Sajith VK <sajithvk@gmail.com> wrote:
> > > >
> > > > Hello all,
> > > >
> > > > Sorry for a much belated response.
> > > > Indian Language support for GRASS (For GUI and
> > > > in the map lables) will be highly benificiary.
> > > >
> > > > A discussion on a better GUI for GRASS is already
> > > > going on. I think it may end up with using GTK or
> > > > QT as toolkit. Both GTK and QT has indian language
> > > > support.
> > > > So this work may become irrelevent, according to the
> > > > future plans of the GUI team. So we may need to switch
> > > > to pango/Qt
> > > >
> > > > On 12/8/05, Swapnil Hajare <dreamil@gmail.com > wrote:
> > > > > HI all,
> > > > > my first post. I hope I am posting this is right list.
> > > > > this is for your comments. If it sounds ok, can some 2-3MB code
> of
> > > > Indix2
> > > > > (indic Shaping Engine) be included in grass code to claim
> something like
> > > > > "GRASS GIS supports 11 Indian Scripts" ?
> > > > >
> > > > --
> > > > Change the rules, or the rules will change you
> > > > ---------Kumaranasan
> > > >
> > >
> > >
> > >
> > > --
> > > Swapnil Hajare
> >
> > --
> > Markus Neteler <neteler itc it> http://mpa.itc.it
> > ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
> > MPBA - Predictive Models for Biol. & Environ. Data Analysis
> > Via Sommarive, 18 - 38050 Povo (Trento), Italy
>

--
Swapnil Hajare

--
Swapnil Hajare

--
Markus Neteler <neteler itc it> http://mpa.itc.it
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy