-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Locale problem and support for UTF-8 file names #721
Comments
Would be be fine to add
Without it I have some errors with large file names sync. This is worsened by another problem: something like ".ocTransferId1997286732.part" is added while ownCloud client tries upload file. |
Hey, I was able to fix said problem by adjusting the locale inside of the container from
It would be lovely if an active maintainer could actually implement the locale setting directly into the Dockerfile, so that this has not to be done manually afterwards and to prevent a lot of confusion. |
@kurzdev do you want to PR this small change? |
@pierreozoux Sure, do you want me to just edit the template Dockerfiles or the Dockerfiles for versions 19.0, 20.0 and 21.0 as well? |
I implemented @QuAzI's method of doing things as it seems more appropriate for the general public to not set the locale more specific than it has to be. As I stated in the pull request, this works only on debian-based images. |
Thanks a lot @kurzdev :) |
@ricardojlrufino did docker-library/php#1187 fix your issue? |
Old tweak (good to know, thanks @QuAzI #721 (comment) EDIT: |
I have the same problem, but I cant fix it editing my env. Here is my Compose:
I dont know how to fix it, I have it in OMV6 running on a Raspberry Pi 4 and I already set the locale.gen to de_DE.UTF-8, also the intl_defaults in php.ini. Still not able to sync files with ä ö ü characters in it. |
Used names of files and folders with accents (Brazil pt_BR). I had to set the chart and set the environment variables.
To work I had to add these environment variables:
Can you add this by default to avoid future problems?
The text was updated successfully, but these errors were encountered: