- From: chaals via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 May 2021 08:16:12 +0000
- To: public-geolocation@w3.org
**IMHO** This is the forum for development on the API. Making it functional for the world at large is a core part of what W3C expects for any piece of work. So no, this issue being dealt with here isn't a tail wagging a dog, it is another example of a problem you have spent 5 years complaining about, in this case being handled correctly, generating some real expectation that the problem will this be fixed by and by. "i18n" has been the term used along with "l14n", and globalisation carries assorted baggage that I suspect will just lead to distractions. -- GitHub Notification of comment by chaals Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/50#issuecomment-833328584 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 May 2021 08:16:14 UTC