Project

General

Profile

Actions

Feature proposal #5267

closed

Implement provider specific language keys

Added by krileon almost 9 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
04 May 2015
Due date:
% Done:

100%

Estimated time:

Description

Language keys are currently generic and shared (e.g. SIGN_UP_WITH_PROVIDER), but should also have a provider specific key. Example as follows.

SIGN_UP_WITH_PROVIDER SIGN_UP_WITH_FACEBOOK
SIGN_UP_WITH_PROVIDER SIGN_UP_WITH_TWITTER

Actions #1

Updated by krileon about 8 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

All language keys with PROVIDER can be more specifically specified replacing PROVIDER with the provider id. Examples as follows.

Generic: PROVIDER_NOT_AVAILABLE
Specific: FACEBOOK_NOT_AVAILABLE

Generic: VIEW_PROVIDER_PROFILE
Specific: VIEW_FACEBOOK_PROFILE

Generic: SIGN_UP_WITH_PROVIDER
Specific: SIGN_UP_WITH_FACEBOOK

Language files will always be parsed with the generic key. Specific keys must be manually specified.

Actions #2

Updated by krileon about 8 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF