Template talk:Infobox Software
Jump to navigation
Jump to search
Categorization and multiple programming languages
The categorization per programming language currently breaks if more than one language is used.
Maybe functionality from {{infobox aircraft}} related to authors, configurations etc. could be borrowed and applied here too.
—Johan G (Talk | contribs) 03:10, 10 September 2020 (EDT)
- That's a good idea. I thought of that a number of years ago, but decided against it as there are were not many pages using this template. There were only the labels to internally translate as well, whereas {{infobox aircraft}} is more specific and a lot of the data is internally translated. But it's worth changing. I'll see if I can quickly format something here.
- Done - that was a rather easy one :)
- Your changes totally missed the point of what I was trying to say, but totally made an improvement anyway. Lol.
- What I meant was that it would be nice to be able to state that a piece of software consisted both of code in one language and in another language, and have the template add the article to both of those categories, for example Category:C++ software and Category:Python software.
- —Johan G (Talk | contribs) 09:06, 10 September 2020 (EDT)
- Oh wait, the categories are still broken! Is there a specific page that does this? I don't see anything at Category:Software_by_programming_language.
- Are the categorization for this one broken here as well? I had that in another one
earlier todayyesterday in Autoflight Navigation and thought that was an isolated hickup. - —Johan G (Talk | contribs) 09:12, 10 September 2020 (EDT)
- Are the categorization for this one broken here as well? I had that in another one
- Click on the categories. Sometimes the CategoryTree extensions show that there are no pages in a category, which is at play here. Clicking on the categories reveal that there are pages in them. (Still have my issue with {{howto other}} and {{Autoflight Navigation}} I cant seem to solve though.)
- I jumped to the conclusion that I'd finished a little early. For the categories, I think a separate {{programming language}} template would be worth while. Then here we could use the #titleparts parser function to split up the writtenin parameter and send each part to the {{programming language}} template (i.e. the separator for each language would be /). I'll see what I can do.
- Now I think I'm done ;) I've created {{programming language}} and this template now uses #titleparts. See the result at Category:Software by programming language.