[00:07:23] "A fallback rendering displays as text, making it indistinguishable from a successful rendering." The final sentence of this snippet looks quite distinguishable to me. I assume you mean indistinguishable for the computer? Even the computer could be told to look for ✏️ (https://www.wikidata.org/wiki/Q110628558) or 🔧 (https://www.wikifunctions.org/wiki/Z41185) or the [00:07:23] accompanying links. [00:08:49] Yeah, you're right — humans will certainly recognize the fallback. But I meant for the computer. Not all fallbacks have necessarily such an icon. [00:09:38] I'll update the text to make it clearer. [00:09:40] We can make sure they do. I don't think I've seen a situation where we can't put them in. (re @vrandecic: Yeah, you're right — humans will certainly recognize the fallback. But I meant for the computer. Not all fallbacks have necessar...) [00:11:17] Why not just make them a proper error message? The red boxes being too clunky? [00:11:33] As you say, extend the configuration type would make it easier. (re @u99of9: We can make sure they do. I don't think I've seen a situation where we can't put them in.) [00:12:28] You mean with the extended configuration type it would then automatically wrap it with an icon? [00:14:40] Because they read better than the red boxes. To a lesser or greater degree they still provide info in text. e.g. the magenta sentence above translates in Google translate to "The eponym for ANZAC Day is the Australian and New Zealand Army Corps", which is pretty much what the sentence is trying to say, the default got it right but perhaps has bad grammar or will do [00:14:40] worse in other [00:14:42] situations. (re @vrandecic: Why not just make them a proper error message? The red boxes being too clunky?) [00:19:17] Just to make sure: are you saying that a) the red boxes are hard to read and should be redesigned to be easier to read, or b) the default may be an acceptable output that could be integrated into an article? [00:20:15] Yes, arranging this would be easier for us if we had it explicitly flagged as either acceptable or not. (re @vrandecic: You mean with the extended configuration type it would then automatically wrap it with an icon?) [00:22:15] I think what I am suggesting to make unacceptable output an error (and we could change the way errors are displayed if that's the concern), and acceptable output maybe normal output together with a warning, or without even a warning, depending on how acceptable it is [00:33:09] The red boxes are appropriate when the system fails to render anything. This looks right to me: : https://tools-static.wmflabs.org/bridgebot/973ee472/file_84998.jpg [00:34:28] Exactly how or whether that blocks language-wiki admins from embedding it in their wiki is fair game for discussion. [00:45:24] When the system can render something, but we haven't configured it for that language yet, a redesign of the red box would be to make it look like the magenta phrase. The main content of the red box would be html-content that we had rendered. But I don't really see the advantage of this over sticking with inline magenta. [00:53:28] I don't think the magenta (language unconfigured) should be integrated into a live article. But I also don't want unnecessary red boxes on AW.