User talk:WOSlinker Voyage Tips and guide

Contents

Hello, WOSlinker! Welcome to Wikivoyage.

To help get you started contributing, we've created a tips for new contributors page, full of helpful links about policies and guidelines and style, as well as some important information on copyleft and basic stuff like how to edit a page. 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 Help, or post a message in the travellers' pub. If you are familiar with Wikipedia, take a look over some of the differences here. Rschen7754 08:26, 14 June 2013 (UTC)Reply

Hi WOSlinker, I see that you have changed the name of the dive site article structure template without previous discussion on the talk page. Could you explain why you found this necessary or desirable? Cheers, • • • Peter (Southwood) ^(talk): 14:36, 27 June 2013 (UTC)Reply

All the other similar template had the skeleton name at the end. You can still use the old name when substituting if you wish. -- WOSlinker (talk) 17:41, 27 June 2013 (UTC)Reply

Thanks for this. I'm quite handy with images and maps, but not at all with templates! --Peter ^Talk 06:47, 4 July 2013 (UTC)Reply

I've moved the page to Template:Worldimagemap/subpagedoc to avoid any further confusion. -- WOSlinker (talk) 07:01, 4 July 2013 (UTC)Reply

Hi there, I guess you've some good knowledge on working with templates. Can you please figure out how to exclude this and this page from being showing in Category:Vfd? Previously, we used {{vfd|example=yes}} in Wikivoyage:Travel topic status. --Saqib (talk) 13:16, 7 July 2013 (UTC)Reply

I've updated both {{ifd}} and {{vfd}} so that they won't show cat on Wikivoyage:Template index. -- WOSlinker (talk) 17:23, 7 July 2013 (UTC)Reply

There's lots of other cats that could do with hiding on that page as well. I'll have a look through the other templates soon. -- WOSlinker (talk) 17:23, 7 July 2013 (UTC)Reply

Thanks. Template talk:Vfd is waiting to be fixed as well. --Saqib (talk) 17:25, 7 July 2013 (UTC)Reply

You're a great Wikivoyager. I have added the autopatrolled right to your account. I hope you'll continue to contribute constructively to Wikivoyage. --Saqib (talk) 17:35, 7 July 2013 (UTC)Reply

Thanks. I mainly do tidying up work but occasionaly edit articles as well. -- WOSlinker (talk) 17:50, 7 July 2013 (UTC)Reply

Yes , you're doing good. Keep it up! --Saqib (talk) 17:58, 7 July 2013 (UTC)Reply

Hi WOSlinker, I would like to create a template for dive site listings so I can clean up the Scuba diving page and several other regional scuba articles using a standardized listing. I started by copying Template:Listing over to Template:Divesitelisting but I am having difficulty working out how it works as it seems to use more complex html than I am familiar with. I have also roughed out what the listing template should do on User:Pbsouthwood/Dive site listings. If you have the time and inclination I would appreciate any advice or help you are willing to give. Cheers, • • • Peter (Southwood) ^(talk): 18:15, 29 July 2013 (UTC)Reply

I can help. I would need some more idea of how it's all meany to look with some examples before I can do much though. -- WOSlinker (talk) 20:57, 30 July 2013 (UTC)Reply

Any help would be much appreciated. At present there is some indication on User:Pbsouthwood/Dive site listings of what the output should be. I will look into producing a model for the output formatting tomorrow, as it is pushing midnight and my eyes are tiring. Cheers, • • • Peter (Southwood) ^(talk): 21:06, 30 July 2013 (UTC)Reply

I have produced some information on what it should contain and how it should look. Could you give me some feedback on whether this is suitable and sufficient? • • • Peter (Southwood) ^(talk): 16:55, 31 July 2013 (UTC)Reply

That's fine apart from the images. For those, would it just be the image name that is passed over as a parameter? And also how would they be displayed? -- WOSlinker (talk) 06:14, 1 August 2013 (UTC)Reply

Did you read the table? I was thinking of optional parameters for image width, alt text and caption. All images to stack down the RHS starting at the level of the top of the listing. Default standard thumbnail size, but with option to enlarge map for legibility. I am also hoping to keep the template compatible with VE to save hassles later.

I will put together a demo of output format for a full listing. • • • Peter (Southwood) ^(talk): 07:27, 1 August 2013 (UTC)Reply

Done. There is now an example of how it should display, what the input should look like, and how the template actually displays. • • • Peter (Southwood) ^(talk): 08:49, 1 August 2013 (UTC)Reply

OK, I'll have a look at it later on today. -- WOSlinker (talk) 12:24, 1 August 2013 (UTC)Reply

It's now done. I've included site-image, site-map, ecology-image & feature-image but not image2 at the moment. Can add image2 if needed. -- WOSlinker (talk) 20:19, 1 August 2013 (UTC)Reply

Nice work, and thanks. I will try to work out how it works, for my own education, and test it out on a few articles tomorrow to see if I have missed anything. No rush for image2, most listings that it will be used on have 1 image if we are lucky. Cheers, • • • Peter (Southwood) ^(talk): 20:47, 1 August 2013 (UTC)Reply

One more request. I seem to have done something wrong at Template:Divesitelisting/Doc as it does not display on the template page. Could you take a look? • • • Peter (Southwood) ^(talk): 08:45, 2 August 2013 (UTC)Reply

The page name needed to be /doc rather than /Doc -- WOSlinker (talk) 11:40, 2 August 2013 (UTC)Reply

Hi, as you appear to be knowledgeable of template I would like some advice. Is it possible to create a syntax check on a parameter? What I want to do is check that the phone parameter in the listing template is of a specific format. Namely starting with + and only containing digits and dashes no brackets or whitespaces, e.g. +1-234-5678-90. Challenge is cannot say how many numbers or dashes will exist.--Traveler100 (talk) 08:14, 29 September 2013 (UTC)Reply

Sorry for the disturbance, I think I have a solution. If the parameter is only numbers, minus and plus then I can do #expr on it and get a number, anything else will give error.--Traveler100 (talk) 10:58, 29 September 2013 (UTC)Reply

Yes, that should work. The main lua function to use if you need something more complex is below.

<syntaxhilight lang="lua">

mw.ustring.match("+1-234-5678-90","^%+[%d-]+$") </syntaxhilight>

Are you just checking just the USA phone numbers or is it all phone numbers since countries such as the UK don't tend to use dashes and use spaces instead. -- WOSlinker (talk) 11:05, 29 September 2013 (UTC)Reply

My proposal is to make all numbers in listing of this format, no matter the country. Reason is to make it possible to have link in web page of phone number for mobile devices. See Wikivoyage talk:Listings#Telephone number Have not investigate how to use lua, something for my to do list.Traveler100 (talk) 11:19, 29 September 2013 (UTC)Reply

Module:LinkPhone is giving a false positive for numbers with bracket in then for example with (0) in front of area code.

Thanks, I've now fixed it. -- WOSlinker (talk) 18:47, 29 September 2013 (UTC)Reply

In most cases a (0) or similar prefix and brackets shouldn't be there; for instance 0- is the trunk prefix to call another city within the UK, but we don't include it in listings, so +44 20 7777-7777 is correct for our formatting convention and +44 (0) 20 7777-7777 not recommended (per Wikivoyage:Phone numbers) as the 0 isn't used when calling from outside the country. For North American numbers, we keep the area code but lose the brackets around it; we'd want +1 867 867-5309 and not (867) 867-5309. Missing or improperly-formatted country code numbers often have the brackets.

