34 lines
1.3 KiB
Markdown
34 lines
1.3 KiB
Markdown
# Missing Features
|
|
|
|
Features not yet implemented in the Zig version:
|
|
|
|
## 1. Language/Localization
|
|
- Accept-Language header parsing
|
|
- lang query parameter support
|
|
- Translation of weather conditions and text (54 languages)
|
|
|
|
## 2. Json output
|
|
- Does not match wttr.in format
|
|
|
|
## 3. Moon endpoint
|
|
- `/Moon` and `/Moon@YYYY-MM-DD` endpoints not yet implemented
|
|
- Moon phase calculation is implemented and available in custom format (%m, %M)
|
|
|
|
## ~~PNG Generation~~
|
|
- Render weather reports as PNG images
|
|
- Support transparency and custom styling
|
|
|
|
This was implemented behind a `-Denable-png` build flag and has been removed. It
|
|
was slow and memory-intensive (a full font stack plus megabyte-scale buffers per
|
|
request), carried its own set of bugs, and saw effectively no use — it did not
|
|
justify its maintenance cost or the dependency surface it pulled in (zigimg,
|
|
freetype via ghostty, and two embedded font packages).
|
|
|
|
## ~~Multiple Locations Support~~
|
|
- Handle colon-separated locations (e.g., `London:Paris:Berlin`)
|
|
- Process and display weather for multiple cities in one request
|
|
|
|
This is advertised as a feature in wttr.in, but it does not work on the live
|
|
site. Given that this would be an unbounded computational risk and a DOS vector,
|
|
this is not going to be implemented. That can be done easily through a script,
|
|
and it will allow the rate limiting to work better that way
|