hi,<br> greetings.<br> 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. <br> 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.
<br><br>bye<br><br><div><span class="gmail_quote">On 12/19/05, <b class="gmail_sendername">Sajith VK</b> <<a href="mailto:sajithvk@gmail.com">sajithvk@gmail.com</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;">
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">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 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></blockquote></div><br><br clear="all"><br>-- <br>Swapnil Hajare