On Mon, 2017-10-23 at 23:46 +0200, Petr Kovar wrote: > On Mon, 23 Oct 2017 11:07:07 -0400 > Shaun McCance <[email protected]> wrote: > > > On Sun, 2017-10-22 at 22:10 -0400, Jeremy Bicha wrote: > > > On Sun, Oct 22, 2017 at 3:10 PM, Shaun McCance <[email protected]> > > > wrote: > > > > https://github.com/shaunix/ducktype-examples > > > > > > Yelp doesn't support Ducktype yet, right? > > > > Correct, and adding Ducktype support to Yelp isn't high on my list. > > I'd > > prefer to just make our build tools understand Ducktype and convert > > to > > XML for installation. > > +1. I guess XML as an intermediate format for translations is another > reason why we want to convert to XML at build time?
Also this. If we always go through XML, then we get to use all the power of ITS for our translations. Doing a direct ducktype2po would be possible, but making it as featureful would be a lot of work. I don't know any other lightweight syntax po converter that can do half of what itstool can. And we actually use quite a few of these features in our docs. -- Shaun _______________________________________________ gnome-doc-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gnome-doc-list
