{"action":"created","issue":{"url":"https://api.github.com/repos/ngx-translate/core/issues/495","repository_url":"https://api.github.com/repos/ngx-translate/core","labels_url":"https://api.github.com/repos/ngx-translate/core/issues/495/labels{/name}","comments_url":"https://api.github.com/repos/ngx-translate/core/issues/495/comments","events_url":"https://api.github.com/repos/ngx-translate/core/issues/495/events","html_url":"https://github.com/ngx-translate/core/issues/495","id":218924739,"node_id":"MDU6SXNzdWUyMTg5MjQ3Mzk=","number":495,"title":"Why ngx-translate exists if we already have built-in Angular2+ i18n ?","user":{"login":"amineparis","id":12094425,"node_id":"MDQ6VXNlcjEyMDk0NDI1","avatar_url":"https://avatars3.githubusercontent.com/u/12094425?v=4","gravatar_id":"","url":"https://api.github.com/users/amineparis","html_url":"https://github.com/amineparis","followers_url":"https://api.github.com/users/amineparis/followers","following_url":"https://api.github.com/users/amineparis/following{/other_user}","gists_url":"https://api.github.com/users/amineparis/gists{/gist_id}","starred_url":"https://api.github.com/users/amineparis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/amineparis/subscriptions","organizations_url":"https://api.github.com/users/amineparis/orgs","repos_url":"https://api.github.com/users/amineparis/repos","events_url":"https://api.github.com/users/amineparis/events{/privacy}","received_events_url":"https://api.github.com/users/amineparis/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":97,"created_at":"2017-04-03T12:58:00Z","updated_at":"2018-12-20T15:58:41Z","closed_at":"2017-04-03T15:06:08Z","author_association":"NONE","body":"why should someone choose this package instead of the official i18n module ?"},"comment":{"url":"https://api.github.com/repos/ngx-translate/core/issues/comments/449046000","html_url":"https://github.com/ngx-translate/core/issues/495#issuecomment-449046000","issue_url":"https://api.github.com/repos/ngx-translate/core/issues/495","id":449046000,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0OTA0NjAwMA==","user":{"login":"ocombe","id":265378,"node_id":"MDQ6VXNlcjI2NTM3OA==","avatar_url":"https://avatars0.githubusercontent.com/u/265378?v=4","gravatar_id":"","url":"https://api.github.com/users/ocombe","html_url":"https://github.com/ocombe","followers_url":"https://api.github.com/users/ocombe/followers","following_url":"https://api.github.com/users/ocombe/following{/other_user}","gists_url":"https://api.github.com/users/ocombe/gists{/gist_id}","starred_url":"https://api.github.com/users/ocombe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ocombe/subscriptions","organizations_url":"https://api.github.com/users/ocombe/orgs","repos_url":"https://api.github.com/users/ocombe/repos","events_url":"https://api.github.com/users/ocombe/events{/privacy}","received_events_url":"https://api.github.com/users/ocombe/received_events","type":"User","site_admin":false},"created_at":"2018-12-20T15:58:41Z","updated_at":"2018-12-20T15:58:41Z","author_association":"COLLABORATOR","body":"For dynamic translations you'll have to bundle the parser with your app (it should work automatically depending on the format of translations that you use).\r\nThe parsers for xlf/xlf2/xtb will be provided by us (since we already have the code in the compiler right now).\r\nBut we are aware that it's a lot of js code to bundle just for that (I think it's at least 10 or 15ko for each parser, because XML sucks!).\r\nWe're thinking about different solutions for that:\r\n- you can bundle the translations at build time, they will be preparsed/optimized and you won't need the parser at runtime, it should also be more efficient. But that doesn't always work, if you're loading the translations from a database for example\r\n- you can use a custom parser, including a json parser which should be very small in terms of size. I'm not sure yet if I'll be authorized to write one for core (but I'm optimist, because there's already an official json format for translations developed by google and called ARB (https://github.com/googlei18n/app-resource-bundle/wiki/ApplicationResourceBundleSpecification), we should be able to reuse that, and it would make sense for us to support that format officially, since it's made by Google!). If not, then I'll write one on my own time anyway, it should be relatively easy and light."}}
{"actor":{"display_login":"ocombe"}}