User talk:Jroberson108

Welcome!

Hello, Jroberson108, and welcome to Wikipedia! Thank you for your contributions. I hope you like the place and decide to stay. Here are a few links to pages you might find helpful:

You may also want to take the Wikipedia Adventure, an interactive tour that will help you learn the basics of editing Wikipedia. You can visit The Teahouse to ask questions or seek help.

Please remember to sign your messages on talk pages by typing four tildes (~~~~); this will automatically insert your username and the date. If you need help, check out Wikipedia:Questions, ask me on my talk page, or ask for help on your talk page, and a volunteer should respond shortly. Again, welcome! South Nashua (talk) 03:20, 10 January 2017 (UTC)[reply]

No final "s" in "occur(s)" ?

Your last sentence : "I'm not certain what you are asking, but I assume you are asking a question about grammar regarding the use of "occur" vs "occurs" in this statement: "a cataclysm and re-establishment of dharma occur". The singular verb is "occurs". Since there are two items (#1 cataclysm; #2 re-establishment of dharma), the plural verb "occur" is used. It deals with subject-verb agreement. BTW, to talk to me directly, I would suggest doing it on my user talk page. Jroberson108 (talk) 20:35, 3 November 2020 (UTC)"

Ok, but, if you have two items, "a cataclysm" and "re-establishment", you must have also twice the determinative "a", one by item, haven't you ? Hello, Madam/Sir. VirguloMane (talk) 10:21, 5 November 2020 (UTC)[reply]

Repeating the indefinite article "a" for two noun phrases sounds more common. I modified it on the Yuga Cycle page. I found a few discussions on this, but no grammatical rule: [1] [2].Jroberson108 (talk) 18:13, 5 November 2020 (UTC)[reply]

Email question on sandhyansa

@VirguloMane: I received your email question. I will respond here. Feel free to ask future questions on talk pages and ping me using Template:Reply_to as I did for your username.

Question: Which could be the meaning of "sandhyansa", more or less?

Answer: A sandhi is a period of time that either starts or ends a larger period of time. Each of the four yugas start and end with these periods. The starting period (dawn/morning) is called the sandhyā and the ending (dusk/evening) is called the sandhyānśa, or more popularly sandhyāṃśa. Click the links on the Sanskrit words to see their numerous translations. For example, the flow of time around Kali Yuga is in this order:

...
Dvapara-yuga-sandhyamsa (dusk/evening; 72,000 years)
Kali-yuga-sandhya (dawn/morning; 36,000 years)
Kali-yuga (Kali-yuga proper; 360,000 years)
Kali-yuga-sandhyamsa (dusk/evening; 36,000 years)
Krita-yuga-sandhya (a.k.a. Satya Yuga; dawn/morning; 144,000 years)
...

There is also a manvantara-sandhya that separates two manvantaras. Jroberson108 (talk) 18:37, 19 January 2021 (UTC)[reply]

Some kinds of "transition periods", if I understand... Thanks to you. :-) 'Bye. VirguloMane (talk) 20:26, 21 January 2021 (UTC)[reply]

What-If... Let's just say

If kali yuga ends in 2025 will my body age increase and will have divine powers like summoning Astras? 950CMR (talk) 17:56, 26 January 2021 (UTC)[reply]

@950CMR: Kali Yuga ending in 2025 is a recent invention that has no bases on Hindu texts. According to Hindu texts, the end of Kali Yuga is far from now, where we are still in the beginning sandhya. Hypothetically speaking, if you were alive when Kali Yuga ends, your lifespan wouldn't change since your karma from previous lives dictates this life's lifespan in the sense that you only have so many breaths or heart beats. As far as attaining Siddhis or powers, they are attained through strict meditation and yogic practices (not given freely with no effort), which can alter one's lifespan in the sense that you slow your breathing and heart beat; thereby, extending your lifespan.

