User talk:Happy5214/Archive 2

The Center Line: Winter 2015

 * —MediaWiki message delivery (talk) on behalf of 18:37, 28 February 2015 (UTC)

Quixotic plea
You are invited to join the discussion at Wikipedia talk:Wikipediholism test. Thanks. —  06:24, 23 May 2015 (UTC)

The Center Line: Spring 2015

 * —MediaWiki message delivery (talk) on behalf of Imzadi1979 12:13, 31 May 2015 (UTC)

The Center Line: Summer 2015

 * —MediaWiki message delivery (talk) delivered on behalf of Imzadi1979 05:23, 3 September 2015 (UTC)

The Center Line: September 2015
  Volume 8, Issue S1 • September 2015 • About the Newsletter
 * Happy 10th Anniversary!

1=

• USRD through the years

• A goal for success

• From the first spinning cogs to controlling the power of the moon 1=

• Article assessment over time

• How to measure a WikiProject's load

• Conflict over article titles 1=

• Arbitration case closes

• Collaboration

• Our valued contributors

 Archives • Newsroom • Full Issue • Shortcut: WP:USRD/NEWS
 * —delivered by MediaWiki message delivery (talk) on behalf of Imzadi1979 (talk) on 23:58, 28 September 2015 (UTC)

ArbCom elections are now open!
MediaWiki message delivery (talk) 16:38, 23 November 2015 (UTC)

The Center Line: November 2015
  Volume 8, Issue 4 • November 2015 • About the Newsletter

1=
 * Departments

• Assessment roundup

• Portal selected articles and pictures

• KML Corner 1=
 * Features

• Constructing a road junction list

• WikiConference USA 2015

• The Junction template and you

• Harnessing map archives 1=
 * State and national updates

• State updates

• In other project news...

 Archives • Newsroom • Full Issue • Shortcut: WP:USRD/NEWS
 * —delivered by MediaWiki message delivery (talk) on behalf of on 22:59, 30 November 2015 (UTC)

WikiProject X Newsletter • Issue 6
Newsletter • January 2016

Hello there! Happy to be writing this newsletter once more. This month:

What comes next

Some good news: the Wikimedia Foundation has renewed WikiProject X. This means we can continue focusing on making WikiProjects better.

During our first round of work, we created a prototype WikiProject based on two ideas: (1) WikiProjects should clearly present things for people to do, and (2) The content of WikiProjects should be automated as much as possible. We launched pilots, and for the most part it works. But this approach will not work for the long term. While it makes certain aspects of running a WikiProject easier, it makes the maintenance aspects harder.

We are working on a major overhaul that will address these issues. New features will include:
 * Creating WikiProjects by simply filling out a form, choosing which reports you want to generate for your project. This will work with existing bots in addition to the Reports Bot reports. (Of course, you can also have sections curated by humans.)
 * One-click button to join a WikiProject, with optional notifications.
 * Be able to define your WikiProject's scope within the WikiProject itself by listing relevant pages and categories, eliminating the need to tag every talk page with a banner. (You will still be allowed to do that, of course. It just won't be required.)

The end goal is a collaboration tool that can be used by WikiProjects but also by any edit-a-thon or group of people that want to coordinate on improving articles. Though implemented as an extension, the underlying content will be wikitext, meaning that you can continue to use categories, templates, and other features as you normally would.

This will take a lot of work, and we are just getting started. What would you like to see? I invite you to discuss on our talk page.

Until next time,

Harej (talk) 02:53, 20 January 2016 (UTC)

WikiProject X Newsletter • Issue 7
Newsletter • February 2016

This month:

One database for Wikipedia requests

Development of the extension for setting up WikiProjects, as described in the last issue of this newsletter, is currently underway. No terribly exciting news on this front.

In the meantime, we are working on a prototype for a new service we hope to announce soon. The problem: there are requests scattered all across Wikipedia, including requests for new articles and requests for improvements to existing articles. We Wikipedians are very good at coming up with lists of things to do. But once we write these lists, where do they end up? How can we make them useful for all editors—even those who do not browse the missing articles lists, or the particular WikiProjects that have lists?

Introducing Wikipedia Requests, a new tool to centralize the various lists of requests around Wikipedia. Requests will be tagged by category and WikiProject, making it easier to find requests based on what your interests are. Accompanying this service will be a bot that will let you generate reports from this database on any wiki page, including WikiProjects. This means that once a request is filed centrally, it can syndicated all throughout Wikipedia, and once it is fulfilled, it will be marked as "complete" throughout Wikipedia. The idea for this service came about when I saw that it was easy to put together to-do lists based on database queries, but it was harder to do this for human-generated requests when those requests are scattered throughout the wiki, siloed throughout several pages. This should especially be useful for WikiProjects that have overlapping interests.

