<br><br>---------- Forwarded message ----------<br><span class="gmail_quote">From: <b class="gmail_sendername">Swapnil Hajare</b> <<a href="mailto:dreamil@gmail.com">dreamil@gmail.com</a>><br>Date: Jan 5, 2006 3:02 PM
<br>Subject: Re: Hindi support in GRASS 6.1 - was Re: [GRASS5] Fwd: Indic support in GRASS GIS with Indix2<br>To:
Sajith VK <<a href="mailto:sajithvk@gmail.com">sajithvk@gmail.com</a>>, grass developers list
<<a href="mailto:grass5@grass.itc.it">grass5@grass.itc.it</a>>, GRASS user list
<<a href="mailto:grasslist@baylor.edu">grasslist@baylor.edu</a>><br><br></span>Hi,<br>
sorry for such a late response.<br>
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<br>
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
<a href="http://203.199.16.202/grass_cvs_comparison.png" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://203.199.16.202/grass_cvs_comparison.png</a> ). 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.<br><br>
We had tried this same thing in past without any rendering engine and
failed. That is why I had filed this bug (<a href="http://intevation.de/rt/webrt?serial_num=3189">http://intevation.de/rt/webrt?serial_num=3189</a> ). I
must apologise for not following it up properly. <br>
<br>
regards<div><span class="e" id="q_10899e8fe97a81dc_1"><br>
<br>
<br><div><span class="gmail_quote">On 12/22/05, <b class="gmail_sendername">Markus Neteler</b> <<a href="mailto:neteler@itc.it" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">neteler@itc.it</a>
> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi again,<br><br>an update for support of Indian languages:<br><br>- we now have messages files in Hindi available (still to be<br> translated)<br>- we can out-of-the-box generate Hindi (or other) scripts<br> in the GRASS monitor using TTF fonts, see screenshot at
<br> <a href="http://grass.itc.it/devel/i18n.php" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://grass.itc.it/devel/i18n.php</a><br> -> example for Hindi<br> <a href="http://grass.itc.it/images/grass61_hindi_hi.jpg" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://grass.itc.it/images/grass61_hindi_hi.jpg
</a><br><br>Note that this is a proof of concept example in Spearfish,<br>done with:<br><br>#extraction of phrase in Hindi:<br>head -37 locale/po/grassmods_hi.po | tail -1 > /tmp/hindi<br>echo "599505|4921010|`cat /tmp/hindi | cut -d'"' -f2 `" |
v.in.ascii out=hindi<br><br>d.rast elevation.dem<br>v.db.select hindi<br>d.vect hindi icon=basic/circle<br>d.font.freetype font=/usr/share/fonts/hi/lohit_hi.ttf<br>d.vect hindi disp=attr attr=str_1 lsize=40 lcol=blue<br>
<br>
Works :-)<br><br>Cheers<br><br> Markus<br><br>On Tue, Dec 20, 2005 at 10:38:44PM +0100, Markus Neteler wrote:<br>> Hi,<br>><br>> I have added Hindi support to GRASS by adding two .po files.<br>> After installing
<br>> kde-i18n-hi-3.4.2-10mdk<br>> locales-hi-2.3.5-1mdk<br>> on my Mandriva box, I can even see the characters. With<br>> d.font.freetype it should be possible to print them on the monitor<br>> such as for Japanese and Chinese. Screenshots asap...
<br>><br>> I fetched the KDE Hindi file and autotranslated the GRASS<br>> messages, some hundred fuzzy translations resulted. Since<br>> my Hindi is a bit rusty, I would leave the verification to<br>> native speakers.
<br>><br>> You can grab the wto hindi files from here<br>><br>> <a href="http://grass.itc.it/devel/i18n.php" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://grass.itc.it/devel/i18n.php
</a><br>> -> Download current .po files from CVS<br>> -> grasslibs_hi.po
<br>> -> grassmods_hi.po<br>><br>> Please send updates to these files regularly, in order to<br>> stay in sync.<br>><br>> If needed, I can add other languages are well.<br>><br>> Cheers<br>
>
<br>> Markus<br>><br>> On Mon, Dec 19, 2005 at 07:43:53AM +0100, Swapnil Hajare wrote:<br>> > hi,<br>> > greetings.<br>> > not sure if the new GTK gui will solve our problem. Does the new GUI means
<br>> > GRASS monitors will use pango for rendering? I guess they will use the same<br>> > monitor. And by the time they come up with new GUI, should we wait for them<br>> > to finish and then start our localised GIS work ? My feeling is this should
<br>> > be seen as a patch for indic support (similar to d.text.freetype used for<br>> > CJK). correct me if I am wrong.<br>> > I am also not sure how many indic scripts are supported well by Pango/QT
<br>> > and what is the quality of rendering for all these scripts. If this solution<br>> > can provide a better rendering solution, it has every right to be accepted<br>> > as a good alternative to Pango/Qt.
<br>> ><br>> > bye<br>> ><br>> > On 12/19/05, Sajith VK <<a href="mailto:sajithvk@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">sajithvk@gmail.com</a>> wrote:
<br>> > ><br>> > > Hello all,<br>> > ><br>
> > > Sorry for a much belated response.<br>> > > Indian Language support for GRASS (For GUI and<br>> > > in the map lables) will be highly benificiary.<br>> > ><br>> > > A discussion on a better GUI for GRASS is already
<br>> > > going on. I think it may end up with using GTK or<br>> > > QT as toolkit. Both GTK and QT has indian language<br>> > > support.<br>> > > So this work may become irrelevent, according to the
<br>> > > future plans of the GUI team. So we may need to switch<br>> > > to pango/Qt<br>> > ><br>> > > On 12/8/05, Swapnil Hajare <<a href="mailto:dreamil@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
dreamil@gmail.com
</a>> wrote:<br>> > > > HI all,<br>> > > > my first post. I hope I am posting this is right list.<br>> > > > this is for your comments. If it sounds ok, can some 2-3MB code of
<br>
> > > Indix2<br>> > > > (indic Shaping Engine) be included in grass code to claim something like<br>> > > > "GRASS GIS supports 11 Indian Scripts" ?<br>> > > ><br>> > > --
<br>> > > Change the rules, or the rules will change you<br>> > > ---------Kumaranasan<br>> > ><br>> ><br>> ><br>> ><br>> > --<br>> > Swapnil Hajare<br>><br>
> --<br>> Markus Neteler <neteler itc it> <a href="http://mpa.itc.it" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://mpa.itc.it</a><br>> ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
<br>> MPBA - Predictive Models for Biol. & Environ. Data Analysis
<br>>
Via Sommarive,
18 -
38050 Povo (Trento), Italy<br></blockquote></div><br><br clear="all"><br></span></div>-- <br><span class="sg">Swapnil Hajare
</span><br clear="all"><br clear="all"><br>-- <br>Swapnil Hajare