There are some cases which may be false positives, w:private branch exchange numbers where one reaches a switchboard and must ask for a specific extension being one. If Kingston (Ontario) city hall still has this, it appears on city-owned listings like:

• Pump House Steam Museum, 23 Ontario St. Kingston, ☎ +1 613-546-4291 ext. 1666. 10am-5pm (May-Aug) 12-4pm (Sep-Nov). City-owned steam-powered water pump house built with the latest in 1891 technology, restored 1973 by the Frontenac Society of Model Engineers. C$5/person.

We do have some listings where users have tried to fit two different telephone numbers into the one field, that's awkward to detect by automated means. Then there are w:phonewords like +1 514-AUTOBUS. Not sure if we want those, I've been writing these as figures in the tel: link. K7L (talk) 16:35, 27 November 2013 (UTC)Reply

Bit of an issue with flags in routebox - Edirne. --Traveler100 (talk) 18:14, 27 November 2013 (UTC)Reply

Thanks for letting me know. I've fixed it. -- WOSlinker (talk) 21:03, 27 November 2013 (UTC)Reply

Hi. I have a test template where I'm trying to create an optional param, ie, it only displays if it has a value. I'm a complete novice at template work. The template is User:Nurg/Template:Unwanted edits and the param is "additional". Can you please have a look at my recent edits & the doc & you'll realise what I'm trying to do. Are you able to fix it. thanks. Nurg (talk) 21:34, 27 November 2013 (UTC)Reply

Thanks you very much for your help. Nurg (talk) 08:52, 28 November 2013 (UTC)Reply

Why would you just go and remove all of my hard work adding index entries to articles? Those templates may not do anything currently, but losing the semantic information that they encode is a step backwards. LtPowers (talk) 01:37, 9 December 2013 (UTC)Reply

Perhaps it's worth documenting what template index does then as it appeared to me that it didn't do anything. It looks as though it just makes it more difficult to edit the articles. -- WOSlinker (talk) 07:46, 9 December 2013 (UTC)Reply

As all templates should be, it's documented at Wikivoyage:Template index. LtPowers (talk) 20:16, 9 December 2013 (UTC)Reply

Yes, but there should be some documentation on the template page as well, so that it's easier to find. Take a look at Template:Index now. -- WOSlinker (talk) 08:10, 10 December 2013 (UTC)Reply

Thank you for adding the documentation to that template page. LtPowers (talk) 14:32, 10 December 2013 (UTC)Reply

I notice you have deleted some of these tags in listings. I think they should remain, even be added to listings that don't have them.

See also discussion at Wikivoyage_talk:Listings#Mailto:. Pashley (talk) 01:00, 8 February 2014 (UTC)Reply

It's just that the listing template adds mailto, so those that have it end up with it twice. Compare the links for:

• Example, mailto:[email protected]. 
• Example, [email protected]. 

So I'm just removing mailto: from the 80 out of 20400 listings that have it included. I'm not removing mailto: from any manual links that are not in listings templates. -- WOSlinker (talk) 07:20, 8 February 2014 (UTC)Reply

I think that your reasoning is correct on this, WOSlinker and may I take this opportunity to thank you for your tireless correcting and improving of our guides.

Do you make all these sort of excellent edits by hand or do you run a bot under individual supervision? Just curious before I go back to editing anonymously... --118.93nzp (talk) 08:40, 8 February 2014 (UTC)Reply

I'm just doing these manually. I downloaded the listings file from Wikivoyage:Travellers'_pub#Looking_for_something_useful_to_do.3F and looked through the data to find ones with issues. -- WOSlinker (talk) 09:09, 8 February 2014 (UTC)Reply

Amazing! Have a Barncompass before I go pzzzzzzzzzzzzzzt...

	The Wikivoyage Barncompass
	This Barncompass is to show appreciation for your great work on Wikivoyage. --118.93nzp (talk) 09:20, 8 February 2014 (UTC)Reply

Well deserved. You're doing good job. --Saqib (talk) 21:24, 8 February 2014 (UTC)Reply

Yes, indeed. Thanks for the explanation above, too; your edits now make sense to me. Pashley (talk) 19:30, 9 February 2014 (UTC)Reply

It looks like Module:LinkPhone is adding pages to Category:Listing with phone format issue when the phone number is blank in the template - for example:

* {{see
| name=Example listing | alt= | url= | email=
| address= | lat= | long= | directions=
| phone= | tollfree= | fax=
| hours= | price=
| content=This is a lovely place, but it does not have a phone.
}}

Would it be possible to modify that module to ignore empty phone numbers? I think that will greatly reduce the number of false positives in the maintenance category and make it easier to fix any phone numbers that do need attention. Also, thanks for all your great cleanup work lately! -- Ryan • (talk) • 01:19, 9 February 2014 (UTC)Reply

Do you have an example page with the issue? It might be one of those hidden unicode characters. For example see this edit. I'll see if I can do some detection of those characters separately. -- WOSlinker (talk) 08:18, 9 February 2014 (UTC)Reply

I was trying to track down the issue with Culver City and tried passing a blank phone number to the LinkPhone module ([1]) and got a category error. However, removing the extension from one of the Culver City articles seems to have fixed the problem ([2]). Sorry for the false alarm. -- Ryan • (talk) • 08:42, 9 February 2014 (UTC)Reply

Template:Listing handlea the blank parameters, so a blank entry never gets passed over Module:LinkPhone. -- WOSlinker (talk) 08:49, 9 February 2014 (UTC)Reply

Hi there, I just deleted the 5 categories you just created. I know you found them on the wanted categories list, but since they belong to an experimental template, they are not necessarily "wanted" just yet. The categorization scheme that template conceives is pretty problematic. For example "Category:Events in Brazil" would just end up being a list of every city in Brazil that has any event listed at any time, which would be most of them and thus not be a very useful category. Texugo (talk) 14:17, 14 February 2014 (UTC)Reply

Hey there. Just wondering if this wasn't just a one-time experiment that can be deleted. Do we need to keep it? Texugo (talk) 18:16, 25 February 2014 (UTC)Reply

Yes, it could be deleted. -- WOSlinker (talk) 23:41, 25 February 2014 (UTC)Reply

Done. Thanks. Texugo (talk) 00:52, 26 February 2014 (UTC)Reply

What do you think about it? TeleComNasSprVen (talk) 06:10, 9 March 2014 (UTC)Reply

Yes, I'd be interested. I'm aware of a number of the policies here, though not all of them yet! I've also had experence of using the mop on the wikipedia site. -- WOSlinker (talk) 09:59, 9 March 2014 (UTC)Reply

Just out of curiosity, how do you see them? When I compare the versions of articles before and after, I have a heck of a time telling the difference. Ikan Kekek (talk) 23:53, 10 March 2014 (UTC)Reply

For some of our end users, they seem to be giving 404s. I think it has to do with the way a browser is configured to handle URLs, as foreign ones can have a tendency to insert hidden left-to-right marks for example. Curiously, this seems to have returned some 404s to the Glenn Miller Orchestra, which had an IP later complaining about it giving him problems, and then I corrected it to point to the landing page. TeleComNasSprVen (talk) 03:35, 11 March 2014 (UTC)Reply

I can't see them myself but once I found one, I managed to trap it between some quotes and then I did a little bit of javascript to do a search and replace on the articles text to remove them. They don't get in the way if you are just reading an article (since they are invisible) but can cause problems if there is some program that it taking the data and processing it, as it can may come across one of these characters when it's not expecting it. -- WOSlinker (talk) 06:57, 11 March 2014 (UTC)Reply

Would you mind marking these as minor edits so the rest of us can easily hide them from recent changes? Thanks! Texugo (talk) 21:50, 11 March 2014 (UTC)Reply

Will do next time, but I've just finished them. -- WOSlinker (talk) 21:52, 11 March 2014 (UTC)Reply

Can I second the request for flagging these types of edits as "minor", including the current round of edits to add country codes? It's really helpful to be able to ignore them in recent changes. Thanks! -- Ryan • (talk) • 07:53, 13 March 2014 (UTC)Reply

Hello. I see that you moved Gillingham (Kent) to Gillingham (England). I am curious about this, as we also have Gillingham (Dorset), and there is a third Gillingham in Norfolk. The Kent town does have 9 times the population, but I am not sure which is the most popular with travellers. AlasdairW (talk) 23:51, 20 March 2014 (UTC)Reply

It was when I was looking at Category:Kent that I saw all the other places were (England), so thats why I'd moved it. I've moved it back to Kent as I hadn't noticed the other places. -- WOSlinker (talk) 07:51, 21 March 2014 (UTC)Reply

Thanks. The Medway towns can be confusing, as all three main ones have duplicates, and we can't be consistent in the naming - Chatham-Kent is in Canada. AlasdairW (talk) 23:24, 21 March 2014 (UTC)Reply

Per Wikivoyage:Administrator nominations#User:WOSlinker I've muddled about in the guts of Wikivoyage, and as a result you should see some shiny new buttons when next you log in. For instructions on using the new powers please see Wikivoyage:Administrator's handbook and if you have any questions feel free to ask any of the current admins. -- Ryan • (talk) • 14:47, 24 March 2014 (UTC)Reply

Congratulations!

Now you can do even more good work correcting some of the errors with protected templates, etc... --118.93nzp (talk) 21:46, 24 March 2014 (UTC)Reply

Thanks for accepting your demotion to Janitor. :-) Ikan Kekek (talk) 02:25, 25 March 2014 (UTC)Reply

Thanks, all. -- WOSlinker (talk) 13:06, 25 March 2014 (UTC)Reply

Your changes to {{routebox}} appear to have broken handling of the case where the size of the highway number icons is not specified on the page. The template used to default to something sensible, about 22px or so, but now by default it displays the icon full-size. Trenton (Ontario)#Go next is one example... the numbers are huge. K7L (talk) 13:38, 10 April 2014 (UTC)Reply

Sorry about that. I'd checked a few pages before & after the changes and hadn't seen that issue because they all had imagesize set. I've fixed it. -- WOSlinker (talk) 15:23, 10 April 2014 (UTC)Reply

• No idea who to contact and I noted that you do a lot of work and may be an admin.
• User Trouble with Bourgois or something like that...
• Moving pages around and hacking pages - Thank you

I'm a little unsure about this edit, moving vanity number phonewords into the phone= field of listings instead of keeping those all-numeric. That seems to break the creation of tel: links (which are clickable links for use on mobile 'phone web browsers - clicking the number places the call on some platforms) and places the page in category:Listing with phone format issue. I've been using 482-5683 over 482-LOVE to avoid this issue. K7L (talk) 17:04, 30 May 2014 (UTC)Reply

It was just that it put all the phone information in one place. Could always just go with the number version and not mention the LOVE bit. -- WOSlinker (talk) 21:52, 30 May 2014 (UTC)Reply

That's what the field phoneextra used to be for. Pity it still hasn't been fixed... -- Alice^✉ 22:21, 30 May 2014 (UTC)

@K7L: I've done a sandbox version of Module:LinkPhone which willconvert a text number into numbers, with some sample outputs below. All the letters need to be uppercase and the only other characters in the phone number are spaces or dashes then the conversion will be done, otherwise it will not and the entry would be added to the tracknig category.

Does this look ok and is it worth doing? -- WOSlinker (talk) 13:14, 2 June 2014 (UTC)Reply

Input Text	Result
+1 234 8378-464	+1 234 8378-464
+1 (234) TEST-ING	+1 (234) TEST-INGCategory:Listing with phone format issueFORMAT
+1 234 test-ing	+1 234 test-ingCategory:Listing with phone format issueFORMAT
+1 234 TEST-ING	+1 234 TEST-ING (8378-464)

Let me see..

+1 613-546-4291 EXT 1666	+1 613-546-4291 EXT 1666
+1 613-546-4291 Ext 1666	+1 613-546-4291 Ext 1666
+1 613-546-4291 ext 1666	+1 613-546-4291 Ext 1666
+1-87-PCT-INFO-1	+1-87-PCT-INFO-1 (728-4636-1)
+1-212-PE6-5000	+1-212-PE6-5000 (736-5000)
+1-212-PEnnsylvania 6-5000	+1-212-PEnnsylvania 6-5000Category:Listing with phone format issueFORMAT

K7L (talk) 01:11, 3 June 2014 (UTC)Reply

Right, The first thing I'll need to add is support for handling EXT nnnn at the end of the number and the other thing is when the WORD is in the middle of the number. I'll get back to you once I've sorted those issues and will look forward to some more test cases. -- WOSlinker (talk) 05:35, 3 June 2014 (UTC)Reply

@K7L: I've made those changes. -- WOSlinker (talk) 20:52, 3 June 2014 (UTC)Reply

Why do you change regular phone numbers to start "+1 ", and toll free numbers to "+1-"?

Example https://en.wikivoyage.org/w/index.php?title=St._Catharines&curid=34057&diff=2610272&oldid=2589192

Shouldn't it be one way or the other? Thanks Cpfan776 (talk) 23:58, 25 June 2014 (UTC)Reply

I'm just following the rules at Wikivoyage:Phone numbers -- WOSlinker (talk) 09:38, 26 June 2014 (UTC)Reply

Thanks, I did not know about that set of rules. IMO, those are dumb rules for Canada and the USA. I'll try to remember to use that format in future, but I won't be editing any pages JUST to make that change. Cpfan776 (talk) 16:14, 26 June 2014 (UTC)Reply

Hi WOS, I don't know if it has been discussed somewhere, but I would ask you about the possibility of managing multiple phone numbers, whose syntax could be +CC XXXXXXX, +CC XXXXXXX, +CC XXXXXXX or maybe with a different separator value. I think that several business show a land line + a mobile phone. And I've seen (without a specific business reason) several companies with more than a land line. Let me know, --Andyrom75 (talk) 06:59, 2 July 2014 (UTC)Reply

Other thing: I can't find where is defined the class phoneinfo, could you help me to locate it? --Andyrom75 (talk) 07:26, 2 July 2014 (UTC)Reply

There has been discussions about multiple phone numbers before (see Template talk:Listing#Phoneextra for one example) but there hasn't been enough support to add it. It could be added, just using the since phone param and splitting it on "comma", "and" or "or". Or the other option as discussed on the template talk page is adding extra phone params, so having phone, phone2 and possibly phone3. You could start a fresh discussion at Wikivoyage_talk:Listings and see if there is any support for adding the functionality. I'm not sure if there is a phoneinfo class. I haven't seen it. -- WOSlinker (talk) 08:24, 2 July 2014 (UTC)Reply

As per your suggestion, I've started a new thread.

In your opinion the class phoneinfo has been inserted by mistake or for future development? --Andyrom75 (talk) 10:27, 3 July 2014 (UTC)Reply

@Andyrom75: I remember now where class phoneinfo is set. It's in Module:LinkPhone for phone numbers that get added to one of the tracking categories. It's there to make it easier to see the phone numbers with issues. You'll need to add the following to your common.css to make them visible. -- WOSlinker (talk) 12:44, 3 July 2014 (UTC)Reply

<syntaxhilight lang="css"> .phoneinfo {

   color: red;
   background: yellow;
   display: inline !important;

} </syntaxhilight>

I've seen phoneinfo in the module, that's why of my question. Now, according to your answer, is correct that it hasn't declared anywhere because is a debug class that should be used by debugger-editor, right? --Andyrom75 (talk) 13:10, 3 July 2014 (UTC)Reply

Yes, the content is hidden be default unless you use the class as described. So it's just there to help those who want to fix phone number issues. -- WOSlinker (talk) 13:13, 3 July 2014 (UTC)Reply

Thanks for the clarification. I'll add it on it:voy as well and I'll inform a user that is debugging those number, to ease his life. --Andyrom75 (talk) 13:18, 3 July 2014 (UTC)Reply

Hi WOS, on it:voy I've changed [A-Za-z%- ]* into [A-Za-zÀ-ÖØ-öø-ÿ%-%.' ]* to catch unicode letters, the period for abbreviations and the apostrophe for certain foreing names. I don't know if it's something that may interest you to be implemented here on en:voy as well. However, do you see any side effects on this syntax or maybe any smarter way to obtain the same result? Let me know, --Andyrom75 (talk) 10:56, 14 July 2014 (UTC)Reply

That would be fine to update. I haven't seen any À-ÖØ-öø-ÿ yet but it would be ok to include them. I have seen a few . and ' though. -- WOSlinker (talk) 12:05, 14 July 2014 (UTC)Reply

An user has found a "č" between brackets, so I'm trying to think a way to avoid to chase time by time this kind of exceptions. What do you think about something like [^0-9]*? This should avoid to confuse the description from the telephone numbers. --Andyrom75 (talk) 14:10, 14 July 2014 (UTC)Reply

Seems ok, just make the change in the sandbox and then try it against a few testcases to see if it works as you expect. -- WOSlinker (talk) 14:34, 14 July 2014 (UTC)Reply

I've tested it in preview and it has seemed to be fine, so I've implemented it on it:voy. Do you want me to add it here as well?

To be improved it should differenciate the sequence of only numbers (categorizing them as a wrong format) from the sequence of characters that contains "also" few numbers that should be good. An example could be a restaurant that has two different buildings in the same city so two different phone numbers: +CC 123 456789 (5th avenue), +CC 123 987654 (74th street). But I can't figure out the right regex for this purpose, so I'm incline to accept it as a reasonable restriction. --Andyrom75 (talk) 15:21, 14 July 2014 (UTC)Reply

Yes, go ahead & make the change. -- WOSlinker (talk) 15:28, 14 July 2014 (UTC)Reply

Done --Andyrom75 (talk) 16:41, 14 July 2014 (UTC)Reply

Moved to Wikivoyage talk:Listings#Multiple_Emails since better place to discuss.

FYI on it:voy I've created a two type of classes to speed up the cleaning activities, one dedicated to a specific task and one generic for all the tasks.

In particular:

1. Dedicated
   • it:Modulo:EmailTracking has mailinfo
   • it:Modulo:LinkPhone has phoneinfo
   • it:Modulo:Citylist has citylistinfo
2. Generic
   • All of them has debuginfo

In this way, if you are interested only in one or more specific task, you can put in your commons.css just the dedicated class, but if you are interested on cleaning the whole issues on the site, you can add directly debuginfo.

If you like the idea, feel free to implement it on en:voy. --Andyrom75 (talk) 17:19, 3 August 2014 (UTC)Reply

Hello! Sorry for writing in English. As you're an administrator here, please check the message I left on MediaWiki talk:Licenses and the village pump. Thanks, Nemo 19:23, 18 September 2014 (UTC)Reply

Hi, I see you have reverted edits on tag sizes. The fact that not all have been changed yet to the new size discussed on the Pub page should not be a reason for reversing the work that has been started. I was thinking of making a single template but not sure if the effort of creating one singe complex template is better then editing all the single ones. --Traveler100 (talk) 07:01, 28 September 2014 (UTC)Reply

It just seemed odd that only 4 out of about 40 had a smaller text size, and it was about 3 weeks ago. Yes, a single master template (similar to ambox) would be good. I could have a look at that if you want. -- WOSlinker (talk) 09:20, 28 September 2014 (UTC)Reply

@Traveler100: I've done an example master template at Template:Classbox WOSlinker (talk) 10:01, 28 September 2014 (UTC)Reply

Am a little but further on with this topic :- template:Stbox see comparison with old and new at User:Traveler100/sandbox-stbox. --Traveler100 (talk) 11:01, 28 September 2014 (UTC)Reply

Thanks for the template updates, does look easier to read. --Traveler100 (talk) 12:29, 28 September 2014 (UTC)Reply

I wonder whats the reason and benefit of tidying up tables? --Saqib (talk) 18:38, 11 October 2014 (UTC)Reply

The only benefit is that the table styling is the same in all articles, rather than being different, which provides a more consistent experience. -- WOSlinker (talk) 19:27, 11 October 2014 (UTC)Reply

	The Wikivoyage Barncompass
	Dear User:WOSlinker, I think it is about time we awarded you your well-deserved Barnstar for your tireless work on all the thankless wikignome tasks you undertake everyday. I hope you will never tire of correcting us :) PrinceGloria (talk) 08:47, 1 November 2014 (UTC)Reply

Thanks. -- WOSlinker (talk) 10:54, 1 November 2014 (UTC)Reply

Hi WOS, considering the work that we have done on the tel parameter on accepting multiple numbers with their description, what do you think about a proposal of merging tel and tollfree, considering that very few listing has a tollfree number?

For example we could merge "| tel=+123 | tollfree=+456" into "| tel=+123, +456 (tollfree)".

This would simply the overall code.

PS

I would keep separated the fax parameter because a hure amount of listing has it, so it worth to keep it separated.

Let me know, --Andyrom75 (talk) 23:23, 21 April 2015 (UTC)Reply

@Andyrom75: Seems ok to do, although I don't really have much of a view either way as to which is best. Also, just wondering if fax is really needed that much these days as well. Could be kept as an option but removed from the examples and skeleton examples, so as to discourage adding it in the first place. -- WOSlinker (talk) 14:42, 27 April 2015 (UTC)Reply

Although I'm not a fax user, a lot of structures published thier fax over webiste, brochure, etc. so I would tend to keep them separated. --Andyrom75 (talk) 22:25, 3 May 2015 (UTC)Reply

I noticed you added a redlink [[Amqui]] to the Saint-Louis-du-Ha! Ha! destination page. There's a "guide"-status article about this place at fr:Amqui, fairly extensive at 38Kb for a small, pop-6000 town on the road from Rimouski to New Brunswick. Would it be worth stealing? K7L (talk) 02:31, 13 September 2015 (UTC)Reply

It was better than linking to user:Amqui. Yes, there's quite a bit on that french page that would be worth adding. -- WOSlinker (talk) 06:00, 13 September 2015 (UTC)Reply

You do a magnificent job!

In this case, though, you missed something, understandably: For some reason, User:Prof tpms has taken to putting content in the "directions" tab. Ikan Kekek (talk) 20:25, 14 September 2015 (UTC)Reply

Do you intend to add the listing to Bodmin? --Traveler100 (talk) 20:34, 16 April 2016 (UTC)Reply

Those listings were a bit sparse, so didn't seem worth adding. I've now found the details for The Globe Inn and The Royal Oak Inn and have added them in Sleep rather than Eat & Drink. -- WOSlinker (talk) 08:34, 17 April 2016 (UTC)Reply

OK thanks. I think it is a good idea to rationalize pages with little detail but do not like loosing listings --Traveler100 (talk) 08:39, 17 April 2016 (UTC)Reply

Interesting list. It is also showing up pages where there are two Wikidata pages for the same topic. e.g. Bethesda (Wales). I have started fixing and d:Wikidata:Requests for deletions. --Traveler100 (talk) 19:43, 15 August 2016 (UTC)Reply

@Traveler100: I've noticed that as well, but I'm just using the "merge with..." option rather than deleting. -- WOSlinker (talk) 21:59, 15 August 2016 (UTC)Reply

I think it is useful, bu does highlight some work to sort out. --Traveler100 (talk) 06:19, 16 August 2016 (UTC)Reply

I noticed you sorted Örö as "Oro". Is there some guidelines on how articles should be sorted? Any local person and anyone who knows Swedish would suppose to find Örö after z (the Swedish alphabet ends "xyzåäö"). The Swedish åäö are letters in their own right, not variations like the German umlauts or French accents. --LPfi (talk) 10:22, 9 September 2016 (UTC)Reply

If you thinks it's wrong then you can undo my chnages. I just though that it seemed odd to have all those articles after the Z articles in the categories. I personally would have expected Örö to be in the O section but if it's wrong then you can undo it and I'll leave it alone. -- WOSlinker (talk) 12:34, 9 September 2016 (UTC)Reply

I only know the Swedish (and Finnish, Norwegian etc.) sorting, so will not comment on e.g. Šumadija. And I do not know the practices in English. It seems Wikivoyage is using plain Unicode code point numeric sort (which happens to mostly work for Swedish & al), so DEFAULTSORT keys are needed for all odd names, but what keys to use is an open question – and perhaps some other collation algorithm should be activated. I change the sort for the Swedish and Norwegian names in your last contributions, but otherwise some discussion seems to be needed. --LPfi (talk) 20:58, 9 September 2016 (UTC)Reply

Please take a look at it. Thanks, --Andyrom75 (talk) 20:32, 9 September 2016 (UTC)Reply

Thanks! Please check also MediaWiki talk:Mobile.css#.topbanner. --Andyrom75 (talk) 18:21, 10 September 2016 (UTC)Reply

