2007/5/24, Mikkel Kamstrup Erlandsen <<a href="mailto:mikkel.kamstrup@gmail.com">mikkel.kamstrup@gmail.com</a>>:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Minutes of meeting, 2007-05-23</blockquote><div><br><SNIP> <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Joe would like to know how i18n works in Turtle.Evgeny has an example here <a href="http://lists.freedesktop.org/archives/xdg/2007-May/008252.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.freedesktop.org/archives/xdg/2007-May/008252.html</a>. He points out that the translation infrastructure (in Gnome) is already ready for .ini and xml files. </blockquote><div><br>Ok, I've been asking around the Gnome camp how we could support i18n of Turtle files. As far as I can tell it is not gonna be trivial. We will have to add the support to intltool, which only supports a hardcoded set of file types... Given we write this patch we still need to convince the maintainers of intltool to put it in which might be hard to convince them about, but I don't know yet. <br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The complexity of implementing a Turtle parser in C is discussed. It seems unclear what the requirements for such a parser would be in our case where we don't need full Turtle. We haven't decided on a Turtle subset yet, so... </blockquote><div><br>Ok, I've been familiarizing myself with Flex/Bison which is also used for the Raptor Turtle parser and I'm not too scared to write one now. I think the i18n might be the biggest issue for me now actually... <br><br>Cheers,<br>Mikkel<br></div><br></div><br>