On Tue, Jul 21, 2015 at 11:31 AM, Richard Olsson <[email protected]> wrote:

>
>
> I think you're right about this, but I'm unsure how this would affect
> syntax. I mean, you still need variable expansion/placeables and there are
> some uses cases for entity references, so it would still need to be in the
> language, don't you think?
>

Yes, naturally.  But perhaps if we agree that entity references should not
be common, we could make their syntax "harder" ($entity) and make variable
syntax "easier" (var).


>  I'm not a big fan of the (somewhat verbose) JSON AST syntax. I like
> compact file formats and have designed a few in my days. So if we wanted
> something more compact, I could take a look.
>

That would be great!

Also, have you seen the recent change in the JSON syntax?  We simplified it
a bit in https://github.com/l20n/l20n.js/pull/49.

$ echo "<hello \"Hello, world\">" | ./tools/parse.js -o entries
hello: Hello, world



> > One of the criteria for "webbiness" is the ability to do a F5-style
> > development, and any compile step prevents that.
>
> I agree, and what a lot of libraries do nowadays is provide a runtime
> parser for development purposes, and then a compiler for
> deployment/production. One example among many being React.js.
>
> Personally I rarely use the runtime parsers because I set up a build
> environment with fast, automatic build-on-save, but it still makes sense
> and could be one option. The runtime parsers are often viable options for
> production as well, although not recommended.
>

That's an interesting approach.  Zibi, Axel, what do you guys think?


>
>
> I understand that was always the intention, and that's what made me wonder
> whether they need to be their own thing at all (since they're not really
> global in any other sense than the $vars are), instead of using the already
> existing context variable space.
>

Yup, I think we're on the same page here.

Thanks!
-stas
_______________________________________________
tools-l10n mailing list
[email protected]
https://lists.mozilla.org/listinfo/tools-l10n

Reply via email to