The newsletter this month is fairly brief; not a lot of news, just checking in to say that we are hard at work and hope to have more for you soon.

Until next time,

Harej (talk) 01:44, 24 February 2016 (UTC)

FM 3005
I see you redirected FM 3005 to a list. I did not see a discussion on the article's talk page, nor did I see in the edit summary why the article was being moved (ie: per consensus at such-and-such page). Please advise -- nsaum75 !Dígame¡ 21:52, 11 March 2016 (UTC)
 * There was a consensus at WT:USRD to merge farm-to-market road articles that were not long enough to substantiate having a separate article into list "articles", using what our project calls the Rockland County Scenario. If it helps, I will link the discussion in the edit summaries for future merges of this type. -happy5214 23:29, 11 March 2016 (UTC)

WikiProject X Newsletter • Issue 8
Newsletter • March / April 2016

This month:

Transclude article requests anywhere on Wikipedia

In the last issue of the WikiProject X Newsletter, I discussed the upcoming Wikipedia Requests system: a central database for outstanding work on Wikipedia. I am pleased to announce Wikipedia Requests is live! Its purpose is to supplement automatically generated lists, such as those from SuggestBot, Reports bot, or Wikidata. It is currently being demonstrated on WikiProject Occupational Safety and Health (which I work on as part of my NIOSH duties) and WikiProject Women scientists.

Adding a request is as simple as filling out a form. Just go to the Add form to add your request. Adding sources will help ensure that your request is fulfilled more quickly. And when a request is fulfilled, simply click "mark as complete" and it will be removed from all the lists it's on. All at the click of a button! (If anyone is concerned, all actions are logged.)

With this new service is a template to transclude these requests: Wikipedia Requests. It's simple to use: add the template to a page, specifying,  , or  , and the list will be transcluded. For example, for requests having to do with all living people, just do. Use these lists on WikiProjects but also for edit-a-thons where you want a convenient list of things to do on hand. Give it a shot!

Help us build our list!

The value of Wikipedia Requests comes from being a centralized database. The long work to migrating individual lists into this combined list is slowly underway. As of writing, we have 883 open tasks logged in Wikipedia Requests. We need your help building this list.

If you know of a list of missing articles, or of outstanding tasks for existing articles, that you would like to migrate to this new system, head on over to Wikipedia Requests and help out. Doing this will help put your list in front of more eyes—more than just your own WikiProject.

An open database means new tools

WikiProject X maintains a database that associates article talk pages (and draft talk pages) with WikiProjects. This database powers many of the reports that Reports bot generates. However, until very recently, this database was not made available to others who might find its data useful. It's only common sense to open up the database and let others build tools with it.

And indeed: Citation Hunt, the game to add citations to Wikipedia, now lets you filter by WikiProject, using the data from our database.

Are you a tool developer interested in using this? Here are some details: the database resides on Tool Labs with the name. The table that associates WikiProjects with articles and drafts is called. Pages are stored by talk page title but in the future this should change. Have fun!

On the horizon


 * The work on the CollaborationKit extension continues. The extension will initially focus on reducing template and Lua bloat on WikiProjects (especially our WPX UI demonstration projects), and will from there create custom interfaces for creating and maintaining WikiProjects.
 * The WikiCite meeting will be in Berlin in May. The goal of the meeting is to figure out how to build a bibliographic database for use on the Wikimedia projects. This fits in quite nicely with WikiProject X's work: we want to make it easier for people to find things to work on, and with a powerful, open bibliographic database, we can build recommendations for sources. This feature was requested by the Wikipedia Library back in September, and this meeting is a major next step. We look forward to seeing what comes out of this meeting.

Until next time,

Harej (talk) 01:29, 20 April 2016 (UTC)

Template:Routelist row/testcases
Module:Road data/util has  function that complies with, and is shared among Template:Routelist row/sandbox and Template:Infobox road/sandbox. I reinstated the test case you reverted. See also Template:Infobox road/testcases. Chinissai (talk) 09:17, 10 May 2016 (UTC)

API change will break your bot
I noticed that HappyBot has been using http:// to access the API, rather than https://  This is going to break soon, because of changes to the API. You can find more information in this e-mail message. If you need help updating your code to use https://, then you might be able to find some help at w:en:Wikipedia:Bot owners' noticeboard or on the mailing list. Good luck, Whatamidoing (WMF) (talk) 22:01, 2 June 2016 (UTC)
 * Thanks for the notice. I need to upgrade my scripts to PWB core anyway, so I'll get to work on that in short order.

WikiProject X Newsletter • Issue 9
Newsletter • May / June 2016

