laravel-js-localization
laravel-js-localization copied to clipboard
Long translations keys (translation strings as keys) support?
I can't seem to make the .json files (as explained here) work with js-localization, and especially the :export command.
Is this supported?
Probably a duplicate of #40. Sorry, but this repo really needs a substitute maintainer 😕
Feel free to re-open if it's not due to the lacking Laravel 5.5 support.
No I believe the Laravel 5.5 support was fixed in #40 with PR #41? I am running Laravel 5.5 and have no problems with either commands at least :smile:
I think this would be a separate issue where one would have to include the language specific .json files in the resources/lang/ directory, if they exist, into the cache (for the :refresh command) and messages.js (for the :export command)?
I have a working implementation of this as well, and should be able to provide a PR for this soon.
Sorry for bumping up this old issue..
@carestad Do you still have the working implementation for translation strings?
No, I'm afraid not :disappointed:
The needs for my project changed and it was no longer necessary.
Plus, if you use full string translations, you kind of already have the JSON for them I suppose, so re-doing the implementation or writing a proxy that reads the right ones souldn't be too difficult.
Yeah, I already found kind of a solution. Thank you!
Now Matice is used: https://github.com/GENL/matice