Igor Chubin

I didn't get the first one; where exactly is the problem? Regarding the second one, is it this? https://github.com/chubin/wttr.in/issues/52

Yes, it is possible, but that's how the data comes from the data source.

They are here, and the date localization too: https://github.com/chubin/wttr.in/blob/master/share/we-lang/we-lang.go Could you please translate them?

Thanks a lot! I've merged it. Please test and please add your name to the translators list (`share/translation.txt`)

There were a couple of outages in the last time, but now it works. Please test

I suppose that the problem here that for the v3 (because it was conceived as a region-based reporting service) you should use `NSW` instead of `Sydney`. Of course you may...

> Why would some people see Sydney working, and others not? I am not sure that `/Sydney` works for anybody. From the screenshot above it is not clear, was query...

No, not yet, but we have several related issues: * #113 * #197 * #221

ASCII encoding will be implemented as part of #587. Probably, it will be needed to specify ASCII frame style too. Something like: `encoding=ascii&frame=ascii` otherwise the frame will be just cut...

I think it is an interesting use-case, and I would be gladly add support for Kindle Paperwhite to wttr.in. I think we have a lot of Kindle owners among wttr.in...