How to export from default translation files with keyed strings? about laravel-translatable-string-exporter HOT 9 CLOSED

Of course, Yurii. Thanks

from laravel-translatable-string-exporter.

Thanks for your question @yurii-github.
It's easy. Just wrap each text string from resources/lang/{lang}/{key}.php into __() function and run export again.

from laravel-translatable-string-exporter.

evening

yes, I understood that I could use such approach, and I did it for some strings, but in result those strings will be saved in en.json file as

[
  "validation.some.error": "error msg"
 ]

but not in en/validation.php as I want

[
 "some.error" => "error msg"
]

So, my point is, to use trans() to store in php file, and use __() to store in json file. Or do you think it makes no sense to separate ton of validation strings into its own space?

regards

from laravel-translatable-string-exporter.

I'll check tomorrow with file persistent-strings.json , so all custom overrides for laravel validation strings won't be deleted. maybe putting all strings into single json file is not such a bad idea..

from laravel-translatable-string-exporter.

yes, I understood that I could use such approach, and I did it for some strings, but in result those strings will be saved in en.json file as

[
  "validation.some.error": "error msg"
 ]

No, they won't.

First of all, if English is your default language, you don't need that en.json.
Secondly, if you only wrap text strings (not keys) into __(), the format of the translation file will be:

{
"error msg": "error msg"
}

If the format of your JSON translation file is not like this, it may be a bug. Please give me more details on the issue. What do you wrap into __() and what result do your receive after export?

So, my point is, to use trans() to store in php file, and use __() to store in json file.

As I know, in Laravel trans() and __() works the same, so I don't see much sense in adding extra meaning to one of them.

from laravel-translatable-string-exporter.

in my app default language can be changed from en to anything else. I just use english strings so I can understand what is all about. in some places i use keys instead, like in validation strings, so errors can be structured, so i use trans() for keyed strings and __() for readable strings

functions don't work the same

// read from structured translation strings, and fallback to json if no found
trans() --> return app('translator')->trans($key, $replace, $locale)->get($key, $replace, $locale)->parseKey($key) 

// read from json file, and fallback to structured if not found
__() --> return app('translator')->getFromJson($key, $replace, $locale);  

something like that

from laravel-translatable-string-exporter.

functions don't work the same

Ah Okay. Good to know. Thanks.

from laravel-translatable-string-exporter.

if you don't mind i will hold this issue open for a while. i may add my solution when have some time or maybe somebody will come up with their own.

regards

from laravel-translatable-string-exporter.

Just added the 'exclude-translation-keys' option to the config file https://github.com/kkomelin/laravel-translatable-string-exporter/blob/master/config/laravel-translatable-string-exporter.php#L40 which allows to ignore/exclude short translation keys from JSON export, so you may try to use both translation approaches together.

from laravel-translatable-string-exporter.