Skip to content
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

csync_update: ignore remote files that cannot be encoded #6177

Merged
merged 1 commit into from
Nov 23, 2017
Merged

Conversation

ogoffart
Copy link
Contributor

This is mainly for linux, whose local is not UTF-8.
For example, in latin1, it is not possible to encode emoji or chinese character.
If there are such character in the filename, Qt would just save the file using
the replacement character ('?'). Then, on the next sync, client would rename
the files using this replacement character.

Avoid this by ignoring the files which cannot be downloaded because the
filename cannot be represented with the user's locale

Relates to issue #5676 and #5719

This is mainly for linux, whose local is not UTF-8.
For example, in latin1, it is not possible to encode emoji or chinese character.
If there are such character in the filename, Qt would just save the file using
the replacement character ('?'). Then, on the next sync, client would rename
the files using this replacement character.

Avoid this by ignoring the files which cannot be downloaded because the
filename cannot be represented with the user's locale

Relates to issue #5676 and #5719
@ogoffart ogoffart requested review from ckamm and guruz November 21, 2017 13:22
@ogoffart
Copy link
Contributor Author

ogoffart commented Nov 21, 2017

I wonder if this should go in 2.4 or 2.5.
2.4.0 is doing some change in the encoding already, and i'm afraid it can be otherwise seen as a regression by some people if we don't put this patch.

Copy link
Contributor

@ckamm ckamm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like something for 2.4 to me.

@ogoffart ogoffart merged commit 72809ef into 2.4 Nov 23, 2017
@ogoffart ogoffart deleted the encoding branch November 23, 2017 11:51
@guruz guruz added this to the 2.4.0 milestone Nov 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants