{"comment":{"url":"https://api.github.com/repos/MoonchildProductions/pale-moon-localization/comments/29392398","html_url":"https://github.com/MoonchildProductions/pale-moon-localization/commit/e422706591b374de0e74ba03b5928d1b5b69b362#commitcomment-29392398","id":29392398,"node_id":"MDEzOkNvbW1pdENvbW1lbnQyOTM5MjM5OA==","user":{"login":"MikkCZ","id":3941344,"node_id":"MDQ6VXNlcjM5NDEzNDQ=","avatar_url":"https://avatars1.githubusercontent.com/u/3941344?v=4","gravatar_id":"","url":"https://api.github.com/users/MikkCZ","html_url":"https://github.com/MikkCZ","followers_url":"https://api.github.com/users/MikkCZ/followers","following_url":"https://api.github.com/users/MikkCZ/following{/other_user}","gists_url":"https://api.github.com/users/MikkCZ/gists{/gist_id}","starred_url":"https://api.github.com/users/MikkCZ/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MikkCZ/subscriptions","organizations_url":"https://api.github.com/users/MikkCZ/orgs","repos_url":"https://api.github.com/users/MikkCZ/repos","events_url":"https://api.github.com/users/MikkCZ/events{/privacy}","received_events_url":"https://api.github.com/users/MikkCZ/received_events","type":"User","site_admin":false},"position":null,"line":null,"path":null,"commit_id":"e422706591b374de0e74ba03b5928d1b5b69b362","created_at":"2018-06-17T14:39:06Z","updated_at":"2018-06-17T14:39:06Z","author_association":"NONE","body":"> it has nothing to do with branding\r\n\r\nBut I never said it has. Feature name are not really brands, that's what we can agree on.\r\n\r\n> they are named features and specific implementations, not generic functions.\r\n\r\nBut this argument about named features being \"the features\" and specific implementations distinguishing the application from other, this argument sounds like a definition of a brand.\r\n\r\n>  In the world of translation, there is and will always be a rift between the technical and the linguistic, whether it is \"translating too much\" or wanting to apply linguistic rules to non-document terms...\r\n\r\nI would like to specifically state here, that in my eyes this is not about translation, but about localization. One can perfectly translate the feature names using any case you want. But it's better to have a product localized, not just translated. By localization I mean to adjust the product for consistency with both language rules and conventions of the specific locale.\r\n\r\n---\r\n\r\nSpeaking in general, are your guidelines for localization specified somewhere, so I can have a look? I would prefer to lead discussions about something documented, not about individual diffs that appear in the repository. Or at least to be able to consider, if it still makes sense for me to watch changes in Pale Moon localization with the potential to fix potentially identified issues in the Czech l10n of Firefox too, or to give feedback about Czech l10n of Pale Moon?"}}
{"actor":{"display_login":"MikkCZ"}}