Check out this month's issue of the WikiProject X newsletter, featuring the first screenshot of our new CollaborationKit software!

Harej (talk) 00:23, 25 June 2016 (UTC)

Wikipedia:WikiProject United States/The 50,000 Challenge
--MediaWiki message delivery (talk) 02:39, 8 November 2016 (UTC)

Hello
I see you recently edited a page about Essex California in San Bernardino country. No reason, but i used to live in essex as a young child. For ten years to be exact Roadster3477 (talk) 16:06, 27 December 2016 (UTC)

CSS styling in templates
Hello everyone, and sincere apologies if you're getting this message more than once. Just a heads-up that there is currently work on an extension in order to enable CSS styling in templates. Please check the document on mediawiki.org to discuss best storage methods and what we need to avoid with implementation. Thanks, m:User:Melamrawy (WMF), 09:11, 6 February 2017 (UTC)

WikiProject X Newsletter • Issue 10
Issue 10 of the WikiProject X newsletter is here!

This month, we discuss the new CollaborationKit extension. Here's an image as a teaser:



23:59, 3 March 2017 (UTC)

The Center Line: Spring 2017
  Volume 9, Issue 1 • Spring 2017 • About the Newsletter

1=
 * Departments

• Assessment roundup

• Portal selected articles and pictures 1=
 * Features

• Commons and Wikidata revamp

• Route logs for junction lists

• Finding friends at the DOT

• This space for rent 1=
 * State and national updates

• State updates

• In other project news...

 Archives • Newsroom • Full Issue • Shortcut: WP:USRD/NEWS
 * —delivered by MediaWiki message delivery (talk) on behalf of on 01:04, 14 April 2017 (UTC)

WikiProject X Newsletter • Issue 11
Newsletter • February 2018

Check out this month's issue of the WikiProject X newsletter, with plans to renew work with a followup grant proposal to support finalising the deployment of CollaborationKit!

-— Isarra ༆ 21:26, 14 February 2018 (UTC)

Upcoming changes to wikitext parsing
Hello,

There will be some changes to the way wikitext is parsed during the next few weeks. It will affect all namespaces. You can see a list of pages that may display incorrectly at Special:LintErrors. Since most of the easy problems have already been solved at the English Wikipedia, I am specifically contacting tech-savvy editors such as yourself with this one-time message, in the hope that you will be able to investigate the remaining high-priority pages during the next month.

There are approximately 10,000 articles (and many more non-article pages) with high-priority errors. The most important ones are the articles with misnested tags and table problems. Some of these involve templates, such as infoboxes, or the way the template is used in the article. In some cases, the "error" is a minor, unimportant difference in the visual appearance. In other cases, the results are undesirable. You can see a before-and-after comparison of any article by adding ?action=parsermigration-edit to the end of a link, like this: https://en.wikipedia.org/wiki/Arthur_Foss?action=parsermigration-edit (which shows a difference in how infobox ship is parsed).

If you are interested in helping with this project, please see Linter. There are also some basic instructions (and links to even more information) at https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2018-April/001836.html You can also leave a note at WT:Linter if you have questions.

Thank you for all the good things you do for the English Wikipedia. Whatamidoing (WMF) (talk) 21:18, 19 April 2018 (UTC)

Nomination for deletion of Module:U.S. States
Module:U.S. States has been nominated for deletion. You are invited to comment on the discussion at the module's entry on the Templates for discussion page. &#123;&#123;3x&#124;p&#125;&#125;ery (talk) 02:27, 7 May 2018 (UTC)
 * I forgot about that one. It doesn't appear to be needed anymore. -happy5214 03:55, 7 May 2018 (UTC)

Nomination for deletion of Module:AASHTO minutes
Module:AASHTO minutes has been nominated for deletion. You are invited to comment on the discussion at the module's entry on the Templates for discussion page. &#123;&#123;3x&#124;p&#125;&#125;ery (talk) 17:23, 16 June 2018 (UTC)

