Igor Chubin

Do I understand it right, that it is correct in three cases of four? Correct: * my browser * your browser * your terminal Incorrect: * my terminal

What terminal do you use? Have you configured it in some special way?

Now I see that it depends on the terminal, and its support of bidirectional texts: A couple of additional examples: vte-based terminal + bidi:  mlterm: 

I think that they will not change the terminal they are get used to just because of wttr.in. Also, it is a good opportunity to make good implementation of Arabic...

I moved the rendering subtasks to #676, and so this issue is only about translation now, and problably it can be closed because Arabic translation is done. @egmontkob I think...

@nakanakaii thank you for your help offer. If you would like to fix some translation errors, the translations are here: https://github.com/chubin/wttr.in/blob/master/share/translations/ar.txt https://github.com/chubin/wttr.in/blob/master/share/translations/ar-help.txt Please feel free to create pull-requests with the...

@nakanakaii corrected some translation errors: #742, #743. Some errors are still there: https://github.com/chubin/wttr.in/blob/master/lib/translations.py https://github.com/chubin/wttr.in/blob/master/lib/translations_v2.py

Have you checked v3.wttr.in (`curl v3.wttr.in`)? The original idea behind it was exactly that

Can you try this in Kitty: ``` curl -s v3.wttr.in/Bayern.png | kitty icat --align=left ```

I think that ideally all options (sixel, MIP, Kitty-protocol and usual pseudographics à la timg) should be supported, and the user should have the choice