<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br>> That's essentially the same as the shaping issue with Arabic isn't<br>> it? Which as Jon says, was solved in mapnik by using the icu library<br>> which is supposed to know about these things.<br><br>Thanks for icu reference<br><br>> > For the web site, yes I think we can rely on the browser for this, with<br>> > testing of course. For other pieces of the ecosystem, it will need more<br>> > inquiry, if there's time this summer. I am aware that IndicTrans has been<br>> > working on an open source solution, but not sure how much work it will be<br>> > to integrate.<br>> <br>>
Translating the web site is a major problem in and off itself. That's<br>> nothing to do with what languages are supported, it's all to do with<br>> the infrastructure and how you separate translatable elements from code<br>> cleanly.<br><br>I was only referring to the rendering of characters in the browser, not to the main task to i18n and l10n the rails_port.<br>I'm pretty familiar with the scale of the task, having helped build the infrastructure at yahoo .. not that we couldn't use all the help we can get with advice and suggestions.<br><br>Mikel<br><a href="http://www.compton.nu/" target="_blank"></a><br></div><br></div></div></body></html>