-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Discovery addon: component creation based on the monolingual template or new base #2084
Comments
Hi @nijel, how complex it is to implement this enhancement ? Where should I start if I want to have a try ? |
The discovery code is in weblate/trans/discovery.py. The problem is that currently it's based on assumption it detects translated files, so it will need some adjustments to work in this case as well. |
With the limited knowledge of Python/Django I have, I gave up ! But found a workaround, while I'm adding a template.pot file for new component, I'm also creating a file test.po which will be matched by the regex. |
Same request here, i create a fake fr.po file by copying the pot file, and do it for thousands of files (the fedora documentation: https://docs.stg.fedoraproject.org/en-US/localization/). |
This issue has been added to backlog. It is not scheduled on our road map, but it might be eventually implemented. In case you desperately need this feature, please consider helping or funding the development. |
I'm also interested in this feature; I wonder if potentially msgmerge add-on could be a place for implementing that behavior (although this way it would be more difficult to configure it probably). |
Currently, the discovery addon creates automatically components if the specified regular expression matches translation files.
In our implementation, the .pot files are generated automatically. But in some cases, there isn't any translations file. It means that a developer must push a translation file for the component to be created.
The idea would be to create the component if the .pot file is found. Then, any translators (even not a programmer) could start a new translation.
Thanks
The text was updated successfully, but these errors were encountered: