10:35:26 <KwBot> [nikola] Xeverous opened issue #3414: Logging API for plugins https://github.com/getnikola/nikola/issues/3414 10:56:11 <KwBot> [nikola] ralsina closed issue #3414: Logging API for plugins https://github.com/getnikola/nikola/issues/3414 10:58:13 <KwBot> [nikola] Kwpolska assigned issue #3414 to Kwpolska: Logging API for plugins https://github.com/getnikola/nikola/issues/3414 10:58:13 <KwBot> [nikola] Kwpolska assigned issue #3414 to Kwpolska: Logging API for plugins https://github.com/getnikola/nikola/issues/3414 23:15:10 <erdgeist> ChrisWarrick: I wonder how "Also available in <LANGUAGE>" would be useful to someone not understanding the source language. Did I mis-configure my nikola? 23:15:45 <erdgeist> ChrisWarrick: I'd rather expect the explainer to be presented in the _destination_ language 23:16:26 <ChrisWarrick> erdgeist: if someone spots their language name, they might click on it 23:16:38 <ChrisWarrick> erdgeist: also available in X / also available in Y doesn’t scale well 23:16:56 <ChrisWarrick> erdgeist: we used to do “read in X”, you can still use those strings if you change your templates 23:17:56 <erdgeist> ChrisWarrick: Hmkay, there's a general problem. Thanks :) 23:18:29 <ChrisWarrick> this also kinda depends on your audience 23:18:37 <ChrisWarrick> and on the language pair 23:19:26 <erdgeist> ChrisWarrick: When there's enough screen estate, that's not a problem. I'm starting to build the site mobile first, so I want to aid the user to their native language, but I don't want to annoy ... 95 % of the site's users with having to skip half a page on their mobiles 23:20:24 <ChrisWarrick> erdgeist: test what works best for you and for your case 23:21:02 <erdgeist> ChrisWarrick: Yep, I just start thinking what I did wrong if the defaults create unexpected results :)