Loading…
 lfji
Comment added |
|
|
lfji
Comment added |
@erinfleming I have now investigated the synchronization issue. I compared the locales JSON bundled in the current production build (chrome-immersive-translate-1.27.1.zip) against the Weblate repository, focusing on Russian so you can verify this yourself. None of the Weblate changes are reaching the production build. Examples:
The alert log confirms this: merge conflicts exist on README.md and even image files. The synchronization pipeline is broken at the repository level, and this has nothing to do with whether anyone edits English strings. 3 weeks ago |
|
lfji
Comment added |
@erinfleming Thank you for explaining the situation. It sounds like working directly with the developer would be the faster path. This is fundamentally the developer's responsibility; accounting for upstream synchronization is beyond the scope of what we as translators should have to worry about. I have already compiled a list of 390 items that need correction, based on the JSON file managed in Weblate. For some reason, bulk updating via JSON file upload did not work for the English language, so I have been applying changes one by one through the UI. I have already updated 250 of them. The fact that the developer has not taken action may mean I need to present a more concrete proposal for how to proceed, so I intend to draft a message to send to them. 3 weeks ago |
 erinfleming
Comment added |
There is currently no synchronization between Weblate and GitHub. 3 weeks ago |
|
erinfleming
Comment added |
No. The problem is known. The developers haven't fixed the broken synchronization for six months. They initially tried to fix the problem, but then abandoned it. 3 weeks ago |
|
lfji
Comment added |
@erinfleming Are you the official developer of Immersive Translate? The English text contains numerous outdated phrases, inconsistent spellings, and literal translations that are inconsistent with the original Chinese text. Therefore, editing is indeed necessary. If there are any persistent issues, I will consider alternative methods such as directly submitting the JSON file to the developer. 3 weeks ago |
|
erinfleming
Comment added |
Changing English and Chinese languages is prohibited, as they are the primary languages! This will cause problems with synchronization later. 3 weeks ago |
|
erinfleming
Comment removed |
Comment removed
3 weeks ago
|
|
erinfleming
Comment added |
It is forbidden to change English and Chinese languages, as they are the main ones! 3 weeks ago |
|
erinfleming
Translation reverted |
|
erinfleming
Source string comment
Changing English and Chinese languages is prohibited, as they are the primary languages! This will cause problems with synchronization later.
lfji
Source string comment
@erinfleming Are you the official developer of Immersive Translate? The English text contains numerous outdated phrases, inconsistent spellings, and literal translations that are inconsistent with the original Chinese text. Therefore, editing is indeed necessary. If there are any persistent issues, I will consider alternative methods such as directly submitting the JSON file to the developer.
erinfleming
Source string comment
No. The problem is known. The developers haven't fixed the broken synchronization for six months. They initially tried to fix the problem, but then abandoned it.
erinfleming
Source string comment
There is currently no synchronization between Weblate and GitHub.
lfji
Source string comment
@erinfleming Thank you for explaining the situation. It sounds like working directly with the developer would be the faster path. This is fundamentally the developer's responsibility; accounting for upstream synchronization is beyond the scope of what we as translators should have to worry about. I have already compiled a list of 390 items that need correction, based on the JSON file managed in Weblate. For some reason, bulk updating via JSON file upload did not work for the English language, so I have been applying changes one by one through the UI. I have already updated 250 of them. The fact that the developer has not taken action may mean I need to present a more concrete proposal for how to proceed, so I intend to draft a message to send to them.
lfji
Source string comment
@erinfleming I have now investigated the synchronization issue. I compared the locales JSON bundled in the current production build (chrome-immersive-translate-1.27.1.zip) against the Weblate repository, focusing on Russian so you can verify this yourself.
None of the Weblate changes are reaching the production build. Examples:
- "add" in production: "увеличить" ("to increase"). On Weblate: "Добавить" ("Add"). Not picked up. https://weblate.immersivetranslate.com/translate/immersive-translate/extension/ru/?checksum=eb1aa57228af5c3d
- "about" in production: "по отношению к" ("in relation to"). On Weblate: "О приложении" ("About the app"). Not picked up. https://weblate.immersivetranslate.com/translate/immersive-translate/extension/ru/?checksum=92959093571d1319
The alert log confirms this: merge conflicts exist on README.md and even image files. The synchronization pipeline is broken at the repository level, and this has nothing to do with whether anyone edits English strings.
lfji
Source string comment
@erinfleming With that in mind: you are a translator, the same as I am. You do not have the authority to "prohibit" other translators from editing any language, and reverting my corrections does not protect synchronization, because there is no functioning synchronization to protect.
@erinfleming With that in mind: you are a translator, the same as I am. You do not have the authority to "prohibit" other translators from editing any language, and reverting my corrections does not protect synchronization, because there is no functioning synchronization to protect.
3 weeks ago