DisplayPort edit

Thanks for your edit here, but to address your comments, a cosmetic change to an article is generally considered a minor change and does not need to be discussed beforehand. The only time a discussion's necessary is when a disagreement arises. After a second look, I actually agree that the Versions section should be moved back to its original location, for now. Ultimately, the best solution would be to merge that section with the Specifications section, since technically the Versions section is describing a technical aspect of each. The Overview section should include more information about the technology's history, so the various versions can get a brief introduction right off the bat. Then we can move the technical specifications sections towards the end of the article, where it truly belongs. Not sure when or if I'll get around to making some of these improvements, but thought I'd share in case you were thinking about working more on its structure. --GoneIn60 (talk) 16:47, 30 March 2016 (UTC)Reply

Thanks. I agree versions and specifications should really be be merged in the future, but it will require some significant reworking, with more tables and less inline listing within paragraphs and bullet points. It does seem like the page was not originally designed with multiple DisplayPort versions in mind :P The most important thing really is to just make sure that the main, general information that people will be looking for (mostly, what the maximum video signal supported by each version is) remains easily visible without scanning the page, rather than being buried within the specifications section among all the other finer technical details. Anyway... work for the future ;) GlenwingKyros (talk) 23:34, 30 March 2016 (UTC)Reply

My edit to "Graphics Display Resolution" edit

I tried to be careful, but please do tell me if I screwed anything up.—DocWatson42 (talk) 02:50, 10 November 2016 (UTC)Reply

Em Dash Usage edit

You removed a pair of em dashes on the HDMI page at 12:01 on 2018 March 2‎ with a comment of "Improper use of em dash". Can you explain what you consider a proper use of the em dash? I've always used them when the main topic gets interrupted by an aside, similar to what parentheses are used for. Commas can also be used (as you did on that page). I feel that any of em dash, parenthesis, or comma would work in that case. I'm not inclined to change any of them to any other as it seems to be a style thing, but you apparently feel otherwise.

I look forward to your comment, WesT (talk) 22:08, 12 March 2018 (UTC)Reply

Mainly what bothered me was that the comment inside the em dash began with "such as", which is a continuation from the previous part of the sentence, whereas an em dash represents a break in the sentence flow. Those two don't quite go together. I could have also removed the "such as" instead of removing the em dashes, either way would have worked. It appears it doesn't matter now though :P And I guess "improper use of em dash" wasn't the greatest description of the edit, but I wasn't putting that much thought into my edit comments :P GlenwingKyros (talk) 00:45, 13 March 2018‎ (UTC)Reply

The resx template: "1920 × 1080" vs "1920×1080" edit

My apologies, but why you're prefer the first version of this template realization? I don't pretend to have a weightily personal opinion, but in most cases i will prefer a compact version of template writing. Maybe you know a special guideline or some ISO (or another) standard about this? 85.202.228.67 (talk) 21:13, 19 June 2019 (UTC)Reply

I decided to include spaces since that is how any other multiplication would be written, not unspaced (i.e. 5 × 2 = 10 rather than 5×2 = 10, or when writing dimensions, i.e. 255 × 392 × 31 rather than 255×392×31). I know when dealing with notations and specs, people like to write things with no spaces for some reason (i.e. 64GB instead of 64 GB, or 60Hz instead of 60 Hz). Despite this being common practice in notation even in the industry, we don't replicate that here. Of course, there is a MOS rule for having a non-breaking space between values and unit symbols and there is no such rule about resolutions, so there is no rule saying it has to be done this way, but I think this notation for resolutions is more consistent with the general style of things on Wikipedia, that's all. I think things are easier on the eyes with spaces anyways. I use thin spaces in the template so they aren't separated by too much, so even if there is a list of several resolutions in a sentence it shouldn't cause any problems, and adding two thin spaces isn't that much more in terms of extra width/excess characters. GlenwingKyros (talk) 23:12, 19 June 2019 (UTC)Reply
Thanks for extensive response! So, i was preferably used this module only as a part of a wikitables, and sometimes the widely version is not a optimal (such as a mobile phone view, or on a old HD screens). But this is not a important aspect, and then, if a regular readability and common usage practice has coming on a first place, so, i'm agreed with this. Cheers! 85.202.228.67 (talk) 04:35, 21 June 2019 (UTC)Reply

Your screen cap at AN edit

Thanks for linking to that screen cap. I hope you don't mind, but I uploaded that pic and posted it at AN. It's a useful illustration of the problem. Please let me know if you'd like me to self-revert. Levivich 22:07, 3 September 2019 (UTC)Reply

I don't have a problem with that :) GlenwingKyros (talk) 22:17, 3 September 2019 (UTC)Reply

Please explain edit

https://en.wikipedia.org/w/index.php?title=Display_resolution&oldid=998979074 Can you please explain what you mean by "If there's data for this resolution, it's completely pointless to have a table entry for it.)" That statement appears self-contradictory. Thanks, --Janke | Talk 09:46, 8 January 2021 (UTC)Reply

Sorry, it was typed on my phone and is meant to say "if there's no data". GlenwingKyros (talk) 09:47, 8 January 2021 (UTC)Reply

Disambiguation link notification for April 14 edit

Hi. Thank you for your recent edits. An automated process has detected that when you recently edited Charging station, you added a link pointing to the disambiguation page Hyundai. Such links are usually incorrect, since a disambiguation page is merely a list of unrelated topics with similar titles. (Read the FAQ • Join us at the DPL WikiProject.)

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 06:08, 14 April 2021 (UTC)Reply

Regarding your reversion of my edit edit

Please see here. LucasA04 (talk) 21:33, 27 April 2021 (UTC)Reply

Thanks. I had set the main article on my watchlist but not the talk page. GlenwingKyros (talk) 21:38, 27 April 2021 (UTC)Reply
GlenwingKyros, That's fine LucasA04 (talk) 21:43, 27 April 2021 (UTC)Reply

Template problem edit

I tried to fix the "hijacked" template at User_talk:Blackraider77, but didn't quite succeed. Hope you approve. --Janke | Talk 09:26, 24 July 2021 (UTC)Reply

Thanks. I really have no idea what happened xD GlenwingKyros (talk) 09:30, 24 July 2021 (UTC)Reply

YouTube videos in low connection resolution, iPhone screen resolution, 16k resolution, etc... edit

Hello GlenwingKyros ;

Why you rollbacked my edit ? I have a reason for iPhone's screen resolution (1 136 × 640, 1 334 × 750, ...), YouTube's screen resolution in low Internet (256 × 144, 426 × 240 & 640 × 360) or the 16k resolution (15 360 × 8 640). Thank you for your regards ! ÉOLE79000 (talk) 08:30, 26 August 2021 (UTC)Reply

The table is just for resolutions and their names (if they have a name). Not for descriptions of what the resolution is used for. The UHDTV standards define 4K UHD and 8K UHD. The 16K resolution 15360 × 8640 is not part of the UHDTV standards and so does not need to be labeled "16K UHD". The names are based on sources, not on just matching patterns. GlenwingKyros (talk) 18:39, 26 August 2021 (UTC)Reply
And 0.002 % of any televisions have the 16K definition. And what is this ? "OHD" for Omega High Definition Television (OHDTV) ? Am I sucked/bad at editings ?! ÉOLE79000 (talk) 16:21, 31 August 2021 (UTC)Reply
I can't tell what you're trying to say. If there's a recognized name, we put a name in the table. If there is not a recognized name, we don't put a name in the table. We don't make up our own names though. There are a lot of grammatical problems in your edits. GlenwingKyros (talk) 17:40, 31 August 2021 (UTC)Reply

Reversion edit

why did you revert my edit on Graphics display resolution? I only put the meaning of nHD and I did not add any vandalism to the article. AKK700 01:26, 30 September 2022 (UTC)Reply

Sorry, my mistake. I have put the edit back.  — Glenwing (talk) 22:10, 30 September 2022 (UTC)Reply

A barnstar for you! edit

  The Editor's Barnstar
I especially appreciate your high-quality contributions on DisplayPort, HDMI, and other articles about display technologies! On top of that, you seem to respond promptly to queries from other editors on the article talk pages! — AP 499D25 (talk) 11:00, 16 April 2023 (UTC)Reply
Thanks!  — Glenwing (talk) 18:29, 16 April 2023 (UTC)Reply

ArbCom 2023 Elections voter message edit

Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2023 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:47, 28 November 2023 (UTC)Reply