Talk:I Don't Care (Ed Sheeran and Justin Bieber song)

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

List templates[edit]

Hey Ss112, the use of other list templates in infobox song is not allowed as per instructions at Template:Infobox song#cite note-plainlist-2. Horizontal list is already embedded into the template itself, hence usage of the hlist template is redundant. If this has already been discussed elsewhere, please let me know. I see no reason to “maintain the original list style”, especially since it contradicts what is already established when the template was created. Hayman30 (talk) 13:41, 10 May 2019 (UTC)[reply]

@Hayman30: We have been through this before. I know what the template says. It's not "not" allowed, it says "should not" primarily because of the redundancy. This was brought up by Livelikemusic with one of the users who encoded/works on the template, and he basically said that there is no real problem with using hlists, it is the use of commas that is the real problem for visually impaired readers. Hlists might be redundant, but it saves on space, and there is no real need to change every use of them around just because flatlisting is encoded into the template and whoever wrote its documentation decided to word it strongly. No need to ping me, I don't wish to go through this again. Ss112 13:46, 10 May 2019 (UTC)[reply]
It literally says “don't use other list templates“, so either use commas, or do it the correct way. The amount of space you could possibly save is extremely minimal and is not a big enough reason to go against the rules. I’m sorry but I don’t see any concrete justification for your reversion. If you believe that there’s something wrong with how the instructions are written, it’s really your responsibility to bring it up on respective talk pages, it’s not acceptable to revert someone who’s making legitimate changes required by the rules. Yes, the documentation did not explicitly specify that an editor should go around and make changes to every article they happen to encounter, but it asserts that the usage of other list templates is fundamentally wrong. I understand that certain articles were created long time ago and their creators may not be aware to these changes, hence they are still using the traditional format, e.g. infobox single etc. But I would assume that you already knew about this when you created this article, but you insisted to use list templates out of what is, obviously, personal preference. You might argue that using the default list style is my personal preference, it is, but it’s also the “official” preference, so why not just give in so you don’t have to “go through this again”? Because I’ll be bringing this up every once in while . Hayman30 (talk) 14:10, 10 May 2019 (UTC)[reply]
Why would I use commas? I don't prefer them, and that is a problem according to one of the users who encoded the template (i.e. not you). If they say hlists are not a problem other than being redundant, you are causing a huge fuss over nothing. Hlists in the code don't cause any problems for visually impaired readers. It's only considered redundant code—that's all. Also, you need to learn the difference between a rule (which would be a policy, by the way) and a guideline—template documentation is tantamount to a guideline for its use, not a policy. It's a recommendation of what we should do. Consistency should also be observed. Also, take it down a notch. "Fundamentally wrong"? Chill out. So you can keep it bringing it up all you like—that doesn't mean I'm required to reply to you. I think it's time for you to move on and focus on more important issues, because this isn't one of them. This will be my final reply on the matter, so you can comment here with some more promised future antagonism if you wish—that sounds more like an issue for you, not for me. Bye! Ss112 14:33, 10 May 2019 (UTC)[reply]

Covers?[edit]

Leon Jaar has a song called When I'm with my baby yeah. It's the same song. What's up with that? 73.26.46.210 (talk) 23:44, 25 September 2019 (UTC)[reply]