mapbox / mapbox/mapbox-plugins-android

Place plugin translation issue

Open
#1,052 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
242
Forks
116
PR merge metrics
No merged PRs in 30d

Description

My country has several languages that they are spoken in some parts of the country, but the main one is Spanish, the problem is that some (not all) streets in the region of Madrid (where they only speak Spanish) are translated as "Carrer Manises" (In Catalan language, only spoken in Catalonia) when the real name of the street is "Calle Manises", we could solve this in the map view, but the autocomplete search shows Carrer. We set the language in PlaceOptions builder as "es" and "en-GB" but the problem still there.
I can't access to the suggestions to change these strange situations. Can I do something to solve this? or I have to just say sorry to my customers because here, those mistakes are controversial.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the autocomplete result using the PlaceOptions builder with languages "es" and "en-GB", comparing it with the map view for the Madrid street example. Trace the autocomplete path and determine whether the incorrect "Carrer" result is produced by the plugin or its place data; done means the Spanish street name is returned consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile, search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.