This is an archive of past discussions with User:Jc86035. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
The sitelink section has been reworked. This will go live on Wikidata on Tuesday. The sitelinks will then be slimmer and they will appear in a sidebar on the right side if there is enough space.
More performance improvements when parsing an item page, ~%15 faster for some pages :)
Usage tracking will likely be deployed on February 2 on Wikidata. This will not be user-visible. It just means that pages using data from arbitrary items get updated/purged when the data changes. Arbitrary access is being tested at Test Wikidata and testwiki:Test Wiki. An example is at testwiki:Kitten on arbitrary page.
Assigning items on Mix'n'match will now make that change on Wikidata for you automatically
Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's appearance, the coming Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. Upcoming plans are posted at the VisualEditor roadmap.
The Wikimedia Foundation has named its top priorities for this quarter (January to March). The first priority is making VisualEditor ready for deployment by default to all new users and logged-out users at the remaining large Wikipedias. You can help identify these requirements. There will be weekly triage meetings which will be open to volunteers beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC). Tell Vice President of Engineering Damon Sicore, Product Manager James Forrester and other team members which bugs and features are most important to you. The decisions made at these meetings will determine what work is necessary for this quarter's goal of making VisualEditor ready for deployment to new users. The presence of volunteers who enjoy contributing MediaWiki code is particularly appreciated. Information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins.
Due to some breaking changes in MobileFrontend and VisualEditor, VisualEditor was not working correctly on the mobile site for a couple of days in early January. The teams apologize for the problem.
Recent improvements
The new design for VisualEditor aligns with MediaWiki's Front-End Standards as led by the Design team. Several new versions of the OOjs UI library have also been released, and these also affect the appearance of VisualEditor and other MediaWiki software extensions. Most changes were minor, like changing the text size and the amount of white space in some windows. Buttons are consistently color-coded to indicate whether the action:
starts a new task, like opening the ⧼visualeditor-toolbar-savedialog⧽ dialog: blue ,
takes a constructive action, like inserting a citation: green ,
might remove or lose your work, like removing a link: red , or
is neutral, like opening a link in a new browser window: gray.
The TemplateData editor has been completely re-written to use a different design (T67815) based on the same OOjs UI system as VisualEditor (T73746). This change fixed a couple of existing bugs (T73077 and T73078) and improved usability.
Search and replace in long documents is now faster. It does not highlight every occurrence if there are more than 100 on-screen at once (T78234).
Editors at the Hebrew and Russian Wikipedias requested the ability to use VisualEditor in the "Article Incubator" or drafts namespace (T86688, T87027). If your community would like VisualEditor enabled on another namespace on your wiki, then you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
Looking ahead
The Editing team will soon add auto-fill featuresfor citations. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to contribute to the Citoid service's definitions for each website, to improve precision and reduce the need for manual corrections.
We will need editors to help test the new design of the special character inserter, especially if you speak Welsh, Breton, or another language that uses diacritics or special characters extensively. The new version should be available for testing next week. Please contact User:Whatamidoing (WMF) if you would like to be notified when the new version is available. After the special character tool is completed, VisualEditor will be deployed to all users at Phase 5 Wikipedias. This will affect about 50 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh. The date for this change has not been determined.
Join the weekly bug triage meetings beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC). Information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins. Contact James F. for more information.
Talk to the Editing team during the office hours via IRC. The next session is on Thursday, 19 February 2015 at 19:00 UTC.
Wikibooks will get access to language links via Wikidata on February 24th. Coordination is happening at d:Wikidata:Wikibooks.
Roughly 17000 of the candidate articles that Google identified as potentially being about the same topic but lacking a language link have been merged. About 17500 are remaining and waiting for you to go through them via https://tools.wmflabs.org/yichengtry/
Did more work on Capiunto to get it into a state where it can be deployed to Wikimedia sites.
Mourned Titan (phabricator:T88550) as its developers were bought up. Began evaluation for which graph database to use instead for a Wikidata query service (mw:Wikibase/Indexing)
Further work on header section redesign
Tweaks to the sitelink section
Worked on making monolingual text datatype accept more languages
Finished showing the language when a language fallback is used
Started looking into fixing the existing Guided Tours after Guided Tours extension API changes
Worked on implementing Lua convenience functions for rendering arbitrary Snaks. This is useful for displaying references or qualifiers. (phabricator:T76213)
The templates for adding badges (good article, featured article, etc) to articles on Wikipedia in the sidebar are getting removed from articles rapidly in favor of getting that information from Wikidata \o/ German Wikipedia even deleted those templates already. English Wikipedia seems to be getting close.
We are hiring! Passionate about Wikidata and know your way around Java Script and co? Apply!
We'll spend the next week working with Nik and Stas from WMF to move queries forward in Berlin
Worked on implementing a Lua interface for arbitrary Snak rendering. This can be used to render eg. qualifiers or references in Wikipedia infoboxes.
Did groundwork for Lua convenience functions that render data in the user’s interface language, rather than the content language (for multilingual wikis, like Commons or Wikidata only)
Did further work on making the Lua interface code nicer and share code with the parser functions
Removed input method selector in the sitelink input as it was hiding the actual input and not very useful there
Fixed some issues in diff views showing new data instead of old data
Created a few scripts to make it easier for 3rd parties to install Wikibase
Fixed icinga notification that tests if dispatch lag gets high
Investigated several issues regarding storage of time values and started fixing them
Fixed editing of qualifiers
Fixed most browser tests after introduction of new header design
I started a substitutable wrapper in the sandbox, you can see the differences in Template:Infobox Paris metro/testcases. I'm not entirely happy with how the access and arrondissement/municipality information are wedged together, but it's probably fine. feel free to add more examples, suggestion/make improvements, etc. I have already made a first pass through to change all the dot maps with proper location maps, so the main preprocessing should be done now. Frietjes (talk) 01:03, 18 February 2015 (UTC)
TfD standard procedure: notifying template creators
JC, in reviewing the TfDs initiated by you over the last several days, I noticed that you did not notify several of the template creators in proposed template deletions and merges. The obligation to notify template creators is primarily that of the TfD nominator, not discussion participants who happen to check; the TfD instructions state the TfD nominator "generally should notify the creator of the template, and it is also considered polite to also notify the main contributors of the template that you are nominating."
I started to ping you on each of the TfDs in which notice was not given, but when I got to the proposed Paris Metro 6-way template merge, I realized that requesting you provide the notice in the middle of each of these TfD discussions had the appearance of "calling you out" -- which is not my intention. Coming to your user talk page seemed to be a more polite way of handling this.
The TfD process works best when all concerned parties are properly notified and given the opportunity to discuss the specific purposes and uses of the particular template(s) involved. Often, the creators (and major contributors) are the best sources of information about the templates, and bypassing them in TfD discussions is not in the best interests of the project -- and it surely is not in keeping with the basic concepts of procedural fairness inherent in our XfD processes. So, please take a few minutes and notify the template creators in each of the pending TfDs and TfMs that you have proposed in the last several days. Thank you for your time and consideration. Regards. Dirtlawyer1 (talk) 21:32, 18 February 2015 (UTC)
@Dirtlawyer1: Apologies for not notifying the template creators. I have done so for the templates where I didn't previously notify the creator and where the creator was an active user. Jc86035 (talk • contributions) Use {{ping|Jc86035}} to reply to me 02:53, 19 February 2015 (UTC)
Thanks, JC. No apologies necessary. The important thing is to notify everyone who should received notice, and that's been accomplished. TfD has generally become rather slack in extending proper notice to concerned parties, and that's something I would like to see remedied. Getting TfD nominators to do so is the first step of several. Cheers. Dirtlawyer1 (talk) 02:56, 19 February 2015 (UTC)
Wikidata weekly summary #146
Here's your quick overview of what has been happening around Wikidata over the last week.
Chaged a number of Lua modules (from deprecated function mw.wikibase.getEntity to mw.wikibase.getEntityObject)
Updated the json documentation
Always link to Wikidata on client pages that don’t have any langlinks. This affects users without JavaScript and logged out users, logged in users will still see the link item dialog. gerrit:168632
Fixes for the Wikibase qunit Jenkins job
Made Vagrant git-update also properly update Wikibase and dependencies
Fix for phabricator:T88254 (malformatted Wikidata entries appearing in Watchlist RSS feed in clients)
Final touches on new header design
Investigated how we can provide language fallback also in suggestions when search or adding new statements
More work on allowing additional languages in monolingual text datatype
Added missing backend piece for quantities with units. Now the remaining piece is the user interface.
I haven't deleted your page, which is why you can still see it. I don't have the ability to do that. What I have done is put the notice up. You shouldn't remove it unless you improve the article in some way or discuss on the talk page why it's not needed, which you haven't done yet (and that's why I put it back up).
About the relisting you just did. Instead of relisting, why not close it as undecided and "invite" (or push) the discussion to continue at the talkpage? That's where complicated template changes can grow. I do not see what another relisting would add, except for admitting that TfD does not work out well in this situation. Enough serious editors have contributed. A bit of boldness by a closing admin could improve the flow and the tempaltes (Just a bit is needed). -DePiep (talk) 10:23, 8 March 2015 (UTC)
(Yes that was the one. Next time I'll spend more time on adding the link/diff). Thanks. Glad I was clear enough. -DePiep (talk) 11:20, 8 March 2015 (UTC)
Firstly, I agree that it should not have been re-listed; it had been running for quite long. However, I'm a little concerned by your readily having taken the advice of an involved party, which—miraculously—favours their preferred outcome. This is not a vote count, and not all !votes are worth equal weight; for example, when a !voter's ignored an earlier suggestion that non-locomotive articles have their infoboxes replaced with more suitable ones, it's OK to dismiss their opinion. Disproportionate focus has been placed on attempting to invalidate the original proposal, rather than resolving what is an obvious case of duplication. Anyway, a "no consensus" close is not unreasonable. Thanks for taking the initiative, and I hope I've not deterred you from closing more TfDs in the future. Alakzi (talk) 13:37, 8 March 2015 (UTC)
Lots of improvements around MixNMatch. It has a new catalog overview page. ~340K IDs have been matched so far with it and it now has an FAQ for institutions wanting to get their identifiers linked in Wikidata
First screenshot of the primary sources tool that'll help with migrating data from Freebase and enriching it with references has been leaked ;-): 1 and 2
Hi. I understand why my updates have been removed. But I may inform that the modifications I had made were taken from the website of the High Court itself. There cannot be an information any more verifiable than this. You may check for yourself and put the updates back there itself since I can't do all this all by my self. Please do the needful and oblige. — Preceding unsigned comment added by Aseemaggarwal (talk • contribs) 13:52, 22 March 2015 (UTC)
I work for GODAN and received authorization to use the same copy from the external GODAN.info website for our Wikipedia page. I've alerted the relevant team to email your permissions team today to authorize the copyright on Wikipedia.
@Klara Cabi: You're not supposed to write articles about yourself or your own company on Wikipedia, and usually good encyclopedia articles aren't copied off PR pages (even with permission). Jc86035 (talk • contribs) Use {{re|Jc86035}} to reply to me 13:37, 24 March 2015 (UTC)
Hello, I am Desmond,thank you for reviewing our page. I have noticed that you have considered our page as too emotional and does not have notability. However, all of the contents are referred to the news articles, academic journals, or the official RTHK website for descriptions of the TV series Below the Lion Rock or the Lion Rock Spirit. Besides, this is a spirit that is of great significance to the culture and development of Hong Kong.
If there are areas that are too emotional, would you mind suggesting us with methods to improve our page?
Lion Rock Spirit
@Gpa4444: I notice you refer to yourself as both "Desmond" and "us". Is your account run by multiple people or are you referring to yourself and the IP editor who did most of the edits on the article?
Anyway, I added the notability and advertising tags to the article because although you have adequate referencing, reading the article it feels like it's an advertisement for the TV show and you're trying to synthesize information. (Maybe you should ask at the deletion discussion as well, because other editors may have different opinions.) Jc86035 (talk • contributions) Use {{ping|Jc86035}} to reply to me 10:19, 24 March 2015 (UTC)
@Jc86035:Thank you for your reply, actually the page is composed by a group of contributors who are interested in acknowledging the Wikipedians of the Lion Rock Spirit. We apologize for any confusions made, as the Lion Rock Spirit is originated from the TV series "Below the Lion Rock" that reflected the living conditions and spirits that Hong Kong people uphold to face the daily challenges. The Lion Rock Spirit is generally one of the core values of Hong Kong people, and thus one of the Hong Kong unique culture.
Regarding the synthesis of different articles, do you mean the article does not have a viewpoint but merely a summary from the articles that are cited?
(Please indent your posts by using one or more colons (:) at the beginning of each paragraph.)
If it is actually "one of the core values of Hong Kong people" (I myself had never heard of the term until I noticed your article in Special:RecentChanges) then it shouldn't spend half the article talking about the TV show and the lyrics of its theme song. As for the article's synthesis, it seems a little like you're just taking information and ideas from the TV show and supplanting them in the sections that don't deal with the TV show with vaguely related information which is probably already contained in Culture of Hong Kong. Jc86035 (talk • contribs) Use {{re|Jc86035}} to reply to me 10:52, 24 March 2015 (UTC)
@Jc86035: Thank you for your explanation. It is true that the TV series and its lyrics have been covered in the passage. However, the TV series is borrowed to reflect the origin of the Lion Rock Spirit, and the background of the TV shows could definitely reflect the historical background of Hong Kong and the Lion Rock Spirit in the 1970s. Besides, the theme song is borrowed to elaborate on the cultural significance of the Lion Rock Spirit, as the lyrics have embedded the Lion Rock Spirit. Through examining how the people manifest the Lion Rock Spirit from the value embedded in the lyrics, this could reflect on how the Lion Rock Spirit represents the cultural identity of Hong Kong people.
It is noteworthy that there are the cultural identity and social section in Culture of Hong Kong. However, it has not mentioned any of the values and characteristics as thoroughly as in the Lion Rock Spirit. It is not possible to merely open a small section under the social or cultural identity part as the Lion Rock Spirit has its own origin, background, and development, which is notable for a new page. Gpa4444 (talk) 18:25, 25 March 2015 (UTC)
About Adonis Georgiadis page
greetings Jc86035
I noticed you have reverted the changes I made to Adonis Georgiadis page. I would like to indicate that some youtube links that are cited are either deleted (for example video cited 15) or in them he (Adonis Georgiadis) does not express the opinion supposedly claimed in the article (for example that "there was no popular opposition to the military regime" or "left-wing ideology has surrendered Greece to the hands of Muslims, and other garbage like that" e.t.c. actually, he used the expression "surrended to muslims and kathe karudias karudi which is by no means translated as "rubbish" but as "persons with unknown or suspicious identity"). I have explained all the above in the talk page, in Greek.
If you do not have any objections please restore the changes I made.
Thanks in advance, I will be at your disposal for any further clarifications
With Citoid in VisualEditor, you click the 'book with bookmark' icon and paste in the URL for a reliable source:
Citoid looks up the source for you and returns the citation results. Click the green "Insert" button to accept its results and add them to the article:
After inserting the citation, you can change it. Select the reference, and click the "Edit" button in the context menu to make changes.
The user guide has more information about how to use VisualEditor.
Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's performance, the Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.
The weekly task triage meetings continue to be open to volunteers, each Wednesday at 11:00 (noon) PDT (18:00 UTC). You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug. Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal.
Recent improvements
VisualEditor is now substantially faster. In many cases, opening the page in VisualEditor is now faster than opening it in the wikitext editor. The new system has improved the code speed by 37% and network speed by almost 40%.
The Editing team is slowly adding auto-fill featuresfor citations. This is currently available only at the French, Italian, and English Wikipedias. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to improve precision and reduce the need for manual corrections by contributing to the Citoid service's definitions for each website.
Citoid requires good TemplateData for your citation templates. If you would like to request this feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
The special character inserter has been improved, based upon feedback from active users. After this, VisualEditor was made available to all users of Wikipedias on the Phase 5 list on 30 March. This affected 53 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh.
Work continues to support languages with complex requirements, such as Korean and Japanese. These languages use input method editors ("IMEs”). Recent improvements to cursoring, backspace, and delete behavior will simplify typing in VisualEditor for these users.
The design for the image selection process is now using a "masonry fit" model. Images in the search results are displayed at the same height but at variable widths, similar to bricks of different sizes in a masonry wall, or the "packed" mode in image galleries. This style helps you find the right image by making it easier to see more details in images.
You can now drag and drop categories to re-arrange their order of appearance on the page.
The pop-up window that appears when you click on a reference, image, link, or other element, is called the "context menu". It now displays additional useful information, such as the destination of the link or the image's filename. The team has also added an explicit "Edit" button in the context menu, which helps new editors open the tool to change the item.
Invisible templates are marked by a puzzle piece icon so they can be interacted with. Users also will be able to see and edit HTML anchors now in section headings.
Users of the TemplateData GUI editor can now set a string as an optional text for the 'deprecated' property in addition to boolean value, which lets you tell users of the template what they should do instead (T90734).
Looking ahead
The special character inserter in VisualEditor will soon use the same special character list as the wikitext editor. Admins at each wiki will also have the option of creating a custom section for frequently used characters at the top of the list. Instructions for customizing the list will be posted at mediawiki.org.
The team is discussing a test of VisualEditor with new users, to see whether they have met their goals of making VisualEditor suitable for those editors. The timing is unknown, but might be relatively soon.
Can you translate from English into any other language? Please check this list to see whether more interface translations are needed for your language. Contact us to get an account if you want to help!
File requests for language-appropriate "Bold" and "Italic" icons for the character formatting menu in Phabricator.
Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
WikiArabia takes place in Monastir, Tunisia, 3-5 April
The GLAM-WIKI 2015 conference in The Hague (10-12 April) features several presentations and tutorials about Wikidata for/with cultural institutions.
The Library world will use Wikidata to link its information to any and all Wikipedias. No longer English only, but every Wikipedia will be exposed in this way.
Went through all the feedback we got for improving watchlist integration on Wikipedia and co and posted our assesment
Put the infrastructure for creating Turtle-Beta dumps in place. All new Wikidata dumps will be in https://dumps.wikimedia.org/wikidatawiki/entities/ from Monday on (the old * directory will be kept around and receive new json dumps for backwards compatibility).
Reduced size of entities pages by removing no longer needed data (to make the UI faster).
Fixed bug that sometimes caused dates and other types of values to be cut short when quickly saving. (phabricator:T92831)
Fixed issues with setting focus after clicking edit.
We are going to change the way value suggestions are ranked when entering a new statement. This will help with "male" and "female" not showing up among the top suggestions. Previously we ranked by number of sitelinks. We will change this to the maximum of sitelinks and labels. So if an item has labels in many languages but no sitelinks like "male" and "female" it will still show up high in the suggestions. (phabricator:T94404)
Discussed how to move forward with identifiers. Outcome: They should get their own datatype. (phabricator:T95287)
Implemented arbitrary access for the {{#property:…}} parser function. This can be invoked on the wikis that have arbitrary access enabled by using {{#property:P123|from=Q42}}. So far this is only Wikidata itself.
Did further performance work on the client (Wikipedia and co) in preparation for arbitrary access
Improved the performance of wbgetentities significantly when loading a large number of entities
Hello, I partly reverted/amended the latest changes you made to Module:MTR. Due those changes the box function was no longer returning the link variable but was returning the text instead. As a result, the links of all lines needing disambiguation (Island line, Admiralty, ...) were pointing to the dab page instead of using the " (MRT)" suffix. Please check if I amended things correctly though, I'm not used to doing it. Rgds, --Midas02 (talk) 15:30, 16 April 2015 (UTC)
In creating a redirect, whatever it was, you trashed the improvements I'd made. No mention in your edit-summary of why. Bad manners and bad editorial practice. Tony(talk) 06:06, 18 April 2015 (UTC)
@Tony1: I changed it to a redirect because there was no new content in the page compared to the parent page that the IP (was it you?) copied the text of. If it was created as a new article instead of from a redirect someone would probably have tagged it for A10 speedy deletion (duplication of another article without any expansion). Jc86035 (talk • contribs) Use {{re|Jc86035}} to reply to me 06:45, 18 April 2015 (UTC)
Jc, and you know, after I wrote that and was offline I thought, damn it, I think I got it wrong. I meant to come back to WP immediately and cross out my post here, but forgot. So ... sorry! I wasn't the IP. Thanks and cheers. Tony(talk) 11:49, 18 April 2015 (UTC)
Wikidata weekly summary #154
Here's your quick overview of what has been happening around Wikidata over the last week.
Wikimedia's monthly GLAM (Galleries, Libraries, Archives, Museums) newsletter now includes a Wikidata report. The draft for the first edition, covering April, may be edited and your contributions will be welcome.
Made label, description and aliases special pages easier to use
Bene* created a new Special:ListProperties special page to list properties by data type
Expanded our set of automated browser tests
Made language fallbacks work in more situations and more consistently. In particular, the entity selector now uses language fallback. This should benefit especially people who want to use Wikidata in a variant such as en-gb.
Continued work on the planned DataModel 3.0 release
Continued discussing and documenting future calendar model support
Continued work on our RDF generator
Continued work on usage tracking for labels on multilingual sites
Addshore worked on various issues regarding redirects
Addshore worked on a special page to turn an item into a redirect
Work on showing entity labels in edit summaries on history pages
Implemented change dispatching based on the new usage tracking mechanism
Fixed issue with page deletions on some Wikipedias not being reported to Wikidata
More work on straightening out date formatting and parsing
Fixed handling of scientific notation for quantity values
Term box: fixed bug causing stale info to be show, and another bug causing babel languages to be ignored sometimes.
Implemented access to other arbitrary items via the #property parser function
Bene* implemented check to make sure two properties can not have the same alias only differing in capitalization
@Alakzi: The point of the table is so that the symbols aren't stuck on the first line (and misaligned) if there's a native language. It's not totally and absolutely necessary but it looks a bit nicer. It should be okay to delete the Space-separated module in favour of the other, and Module:Br separated entries could probably be merged as well. Jc86035 (talk • contribs) Use {{re|Jc86035}} to reply to me 11:44, 19 April 2015 (UTC)
OK, could you slap a speedy tag on the module? There's no use dragging it to WP:MFD. As for the icons - can you show me an example in which they're misaligned? You're still using a table for layout, which is frowned on. Alakzi (talk) 11:56, 19 April 2015 (UTC)
As for the icons, Kilkenny railway station (Ireland) has the icon on the first line, which seems odd given that |name= and |native_name= are the same size. Having a table (or a div, if possible?) would fix that by putting it between them. Jc86035 (talk • contribs) Use {{re|Jc86035}} to reply to me 12:58, 19 April 2015 (UTC)
Moved to Template talk:Infobox station