Actually Dwapara yuga didn't lasted that long honestly if we were to talk about ramayana events happened in 70K BCE and mahabharata events happened in 30K bce according to scientists and astronomers and the ending of events of ramayana was likely the end of Treta Yuga therefore the end of kali yuga is a possibility since Dwapara yuga lasts for 800k years people still thinks that we're in Dwapara yuga if we were in Dwapara yuga our lifespan would be minimum atleast 800 hundred years 950CMR (talk) 19:09, 26 January 2021 (UTC)[reply]

Wikipedia:Proposed deletion

Hello, Jroberson108,

Only articles and files can be tagged for Proposed Deletion so please do not tag any more templates with PROD tags. If you believe a template should be deleted, please nominate it for deletion at Templates for Discussion along with your argument for why it should be deleted. Thank you. Liz ^{Read! Talk!} 19:18, 9 February 2022 (UTC)[reply]

@Liz: Will do. Thanks for the info. Jroberson108 (talk) 22:20, 9 February 2022 (UTC)[reply]

Accessibility (scope) changes

What do your changes to Template:COVID-19 pandemic data/Texas medical cases by county do - I notice that the county names are no longer bold nor centered? Scratch that, are the changes something that should be rolled out to other such tables? I can easily do this with the other tables I edit. I machine generate the markup and simply would need to change boilerplate in two spreadsheet cells. EphemeralErrata (talk) 10:50, 10 February 2022 (UTC)[reply]

@EphemeralErrata: scope="row" is an attribute that should go on the row header that describes that row's data. They were incorrectly used before. In the case of your tables, the row headers are each location. If you want it bold and centered, then you can try removing the "plainrowheaders" class used on the table. Yes, all tables should have that change. Jroberson108 (talk) 11:00, 10 February 2022 (UTC)[reply]

So this was a long standing bug! Previously, the row headers were not marked as such, thus the ! formatting applied. Once they were marked as header cells, plainrowheaders override the ! and made them plain. I've removed this attribute so that the county name cells retain their historical appearance. I also made the second row, the one with totals, retain its historical appearance. EphemeralErrata (talk) 10:18, 12 February 2022 (UTC)[reply]

@EphemeralErrata: The "plainrowheaders" class changes all header cells with scope="row" attribute so they are plain font-weight and left aligned. I don't really see any value in the historic appearance since it is quite heavy and harder to read, but if other users request it then so be it. Jroberson108 (talk) 11:43, 12 February 2022 (UTC)[reply]

Help:Sorting section on scrolling

See diff. Edit summary: "(→‎Scrolling: Remove note. Example is sufficient and directing all help to one user seems inappropriate.)"

See other examples of the same thing that have been there for a long time.

No one has complained. Why would they? This is a help page, not a Wikipedia article.

Can I put back the note? --Timeshifter (talk) 20:51, 19 February 2022 (UTC)[reply]

@Timeshifter: For making a table scrollable, the code example is sufficient. Jroberson108 (talk) 21:07, 19 February 2022 (UTC)[reply]

People have questions. I have had many questions for you. I am not unique. :)

Are you embarrassed to have your user name on the help page? --Timeshifter (talk) 21:20, 19 February 2022 (UTC)[reply]

KCA table (again)

Hi- I'm coming to you due to your previous help/responses over at Help talk:Table#Nickelodeon Kids' Choice Awards table cleanup. I've just started the new combined table today (at User:Magitroopa/sandbox/KCA cleanup) and am now stuck at 2000. I feel stupid... but what exactly am I doing wrong? :P I'm guessing I maybe messed something up within the 'rowspan' numbers, but I'm just trying to extend Rosie down 1, as she also hosted in 2000. It also might have to do with my placement of either 'Hollywood Bowl' or that year's other hosts, as messing with that is getting me somewhat closer, but I still can't quite figure it out. Thanks in advance! Magitroopa (talk) 22:15, 28 April 2022 (UTC)[reply]

@Magitroopa: Since she was a cohost for 2000's Hollywood Bowl, I recommend duplicating her name in the hosts cell, similar to what is on Nickelodeon Kids' Choice Awards#Ceremony hosts. Jroberson108 (talk) 23:36, 28 April 2022 (UTC)[reply]