Highway 2
Hey, thanks for the help with Highway 2 (Israel). I don't get one thing though, why does the Infobox not work without the Module? Is the Infobox doc out of date? I also don't think its really logical to think that an editor will know how to create a Module (I have no idea where to even start), but even more so if it's not mentioned at all in the docs. --Gonnym (talk) 07:48, 31 July 2018 (UTC)
 * Infobox road invokes Module:Infobox road, which invokes a function in Module:Road data/browse (the actual browse box generator). That uses Module:Road data/parser and data stored in string modules, like the one I created for Israel, to generate links and shields. Other applications, like jct and routelist row, also use the same data.
 * I agree that the docs are a mess and largely out-of-date. The established (American) road editors all know where the string modules are and the basics of adding to them, and the fact that we haven't had to account for new editors by updating the docs is a sad statement about Wikipedia and WP:HWY. Infobox road has been undergoing a rewrite for years now, but progress has stalled due to RL. I think we were hoping until it was finished to update the docs. We may have to expedite it. -happy5214 08:08, 31 July 2018 (UTC)
 * Ah, thanks for that info! I always read to docs so see what info I need to add and what previous info is deprecated so was surprised by that module. Another thing which I can't change and it's probably module-related - how is "Highway 2" being translated into Hebrew? It's not a field from the infobox. If it is inside the module, then there is a bug with Hebrew. Currently, its translating it like a Latin left-to-right language, but Hebrew is a right-to-left language so instead of "Highway 2", it would be "2 Highway". Can this be fixed? --Gonnym (talk) 20:34, 1 August 2018 (UTC)
 * The translations are not in Lua yet. The translation page for Israel is Template:Infobox road/translation/ISR, which I have edited to hopefully fix that issue. It was RTL, but the number was out of position. -happy5214 21:21, 1 August 2018 (UTC)
 * Yes, it's fixed now. Thank you! --Gonnym (talk) 22:36, 1 August 2018 (UTC)
 * Actually one more issue with Infobox Road. Currently it has an option for alternate_name but there is no companion field for a translated_alternate_name nor is the alternate_name option numbered. So visually I guess it works just putting them all together (though it too might be debatable), but from my understanding of the point of infoboxes, it was so they would all be key-value pairs. If so, it does work, as in this example there are 2 English alt names with 2 translated Hebrew names. Is this an issue? If so, is this fixable? --Gonnym (talk) 22:43, 1 August 2018 (UTC)
 * I don't think it's a huge issue. All numbering the parameters would do is switch the plainlist code to the template, making it less flexible. -happy5214 22:57, 1 August 2018 (UTC)
 * Well that isn't the only thing they'd do, they'll then be able to match a translated_alternate_name field as the translated value. For a name at alt_name_1 the translated value will be at translated_alt_name_1. --Gonnym (talk) 23:15, 1 August 2018 (UTC)

It would be much easier to do in Lua. Using normal template code, we'd have to explicitly specify an arbitrary number of alternate names. The coding would be an absolute mess. -happy5214 23:44, 1 August 2018 (UTC)
 * That I can imagine (though Template:Infobox officeholder do this and allow up to 16 repeating full sections). If this is done in Lua, how does this translate to actual editor use? --Gonnym (talk) 23:50, 1 August 2018 (UTC)
 * By the way, I outdented the discussion, so indent one level from this post in your reply.
 * A Lua module could do a loop on the numerical indices for these parameters (see jct and  in Module:Jct for an example of such a loop), so we could have an unlimited number of alternate names without making the template code longer. jct used to only allow 4 routes, but now we can enter any number of routes into it with minimal additional overhead.
 * A normal user (like you) would see something like you suggested (alternate_name1 and alternate_translation1; alternate_name2 and alternate_translation2; and so on). The fact that it's done in Lua rather than ordinary Wiki syntax should be transparent to non-template/module writers. -happy5214 00:00, 2 August 2018 (UTC)
 * Ah, that's amazing, it's exactly what I wanted. Well, hope that one day it would be added. Thanks for all the info and help! --Gonnym (talk) 00:05, 2 August 2018 (UTC)

