-
-
Notifications
You must be signed in to change notification settings - Fork 959
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
HTML filter: existing translations are not imported #7929
Comments
Might be addressed by #7928 |
@nijel Thanks for the prompt reply. I'd like to test your changes. Is it enough to apply them inside the docker container, or do I have to restart any of the services running as well? |
Yes, you need to restart them. The docker container uses supervisor inside. |
Thank you for your report; the issue you have reported has just been fixed.
|
@nijel This commit does unfortunately not resolve the issue. I applied your changes and restarted the container. The issue is still the same. Can you please test yourself with the testcase I provided? |
I created a test-repository: https://github.com/dleidert/weblate-issue-7929-test |
If you restart the container, any changes in it are discarded |
@nijel I adjusted |
@nijel Do you have any feedback for me? Were you able to test it yourself with the test-case I supplied? This issue is really a showstopper because we have quite a lot of already translated HTML content and we "loose" it all on import. If this can or is fixed, this would mean a lot to us, and it would spare us that we have to manually use html2po and po2html to deal with translating HTML content. |
If you do restart the container, any changes are discarded. The easiest approach to test these changes is to use |
@nijel I tested today with the |
Thank you for your report; the issue you have reported has just been fixed.
|
Thanks for providing the test files, it should be now fixed for good. |
@nijel Tested again. This time it worked. Thanks! |
Describe the issue
I have a few HTML files in multiple languages (a testcase is attached). When I create a component for a file, for which translations already exist, those existing translations are dismissed except if they are the same word/phrase as in the base file, in which case they are marked as "needs editing". Consider these two files
main.en.html
andmain.de.html
If I import them as a component using the HTML filter, the existing translations for the paragraphs have been dismissed. Instead, I expect them to be there, but maybe marked as "needs editing".
I already tried
Steps to reproduce the behavior
Use the two files shown above, add them to a repository, create a new translation project. For this project, create a component and use the HTML filter and the existing main.*.html files. Check the status of the German translation after finishing the compionent creation. The title string is shown in the user interface and marked as "needs editing". For the two paragraphs, they are shown as untranslated with no German string whatsoever.
Expected behavior
The component should contain three translatable strings, and all strings should already have a German translation in this case. These strings could be marked as "needs editing", but they must not be empty.
Screenshots
Fiilter:
Result:
Translation is missing:
Exception traceback
No response
How do you run Weblate?
Docker container
Weblate versions
Weblate deploy checks
Additional context
No response
The text was updated successfully, but these errors were encountered: