-
-
Notifications
You must be signed in to change notification settings - Fork 2.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
Accented characters allowed as DBF columns #23527
Labels
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
Data Provider
Related to specific vector, raster or mesh data providers
Comments
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Giovanni Allegri (@giohappy) DBF standard defines ISO8859-1 as the default (and theorically the only accepted) encoding. We should guarantee support at least for this encoding... |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Paolo Cavallini (@pcav) Still true in QGIS 3
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
Data Provider
Related to specific vector, raster or mesh data providers
Author Name: Paolo Cavallini (@pcav)
Original Redmine Issue: 15604
Affected QGIS version: 3.0.0
Redmine category:data_provider
QGIS desktop accepts accented characters as column names for shapefile dbf, and everything seems to work smoothly.
The same files however are not displayed in QGIS sever when that field is used for classification.
I think they should not be allowed anywhere, but if they are, they should work the same in desktop and server.
The text was updated successfully, but these errors were encountered: