im sure the welsh fall into those categories somewhat, but i am mainly thinking of africa and india

Of course

...by the way, how does localisation work in haxeui?

scroll up about 1000 pages 😄

I read through it but I didn't get much from it

but basically

{{foo}}

gets replaced by another string... it does a little more than that, but not much more

and certainly nothing NO WHERE NEAR clever enough (as i've learnt today)

☝️ this is basically the plan

probably still not perfect, but better then what there is currently i think

my biggest stumbling point is the plurals stuff in the .po file

i have a SimpleExpressionParser... but im basically 100% sure that its not gonna work with things that complex

falls over on the first hurdle:

haxe
SimpleExpressionEvaluator.eval("a == 2", {a: 2, b: 3}); // true
SimpleExpressionEvaluator.eval("(a == 2)", {a: 2, b: 3}); // false

🥳

i would be quite interested in helping with that

can you not use hscript or something?

i dont want the dependency, thats was the whole reason for it in the first place

fair enough

can you copy from haxe itself?

from hscript you mean?

the problem with simpleexpressioneval is it was never supposed to work with things like

((n==1)?(0):(((((n%10)>=2)&&((n%10)<=4))&&(((n%100)<10)||((n%100)>=20)))?(1):2));

i mean, haxe the language has to have an expression parser somewhere in it

OCaml i presume

oh, yeah, probably

you could use something more like what crowdin does

you know what though... i could use haxe's ast as a sort of guide though... i mean, we know it works

example from mastodon:

{count, plural, one {{counter} person} other {{counter} people}} in the past {days, plural, one {day} other {{days} days}}

=>

{count, plural, zero {neb} one {{counter} person} two {{counter} berson} few {{counter} pherson} many {{counter} pherson} ={<10} {{counter} person} other {{counter} o bobl}} yn y {days, plural, one {diwrnod diwethaf} two {ddeuddydd diwethaf} other {{days} diwrnod diwethaf}}

it would be easier if i said "all language files have to available at compile time", then i could offload it all to the haxe compiler... but the more i think about it the more i think its valid for an application to have the option to discover and load language files at runtime

it's very useful, especially for development, but it also means more files for the user to have to download and keep track of

it would be optional, ofc, you could also just package them into your app and be done with it

but if it is an option (as i think it should be) it means i cant build the expression from the string at compile time