Téléverser vers blender/script/modules/bl_i18n_utils #109200

The title does not describe what this does.
You haven’t added any description to the pull request.
You haven’t closed the other PR that this one replaces.
All lines have changed in locale/languages, as can be seen from the diff (the Files Changed tab at the top of this page). I haven’t checked out the change but I suspect it’s a line ending issue, probably using DOS line endings when Blender uses UNIX.
You added a duplicate file: script/modules/bl_i18n_utils/settings.py (the existing file was in scripts with an s).

If you haven’t already, please read this page on the wiki.

I’m guessing you are using this web interface, Gitea, to upload your changes. While this works in theory, it can lead to this kind of issues so I strongly advise you to learn git if you haven’t already. It would at least help solve the line ending and file renaming issues.

In addition, I still don’t agree with the basic premise of this PR, but since I am not the one who can approve or reject it since I can’t merge pull requests, my opinion may not be so important. Anyway, I’ll still explain it below.

In #109173, I wrote:

the reason I haven’t fixed them myself is that I don’t speak those languages and I want to have feedback from people who actually speak the language, instead of just relying on information found on the Internet that could be wrong. This happened for instance with Estonian: I thought it was Eesti, but it turned out to be Eesti keel.

So my question is: do you really have a very good proficiency for all of these languages? If not, I’d rather wait until we get confirmations from native or at least very proficient speakers, because introducing a new error gives no benefit over the current situation.

And you replied:

For my part, I do not speak any of its languages. However, I think we can do an update and add new fixes afterwards if necessary, because that way we can get direct feedback from anyone who hasn't seen this PR. I have no problem to worry about any updates, you just have to mention me so that I know.

To me, making a change hoping for it to draw attention to it even if it may be wrong is a bad approach. The right one would be in my opinion to reach out to users or developers, maybe through the devtalk or Blender Artists forums, and get confirmation from actual speakers that the change is actually an improvement. The reason I haven’t is that I had already tried through blender.chat, and I didn’t consider this a very urgent change. But feel free to do it if you believe it’s worth it.

Hi, thank you but there are still issues with this PR: - The title does not describe what this does. - You haven’t added any description to the pull request. - You haven’t closed the other PR that this one replaces. - All lines have changed in locale/languages, as can be seen from the diff (the _Files Changed_ tab at the top of this page). I haven’t checked out the change but I suspect it’s a line ending issue, probably using DOS line endings when Blender uses UNIX. - You added a duplicate file: script/modules/bl_i18n_utils/settings.py (the existing file was in script***s*** with an `s`). If you haven’t already, please read [this page](https://wiki.blender.org/wiki/Process/Contributing_Code) on the wiki. I’m guessing you are using this web interface, Gitea, to upload your changes. While this works in theory, it can lead to this kind of issues so I strongly advise you to learn [git]( https://wiki.blender.org/w/index.php?title=Tools/Git) if you haven’t already. It would at least help solve the line ending and file renaming issues. --- In addition, I still don’t agree with the basic premise of this PR, but since I am not the one who can approve or reject it since I can’t merge pull requests, my opinion may not be so important. Anyway, I’ll still explain it below. In #109173, I wrote: > the reason I haven’t fixed them myself is that I don’t speak those languages and I want to have feedback from people who actually speak the language, instead of just relying on information found on the Internet that could be wrong. This happened for instance with Estonian: I thought it was Eesti, but it turned out to be Eesti keel. > So my question is: do you really have a very good proficiency for all of these languages? If not, I’d rather wait until we get confirmations from native or at least very proficient speakers, because introducing a new error gives no benefit over the current situation. And you replied: > For my part, I do not speak any of its languages. However, I think we can do an update and add new fixes afterwards if necessary, because that way we can get direct feedback from anyone who hasn't seen this PR. I have no problem to worry about any updates, you just have to mention me so that I know. To me, making a change hoping for it to draw attention to it even if it may be wrong is a bad approach. The right one would be in my opinion to reach out to users or developers, maybe through the devtalk or Blender Artists forums, and get confirmation from actual speakers that the change is actually an improvement. The reason I haven’t is that I had already tried through blender.chat, and I didn’t consider this a very urgent change. But feel free to do it if you believe it’s worth it.

				`@ -0,0 +1,737 @@`
				`# SPDX-License-Identifier: GPL-2.0-or-later`

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Téléverser vers blender/script/modules/bl_i18n_utils #109200

Pull request closed