Highway 2 table templates
Hey, I was trying to create the table in my sandbox like in your example but couldn't to get it to work as I ran into a few issues. Thanks for helping out! --Gonnym (talk) 15:01, 9 August 2018 (UTC)
 * 1) Several exits are on city boarders. How do I input the names and have both city articles linked? Currently it does City A and City B.
 * 2) The Name column information does not appear in the column.
 * 3) How do I add more than 1 road information to the Destinations column? Some exits have different roads going west and east.
 * 4) How do I add a non-Highway or Route road? I'm getting invalid type.
 * First of all, start at the southern terminus at Highways 20 and 1. We are required to include non-freeway intersections with notable roads (in this case, those signed as numbered Highways or Routes). I'll answer the rest in the above order.
 * The U.S jctint versions allow you to add a location2 parameter, which would result in it being formatted like (from Interstate 5 in California) "Irvine–Tustin line". Unfortunately, that's a U.S.-specific feature right now. For now, just do similar markup manually and use location_special instead of location.
 * I don't really understand this question.
 * To add multiple numbered roads, just add extra parameters to jct, as I did in my sandbox for the second row. For additional unnumbered roads, just tack them onto the end of road and separate them with " / " (with the spaces).
 * First of all, only add unnumbered roads if it's a grade-separated interchange. In this case, don't use jct and just add the wikitext directly, following the above "spaced slash" rule.
 * Hope this helps. -happy5214 22:16, 9 August 2018 (UTC)
 * Regarding the southern half, I agree that should be added, I just wanted to start converting the existing table first. Issue #1 resolved. #2 had was an issue where the names weren't appearing, but somehow it fixed itself... #3+#4 - could you explain this in more detail? Some are grade-separated, while others are not interchanges at all and just normal exits. Should these not be listed? Also, additional question, is there an option for a "sub1name_ref" for the "District" column? I want to add the official map with boarders as a ref to it. --Gonnym (talk) 22:34, 9 August 2018 (UTC)
 * There is sub1_ref, which is probably what you want. If that's the source you'll want to use for all Israeli highways, I can hardcode it into ISRtop when I write it.
 * The best way to define what to include in a junction list is all notable intersections. By consensus, all grade-separated interchanges and all at-grade intersections with "notable" roads (in this case, numbered Highways and Routes) should be included. If this example helps, I checked the two exits south of Netanya (where there is no crossing), and I'd say to include those as well. -happy5214 22:57, 9 August 2018 (UTC)
 * Both sub1_ref and sub2_ref could be hardcoded. One is a map of district boarders, the other is a map of municipality boarders. Both from the official government map. Regarding my question from the Highway 2 talk page, do you think it's possible to add another field to ISRint for "name_local" which would then format any name entered here on a separate line with brackets around it? --Gonnym (talk) 07:21, 10 August 2018 (UTC)
 * Another issue,  leads to Central District instead of Central District (Israel). I tried adding   but that didn't work. This probably should also be hardcoded if possible. --Gonnym (talk) 07:54, 10 August 2018 (UTC)
 * One more issue - I was trying to split the Haifa exits like you did, but for some reason my second row isn't formatting correctly. No idea what I did wrong. --Gonnym (talk) 14:16, 10 August 2018 (UTC) - fixed. --Gonnym (talk) 16:35, 10 August 2018 (UTC)
 * It would be possible to add a parameter like name_trans, though I'd prefer to wait until we have consensus on the formatting before adding it. sub1dab only works with jctint/core directly (it's cdab in ISRint, which should really be ddab), and surprisingly it doesn't disambiguate the district, but rather the location. There's no parameter in Module:Jctint/core to override the sub1 link other than the region, which creates an American-style disambiguation (in this case, the link would be to "Central District, Israel" instead of "Central District (Israel)"). We'll have to develop an internationally sensible solution to this. Until then, use district_special and hardcode the link.
 * Also, I checked with a fellow USRD member on IRC, and he said that the only intersections in Tel Aviv which should be included are the ones in my version of the junction list. In addition, my rule is that the distances should be measured to the point of crossing, not at the ramp. You can use km2 if you want to do a range of distances (say, from the exit ramp to the entrance ramp). Somehow, you managed to lose a kilometer off the total distance. -happy5214 21:50, 10 August 2018 (UTC)
 * the KM loss might be because of the ramp distance. Either that or I messed up my calculation somewhere along the way. Regarding the Tel Aviv intersections, what is the criteria that you choose which to add to a list? Thanks for all that information! I think I'm done with the current table until the discussion at the article decides what to do so I won't redo work that will later be removed (including fixing locations on the google map and the tel aviv list). --Gonnym (talk) 22:07, 10 August 2018 (UTC)
 * Just rechecked and my 2 maps distance is the same as yours, so I probably made a mistake somewhere in the northern section. --Gonnym (talk) 22:24, 10 August 2018 (UTC)
 * Fredddie had mentioned an "exception" to the grade-separated intersection rule I mentioned earlier. He said that the grade-separated intersections within Tel Aviv with unnumbered roads looked to him to be "local-express" situations and that they shouldn't be included. The remaining intersections you have with unnumbered roads appear to be at-grade and shouldn't be included anyway.
 * As for the distances, you really don't need two different maps. What I do is map the whole route, then check the distance to a given intersection from the start of the route. Adding up distances from smaller segments can cause inaccurate results due to round-off error. This highway is tricky, as it kept rerouting me to Highway 20 (being the faster route). -happy5214 23:22, 10 August 2018 (UTC)
 * I initially did that but then decided that while for me it would be easier, it makes a sub-par source. With my source you were clearly able to see that I calculated at the ramp and not at the intersection, making verifying the distance much easier, compared to just the route which everyone can calculate a bit differently. However, I don't think my map will work with the intersection as then it won't be 1 straight route. I will have to see if there is some workaround for that. Regarding the "local-express", I have no idea what that is. If "importance" is a factor, then the ones at the the KM markers of 3.3 (leads to one of the biggest train stations, entrance to highway 2, and an entrance to another city), 4.7 (leads to another big train station and entrance to highway 2), 5.6 (leads to entrance to highway 2 and an entrance to another city) and 6.6 (central road which connects a few cities and has entrances to highway 2) are important, but all are grade level as if I'm not mistaken, all Tel Aviv ones are. --Gonnym (talk) 23:41, 10 August 2018 (UTC)

