Igor Chubin

@iago-lito Sorry for delay; I've just merged it. Let us check it live: ``` curl fr.wttr.in/Lyon curl fr.wttr.in/:help ``` Does it look good to you? Are you ready for `v2.wttr.in`?...

Regarding the phrasing length in v1, the only possible solution I see here it the popping up tooltips, because sometimes the phrasing is too long for any table of any...

I want to abuse the hyperlinks feature for that. If your terminal supports this feature, try: ``` printf '\e]8;;Partiellement couvert\e\\Partiellement …\e]8;;\e\\\n' ``` If your terminal does not support it, just...

(wrong button pressed; never mind)

Yes, I do, but not in the main view, because it may be incompatible with some terminals, that's why we need some additional view for that, `v3` or `v1t` ,...

We should add this translation to fr.txt (and everywhere after that). Can you please add without a code, and then I will add its code too?

@iago-lito Finally v2 translation! Could you please take a look at it? It is just a single line: [lib/translations_v2.py](https://github.com/chubin/wttr.in/blob/master/lib/translations_v2.py)

The translation is here: https://github.com/chubin/wttr.in/blob/master/share/translations/fr.txt The problem is that we can't foresee what new conditions the data source will add to its data. What is possible though, we can register...

The bug with comma-separated translation is fixed now, but there are some new untranslated terms: ``` : Schneeverfrachtung : Low drifting snow : Nebelfelder : Patches of fog : Nieselregen...

@iago-lito Happy new year :) and Happy new Chinese New Year :) I finally found some time for our beautiful translations issues. I've added your suggestion, + added yet another...