Re:Fluent – A localization system for natural-sounding trans...
by jfk13 on Sunday June 11, 2023 @04:12AM
(#36279315)
> A bit too simple
Why do you say that -- are there particular capabilities it is lacking?
Re:Fluent – A localization system for natural-sounding trans...
by Ygg2 on Sunday June 11, 2023 @07:37AM
(#36280404)
Dynamic message references.
Like say you want to make message like X skeleton(s) attacked Y dragon(s) generic over type of attacker/defender.
Currently only option is to duplicate it or deal with it in program.
Re:Fluent – A localization system for natural-sounding trans...
by ReleaseCandidat on Sunday June 11, 2023 @10:43AM
(#36281876)
That doesn't work. You need to know the gender and actual number `X` of `X skeletons` to be able to (correctly ;) translate `attacked` in many languages. To correctly translate `X skeletons`, you need to know `X` and whether they are the attacker or being attacked. Same for `Y dragons`. In the end, you do not gain much but have a _really_ complex template (for such a simple phrase).
Re:Fluent – A localization system for natural-sounding trans...
by Ygg2 on Sunday June 11, 2023 @03:08PM
(#36284562)
Sure it does, you need a way to pass arguments for case/gender etc. It's not impossible to make it work, I already implemented a prototype for it, but it requires changes to how it handles references.
See https://github.com/projectfluent/fluent/issues/80 for more details.
I ported fluent.rs to C# after current FluentDotNet Ftl implementation was abandoned.
Interesting format, very simple compared to MessageFormat2. A bit too simple. To be honest.