Remove all translations for obsidian-tasks-plugin - 删除所有 obsidian-tasks-plugin 的翻译文件。

[claremacrae]

As I understand it, this plugin modifies the source-code of installed plugins.

I would love to accept a well-written PR to introduce i18n in to Tasks, but I am absolutely not willing to do user support on modified code, that I have not run automated tests on.

Please remove all translation files for obsidian-tasks-plugin, and do not re-introduce them for future releases.

Thank you in advance.

[claremacrae]

据我了解，此插件会修改已安装插件的源代码。

我很乐意接受一份写得很好的 PR，将 i18n 引入 Tasks，但我绝对不愿意对修改后的代码进行用户支持，因为我还没有对其进行过自动化测试。

请删除 obsidian-tasks-plugin 的所有翻译文件，并且不要在将来的版本中重新引入它们。

提前谢谢您。

[claremacrae]

Just to be clear, I would be willing to make time to work - via pair-programming - with someone experienced in internationalisation to incorporate the translations in the Tasks plugin, in a way that will enable translations to other languages in future as well.

需要明确的是，我愿意花时间通过结对编程与国际化方面经验丰富的人员合作，将翻译合并到任务插件中，这样将来也可以翻译成其他语言。

[claremacrae]

These are the references to the plugin's ID:

这些是对插件 ID 的引用：

https://github.com/search?q=repo%3A0011000000110010%2Fobsidian-i18n%20obsidian-tasks-plugin&type=code

[dangehub]

You need not do user support on modified code. The user agreement that pops up when the i18n plugin starts states that users should be aware that modifying the source code to implement translations may lead to errors. They should not report any bugs to the original plugin author.

4. If you find that certain functions of the original plugin are affected and fail after translating using this plugin, please uninstall and reinstall the original plugin, and then check again if the functions have returned to normal. If the problem still exists, it can be determined that the problem is with the original plugin.Avoid disturbing the original author due to translation problems.
   (Important! Important! Important!)

[zenozero-dev]

关于插件的国际化问题，我想分享以下几点个人见解：
Regarding the internationalization of the plugin, I would like to share the following personal insights:

一、我对Obsidian插件的国际化体验感到失望，似乎官方和开发者并未充分重视插件的国际化（I18N）工作。
1、 I am disappointed with the internationalization experience of Obsidian plugins, as it seems that the official team and developers have not given sufficient attention to the internationalization (I18N) efforts of the plugins.

二、虽然提交Pull Request（PR）被看作是一种解决方案，但我们必须考虑到，我们用户群体中使用小语种的用户比例。在这些用户中，又有多少人具备理解和修改插件代码的能力？对于大多数用户来说，这种解决方案并不现实，因为它要求用户不仅要有技术背景，还要能够投入大量时间参与开源项目的维护。
2、While submitting Pull Requests (PRs) is considered a solution, we must consider the proportion of our user base that uses minority languages. Among these users, how many have the ability to understand and modify plugin code? For most users, this solution is not practical as it requires not only a technical background but also a significant amount of time to participate in the maintenance of open-source projects.

三、在当前情况下，除了实时修改DOM，是否有比直接修改源代码更优的解决方案？对于那些不熟悉代码的用户来说，提交Pull Request（PR）无疑是一个难以克服的挑战。
3、In the current situation, aside from real-time DOM manipulation, is there a better solution than directly modifying the source code? For users who are not familiar with coding, submitting Pull Requests (PRs) is undoubtedly a significant challenge.

四、这种现状不仅忽视了小语种用户的实际需求，也限制了插件的发展潜力和普及范围。我期望官方和开发者能够更加重视这一问题，采取更为全面和包容的措施，确保每一位用户都能获得平等且优质的使用体验。
4、This state of affairs not only overlooks the actual needs of users of minority languages but also limits the potential and reach of the plugin. I hope that the official team and developers can pay more attention to this issue and take more comprehensive and inclusive measures to ensure that every user can have an equal and high-quality experience.

