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

Improve translations and label generation #30

Merged
merged 10 commits into from
Oct 14, 2016
Merged

Conversation

vesameskanen
Copy link
Member

@vesameskanen vesameskanen commented Oct 4, 2016

  • lots of new translations for NLSFI and OSM categories
  • 'default' is no longer used as the language for translations. It represents a state where we could not figure out the language, and API should use the preferred real language
  • name extensions for label generator no longer overwrite the original name (makes testing more predictable)
  • sv neighbourhood and street name translations added

Enlish version is now used as a category in nlsfi import
- use lowercase for NLSFI categories
- drop 'default' translations (it is not a language)
- add a couple of new translations
Problematic 'default' language should be handled by api logic, not by
repeating fi translations.
For example, API will not try to return results in 'ru' language
unless it is explictly configured in pelias.json config file.
'default' is not a real language, but represents a state where
we do not know the language. In such a case, it is wisest to
keep the original preferences (api param or lang[0] of pelias config).
Instead, use a new expandedName field to store the more detailed
name version. Modifying the actual name can break fuzzy and unit tests.
This fixes mixed names such as 'Borgbacken, Tivolikuja 1, Helsingfors'
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.

2 participants