How does the sandbox page look now? I'm thinking of possibly adding in the dates of the ceremonies- similar to List of Tony Awards ceremonies#Ceremonies and Teen Choice Awards#Ceremonies (by year). Other than that, I'm wondering if the the table should be sized differently so it's centered/not just one long rectangular table- again, similar to those other two awards shows tables. Or is the rectangular table fine as that? I'm just thinking it might look a bit weird with all the white/empty space to the side (unless maybe images of some of the hosts are added? Obviously would have to include Rosie, Jack Black, John Cena, Whitney Houston, and Candace Cameron Bure due to their notability/the 'Multiple year hosts' section). Magitroopa (talk) 01:36, 29 April 2022 (UTC)[reply]

@Magitroopa: Adding a month and day sounds useful, especially if the first and second venues in 1994 and 1996 are held on different dates. If all the venues are held on the same month and day of each year, then perhaps putting the month and day in a note above or below the table might look less redundant.

I'm not sure what you mean by centered since all the tables are horizontally aligned to the left. If you want to make the table less tall and spread the data out some, which I recommend, then you can separate the hosts with commas instead of new lines, similar to one of your examples: List of Tony Awards ceremonies#Ceremonies. Five hosts doesn't look too odd next to a cell with one host and it would wrap naturally on small screens. Comparing visible data on my desktop, newlines make 1987-2005 and commas make 1987-2017 data visible without having to scroll. Even if you maintain the new lines, I would still recommend adding commas due to a long host name potentially wrapping on small devices per my last comment at Help talk:Table#Nickelodeon Kids' Choice Awards table cleanup. Omitting new lines and using middle dots instead of commas like the "Performers" column of Teen Choice Awards#Ceremonies (by year) might work better because they would add a little more whitespace between each host making them more readable.

As far as adding images of hosts, it doesn't seem necessary to add them to the table since their names link to their bio pages. You could float some images to the right of the table of some of the more popular hosts at some of the bigger venues. Jroberson108 (talk) 02:56, 29 April 2022 (UTC)[reply]

I've just added the # ceremonies, dates, and listed multiple hosts through {{hlist}}. Definitely looks much better, lol. And yeah, I see my misunderstanding on the 'centering' of the table.. it appears the Tony Award + Teen Choice table just did as you said ("...spread the data out some...") and set them to certain sizes to stretch them out. I don't think the performers really need to get listed, like they are in the Teen Choice table (I think Teen Choice might have a bigger focus on them?...) so I'm thinking it's likely close to being good/done (either way, much better than with the two separate tables, lol). Magitroopa (talk) 06:16, 29 April 2022 (UTC)[reply]

@Magitroopa: It does look better, especially with the full date. The "#" column helps to see how many rows there are. Regarding the "Performers" column, I was only referring to the format of the data, not adding a new column. So that the dates wrap properly on small screens (see MOS:DATERANGE), you will want to replace the en dash and its spaces (" – ") with {{snd}}, and replace the space between the months and days with  . For accessibility (e.g. screen readers), you can add scope="col" to all column headers, and you may need to use {{abbr|#|Number}} or something similar in the first column header. A table caption to summarize the content would help with accessibility too. The only other concern I have is that the links in the "#" column might be considered MOS:EGG, but not sure. If the column header were named "Ceremony", then it might be less likely; it's up to you. Jroberson108 (talk) 09:36, 29 April 2022 (UTC)[reply]

I think this should cover most of it. Not entirely sure on MOS:EGG regarding the # column, but if it really is against that, I'm sure that can easily be fixed in the future if needed- for now, I'll probably just leave it as-is. Only additional thing (apart from all of what you said) was adding the caption at the top of the table- per MOS:TABLECAPTION. This cleanup should also help with updating/adding future ceremonies for however many years it'll keep going- rather than needing to update the two separate tables. Magitroopa (talk) 18:20, 29 April 2022 (UTC)[reply]

@Magitroopa: I added missing code for the column headers' row. I would elaborate a bit more on the caption like appending ", venues, and hosts" or something similar, which helps with accessibility. Other than that, everything looks good. Jroberson108 (talk) 03:03, 30 April 2022 (UTC)[reply]

Hm, maybe "Kids' Choice Awards ceremony hosts and venues"?... I'll think about it and see if my mind comes up with anything else, lol. Either way, apologies for all the responses here, but thank you very much for all the help with the table- greatly appreciated! Magitroopa (talk) 07:31, 30 April 2022 (UTC)[reply]

@Magitroopa: You're welcome. Jroberson108 (talk) 07:48, 30 April 2022 (UTC)[reply]

No minor

Hello Jroberson108, I suppose you are right with your recent edit on Kalpa (time), but it is no minor edit. See Help:Minor edit#What not to mark as minor changes. It was not "Removing obvious vandalism". (I am not interested in the subject, i came to the article while repairing nbsp accidents, i.e. articles where "nbsp" is displayed accidently in the read view. I am de-N, en-2.) --Himbeerbläuling (talk) 07:02, 17 October 2022 (UTC)[reply]

@Himbeerbläuling: Good to know. I'll try to remember what is considered minor. Jroberson108 (talk) 07:34, 17 October 2022 (UTC)[reply]

Regex cleanup at List of Scottish clans

I'm doing some more now in a text editor to clean up the list's motto stuff, e.g. I've already replaced all the [from Latin: "English Version Here"] translations to [Latin: 'English Version Here'] per MOS:SINGLE and because this "from" is a useless word. (But I haven't saved that all into the article yet; still doing other cleanup.) I'm not sure what to do about all the instances of things like '''Motto:''' ''IN ARDUA NITOR'' which are against MOS:ALLCAPS. I guess they need to be converted to Title Case Like This, then the instances of short articles and pepositions like what are presently rendered as "IN" and "ET" and "PER" should be fully lowercased manually to "in" and "et" and "per", except at the beginning of the motto. And then later need to also replace the bare italics with {{lang|la}}, etc., as appropriate. But I'm not sure what to do about the IN ARDUA NITOR conversion to mixed case. I'm sure that's doable (if not in Notepad++ then in something, even if it's a bash script in Linux using sed or awk or something), but I've not had to contend with something like that in a decade or more. Any ideas? PS: Slogan (heraldry) also needs this all-caps cleanup, but is fortunately much shorter. — SMcCandlish ☏ ¢ 😼 07:04, 26 August 2023 (UTC)[reply]

@SMcCandlish: BTW, I did the regex find/replace in Sublime Text; switched from Notepad++. For the lowercase of the mottos, there should be some more advanced regex. Seems simular to one of the answers here. I'll have to look more into it tomorrow. Jroberson108 (talk) 07:32, 26 August 2023 (UTC)[reply]

Thanks, and no hurry. I've asked over at WT:HERALDRY whether these should really be in title case or in sentence case (external source usage seems mixed). Anyway, the clans article really has a lot of other formatting problems (excessive use of boldface, <small>...</small> all over the place, inconsistent linebreaking, extraneous "." everywhere, etc.), so there's a lot to do in the interim. :-) — SMcCandlish ☏ ¢ 😼 07:36, 26 August 2023 (UTC)[reply]

Update: Done with my cleanup run on that article for now, aside from the ALL-CAPS issue. — SMcCandlish ☏ ¢ 😼 10:48, 26 August 2023 (UTC)[reply]

@SMcCandlish: So will there be a case change? Also, I came up with a regex that will allow me to encapsulate all mottos after a few manual fixes, which should make it easier to target the actual motto text, especially if there is a case change.

Ex 1 orig = '''Motto:''' ''SALUS PER CHRISTUM'' [Latin, 'Salvation Through Christ']

Ex 1 tag = '''Motto:''' <motto>SALUS PER CHRISTUM</motto> [Latin, 'Salvation Through Christ']

Ex 1 done = '''Motto:''' {{lang-la|SALUS PER CHRISTUM}} [Latin, 'Salvation Through Christ']

Ex 2 orig = '''Motto:''' ''IN DEFENCE OF THE DISTRESSED''

Ex 2 tag = '''Motto:''' <motto>IN DEFENCE OF THE DISTRESSED</motto>

Ex 2 done = '''Motto:''' IN DEFENCE OF THE DISTRESSED

Some will use "lang-la" or "lang-fr" based on the mention of Latin or French on the same line. The surrounding italics has been removed too since the lang template displays italics and English doesn't need it.

Assuming the page doesn't change, this is what I have to add the <motto> tags and change them to "lang" templates. Note: to display the tag on the page, they would need to be commented out  and .

Only edit table code.

Manually fix spacing and change to curly quote:
- Motto:''''' VRAYE FOI
- Motto:'''Concedo nulli
- Motto:''' THIS I"LL DEFEND
- Motto:''' I'LL DEFEND
- Motto:''' THIS I'LL DEFEND
- Motto:''' ''Bi'se mac ant' Slaurie
- Motto:''' ''J'ESPERE

Add tags:
f [regex, 295]: Motto:''' ('{2})?([\w’\- ]+)
r: Motto:''' $1<motto>$2</motto>

Manually add tags:
- Motto: A)''' BE IT FAST
- Motto: B)''' ''DISSIPATE
- Motto:''' ''{{'}}S RIOGHAL MO DHREAM
- McDowell (2nd motto)

Change curly quotes to straight per MOS:
f [8]: ’
r: '

Remove italics around motto:
f [regex, 221]: ''(<motto>[^<]+</motto>)''
r: $1

Remove trailing period:
f [56]: </motto>.
r: </motto>

Move trailing space outside tag:
f [6]:  </motto>
r: </motto> 

Change motto tags to lang template:
f [regex case, 137]: <motto>([^<]+)</motto>([^\[]+\[Latin,)
r: {{lang-la|$1}}$2
f [regex case, 18]: <motto>([^<]+)</motto>([^\[]+\[French,)
r: {{lang-fr|$1}}$2
f [regex case, 2]: <motto>([^<]+)</motto>([^\[]+\[Middle French,)
r: {{lang-frm|$1}}$2
f [regex case, 1]: <motto>([^<]+)</motto>([^\[]+\[<nowiki />\[\[Middle French\]\],)
r: {{lang-frm|$1}}$2
f [regex case, 2]: <motto>([^<]+)</motto>([^\[]+\[Scots,)
r: {{lang-sco|$1}}$2
f [regex case, 1]: <motto>([^<]+)</motto>([^\[]+\[<nowiki />\[\[Scots language\|Scots\]\],)
r: {{lang-sco|$1}}$2
f [regex case, 6]: <motto>([^<]+)</motto>([^\[]+\[Scottish Gaelic,)
r: {{lang-gd|$1}}$2
f [regex case, 5]: <motto>([^<]+)</motto>([^\[]+\[<nowiki />Scottish Gaelic,)
r: {{lang-gd|$1}}$2

Manually change motto tag to lang template:
- Abercromby

Remove remaining motto tags (assume English):
f [regex, 96]: <motto>([^<]+)</motto>
r: $1

Missed:
40 x Latin,
5 x French,
1 x Scottish Gaelic,
1 x Scots,

Jroberson108 (talk) 00:34, 27 August 2023 (UTC)[reply]

Lawdy! That's complicated! I didn't get an answer to my style queries at WT:HERALDRY, so I guess the thing to do is go with "Sentence case like this", in agreement with the majority of the source material on such matters. Of the books I have that are pertinent (heraldry works and clans-and-tartans books), they all use that format but one. All the conversion I did last night of the English translations to 'Title Case Like This' will need to be undone. Dammit. I was approaching them like book or song titles, but should have checked first how clan books were treating them. Some of what you listed above might be better to do as its own cleanup pass (remove trailing ".", fix curly quotes, etc.) to make the raw data more consistent. — SMcCandlish ☏ ¢ 😼 00:45, 27 August 2023 (UTC)[reply]

@SMcCandlish: I found some other languages and am adjusting the code above to accommodate. I wonder if it would have been faster to just have someone manually adjust the data, maybe 300 rows. This is all single use too. Anyways, did you want me to also adjust to "Sentence case" or do you have a manually adjusted one to post? You mentioned "Title Case", so if all that is left is to change the case, then less find/replace with regex. Jroberson108 (talk) 01:58, 27 August 2023 (UTC)[reply]

@SMcCandlish: I don't think doing this through regex is the best approach. It's quite complicated and is probably best to manually change it. Identifying the language through regex is the problem. Even with the above code, at least 47 mottos aren't adjusted with a language that should be, mostly because of ref tags containing links that separate the motto and the language. I think I'll call this one quits. Jroberson108 (talk) 02:37, 27 August 2023 (UTC)[reply]

Ah, okay. Well thank you for the effort in trying! I guess 200-something entries isn't that bad a job to deal with by hand. — SMcCandlish ☏ ¢ 😼 02:41, 27 August 2023 (UTC)[reply]

Got it done. My wrists hurt from all that typing, LOL. But it's a vast improvement. No more SCREAMING ALL-CAPS ALL OVER THE PLACE. — SMcCandlish ☏ ¢ 😼 05:04, 27 August 2023 (UTC)[reply]

@SMcCandlish: Well that took much less time than what I was doing (about 1 day) through regex and testing, and probably more accurate too. For the other task of moving the crest images to a new column, I think it took me an hour to write the regex and do some testing and adjustments, probably faster than doing it manually. It really depends on the complexity. Jroberson108 (talk) 05:32, 27 August 2023 (UTC)[reply]

Aye. Well, sorry if I wasted your time. Dang. I did end up using some regex stuff to help with what I did in that last pass, e.g. to find all the ALLCAPS mottoes (but only the mottoes), and so on, in multiple passes, and what you wrote out above helped with that. Then there was lots and lots of manual tweaking. Still need some stuff, like Modern English equivalents of some of the more opaque Middle English mottoes. But enough for one day! — SMcCandlish ☏ ¢ 😼 06:30, 27 August 2023 (UTC)[reply]

Nomination for merger of Template:COVID-19 pandemic data/styles.css

Template:COVID-19 pandemic data/styles.css has been nominated for merging with Template:COVID-19 pandemic data/styles2.css. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. House Blaster^talk 19:30, 26 December 2023 (UTC)[reply]

@HouseBlaster: Thanks for explaining the TfD process at Template_talk:Static row numbers#All subtemplates should be deprecated or auto-substituted. Because of that, I can now see that the styles are in "To review" at Wikipedia:Templates for discussion/Holding cell. Jroberson108 (talk) 10:42, 14 January 2024 (UTC)[reply]

Persistent "Senior posting" section in Hindu leader infobox

Jroberson108, many thanks for your valuable input on A._C._Bhaktivedanta_Swami_Prabhupada's proposed revision. Just posted the two pairs of chapters that you had suggestions on, asking for feedback.

You might have noticed that the Hindu leader infobox used there has an odd "Senior posting" section. I asked for help on the template's talk page, where others reported the issue as well, but looks like the talk page is as abandoned as the template itself. Still, it works fine, used in a number of articles, and has features that its proposed replacement doesn't — like a convenient module for audio recordings. Since templates seem to be your area of interest, would you have a suggestion how to get rid of that section or rename it to something more apropos? Thank you. Regards, Cinosaur (talk) 12:28, 7 April 2024 (UTC)[reply]

@Cinosaur: I took a quick look at the source code for {{Infobox religious biography}}. The "post" section header changes based on what the "religion" property is set to. I responded on that talk page in more depth, but you just need to change "religion" to Hinduism and move the rest to "denomination" for the header to be "Religious career". Jroberson108 (talk) 17:55, 7 April 2024 (UTC)[reply]