Next update!

I marked c-l.js bug as FIXED, because at this point c-l.js is fully operational 
[0]

I filed a new bug to start using c-l.js in Elmo[1] with instructions. Next step 
is for Axel to test this in his environment.

I updated JS parser in my v3-features branch to support everything I want to 
support for now, and added lots of tests.

Lastly, I branched the python-l20n parser as 1.0.x to match l20n.js 1.0.x and 
updated the master python-l20n parser to be a perfect port of the JS parser.

At this point, both parsers produce exactly the same AST. I believe there's 
some room to wiggle with the exact AST and once we start working with that AST 
we may want to fine tune it because I made some changes, but overall, it should 
be good to start developing in your code.

Next step is to integrate the parser into Stas's v3 branch and get the pootle 
code to work with the python parser.

zb.

[0] https://bugzilla.mozilla.org/show_bug.cgi?id=1037052 
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1158976
[2] 
https://github.com/zbraniecki/l20n.js/blob/v3-features/src/lib/format/l20n/parser.js
_______________________________________________
tools-l10n mailing list
[email protected]
https://lists.mozilla.org/listinfo/tools-l10n

Reply via email to