Not sure where to put properties files (both reference and translated). Perhaps we could just follow mozilla and have them in the locales/ directory. It's a bit too similar to locale, which we are using to generate translations for native activities but it shouldn't be too confusing since for web activities that directory shouldn't exist.
On 4 June 2013 00:21, Daniel Narvaez <dwnarv...@gmail.com> wrote: > We could have activity authors provide the reference properties files in > the locale directory. Bundle builder would generate the pot file from those > using > > prop2po -P > > When building the xo bundle, it would then generate translated properties > files using > > po2prop -t > > It seems like it should work and no real code to write other than the > build bits :) > > > > > > On 4 June 2013 00:05, Daniel Narvaez <dwnarv...@gmail.com> wrote: > >> Well, Jed apparently requires converting po to json too, so we won't save >> on the build bits. It probably doesn't solve the problem of extracting >> translatable strings either. >> >> >> On 4 June 2013 00:00, Daniel Narvaez <dwnarv...@gmail.com> wrote: >> >>> An alternative could be to combine webL10N and Jed >>> >>> http://slexaxton.github.io/Jed/ >>> >>> Either adapt webL10N to use Jed or add the dom bits of webL10N to Jed. >>> The webL10N code is pretty simple, so it might easier then figuring out how >>> to setup the prop2po build bits. >>> >>> >>> On 3 June 2013 23:20, Daniel Narvaez <dwnarv...@gmail.com> wrote: >>> >>>> I had a look at the code and I don't see anything firefox specific, I >>>> suspect the full API will work on latest webkit (they try to support really >>>> old browsers and that's probably where they only support a basic API). >>>> >>>> The thing I'm not convinced about is using .properties files. But >>>> unless we can find a library which uses gettext and support translating >>>> html... perhaps we can just use prop2po. >>>> >>>> >>>> On 3 June 2013 22:56, Daniel Narvaez <dwnarv...@gmail.com> wrote: >>>> >>>>> Hello, >>>>> >>>>> we didn't really think about how to support translations of the web >>>>> activities. This is how mozilla is doing it >>>>> >>>>> https://github.com/fabi1cazenave/webL10n >>>>> >>>>> It claims to be cross browsers but they have a "modern" API which is >>>>> firefox only. I'm not sure what that exactly mean, but a basic API is >>>>> probably better than having to write our own thing. >>>>> >>>>> They use ini files, but there are tools to convert to and from po >>>>> files. >>>>> >>>>> >>>>> http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/prop2po.html?id=toolkit/prop2po >>>>> >>>>> -- >>>>> Daniel Narvaez >>>>> >>>> >>>> >>>> >>>> -- >>>> Daniel Narvaez >>>> >>> >>> >>> >>> -- >>> Daniel Narvaez >>> >> >> >> >> -- >> Daniel Narvaez >> > > > > -- > Daniel Narvaez > -- Daniel Narvaez
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