See local-express lanes for that definition. If you look at the source of my sandbox, you'll see three commented-out rows for the "local-express" intersections I asked Fredddie about. Those are the only grade-separated intersections I found between the Highway 20 intersections.

If an intersection has explicit signage pointing to a numbered highway (like TO Highway 1 in the second row), we often include it. But since Highway 20 is so close to Highway 2, it may be too cluttered in this case to include every such intersecting road. -happy5214 00:07, 11 August 2018 (UTC)

A question
Hi! First off, thank you so much for your help on the Template:TURint, it really helped me out. I do however have one more question. I am a major n00b when it comes to Lua and I was wondering if there was a way to extend only the bridge/tunnel column further than one row. For example if a long tunnel crosses both a county and provincial line, would there be a way I could extend the tunnel column to show it on the template? Thanks in advance! (Central Data Bank (talk) 09:04, 29 August 2018 (UTC))
 * Greetings! For row spanning, Module:Jctint/core allows jspan (for everything, but which allows per-column overrides) and pspan (specifically for "places" like bridges and tunnels). However, neither is currently mapped within TURint. If what you're trying to do is have a tunnel that crosses a boundary span 2 rows, where each row is a separate province or county, that's generally discouraged. The examples on MOS:RJL, as well as most articles I've seen in the U.S., instead use a single row. The province would say something like (using an American state example) "California–Nevada line". I think the reasoning is accessibility-related, but I'm not 100% sure about that. U.S. versions of this template (like CAint) have parameters like county2, which the template will recognize and output in the appropriate form. TURint doesn't yet, so I'll go ahead and massage that in. I'll let you know when I'm done. -happy5214 09:31, 29 August 2018 (UTC)
 * Thank you so much!!
 * There's no need to ping me on my own talk page. The ping didn't even go through because you didn't sign your post. ;) In any event, I think I'm done. Please test it. Use province for 1 province and province1 and province2 for 2 provinces. Districts work similarly. I also reinstated province_special and district_special, so if there's anything not handled, you can just pass the wikitext to one of those. -happy5214 10:03, 29 August 2018 (UTC)
 * Thanks for the changes! However, when I tested it, all the provinces and districts appear in red since they are linked to a (district), Turkey article. For example, instead of being linked to the district Bornova, it is linked to Bornova, Turkey. Same goes for the provinces. Perhaps I'm doing something wrong when I test it? Check out the article Otoyol 30 as a reference. In any case, thank you for all your help! (Central Data Bank (talk) 10:12, 29 August 2018 (UTC))
 * It's not you. I forgot to remove a parameter in the code. It should be fixed now. Be aware, though, that if any districts have to be disambiguated by province, you'll have to use district_special and manually provide the link. -happy5214 10:23, 29 August 2018 (UTC)
 * You, sir, are an awesome human being. Thank you so much! :) (Central Data Bank (talk) 11:15, 29 August 2018 (UTC))

WikiProject X Newsletter • Issue 12
Newsletter • August 2018

This month: WikiProject X: The resumption

Work has resumed on WikiProject X and CollaborationKit, backed by a successfully funded Project Grant. For more information on the current status and planned work, please see this month's issue of the newsletter!

-— Isarra ༆ 22:24, 30 August 2018 (UTC)

Module:Jcon
I don't feel like I need consensus as the version you made wasn't used since 2014. The changes make it return the output it should. Jcon is different from jct in may ways. If you want I can add it to TfD. – BrandonXLF   (t@lk)  20:07, 4 October 2018 (UTC)
 * You have broken several articles with your changes. Consensus aside, please test your changes before disrupting articles. -happy5214 20:10, 4 October 2018 (UTC)
 * The errors are fixed. And they were when you reverted my edits. Look at Category:Pages with script errors. What's wrong now? – BrandonXLF   (t@lk)  20:13, 4 October 2018 (UTC)
 * You don't need to ping me on my own talk page. I checked Ontario Highway 11 before reverting your changes, and there were script errors. After the revert, they're gone. I don't think that's a coincidence. As an aside, you should try to integrate your changes into the modules I linked to on your talk page. -happy5214 20:17, 4 October 2018 (UTC)
 * I didn't see errors. Maybe you didn't purge? I'm going to restore my changes on the module as it's not used and do more testing. I pinged you because I forgot to sign my post and I don't know it that messed things up. – BrandonXLF   (t@lk)  20:19, 4 October 2018 (UTC)
 * I'd prefer that you use a separate sandbox version so as to not inhibit any testing I may do on my original code. As long as you leave the template itself alone, it should be fine. -happy5214 20:23, 4 October 2018 (UTC)
 * I'm not getting any error at User:BrandonXLF/A (a copy of Ontario Highway 11). Any more issues? – BrandonXLF   (t@lk)  20:44, 4 October 2018 (UTC)
 * The expensive parser function count is within limits, though I'd argue it's still too high. I'm still trying to understand why you need a completely Ontario-specific module instead of just wrapping Module:Jct and mapping the jcon interface to that, as I had done in my version of the module. -happy5214 08:02, 5 October 2018 (UTC)
 * It wasn't working as the template did. I'll remake it in the sandbox and we can see what can be done? There's test cases at Template:Jcon/testcases. – BrandonXLF   (t@lk)  14:07, 5 October 2018 (UTC)