Sorry for disturbing you, but to complete the activation of the GPX indicator I need to modify mediawiki files as follow (and I personally can't):

• MediaWiki:Common.css: add #mw-indicator-GPX { display: none; }
• MediaWiki:Common.js: add $(".geo, #GPX-track").parents("#content").find("#mw-indicator-GPX").css("display","inline");

Once done I'll patch the Template:Pagebanner. Thanks, --Andyrom75 (talk) 09:42, 14 October 2016 (UTC)Reply

Done -- WOSlinker (talk) 12:18, 14 October 2016 (UTC)Reply

Gosh, sorry... I haven't noticed that Template:Pagebanner is protected, so I need to disturb you again.

Please change the second line from

-->{{PAGEBANNER:{{#switch: {{{1|}}}

to

-->{{GPX indicator}}{{PAGEBANNER:{{#switch: {{{1|}}}

Thanks, --Andyrom75 (talk) 18:11, 14 October 2016 (UTC)Reply

Done, but I've now also protected Template:GPX indicator as it will be high use. -- WOSlinker (talk) 19:18, 14 October 2016 (UTC)Reply

Thanks a lot! No problem for the protection; the code should be fine. --Andyrom75 (talk) 19:25, 14 October 2016 (UTC)Reply

I have noted that you have been removing address elements from listings I took the trouble to enter addresses into. I have not yet reverted your edits (as I have no wish to enter an edit war) and the issue of this may easily mean I leave being a contributor to the site. I have started a discussion and given reasons why removal of address elements is a massive mistake on Wikivoyage talk:Listings#Practice of Address Abbreviation/Element Removal/Shortening - And The Shortsightedness of Doing This. I have a fair amount of experience with addressing issues in mapping apps and the grief that can be caused by missing elements (and I'm still helping one of the biggest Calendar app developers sort out the addressing grief caused by this practice that was for a short time used by the platform provider ...).

To spend significant time contributing one has to believe the site is "going somewhere" and that users can really make use of the data you spend your time entering. If I do not believe that is the case then I will spend my time elsewhere (where the effort my effort will not be partially wasted wasted). And removing address elements such that using the address outside WV means all sorts of cutting and pasting and merging page titles into the right part of the address and/or where using the "abbreviated" address in some navigation apps will not cause an error - just may mark and send you to somewhere between 2 and 8 miles away from where you want to go! (the 2 and 8 miles are from a couple of addresses I use to help the app developer sort out the issues they face with the address "abbreviation".

I do not mean to sound rude or short (expressing things you feel strongly about can be hard through text without spending forever reviewing, adjusting, etc. text) but it is something I feel very strongly about from personal experience. PsamatheM (talk) 18:38, 2 May 2017 (UTC)Reply

I'm sorry you feel that my edits may make you leave this site. This was not my intention. I've just been removing the town/city name that matches the article name and also occasionally the county. As mentioned on Wikivoyage:Listings, it states that for addresses: do not include the city (if the same as the page title), the state/province or postal code (except for addresses in the United Kingdom, which should include the post code), which is why I was removing some, just to shorten the listings text. -- WOSlinker (talk) 19:41, 2 May 2017 (UTC)Reply

As you can see form the discussion liked to above I provide an example for France where removal of the postcode makes an address ambiguous and and traveller would stand a 50:50 chance of turning up at the wrong place. As outlined in the discussion, external apps will often want a complete address to work properly (and may just send you to the wrong place without warning with incomplete addresses) even with a postcode. WV needs to consider increasing use of addresses outside of just being ready by eyeball within the site itself and the only way to do that is to provide the address - not the address with elements removed! I've personal experience of the grief caused by address element removal and I'm still working testing beta software where the app developer relied on the OS provider for address handling and the OS provider went through a phase of address element removal (though they removed it after a bit because of the problems it caused) - all very mainstream platforms. The best time to collect complete accurate information is when the contributor initially enters the data. To remove information from a complete entry severely limits utility of the data other that eyeball within the site and WV really should be thinking about wider use than that. Blindly following a bad policy that permanently damages data raises questions for me as to whether my time contributing is "well spent". PsamatheM (talk) 19:50, 2 May 2017 (UTC)Reply

Hello WOSlinker, you reacted to problems mentioned at Wikivoyage:Travellers' pub#Page banner content. But not only at the English WV, but also on the Dutch WV we have problems. Furthermore I cannot find any discussion about the change. --FredTC (talk) 11:53, 15 June 2017 (UTC)Reply

If you make the same change that I did here, it will hide the problem. I don't know what the actual cause of the problem is. My change is just a fix to hide the problem. -- WOSlinker (talk) 13:21, 15 June 2017 (UTC)Reply

Hi WOSlinker, you did not give a reason at your change on Leipzig, why you removed the dmoz entry. Are you able to explain me here, why you chose to remove it?--Johayek (talk) 14:20, 25 January 2018 (UTC)Reply

I'm not WOSlinker, but I assume the dmoz link was removed because "DMOZ was closed on March 14, 2017 and DMOZ support in the RelatedSites extension was removed from MediaWiki." ϒpsilon (talk) 15:08, 25 January 2018 (UTC)Reply

There were only 4 articles left with dmoz links on them, so I removed them. see this search for dmoz links -- WOSlinker (talk) 21:37, 25 January 2018 (UTC)Reply

You have been removing <p> tags in listings. Why? In Dumaguete#Along_the_boulevard, you removed two in the listings for Bogart's and Why Not? I fixed the formatting, inserting a blank line into each, and the software converted that back to a paragraph tag. Pashley (talk) 10:33, 30 March 2018 (UTC)Reply

When it didn't seem necessary to have in separate paragraphs, I've removed a few to just make it a single paragraph. -- WOSlinker (talk) 17:34, 30 March 2018 (UTC)Reply

During the absence of Ryan, could you help with the above? Thanks, --Andyrom75 (talk) 07:09, 19 July 2018 (UTC)Reply

You are now an interface admin. I apologize for not taking care of this in a timely fashion. You were of course unanimously confirmed for this role. Thanks for all you do!

All the best,

Ikan Kekek (talk) 04:53, 28 August 2018 (UTC)Reply

Just wanted to drop you a line to say thank you for your help in updating our Abuse Filters. That recent spate of vandalism was really starting to get under my skin.

-- AndreCarrotflower (talk) 02:51, 1 September 2018 (UTC)Reply

Thanks. I'll try to refine them a bit of time as well. -- WOSlinker (talk) 08:48, 1 September 2018 (UTC)Reply

He's back... -- AndreCarrotflower (talk) 19:26, 7 September 2018 (UTC)Reply

Hi, any ideas on my question Module talk:Wikidata#get site link from qid (i.e. not current page)? --Traveler100 (talk) 13:16, 11 November 2018 (UTC)Reply

The code was different. I've updated it and it's working now. -- WOSlinker (talk) 13:38, 11 November 2018 (UTC)Reply

Hi, what method did you use to make this change? Not sure we want see listings changing format. --Traveler100 (talk) 16:17, 10 December 2018 (UTC)Reply

I used the ListingEditor2 (beta) gadget. -- WOSlinker (talk) 16:56, 10 December 2018 (UTC)Reply

(sorry for butting in) Hi @Traveler100: The format changes were discussed at Wikivoyage talk:Listing editor#New changes, near the bottom. I can't think of a reason not to change them other than things will be inconsistent for a while, and there are some benefits. I mentioned there that if anyone can think of any drawbacks, I'd like to consider them. You're welcome to leave feedback over there on this change or any of the other changes. Thanks, ARR8 (talk) 17:57, 10 December 2018 (UTC)Reply

Made some changes to js and css. Could you update the beta? Thanks, ARR8 (talk | contribs) 16:32, 20 January 2019 (UTC)Reply

@ARR8: I've done that. -- WOSlinker (talk) 20:41, 20 January 2019 (UTC)Reply

Thanks again. Could you do it once more? If all goes well, this will be the last revision of these changes except for some debug code removal before rollout. ARR8 (talk | contribs) 00:36, 27 January 2019 (UTC)Reply

@ARR8: I've done that. -- WOSlinker (talk) 10:19, 27 January 2019 (UTC)Reply

Would appreciate some assistance, maybe you can see why this is not working on mobile display? --Traveler100 (talk) 14:22, 12 February 2019 (UTC)Reply

Had a quick look earlier on but didn't spot anything. Will need to look in more detail tomorrow. -- WOSlinker (talk) 23:11, 12 February 2019 (UTC)Reply

Hi, I have got two interface requests for you at your convenience:

1. The changes I outlined at MediaWiki_talk:Common.js#Listing_buttons. Let me know if you would like me to write the code snippet for the 'go' button.
2. The Main Page text was changed, but the <title> for the Main Page still reflects the old text (capital FREE, etc). I'm not sure where this is changed, but guess it is interface related.

Thanks, ARR8 (talk | contribs) 03:29, 23 February 2019 (UTC)Reply

Hi ARR8, yes please, put the code snippet on MediaWiki_talk:Common.js and I can add it. I think in a few more months time, you may want to see about getting added to the interface-admin group yourself. Best to wait for now though as you've just recently got the admin group. When trying to find the interface page, you can add uselang=qqx to the url, for example https://en.wikivoyage.org/wiki/Main_Page?uselang=qqx and then see what information is shown inside the bracket for each bit of text. However, it's not showing the title page in this case. So, I looked at Special:AllMessages and found that the page you'll need to edit is MediaWiki:Pagetitle-view-mainpage -- WOSlinker (talk) 19:45, 23 February 2019 (UTC)Reply

Thanks greatly for your help. I've put the code on the talk page as requested. ARR8 (talk | contribs) 20:07, 23 February 2019 (UTC)Reply

A couple more, if you don't mind:

1. Removal from common.css of pagebanner styles, moved into templatestyles here
2. A slight modification to MediaWiki:Gadget-ListingEditor.js - there are two section header strings, 'See_and_Do' and 'Eat_and_Drink' which should have the second word decapitalized to 'See_and_do' and 'Eat_and_drink'

Thanks again. ARR8 (talk | contribs) 01:20, 2 March 2019 (UTC)Reply

ARR8, I've done those changes. -- WOSlinker (talk) 08:40, 2 March 2019 (UTC)Reply

Due to unforeseen problems, the common.css change must be undone ASAP. Please do so when you can. ARR8 (talk | contribs) 14:01, 2 March 2019 (UTC)Reply

I've put them back in. -- WOSlinker (talk) 14:22, 2 March 2019 (UTC)Reply

ARR8, MediaWiki:Mobile.css also has some banner css. It's just the icons part though. So maybe that part is fine to remove from both MediaWiki:Common.css and MediaWiki:Mobile.css? -- WOSlinker (talk) 14:31, 2 March 2019 (UTC)Reply

I think it has to stay in both until we can figure out a way to move it into the template, seeing as how the icons didn't work when removed from common. Good to know that it's duplicated in two places, though. ARR8 (talk | contribs) 14:35, 2 March 2019 (UTC)Reply

Two requests again:

1. A bugfix for the listing editor, diff here
2. I drafted some CSS at my user talk page here. I think it may be best suited in MediaWiki:Mobile.css, sans the media query (i.e. the first and last lines). But, if you can think of a place it is better suited, feel free to put it there. ARR8 (talk | contribs) 01:56, 23 March 2019 (UTC)Reply

Thanks as usual. ARR8 (talk | contribs) 01:56, 23 March 2019 (UTC)Reply

I've made those changes. -- WOSlinker (talk) 14:46, 24 March 2019 (UTC)Reply

I don't know if you aw my reply at the Travellers' pub but your tip was exactly the solution I needed. thank :) is there any similar mediawiki page I could use to add HTML keywords/description to all the articles for SEO purposes? I found this but I was wondering if there is a simpler way to do that. ויקיג'אנקי (talk) 19:10, 25 July 2019 (UTC)Reply

Sorry, nothing I can think of. -- WOSlinker (talk) 21:03, 25 July 2019 (UTC)Reply

Hi WOSLinker,

I'm unclear whether you're a person or whether this is a bot. If it's a bot, then could your owner arrange to have you marked as a bot? While all these recent changes to update Hilton Hotel URLs are useful, it clutters up everyone's watchlist, and not being able to filter it out as bot edits kinda sucks.

(If not, at least they're marked as minor edits, which can be filtered... carry on.)

Thanks! --Bigpeteb (talk) 18:12, 6 October 2019 (UTC)Reply

I need your support to test a new version of LE that I've already implemented in the beta version of it:voy and just enabled en:voy.

• MediaWiki:Gadget-ListingEditor2.css can be replaced with User:Andyrom75/ListingEditorTest.css
• MediaWiki:Gadget-ListingEditor2.js can be replaced with Special:Permalink/3873125
• Template:Pagebanner can be replaced with Template:Pagebanner/sandbox

The last one affect production articles, as you can see {{CountryData2HTML}} only ad a not visible SPAN tag with information used by the new listing editor. I've just applied the sandbox template to Florence.

If you want to see the effect of the new version, feel free to use the script in your common.js or use the beta version in it:voy.

I would appreciate to have more feedback on this revision. --Andyrom75 (talk) 14:05, 28 October 2019 (UTC)Reply

Andyrom75, I've made those changes. -- WOSlinker (talk) 21:26, 28 October 2019 (UTC)Reply

Andyrom75, I've just been looking at the new phone number feature I think it's very good. I have a couple of comments though. The first is that when clicking on either of the number parts, I would usually also want to include a space afterward, so for example instead of just "+1", it should insert "+1 ". The second is that the local dialing code sometimes begins with a 0 in wikidata. Most of the time, that 0 is not needed when inserting the local code rather the country code, so might be better to remove any leading 0 from the local code. Examples include Bristol, Dublin, Munich, Christchurch. -- WOSlinker (talk) 21:51, 28 October 2019 (UTC)Reply

For the space no problem, I agree. I can work on it.

Regarding the local dialing code, the discussion is definitely broader. Few years ago I've asked without success to some wikidata-bot-operator to clean that property. There are nations like Italy where the 0 is needed, so we can't just remove it. We need another information but I don't know if it's stored on Wikidata (give more time to retrive it). If not, I can add it manually just like I've done with the currency symbol.

Furthermore there is another problem highlighted in Wikidata as well. Some people have added code like the following "(0) 123", but "(" and ")" are symbols that do not respect the syntax and should be removed. Same thing with those that include again the country code inside the local code.

Basically, we should clean Wikidata before apply a change on our script logic. --Andyrom75 (talk) 22:00, 28 October 2019 (UTC)Reply

Here we go. This is the property I've mentioned you before. Basically it tells which are the numbers to remove if any. --Andyrom75 (talk) 22:05, 28 October 2019 (UTC)Reply

To add the spaces in the telephone fields, to fix a bug that prevent the use of the old Wikidata sync in other languages, plus other minor fixes you can just simply copy this page to MediaWiki:Gadget-ListingEditor2.js. --Andyrom75 (talk) 15:06, 30 October 2019 (UTC)Reply

I've noticed that the script has been already updated, so there is no further action need a part the approval of this beta test to be copied to the main script. --Andyrom75 (talk) 13:31, 5 November 2019 (UTC)Reply

Hi, I am not sure how to do this and I see you are an Interface administrators. In preferences on Wikipedia there is an appearance gadget "Display links to disambiguation pages in orange", any chance of getting that option here? --Traveler100 (talk) 08:33, 25 January 2020 (UTC)Reply

I've installed it the experimental section. It uses a single shared of orange for both visited and not-visited links. I could change that so that there are slightly different shades if you want. Also, just wondering, if you would be interested in showing redirects in green, maybe as a separate gadget? -- WOSlinker (talk) 12:33, 26 January 2020 (UTC)Reply

Hi WOSlinker, I noticed that MediaWiki:Revision-info still uses its own background styling despite MediaWiki now having its own banner. If you look at an old revision like Special:Permalink/3944452 you'll see that there are two boxes; is this intentional? If not you may want to remove the background color and border color elements styles from the interface page. Wugapodes (talk) 21:24, 3 April 2020 (UTC)Reply

Thanks, I've removed the styling from MediaWiki:Revision-info. -- WOSlinker (talk) 21:42, 3 April 2020 (UTC)Reply

Please perform this change that will allow to personalize better the namespace where the listing is used. I've done this because in it:voy we need also NS:104 and I've preferred to use in the code a customized array. PS Sorry to ask you this all the time :-) --Andyrom75 (talk) 20:56, 8 June 2020 (UTC)Reply

Done -- WOSlinker (talk) 21:24, 8 June 2020 (UTC)Reply

Please perform the following page replacement:

• MediaWiki:Gadget-ListingEditor2.css with User:Andyrom75/MediaWiki:Gadget-ListingEditor.css
• MediaWiki:Gadget-ListingEditor2.js with User:Andyrom75/MediaWiki:Gadget-ListingEditor.js

All the changes are listed inside the script as usual. Script has been already tested and implemented in it:voy but since it required to be adapted for en:voy I prefer to test it first in beta version.

A part minor changes, the most important ones are two: 1) table 2 div conversion: this is the first fundamental step to enable listing editor on mobile view. I'll take care of it in a following phase. 2) DMS notation support. it:voy and de:voy use since many years DMS notation on listing, but Wikidata use DD notation. Now I've implemented a conversion function. This function do not change DD notation provided as an input, hence do not affect en:voy current behaviour. If requested en:voy can be enable to use DMS notation also on listing (IMHO this will simply writer's life)

Thanks, --Andyrom75 (talk) 17:03, 8 July 2020 (UTC)Reply

I've just noticed that your last access is around 1 month ago. To avoid to disturb you all the times with these operation, could you help me to get the interface admin right on en:voy? This should make me autonomous. Thanks, --Andyrom75 (talk) 08:41, 9 July 2020 (UTC)Reply

I've been spending more of my time over at Wikipedia at the moment. I've added a nomination for you at Wikivoyage:Administrator nominations. I've also updated the pages as requested. -- WOSlinker (talk) 21:30, 9 July 2020 (UTC)Reply

Thanks for the nomination. In the meanwhile, I keep on disturbing you :-) Please refresh the ".js" with the latest User:Andyrom75/MediaWiki:Gadget-ListingEditor.js, I've made a little improvement. Now I'll stop coding until I get interface admin right to be autonomous :-)

Feel free to perform some test, letting me know any wrong/strange behaviour. --Andyrom75 (talk) 06:44, 10 July 2020 (UTC)Reply

Andyrom75, You seem to have logged off there. Anyway, I applied the latest changes, but I'm not sure if they are totally correct, so you may need to review. -- WOSlinker (talk) 22:27, 9 July 2020 (UTC)Reply

I've done some test this morning and apparently everything works. Have you experienced some errors? --Andyrom75 (talk) 06:44, 10 July 2020 (UTC)Reply

This change added a d to the end of the author ARR8 and the DEFAULT_PLACEHOLDERS wording changed from English to Italian. I haven't had a chance to do any testing yet. -- WOSlinker (talk) 08:58, 10 July 2020 (UTC)Reply

Shame on me! You're right. I've made the wrong copy and paste, but now I've fixed it. Please refresh the script. --Andyrom75 (talk) 15:43, 10 July 2020 (UTC)Reply

Done. -- WOSlinker (talk) 17:14, 10 July 2020 (UTC)Reply

Inside the discussion in the subject I've seen the request of adding "mediawiki.user" as a dependency for the Listing Editor, but I don't understand the reason why. In it:voy we don't have it and everything works correctly. --Andyrom75 (talk) 20:18, 14 July 2020 (UTC)Reply

It's only set as a dependency on the beta version as well, so I'll go ahead and remove it. -- WOSlinker (talk) 10:27, 15 July 2020 (UTC)Reply

Hi!

You get this message because you are an admin on a Wikimedia wiki.

When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.

Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.

If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.

We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.

Thank you. /Johan (WMF)

18:14, 4 January 2022 (UTC)

Question for you since you are a Template Editor here, and are familiar with delinting on en.wiki and with me.

There are a few lint errors here on Voyage that I think would be better cleared by editing the templates used, rather than editing the pages claiming the errors. I wondered if the following would be agreeable, non-controversial, template adjustments.

On Template:Infobox, the text parameter uses string, which reports a misnested lint error whenever manual line breaks are used. Replacing them with break tags (or paragraph tags) will clear the errors, but the typical user isn't going to think about using those, so it makes more sense to me to change that parameter type from string to something else that would accept manual line breaks. I'm not sure what type to replace it with at the moment, unless the text parameter type is exactly that? Do you know what type would solve this issue, and is this something you'd be willing to update on the template to the appropriate type?

There's also a similar, and more prevalent, issue on the See/Eat/Play/etc templates that is affecting 150 some pages. The content parameter of these templates seems to logically be a few lines of text, and people are going to use manual line breaks in those. Could the See/Eat/Play/etc Templates also be updated to accommodate the manual line break from a similar parameter type change, or are these intended to be short and sweet, single line statements and these are the rogue few that are too long? Template:Listing says "content=BRIEF DESCRIPTION OF THE LISTING", where the others don't say anything. Zinnober9 (talk) 16:34, 28 August 2024 (UTC)Reply

For infobox, maybe replace the <strong> with <div style="font-weight:bold;">? Not sure what to do with the listing one. Sometimes I merge the multi-line content ones to a single line with added br tags. -- WOSlinker (talk) 18:40, 28 August 2024 (UTC)Reply

I don't have template editor abilities, so I wouldn't be the one to change it directly unless I did change request. I just tested changing <strong> with <div style="font-weight:bold;"> with the template's sandbox however, and then borrowed a test case (original to my profile, changing it to call the sandbox's code). Test was successful, error-free, and displayed the same way, so I think that would be a clean and easy solution for those pages affected. Shall I make such a change request, or are you happy with these results that you'd be willing to make this change per this discussion? Zinnober9 (talk) 21:59, 28 August 2024 (UTC)Reply

I've made that change. I've also edited a few of the articles, so there are less issues there as well now. -- WOSlinker (talk) 22:04, 28 August 2024 (UTC)Reply

Thank you! Zinnober9 (talk) 22:15, 28 August 2024 (UTC)Reply

In a lot of articles you have removed blanks, such as "+44 1992 572 388" → "+44 1992 572388". I think the former format is much more readable, and United Kingdom#Connect gives the example number "+44 20 xxxx-xxxx, so the numbers don't seem to be standardised to the format you change them into (the hyphen should be there for numbers that can be dialled locally without the area code, not otherwise, but I think the grouping should be the same regardless). Readability makes little difference when calling the number by tapping it (I suppose mobile phones are the reason for not everybody grouping digits any more), but there are many situations where you want to be able to read it. (In general, mass changes like this should be done only when there is an established consensus, although here it seems there was mixed usage on the pages.) –LPfi (talk) 18:06, 14 December 2024 (UTC)Reply

They can be grouped into one if the phone number is 6 digits but 7 or 8 would usually have a dash in it. However, if not changing "+44 1992 572 388" to "+44 1992 572388" then they should be changed to "+44 1992 572-388" rather than left with a space in them. -- WOSlinker (talk) 18:46, 14 December 2024 (UTC)Reply

Is this discussed or told somewhere? I don't see from where the rule of 6 vs 7–8 comes. I really have difficulties myself copying or memorising a non-grouped 6-digit number (I need to check several times that I got it right, with the font size I get on desktop, never mind on mobile).

For Finland, I try to maintain a standard where you can see the prefix (area code or otherwise) and how the number should be dialled from local land lines, but that requires some familiarity with what length different prefixes have and which ones are area codes. I cannot tell what area codes can be left out locally in the UK (which is the determining factor in whether to use hyphens – I didn't know that the listings accept figure dashes: ☏ +44 1992 572‒388).

–LPfi (talk) 18:59, 14 December 2024 (UTC)Reply

Numbers with an area code starting 1 or 2 can be called without the area code if you are in that area. The others (3, 7, 8 & 9) need the full number all the time. The area codes vary in length from 2 to 4 digits with larger cities getting shorter codes. -- WOSlinker (talk) 20:27, 14 December 2024 (UTC)Reply

Thanks. I added that info to United Kingdom#Telephone. –LPfi (talk) 07:52, 15 December 2024 (UTC)Reply

LPfi: Just to add, I've done about 200 edits updating the phone numbers recently. There are now about 1200 pages in the +44 1xxx xxxxxx format (was previously 1000), 70 pages in the +44 1xxx xxx xxx format (was previously 270) and only 5 pages in the +44 1xxx xxx-xxx format, so even before my changes the +44 1xxx xxxxxx format was the most common for the numbers where the non-area code part is 6 digits. -- WOSlinker (talk) 23:11, 14 December 2024 (UTC)Reply

When you are at your computer and have a phone number displayed, dialing the number goes more often wrong if you have to read xxxxxx; if you read xxx xxx mistakes are less frequent. FredTC (talk) 05:27, 15 December 2024 (UTC)Reply

ThunderingTyphoons! undid my edit to tell what numbers can be dialled without area code. So those that start with 1 and 2 are real area codes and you can usually dial them locally without area code, but that is forbidden in some untold areas. Does that mean that a traveller should generally include the area code also when calling locally from a land line? That seems to be the advice we now are giving. In Finland that doesn't work, but I suppose it does in the UK. –LPfi (talk) 07:28, 17 December 2024 (UTC)Reply

If that's our advice, we should not use dashes or hyphens in UK phone numbers, except when the editor knows the shorthand is legal – or never, as we don't know that they know the situation, unless explicitly told in the Connect. –LPfi (talk) 07:33, 17 December 2024 (UTC)Reply

Sorry, mate, I did not realise your edit was a whole thing spawned by discussion.

I am not aware of any area codes that don't allow the short number for local calls. Though when calling from a mobile (which most travellers will be), you always have to dial the full number, as mobile numbers are non-geographic. The 03 etc prefix cases aren't relevant, because travellers will never be dialling from one, much less between two of them.

Hyphens aren't normally used for phone numbers in Britain, but spaces often are. I tend to think spacing makes the number more readable, but also appreciate the necessity to demarcate the prefix for people who aren't familiar with a country's phone numbers.--ThunderingTyphoons! (talk) 03:04, 19 December 2024 (UTC)Reply