Closed falconsmilie closed 2 years ago
Hey, I'm the creator of this package, but @musmanikram is a contributor and I'm grateful for him 😅.
You're right the keys should not be integers in any case, I'll mark this as a bug.
Regarding the indentation I'm not sure, maybe the regex I'm using is messing it up. Are you using tabs or spaces? And how many?
Sorry @amiranagram , my mistake. Thank you also for the package! :D
I am using 4 spaces for indentation.
Sorry i should also mention i haven't noticed any other formatting errors when running localize
. In fact your package cleans up a lot of rubbish introduced from BabelEdit.
You're welcome.
Sorry i should also mention i haven't noticed any other formatting errors when running localize. In fact your package cleans up a lot of rubbish introduced from BabelEdit.
That's great, thanks for info.
Hey @falconsmilie I gave it a look during the weekend and I didn't find a "clean" solution to keep the number strings as PHP evaluates them automatically as integers. Might have to do a regex after all 😬
In any case I'll have a patch ASAP
Hi @musmanikram . Thanks for the great localization package.
For key based translations, when i have this;
and then run
localize
it is being converted to this;Changing string keys into integers causes issues for me with BabelEdit because it requires all keys be strings.
Not sure if it's just a side effect of the key conversion, but the indentation also gets messed up;