I am planning a move from Elm to Bucklescript (most probably using bucklescript-TEA via philip2), and I have a whole bunch of questions relating to Intl and other internationalization/localization topics. It’s probably going to make most sense for me to explain and ask all my questions at once.
So I’m fairly heavily invested in Fluent as an l10n solution at the moment, and I’m planning on staying that way, because it is a very nicely designed system, and elm-fluent turned out really well. So I’m thinking about how to port all of this to Bucklescript.
For elm-fluent, I was using an Elm wrapping of these browser APIs provided by elm-intl, which is very nice (unfortunately only for Elm 0.18, and Elm 0.19 has restricted the usage of this kind of library, with no workaround, which is one of my blockers on Elm 0.19).
Question 1 - are there other places I should be looking or other community efforts I should know about?
Question 2 - are there any plans to get something like this in the standard library, or should I be just using a community package and contributing to that?
Once that is resolved, I’ll need to think about re-writing elm-fluent to target OCaml/Bucklescript instead of Elm.
I think that will be mostly straightforward due to the similarities at the language level, and the way I’ve written the compiler so that code generation is mostly separated out. But I still have a ton of questions:
Question 3 - is there likely to be interest in the wider OCaml community for something like this, or should I just be focusing on Bucklescript/Reason?
Question 4 - is there is interest in the ReasonReact community? Given the design of elm-fluent, which I think will map very well across to Bucklescript, most of the API will be usable from both something like ReasonReact and bucklescript-tea, as most of the time you just need plain text messages, not HTML. For elm-fluent, I did have a pretty nice solution for messages that embed HTML, and this was specific to the Elm virtual DOM, which I think will map very nicely to bucklescript-TEA, and perhaps something similar could be done for ReasonReact.
Question 5 - The elm-fluent compiler is currently written in Python, and when I port it to output Reason/Bucklescript instead I will most likely start from a fork of that project, rather than start from scratch. Is this use of Python likely to hinder adoption in Bucklescript world? I’d be very open to having a OCaml/Bucklescript/Reason implementation etc., but don’t know when I’ll get the time for something like that.
Question 6 - Is anyone interested in helping with any of this? For me this is all in aid of a side project, not paid work, and I have a very small time budget for this, so any help would be greatly appreciated. In addition, for some questions about what the output of the Fluent-to-Bucklescript compiler should produce I’d really value the input of someone with more experience.
Thanks! As mentioned I’m busy with other things so may not be able to reply very quickly.