The Database Hub | Back4App
The Database Hub | Back4App
How it works
  • Log In
  • Sign Up

  1. Back4App
  2. World Continents, Countries, and Cities
Public

1210
5628
1210
5628
  • DatabaseDatabase
  • GraphQL API PlaygroundAPI Playground
  • Get Started GuideGet Started
  • IssuesIssues
  • ContributorsContributors
  • Database
    Database
    GraphQL API Playground
    API Playground
    Get Started Guide
    Get Started
    Contributors
    Contributors

  1. IssueOpen
  2. don't support utf-8

New IssueNew

cvalera.id commented this issue on Jun 2020

When I try to get provinces from argentina or some another south american country I get errors..

eg: Gal�pagos (should be Galápagos)

george commented this issue on Jun 2020

Thanks for reporting the issue! We corrected the special characters issue from Argentina. Can you please check on your end?

cvalera.id commented this issue on Jun 2020

I've just checked but it's still the issue... for example for peru, ecuador, etc.. I think almost all south american countries which have special characters like áéíóú or ñ have those issue

leogt-15 commented this issue on Sep 2020

Hello! The same is happening with Portuguese provinces (and only provinces, the cities are ok). AFAICT, the issue relies on encoding. You're probably encoding the province names in Latin1, so some characters not supported by Latin1 are turned into �. Then, you're sending them along with the entire JSON object (which by default is UTF-8), which makes it impossible to decode the correct values of those characters because by then they are just � (\uFFFD). If you could change the string encoding of province names to UTF-8 instead of Latin1, that may solve this issue for every province name.

https://stackoverflow.com/questions/2708958/differences-between-utf8-and-latin1 https://github.com/dart-lang/http/issues/175

alex commented this issue on Sep 2020

Hey @leogt-15! Thank you for your comment and collaboration. We were already aware of that but, as you know, the Database Hub is a collaboration platform and the collaborator that uploaded the Provinces sent the data with that encoding, so we do not hold the original JSON to change the encoding and fix that issue. But, again, as a collaboration platform, anyone is free to join in as a collaborator and fix those. We can fix manually the records if you send us the Object ID of the broken ones and the correct value too.

leogt-15 commented this issue on Sep 2020

I'd be pleased to help. Since I'm using this API, and it's turned out to be one of the best I've found, I can myself collaborate with the changes. I'm just not sure how to do it. Otherwise, I can send you the broken Object IDs.

lnnnews.info commented this issue on Jun 2021

I think when this fix was done, some names broke. For example: Subdivisions_States_Provinces Object ID: EABZS6LIpb Current name: Neuqu_n Correct name: Neuquén

alexb4abr commented this issue on Jun 2021

Hey @lnnnews.info! I corrected that one record. Please let me know if you find more of those.

alexanderrauber commented this issue on Nov 2021

@alexb4abr Colombia and Chile still have problems:

Atl�ntico Bol�var C�rdoba

Biob�o Valpara�so

Please enter a comment for this issue.