五、如果可能的话，我希望能够将我的这些看法传达给开发者和Obsidian官方，以便他们能够更深入地理解这些问题，并采取行动，推动插件国际化的进程，使其能够服务于更广泛的用户群体。
5、If possible, I would like to convey these thoughts to the developers and Obsidian officials, so that they can gain a deeper understanding of these issues and take action to advance the internationalization process of the plugin, serving a broader range of users.

[zenozero-dev]

既然情况如此，我似乎已经没有什么可说的了。如果官方没有强制要求你们内置国际化支持（i18n），那么作为插件开发者的你们似乎也没有主动去开发一套内置的i18n系统，而是在等待社区的Pull Request（PR）。难道说，如果没有人提交PR，你们就打算一直保持原语言状态，不进行任何更新吗？哪怕你们能提供一个基础的翻译文件作为内置，其他语言的用户也可以根据这个基础进行翻译工作。但看起来，你们选择了不采取任何行动。
Given the situation, it seems there's little more for me to say. If the official stance doesn't enforce the implementation of built-in internationalization support (i18n), then as plugin developers, it appears you haven't proactively developed an internal i18n system and are instead awaiting Pull Requests (PRs) from the community. Is it the case that without a PR, you intend to maintain the plugin in its original language without any updates? Couldn't you provide a basic translation file as a built-in reference, allowing users of other languages to translate based on that foundation? However, it seems you have chosen to take no action.

[zenozero-dev]

如果您期望我撤回对贵插件的支持，那么请您亲自着手将国际化（i18n）功能纳入您的插件之中。一旦您完成了这项工作，我自然会毫不迟疑地将现有的译文从流通中撤下。
If you expect me to withdraw my support for your esteemed plugin, then I kindly request that you take the initiative to incorporate internationalization (i18n) features into your plugin. Once this task is accomplished, I will, without hesitation, proceed to withdraw the existing translations from circulation.

[claremacrae]

You need not do user support on modified code. The user agreement that pops up when the i18n plugin starts states that users should be aware that modifying the source code to implement translations may lead to errors. They should not report any bugs to the original plugin author.

Thank you for this.

4. If you find that certain functions of the original plugin are affected and fail after translating using this plugin, please uninstall and reinstall the original plugin, and then check again if the functions have returned to normal. If the problem still exists, it can be determined that the problem is with the original plugin.Avoid disturbing the original author due to translation problems.
   (Important! Important! Important!)

I installed the plugin and put this screenshot in to ChatGPT to get a translation:

... and it mostly matches your translation...

Except that it did not include "avoid disturbing the original author due to translation problems.".

[dangehub]

You need not do user support on modified code. The user agreement that pops up when the i18n plugin starts states that users should be aware that modifying the source code to implement translations may lead to errors. They should not report any bugs to the original plugin author.您无需对修改后的代码提供用户支持。 i18n 插件启动时弹出的用户协议指出，用户应该意识到修改源代码来实现翻译可能会导致错误。他们不应向原始插件作者报告任何错误。

Thank you for this.  谢谢你。

> 4. If you find that certain functions of the original plugin are affected and fail after translating using this plugin, please uninstall and reinstall the original plugin, and then check again if the functions have returned to normal.如果您发现使用本插件翻译后，原插件的某些功能受到影响而失败，请卸载并重新安装原插件，然后再次检查功能是否恢复正常。 If the problem still exists, it can be determined that the problem is with the original plugin.Avoid disturbing the original author due to translation problems.如果问题依然存在，则可以确定是原插件的问题。避免因翻译问题打扰原作者。 > (Important! Important! Important!)（重要！重要！重要！）

I installed the plugin and put this screenshot in to ChatGPT to get a translation:我安装了该插件并将此屏幕截图放入 ChatGPT 中以获取翻译：

... and it mostly matches your translation......它大部分符合你的翻译...

Except that it did not include "avoid disturbing the original author due to translation problems.".只不过没有包含“避免因翻译问题打扰原作者”。

This words means that "avoid disturbing the original author due to translation problems.", Chinese users can understand it.

GPT cannot translate it accurately.

We are considering how to emphasize this point more strongly, and ensuring the harmonious operation of the community is always our top priority.

[claremacrae]

At first, I was impressed by the effort put into this translations plugin. I had decided to:

