Page MenuHomePhabricator

Investigate localized wordmark assets
Closed, ResolvedPublic

Description

Investigate the pros and cons of the different options for presenting a localized wordmark for use on:

Options

  1. Maintain a library of workdmark SVGs

We can do this in two ways:
(a) Manually creating SVG asset for each wikipedia, using the full svg asset available in commons here.
(b) Outreach to Community to upload individual wordmark-only assets.
Example of the wordmark for ru.wikipedia.org

pasted_file (75×237 px, 22 KB)

  1. Use the English wordmark with the name of the primary language wikipedia in that language under the wordmark.

We would need have a full list of the language names for all wikis.
Example of the wordmark with Russian underneath

pasted_file (69×235 px, 21 KB)

  1. Investigate use of existing fonts to render the wordmark in an equivalent style as the svg.

There is an existing list of the wordmark in different languages here

Event Timeline

Outcome from spike

Proposed implementation on iOS and Android

  • The English wordmark will be used on initial versions while assets are being generated.
  • Other language wordmarks will not be part of the app, but retrieved only to replace the default English wordmark when that respective Wikipedia is detected as the primary language on the device. This mitigates concerns with app size increase as a result of using localized assets.
  • English wordmark acts as fallback wherever the other language svg asset is not available.

Actions
A separate ticket for creation of assets has been opened as T142426

JMinor subscribed.

This sounds like a good plan.