Jump to content

Template talk:Infobox mobile phone

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

Display size

[edit]

The display size usually given as the screen diagonal, which is misleading due to different aspect ratios (not to mention that the area doesn't increase proportionally to the diagonal). I think the comment guidance and the parameters section on this template's page should specify that the display size may or should be given as the screen area. — Preceding unsigned comment added by Andibrema (talk • contribs) 11:36, 8 May 2021 (UTC)[reply]

Deprecate slogan parameter

[edit]

I propose we deprecate the |slogan= parameter, as a (soft) step towards deletion. The conversation has gone back and forth many times over the years, with the parameter being removed and added at various points over the years, as well as these discussions, which are generally in favor of removal:

The following discussions resolved to remove the equivalent parameters from other infoboxes in 2018 and 2019:

Info: Deprecation here would mean removing the parameter from recommended use in the documentation, and deprecating explicitly in the TemplateData, which would warn against its use in the visual editor (details here: MW:Help:TemplateData#Deprecated). Deprecation does not remove the parameter or affect appearance for readers. Infoboxes can then be individually edited to remove the parameter, before deleting it from the template. — HTGS (talk) 00:02, 9 February 2024 (UTC)[reply]

I think there is a rough consensus to deprecate it, but not enough people watch this page for us to have a clear consensus. InfiniteNexus (talk) 06:53, 22 March 2024 (UTC)[reply]
What I foresee is that we depreciate it, as described above, and then start removing it (very slowly) from infoboxes, referring in edit summaries to this page. If anyone has an issue with the removal, they can raise it here, and we can consider walking it back, or coming up with some sort of a compromise (maybe a strict guideline for when to include it), or we end up doing an RfC or something more formal like that. Honestly, I don’t think it’ll come to that, but if it does, we can easily walk back the depreciation if it comes to it.
I just think it’s too trivial an issue to be raising a formal discussion without any objection in the last month and a half. Depreciation is still a soft step, after all. I certainly wouldn’t object if you wanted to notify relevant forums or wikiprojects though. — HTGS (talk) 08:43, 23 March 2024 (UTC)[reply]
@InfiniteNexus (and anyone else interested) I’m going to go ahead with the above steps. If I get pushback I’ll stop and we can discuss, but I just can’t see most product slogans as having lead-level relative emphasis. — HTGS (talk) 23:08, 17 July 2024 (UTC)[reply]

It’s been a year, and I haven’t seen any slogans in infoboxes that (IMO) would merit inclusion in the lead / infobox. Nor have I had any pushback for removing (some) of them. How do we feel about deleting the parameter, InfiniteNexus? It feels promotional in most cases, and peripheral in all (that I can tell). — HTGS (talk) 22:16, 29 October 2025 (UTC)[reply]

Well, consensus is presumed unless reverted, so go ahead. If objection arises, then we can discuss. InfiniteNexus (talk) 22:24, 29 October 2025 (UTC)[reply]
Whoops, apparently the template’s protection settings have changed since I last edited it.
@Zackmann08, would you mind removing the slogan parameter for us? — HTGS (talk) 01:29, 30 October 2025 (UTC)[reply]
 Done - Zackmann (Talk to me/What I been doing) 01:56, 30 October 2025 (UTC)[reply]
@HTGS: you might have missed a few... Category:Pages using infobox mobile phone with unknown parameters (0). I'll hit em with my JWB script. Zackmann (Talk to me/What I been doing) 02:11, 30 October 2025 (UTC)[reply]

Deprecate codename and modelnumber parameters

[edit]

I have boldly deprecated the |codename= and |modelnumber= parameters. I have seen no articles where this information is so important that it needs to be listed in the lead. — HTGS (talk) 07:34, 27 October 2024 (UTC)[reply]

I very much don't agree this was a right decision. The model number is actually very important for older models. Especially products from Samsung, LG and Sony Ericsson. For example Samsung Galaxy S II has a model number of I9100 in most regions. Back then, the model number was very often marketed along with the normal text product name and was known and identifiable. Samsung Champ is an example of one with a model number but with different marketing names (opposite case). I get that it isn't needed anymore now where every product is generally marketed under its friendly name only, but it has to be preserved because of these older ones. Kllom (talk) 17:14, 5 November 2025 (UTC)[reply]
Samsung Galaxy S II currently lists some 26 or so model numbers in its infobox. Do all of these consitute important information for a reader of an encyclopedia to get up first? I’m not familiar with how the phone was marketed, but it sounds like it would still have been known primarily as the “Samsung Galaxy S II”? What do the model numbers communicate to the reader exactly? At a glance, they look like they were just designations for regional variances in chip specs. — HTGS (talk) 13:26, 8 November 2025 (UTC)[reply]

Convert

[edit]

So I’m doing a clean out of Category:Pages using infobox mobile phone with unknown parameters (0) and I’ve noticed that a LOT of pages that use this infobox don’t convert their |weight= or |dimensions= values. I was thinking of writing something along the lines of {{Infobox person/weight}} to automatically perform these conversions (when possible). Is there any reason NOT to pursue this? To be clear the only thing that would change on the front end is that both imperial and metric units would be displayed. Open to thoughts. (@Frietjes: would love to hear your thoughts as the creator of Infobox person/weight). —Zackmann (Talk to me/What I been doing) 01:10, 15 September 2025 (UTC)[reply]

@HTGS and Qa003qa003: you both recently edited this template, any thoughts? —Zackmann (Talk to me/What I been doing) 05:24, 15 September 2025 (UTC)[reply]
So you would take unconverted data and it would be converted? No issue for the many pages that do already include a conversion? I don’t see a problem with this. — HTGS (talk) 06:20, 15 September 2025 (UTC)[reply]
Precisely. It would ignore any page that doesn’t match a very specific WP:Regex. I’m basing it off of {{Infobox person/weight}}. If you pass in {{cvt|154|lbs}} then the template does nothing, but if you pass in 154 lbs then it converts it and spits out 154 lb (70 kg). So I would do the same. It obviously wouldn’t convert 100% of the time, but would at the very least lessen the number of pages that don’t have a convert runnning. Zackmann (Talk to me/What I been doing) 06:24, 15 September 2025 (UTC)[reply]
Neato.
As I say, I don’t see a problem. One of my current goals is to make this infobox shorter and more to-the-point, but I can only see your implementing this as a quicker pathway to unconverting again if that were an eventual goal of the infobox.
I should add, I have been converting the conversion to the {{cvt|1xx2xx3|mm}} --> 1 × 2 × 3 mm (0.039 × 0.079 × 0.118 in) format for the dimensions, as that is more compact than the standard {{cvt|1x2x3|mm}} --> 1 mm × 2 mm × 3 mm (0.039 in × 0.079 in × 0.118 in). — HTGS (talk) 06:38, 15 September 2025 (UTC)[reply]
Sounds good. Going to do some experimenting and see what I can come up with. —Zackmann (Talk to me/What I been doing) 07:09, 15 September 2025 (UTC)[reply]
No idea, my change is to distinguish between OEM and manufacturing plants. Qa003qa003 (talk) 08:50, 15 September 2025 (UTC)[reply]
User:Zackmann08, seems like a pretty good idea. it could be a bit more complicated that the person height/weight case since the dimensions are multivalued, but so long as the fallback is to not do anything when the pattern is not recognized, it should be fine. I would suggest starting with the most common cases and going from there. you can have the module add a tracking category when it sees a pattern you do not expect, which is what we did with Module:Infobox cyclist tracking for example. Frietjes (talk) 14:59, 15 September 2025 (UTC)[reply]
Thanks for the tip Frietjes! I’m going to start on this tonight. —Zackmann (Talk to me/What I been doing) 23:00, 15 September 2025 (UTC)[reply]
Ok so rolled out Template:Infobox mobile phone/weight no problem. That was relatively easy. The hard one is proving to be the Template:Infobox mobile phone/size… The myriad of different formats that people are feeding in the information is proving to be a pain to deal with. Particularly when you have multiple models on the same page (iPhone 15 & iPhone 15 Plus for example). I’ve got it working pretty well, but it absolutely requires some more testing. I’m not yet confident that I can roll it out without breaking existing stuff, but I’m getting there. If I could get some peer reviews of the code over at Template:Infobox mobile phone/size that would be awesome! — Zackmann (Talk to me/What I been doing) 07:38, 16 September 2025 (UTC)[reply]
@HTGS: so I just found out that there is also a {{cvt|3*4*5|mm}} which produces the much more compact 3×4×5 mm (0.12×0.16×0.20 in)… Should we use that instead??—Zackmann (Talk to me/What I been doing) 09:13, 16 September 2025 (UTC)[reply]
Yeah, sounds good; I didn’t even know that was an option lol — HTGS (talk) 01:26, 17 September 2025 (UTC)[reply]
User:Zackmann08, "stlb" is for stone weight, which is hopefully not needed for mobile phones :) Frietjes (talk) 14:33, 16 September 2025 (UTC)[reply]
Hahah! Thanks Frietjes. Fixed that. - Zackmann (Talk to me/What I been doing) 00:13, 17 September 2025 (UTC)[reply]
Rolled out {{Infobox mobile phone/size}}. Let me know if anyone sees any issues. Pretty well tested (see template documentation). —Zackmann (Talk to me/What I been doing) 04:44, 17 September 2025 (UTC)[reply]
So I’ve rolled back my rollout of {{Infobox mobile phone/size}} because it caused a TON of errors so going back to the drawing board to better handle edge cases… —Zackmann (Talk to me/What I been doing) 05:17, 17 September 2025 (UTC)[reply]
I’m afraid I can’t read that Lua, but I will add: you could look for br tags and ubl templates as delimiters. I think the br is more common for pages where they aren’t already using cvt. — HTGS (talk) 05:49, 17 September 2025 (UTC)[reply]
There is a better solution which is to basically say if it isn’t in a format that can be converted, then ignore it. :-) —Zackmann (Talk to me/What I been doing) 05:55, 17 September 2025 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Template_talk:Infobox_mobile_phone&oldid=1321069099"