1. Reply to some of the comments here.
2. Make adding translation support to Tasks a much higher priority.

起初，我对这个翻译插件所付出的努力印象深刻。我决定：

1. 在这里回复一些评论。
2. 优先考虑为任务添加翻译支持。

---

Then I saw this message:

然后我看到了这条消息：

如果您期望我撤回对贵插件的支持，那么请您亲自着手将国际化（i18n）功能纳入您的插件之中。一旦您完成了这项工作，我自然会毫不迟疑地将现有的译文从流通中撤下。

If you expect me to withdraw my support for your esteemed plugin, then I kindly request that you take the initiative to incorporate internationalization (i18n) features into your plugin. Once this task is accomplished, I will, without hesitation, proceed to withdraw the existing translations from circulation.

---

Unfortunately, this message has undone the goodwill created by your earlier replies and by the translators' hard work.

No, I cannot agree to such demands.

不幸的是，这条消息已经化解了您之前的回复和翻译人员的辛勤工作所建立的善意。

不，我不能同意这样的要求。

---

However, as a gesture of goodwill despite this message, I am willing to offer a compromise:

I plan to start preparing the next Tasks release on Thursday, 26th December.

If, and only if, the Tasks translations are removed from this plugin before that date, I will:

1. Pause the next release.
2. Add a translation framework to the Tasks plugin.
3. Allow 2–3 days for someone from your project to migrate the translations into the new framework.
4. Then release the updated version of Tasks.

The decision is now yours. Please let me know what you choose.

然而，尽管有这样的信息，作为一种善意的姿态，我愿意提供一个妥协：

我计划在 12 月 26 日星期四开始准备下一个任务版本。

当且仅当在该日期之前从该插件中删除任务翻译时，我才会：

1. 暂停下一个版本。
2. 在任务插件中添加翻译框架。
3. 给项目中的人员 2-3 天的时间将翻译迁移到新框架中。
4. 然后发布Tasks的更新版本。

现在决定权在你了。请让我知道您的选择。

[zenozero-dev]

既然我们都致力于提升插件用户体验，我又怎能拒绝呢？（我们将会移除对贵插件的所有提及）
Since we are all committed to enhancing the user experience of the plugin, how could I refuse? (We will remove all references to your plugin.)

我之所以感到情绪上的波动，您要知道，我投入了几个月的时间来学习和编写代码，以实现插件的功能。然而，在你们的讨论中，你们似乎并没有充分考虑到插件国际化的必要性，甚至提出了一些可能会让我之前的努力变得无用的想法。
I'm experiencing emotional fluctuations, and you should understand that I've dedicated several months to learning and coding to achieve the functionality of the plugin. However, in your discussions, it seems that the necessity of internationalizing the plugin has not been fully taken into account, and some ideas have even been proposed that might render my previous efforts futile.

我们并非编程专家，而是一群热爱记录的普通用户。我们库中的大部分内容都是由不懂编程的人，通过不断尝试和提取内容，自行判断哪些是文本，经过反复实验才得到的成果。作为审核人员，我们同样不是专业的程序员，对于某些代码修改也难以理解。我们的任务是测试别人修改后的内容，只要功能正常，我们就会批准通过。因此，源代码的修改是难以避免的，除非官方亲自介入进行维护。
We are not programming experts, but ordinary users who are passionate about recording. Most of the content in our library is the result of non-programmers who, through continuous trials and content extraction, have determined what is text on their own and achieved success through repeated experiments. As reviewers, we are also not professional programmers and find it difficult to understand some code modifications. Our task is to test the content modified by others; as long as the functionality is normal, we will approve it. Therefore, modifications to the source code are inevitable unless the official team steps in to maintain it themselves.

[claremacrae]

Hello, I just wanted to reassure you that I have not forgotten this work. The work I was already doing is just taking longer than I had expected/hoped.
你好，我只是想让你放心，我没有忘记这项工作。 我已经在做的工作只是比我预期/希望花费的时间更长。

I am still going to add the translation component before the next release.
我仍然会在下一个版本之前添加翻译组件。

I will let you know when I start on the translation work...
当我开始翻译工作时我会通知你......