Missing extension language translation when upgrade

peopleinside

Hi, we hear in the new year.
I hope you are well!

Every time I update Flarum and so extensions I miss my custom translation it.yaml file for many different extensions.
All time I need translate again this and I miss it...

How can I avoid this?
Thank you.

Example I miss my custom translation for:
user bio, disposable email, draft, etc

luceos

peopleinside how did you implement those custom translations?

peopleinside

luceos just creating the it.yaml file into locales duplicate of the en.yaml than translated and clearing cahce from the admin interface of Flarum.

PS: Hi luceos, nice to hear you. Hope you are well 😉

I'm not a developer just the user.
This extension never support Italian so I create the translation for it but I loose all time I upgrade and have to translate from zero all times.

luceos

Are these translations specific to your community and are there only a few? Use linguist. If they can be reused by the community, maybe get involved in translating to the Italian pack openly? If you really want to keep them private and forward compatible, your best bet is using a local extender, I can whip up an example in the morning if you need it.

peopleinside

luceos
I create the it.yaml file for some extension that miss it like user bio, disposable email, draft, etc.

I don't know how I can share and submit this translations I made to the extension so can be added by the developer.
I want maybe know:

How I can send my it translation to the extension developer for be added in future updates?
How I can have the translation of an extension made by me active even if this is not added by the extension developer and avoid my translation is missed on next update?

Use linguist.

If Flarum is updated and this extension is not? Maybe anyway I have to try linguist.

If you really want to keep them private and forward compatible, your best bet is using a local extender, I can whip up an example in the morning if you need it.

Umh don't know what you mean and if something of hard for developers 😀 I will maybe see if with linguist I can solve.

PS: luceos you have added a message to this topic without mention me. I have no notification even in the forum about your new message. Is this a bug with Beta 15?

Also no notification for the roby message. I don't pretend to be notified by email because n mention but a notification in the bell... I created this discussion... some users replied and I don't get any notification even in the forum? Looks like to be not correct to me. On the right I see I'm not following the discussion. In my profile I have disabled "Automatically follow discussions that I reply to" maybe I'm to be forced to activate this.

Installed linguist and seems solve for 90% my issue.
Disposable email is not supported means linguist doesn't allow me to translate and I have text to translate. I will ask support on linguist extensions. Thanks.

rob006 thanks for the tips and the article.
I understand that I can create locale folder than add this locale to extend.php but I have no idea on how translate for example two different extensions. Actually I simply create an it.yaml file inside the extension. The locale folder that you suggest to create is not for a specific extension and I don't see example, in your blog, on how translate two different extensions... for example.

rob006

If you're doing these modification inside of vendor directory, every extension update will overwrite your changes - vendor directory is for dependencies and Composer simply replaces old content with new version downloaded from GitHub. You should add your translations outside of vendor directory, I explained how to do this this on my blog.

rob006

peopleinside You can put translation for all extensions in one file (it.yml).

peopleinside

rob006 and how? I have no idea on how to do.
Consider that actually I copy the en.yaml renaming into it.yaml than just replacing strings.

I can just put all inside it.yaml coping the content of any en.yaml extension putting insdie the new it.yaml?
Maybe...?! I will try , thanks. This will maybe useful for disposable email that is not currently translatable with linguist.

rob006

peopleinside I can just put all inside it.yaml coping the content of any en.yaml extension putting insdie the new it.yaml?

Yes, as long you don't mess with YAML syntax and extensions does not have duplicated keys (most of extensions use extension ID as key prefix, so this should be rare situation).