Template talk:Essay
Latest comment: 5 years ago by Tacsipacsi in topic Category
Source
editCribbed from w:Template:essay obviously. Hopefully fixed all differences but if you spot any... ++Lar: t/c 17:53, 18 January 2008 (UTC)
Category
editCurrently, it doesn't seem to add the category automatically (?); e. g.: Commons:Don't be bold, Commons:Not staying mellow. --Djadjko (talk) 20:58, 26 July 2017 (UTC)
- @Djadjko: I think it works now. - Alexis Jazz 15:13, 31 March 2018 (UTC)
- @Tacsipacsi: Interesting. The template now categorizes many pages as Category:Commons essays , which, apparently, works. I was using codes because I've gotten used to wiki stripping all whitespace characters at the start and end. And now to get a space after "in user space", nbsp is actually needed. - Alexis Jazz ping plz 21:02, 25 July 2019 (UTC)
- @Alexis Jazz: In fact not. MediaWiki is very generous about spaces in links, so double space in Category:Commons essays in German is OK. However, Category:Commons essays in user space in German is not—and not because of the non-breaking space (it gets translated to a regular space in the link), but simply because the category doesn’t exist. I don’t think user space essays should be categorized by language, as this would need creating more than a dozen categories (one for each language present in the #switch) to make sure they won’t become red links. I think it’s an overkill and should not be introduced as long as Category:Commons essays in user space is not overpopulated. —Tacsipacsi (talk) 21:28, 25 July 2019 (UTC)
- @Tacsipacsi: Without nbsp, it seemed to become "Commons essays in user spacein German". Currently, such language-specific categories for user space essays are indeed unneeded. But if they are needed in the future, the functionality is there. Any language-specific category should only be created when there's something to put in it. - Alexis Jazz ping plz 22:16, 25 July 2019 (UTC)
- @Alexis Jazz: Functions maybe-needed-in-a-few-centuries can be stored in comments. With the current code, as soon as a language-suffixed user page appears, it gets the red category. The user who puts the template on the page may have no idea what they should do with it. Either create the categories, or make sure they won’t be populated on pages. —Tacsipacsi (talk) 20:56, 26 July 2019 (UTC)
- @Tacsipacsi: I think you're overthinking it. Creating empty categories isn't allowed. A few centuries is silly, if any German user writes 4 German essays, that category will be useful. I've never seen a language subpage in user space. I doubt they're all that common. The only other way is to use the parameter. And even if the result is a red category, who says the user will even care? - Alexis Jazz ping plz 23:28, 26 July 2019 (UTC)
- @Alexis Jazz: And if a German user writes some essays, will they suffix them with “/de”, when there’s no English “original”? I don’t think so. Given that, the automatic categorization makes no sense in user space, it’s better left for the user to manually specify the language. And even then, a Category:Commons essays in user space in French with not more than one item makes no sense, it’s enough to place that page in Category:Commons essays in user space and Category:Commons essays in French, so the template should check if the category exists, or simply not even try to use it as long as there are that few pages in Category:Commons essays in user space (currently 27). And who will care of the red category? For example someone who tries to find the page. Red categories cannot be found with browsing the category tree, so a page having only a red category link is practically uncategorized. It’s still better to use a broader category than a non-existent. —Tacsipacsi (talk) 09:19, 27 July 2019 (UTC)
- @Tacsipacsi: I think you're overthinking it. Creating empty categories isn't allowed. A few centuries is silly, if any German user writes 4 German essays, that category will be useful. I've never seen a language subpage in user space. I doubt they're all that common. The only other way is to use the parameter. And even if the result is a red category, who says the user will even care? - Alexis Jazz ping plz 23:28, 26 July 2019 (UTC)
- @Alexis Jazz: Functions maybe-needed-in-a-few-centuries can be stored in comments. With the current code, as soon as a language-suffixed user page appears, it gets the red category. The user who puts the template on the page may have no idea what they should do with it. Either create the categories, or make sure they won’t be populated on pages. —Tacsipacsi (talk) 20:56, 26 July 2019 (UTC)
- @Tacsipacsi: Without nbsp, it seemed to become "Commons essays in user spacein German". Currently, such language-specific categories for user space essays are indeed unneeded. But if they are needed in the future, the functionality is there. Any language-specific category should only be created when there's something to put in it. - Alexis Jazz ping plz 22:16, 25 July 2019 (UTC)
- @Alexis Jazz: In fact not. MediaWiki is very generous about spaces in links, so double space in Category:Commons essays in German is OK. However, Category:Commons essays in user space in German is not—and not because of the non-breaking space (it gets translated to a regular space in the link), but simply because the category doesn’t exist. I don’t think user space essays should be categorized by language, as this would need creating more than a dozen categories (one for each language present in the #switch) to make sure they won’t become red links. I think it’s an overkill and should not be introduced as long as Category:Commons essays in user space is not overpopulated. —Tacsipacsi (talk) 21:28, 25 July 2019 (UTC)
- @Tacsipacsi: Interesting. The template now categorizes many pages as Category:Commons essays , which, apparently, works. I was using codes because I've gotten used to wiki stripping all whitespace characters at the start and end. And now to get a space after "in user space", nbsp is actually needed. - Alexis Jazz ping plz 21:02, 25 July 2019 (UTC)