-
-
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
Missing documentation: How to manually update .pot file? #4962
Comments
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! |
In case you want to replace single file, use "Replace existing translation file" on upload. For monolingual translation, it will automatically update it. For bilingual you want to use msgmerge to update the translation files. |
I have gettext bilingual setup with 7 translated languages (.po files) + one "messages.pot" file. The When the source code is updated and I run xgettext to include new 'msgid' strings into messages.pot, how I'm supposed to get all languages to have empty translations for the new strings? Is the expected way to really use If this is indeed the expected workflow, it would deserve a paragraph or two in the official documentation. I would have expected some UI where I can drop the new messages.pot file. Preferably at the component level, not on a single language level because the template file is shared by all languages. |
It was hidden somewhere deep in the user docs. Make it prominent top level document as it describes the basics. Issue #4962
Yes, with traditional Gettext workflow, you are supposed to run msgmerge. See https://docs.weblate.org/en/latest/devel/gettext.html or https://www.gnu.org/software/gettext/manual/html_node/Overview.html |
Do you understand that in my opinion the weblate UI should have different UI for sending the template (shared between all languages) and another UI for sending the translation for a single language? Creating a new component does already work but updating existing component to use new messages.pot file has usability problems in the Weblate UI in my opinion. |
When pot is present, the source translation now has a filename. Issue #4962
The interface is there on the source language. I've just noticed that there is a bug that it doesn't show the "Update source strings" in some situations: 42bc1bc |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed soon if no further action occurs. Thank you for your contributions! |
Describe the issue
I'm trying to use Weblate without trusting it to access the real git repository I'm using (neither push nor pull). I was able to submit existing messages.pot and partial localization .po files using the zip package upload while adding a component.
However, the method to update the messages.pot without using git repository connection is non-existant or the UI is hidden so well that I cannot find it.
I already tried
To Reproduce
Steps to reproduce the behavior:
There appears no way to upload a new messages.pot file when I add new base strings. If the only supported method is to always create new component without version control connection this should be documented.
My intent is to submit new messages.pot into weblate and collect modified translations using "Download translation files as ZIP file" from the component view.
Server configuration and status
$ lsb_release -d
Description: Ubuntu 20.04.1 LTS
$ pip show weblate
Name: Weblate
Version: 4.3.2
Summary: A web-based continuous localization system with tight version control integration
Home-page: https://weblate.org/
The text was updated successfully, but these errors were encountered: