-
Notifications
You must be signed in to change notification settings - Fork 94
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
[Bug]: translated readme.md (for the folder) doesn't show when switching language #5953
Comments
Moving to the text repository as the related code is here: https://github.com/nextcloud/text/blob/main/lib/Service/WorkspaceService.php |
@audunmb Thanks for your report. You have a point. We'll need to discuss how best to address this. |
Related: #5446 |
@max-nextcloud is there a workaround until this is fixed? For non english and non technically skilled persons it's currently not possible to add folder descriptions. Update: Just double checked on NC29.0.7 and realized that folder descriptions are now recognized even if those are automatically translated. Can you confirm that this issue was fixed in the meantime? |
@XueSheng-GIT I don't think anything has changed. Here's how I understand the problem:
The user in 2. may be an entirely different user, or the same user after switching the language setting. |
@marcoambrosini I think this is a UX issue - and right now I don't know any way out. Two interests are conflicting here:
I see different options:
Personally I don't like the name |
Some older discussions about it: |
@max-nextcloud From a UX perspective, I think it's best to hide the readme.md file. We can also change the name into something you deem more appropriate. |
One solution could be:
A readme.md in another language would be better than none most of the time. Multilingual users would usually grasp the contents of the readme regardless of language. For some places there should be some more steps in part 2. For instance in Norway where we have two written variations of Norwegian (Nynorsk/Bokmål) which most can read interchangeably, but which register as different languages in a localisation setup. So 2 would be check both NO_nb (bokmål) and NO_nn (nynorsk) before defaulting to English. |
We had some discussion about using a hidden file in the past, but then it is not really discoverable on the desktop. If we consider that acceptable (I don't have a strong opinion there) then we could just go for |
Thanks for the reminder about the desktop Julius. I think we should do the following: Creating folder description:
Checking for readme file:
This preserves the current behavior for existing files, avoids the problem with switching languages and enables hiding the readme file for people who are confused by it. |
Bug description
Readme.md-files are saved as lesmeg.md when I use Nextcloud in Norwegian. Though, when someone uses Nextcloud in English, the lesmeg.md-file is not interpreted as a readme.md-file for that folder, and it is not shown as a description for that folder.
I guess this happens with other languages as well.
Steps to reproduce
Expected behavior
Expected behaviour is that folder descriptions are shown regardless of which language the user has.
I guess the current behaviour is the result of having an option to have translated folder descriptions, but when the result is that folder descriptions aren't shown at all if a user has a different language than what is used for the default description this is a bug.
As in my case, multilingual users will have no problem reading folder descriptions in Norwegian, despite choosing English as the default language (or vice versa).
Installation method
None
Nextcloud Server version
27
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
I'm on a hosted solution by Tab.Digital, so don't have access to all the technical details of the setup. They aren't relevant for this bug.
The text was updated successfully, but these errors were encountered: