{"action":"closed","issue":{"url":"https://api.github.com/repos/sprin/client-side-hash-calculator/issues/1","repository_url":"https://api.github.com/repos/sprin/client-side-hash-calculator","labels_url":"https://api.github.com/repos/sprin/client-side-hash-calculator/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/sprin/client-side-hash-calculator/issues/1/comments","events_url":"https://api.github.com/repos/sprin/client-side-hash-calculator/issues/1/events","html_url":"https://github.com/sprin/client-side-hash-calculator/issues/1","id":160251766,"number":1,"title":"Internationalization","user":{"login":"sprin","id":1452117,"avatar_url":"https://avatars.githubusercontent.com/u/1452117?v=3","gravatar_id":"","url":"https://api.github.com/users/sprin","html_url":"https://github.com/sprin","followers_url":"https://api.github.com/users/sprin/followers","following_url":"https://api.github.com/users/sprin/following{/other_user}","gists_url":"https://api.github.com/users/sprin/gists{/gist_id}","starred_url":"https://api.github.com/users/sprin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sprin/subscriptions","organizations_url":"https://api.github.com/users/sprin/orgs","repos_url":"https://api.github.com/users/sprin/repos","events_url":"https://api.github.com/users/sprin/events{/privacy}","received_events_url":"https://api.github.com/users/sprin/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-06-14T18:30:13Z","updated_at":"2016-06-15T02:36:51Z","closed_at":"2016-06-15T02:36:51Z","body":"The application should try to match the user's locale to an available translation. Strings should appear in the language of the user's locale. The user should also be able to select from available languages. The application should fall back to a default locale if the user's locale cannot be matched to a translation. This cannot depend on any special server-side configuration, such as reflecting the `Accept-Language` header.\r\n\r\nI review of existing i18n libraries reveals that there aren't any libraries appropriate for the extremely minimal needs of this application. Most libraries provide support for numbers, currency, dates, and pluralization. This application needs only very simple string translation, so a few custom functions will be sufficient, rather than a bringing in a large library.\r\n\r\nWe can create a function to translate from message ids to localized message strings, which are stored as mappings in a localization object. Each element that will contain localized text can have a message id as an attribute. We can create another function to find and translate all localized elements in the DOM. These functions should cover both cases of translating existing DOM elements on page load and translating dynamically-generated elements."}}
{"actor":{"display_login":"sprin"}}