-
-
Notifications
You must be signed in to change notification settings - Fork 958
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add gettext add-on to linked components #8564
Comments
If you create the components manually, you have to manually install the add-ons as well. For the component discovery there is an option to clone add-ons from the base component. |
Also, if you want the Gettext add-on configured in all cases, this might be for you: https://docs.weblate.org/en/latest/admin/config.html#default-addons |
This would only apply to newly created components. Is there a chance to add it to exisiting ones? We have a lot of them :-) |
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you! |
This issue has been automatically marked as stale because there wasn’t any recent activity. It will be closed soon if no further action occurs. Thank you for your contributions! |
Describe the issue
It seems the gettext add-on needs to be installed manualy for each component in a project. For projects with component discovery active it would be very helpful to have the plugin also active for the linked components to e.g. prevent line wrapping in all PO-files of a project.
I already tried
Steps to reproduce the behavior
-> The gettext add-on is only active for the master component
Expected behavior
The gettext add-on should be installed for all linked components
Screenshots
No response
Exception traceback
No response
How do you run Weblate?
weblate.org service
Weblate versions
No response
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: