Thanks for checking out our work! :)

> I have not yet encountered one example where the text is actually being localized, just examples in English.

Haha, yeah, our website is not localized itself. It may sound funny, but we believe our target audience at this stage of the project development is pretty much English-speaking, so we didn't invest in localization of it :)

> I'd like to see an example on the first page on how would I add a translation for a language that requires different wording for numbers 2 to 5 for example.

Polish is an example of such language. An example of a plural variant selector with it would be:

  shared-photos =
      { $user_name } { $photo_count ->
          [one] dodała jedno zdjęcie
          [few] dodała { $photo_count} zdjęcia
         *[many] dodała { $photo_count } zdjęć
      }.

And we use just standardized `Intl.PluralRules` that gets the correct category - https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

> Also, why [0] and then [one] ?

This is a "smart selector". By default, since the selector is a number we guessed that it should be run via plural selector and then matches against result category list (hence one,few,many)

But on top of that we also experience a common use case where the UX wants to add a special form of the sentence for particular values - usually for 0, like this:

  shared-photos =
      { $user_name } { $photo_count ->
          [0] hasn't added any photos yet
          [one] added one photo
         *[other] added { $photo_count } photos
      }.

Hope that helps!

The project definitely seems interesting to me. What is the current project guidance? A Swift version would be quite useful and I might be interested in contributing.

We decided to start kind of low level and build blocks and combine them per use case.

Here's our roadmap - https://github.com/projectfluent/fluent/wiki/Roadmap

For 1.0 we're aiming at JavaScript, Rust and Python. But if you look at the issues people are talking about Java, C#, Kotlin etc. ports so Swift sounds like a good candidate as well! It all comes down to use cases.

We're currently finalizing 0.7 release which we hope will be the last one including syntax changes (very, very minor - mostly white space relaxation and normalization), and it will allow us to stabilize our EBNF and parser/serializers which, in turn, will make it easier for ports to be written.

Contributors welcomed :)

Can you help us understand what can we do to better promote the unique features we offer?