I've imported your new regional shield names into the string module that jct uses, so those match. The shield spacing is cosmetic, so I won't worry about that. Here are the other issues I saw: Anything else? -happy5214 14:39, 5 October 2018 (UTC)
 * nolink doesn't work. This is actually an issue in jct that we'll have to fix.
 * I don't believe the shield sizes should be adjustable by a template user. The sizes are chosen for a reason.
 * Highway 407's ETR shield should not be in the default Highway type. The proper usage for something like that would be  (which produces ). I've also added a Toll type for the provincially managed toll highways. I don't believe the typical shields are used on any of these tolled highways (you would know better than I would, though), so using the default ON 407 shield might be factually incorrect.
 * The street name placement is an issue, which would have to be fixed either in Module:Jcon or in Module:Jct.
 * I have no idea what ot is for. The parameters in general are poorly named.
 * The extra icons are in, or can be added to, Module:Jct.  (producing ) has the bus symbol, for example. But such an icon by itself can easily be an MOS violation.
 * Just because you don't believe some parameters shouldn't be included, doesn't mean they shouldn't. There are many reasons why you'd want to change the size. And It only takes up at most 3 lines of code. Not allowing is just lazy. Also when a name is specified of a street it looks like Highway1(name)/Highway2/Highway3 rather then Highway1/Highway2/Highway3(name). It produces red links (unlike the current version of Module:Jcon). It doesn't support parameter ot, dir and condir. You can see all this at Template:Jcon/testcases. – BrandonXLF   (t@lk)  14:51, 5 October 2018 (UTC)
 * Ot sands for Only text. It use is clearly stated in the documentation. For the 407 I think you're right. Although ETR isn't really a road type, it more of the slogan of the highway. – BrandonXLF   (t@lk)  14:54, 5 October 2018 (UTC)
 * The types are more like "data types" (where the data are shields, links, abbreviations, etc.), rather than "road types". U.S. state modules have plenty of toll-road types, and some "types" are really just one highway with an unusual set of data. That's common with toll roads, like in Texas.
 * Regarding ot, I must have missed that when I looked through the docs. But, ideally, the parameter names should be as self-documenting as possible. If you have to check the docs in order to figure out the meaning of a parameter, it's probably poorly named. only_text would have been suitable. I partially fixed ot in the sandbox. Now, the shield does not display, and the link will disappear as soon as I fix that aforementioned nolink bug in jct.
 * As for your first reply, I've already conceded that the name positioning was not correct and needed to be fixed. I need to determine if the fix will be in Module:Jcon (specifically the version that wraps around jct, which is the current sandbox) or "upstream" in Module:Jct. It will depend on if the fix would be useful outside of Ontario.
 * The size of the shields is specified in MOS:RJL. That guideline says that "If route marker graphics are used, generally, they should have a height of 20–25px." It does say "generally", but I don't know any specific exceptions off the top of my head.
 * I think the direction parameters are very poorly designed. Looking at the testcase second from the bottom, I don't know what the current jcon version is saying. Which highways go east and which ones go west? The directions really should be handled on a per route basis.
 * Lastly, what happens if a route intersects with both a provincial highway and a regional/county road at the same intersection? jcon as currently designed cannot handle that at all, unless you use a second template invocation. Multiple jct calls are considered less-than-ideal, and since jcon serves a similar role, the same convention should apply. -happy5214 15:35, 5 October 2018 (UTC)
 * You can't have a provincial highway and a regional/county road at the same time, one road can be maintained by two different groups. Having multiple roads is for when multiple routes use the same road (such as the QEW and the 403), so they'll be going the same direction(s). jcon is not for when multiple roads share a intersection (once again why it's different from jct), in that case you'll need to use it once for each road. – BrandonXLF   (t@lk)  15:44, 5 October 2018 (UTC)
 * I don't know if it's different there, but here in the U.S., there are a lot of concurrencies where roads are signed in different directions despite going in the same physical direction on a particular stretch. Using a fictional example, you can have a concurrency between Highways 1, 2, and 3, where Highway 1 and 3 are signed as going south while Highway 2 is signed as going east. Saying that the three highways together are going "south and east" is useless, because you don't know which highways are going south and which are going east. And if such concurrencies don't happen, then the testcase is useless.
 * Did you mean to say that "One road can't be maintained by two different groups."? The first two sentences of your reply as written don't match. I think what you're saying is that there are no concurrencies between provincial and county highways. But why do you want two template calls for the scenario I gave instead of a single call? -happy5214 15:56, 5 October 2018 (UTC)
 * Oh, and I deployed the link fix to Module:Jct, so the jcon sandbox works right. -happy5214 15:57, 5 October 2018 (UTC)
 * Ok, for the direction thing that is true. One example would be 21,26 and 6. We can have it so it's like Highway1 (dir/condir) / Highway2 (dir2/condir2) / Highway3 (dir3/condir3) and if only dir/condir are specified it'll be like Highway1 / Highway2 / Highway3 (dir/condir). Currently that only dir/con part doesn't work (in the sandbox) and the directions aren't in brackets. The results of is messed up . The street name isn't at the end as I said it should be. And  renders as  and not  as it should. There's a lot of exceptions in Module:jcon that should be considered. –  BrandonXLF   (t@lk)  16:09, 5 October 2018 (UTC)

I didn't say I fixed the name yet. It will probably be more involved, as I'll have to talk to some jct users to see if the code should go there or in Module:Jcon. I'm not clear on the difference between dir and condir. Right now, condir is like dir2 in jct, so wouldn't con2dir be like jct's dir3? But are you suggesting that dir and condir would parallel each other? As for the exceptions, I can see QEW (which is either  or  ; I really don't think the full name should be used) and Highway 407 (which would be    for the ETR section,    for the provincially maintained portion, and    for both shields at once). Are there other "exceptional" highways? The MTO icons really shouldn't be in the first parameter, as that's abusing the interface. If we can make that a named parameter, we could use it in the same call as highways. -happy5214 17:09, 5 October 2018 (UTC)
 * Condir and dir are parallel so it be (dir/condir) or (east/west). I think for the QEW we should use the full name as it's what the original template used and it's more correct. Besides that and the name that's it for now I guess. – BrandonXLF   (t@lk)  17:33, 5 October 2018 (UTC)
 * As a side note, this has been a contentious topic in the past, see  Currently while it would be ideal to have it all handled by one template I see that as a very low priority. --Rschen7754 18:15, 5 October 2018 (UTC)
 * Good times hah :D -  Floydian  τ ¢ 18:52, 15 October 2018 (UTC)
 * I'll do the name functionality at some point in the (hopefully near) future, as I'm swamped right now with RL work and have spent way more time on this than I actually had to work with. Abbreviations should be used whenever possible, so ask at WT:CRWP if the full name is desired over the abbreviated "QEW". For now, if you want, you can edit the Ontario string module and change the abbr values for QEW to the full name. As for parenthesizing the directions, I will not do that as the original jcon didn't either, and I've never seen it done anywhere else. I will implement my suggested solution for directions (with con2dir) for now, with a possibility of doing something in jct similar to the name code (with a dir parameter that goes at the end). I'll wrap my interim code up shortly. -happy5214 18:18, 5 October 2018 (UTC)
 * Edit: condir2 already exists for that purpose. -happy5214 18:18, 5 October 2018 (UTC)


 * I don't spend enough time on here anymore to really make any calls, but I'll summarize my opinion with "If it ain't broke, don't break it!". -  Floydian  τ ¢ 15:47, 10 October 2018 (UTC)
 * Also, to add to a point made above, there are instances of concurrent provincial and regional numbering for continuity purposes. These are generally very brief sections (i.e. Peterborough County Road 36 and Highway 28, Kawartha Lakes Road 8 and Highway 35). Maintenance, lighting and signalling/signing is in provincial hands, but the road is still signed regionally. -  Floydian  τ ¢ 15:54, 10 October 2018 (UTC)

Please sign
In the page https://en.wikipedia.org/wiki/Template_talk:Jctint/core, please sign your last comment with (4 tildes).Adithyak1997 (talk) 14:09, 26 November 2018 (UTC)
 * Sorry, momentary lapse. It has been added. I thought User:SineBot would have taken care of that, but I have too many edits for that. Thanks for the catch! -happy5214 15:04, 26 November 2018 (UTC)