[03:50:32] <wm-bb>	 <Nikki> apparently I'm supposed to use a language selector provided by wikifunctions to change the language, in which case there's a different bug, because I have no idea where that is
[03:58:21] <wm-bb>	 <Nikki> and it seems really strange that wikifunctions needs a custom language selector to change the interface language. if uls can't do something wikifunctions needs, surely it would make more sense to improve uls?
[04:01:09] <wm-bb>	 <Nikki> (wikifunctions and uls are both wmf projects, aren't they?)
[04:07:03] <wm-bb>	 <mahir256> well languages are themselves objects, and are used to index into label/description lists of other objects, and given that there's nothing preventing two language objects from mapping to the same language code "de", some mechanism to choose the right language object given e.g. ?uselang=de needs to exist someplace (re @Nikki: and it seems really strange that wikifunctions needs a  <clipped message>
[04:07:03] <wm-bb>	 <mahir256> custom language selector to change the interface language. if uls can't d...)
[04:08:16] <wm-bb>	 <Nikki> I'm not sure how that's relevant to changing the interface language though
[23:52:22] <wm-bb>	 <quidditywiki> That seems reasonable and helpful to me. Go for it. :) (re @bgo_eiu: Regarding the natural language string operations section on the function catalogue: would it be OK to remove "string operations"...)