Talk:Wiki

If you have ideas for the wiki, you can generally just do them, by editing the wiki! Big restructuring can be discussed in relation to WikiProject Cleanup, but in general we would encourage you to be bold.

If you have ideas for technical improvements to the way the wiki works, e.g. extensions we should install, you might add them here, and/or create issues in GitHub: openstreetmap/operations/issues/. Older requests can be found in trac (raised as 'component=wiki'): https://trac.openstreetmap.org/query?status=new&status=assigned&status=reopened&component=wiki&order=priority

Older requests can be found here:

---

Visual editor isn't usable because of {{Fa}} template

By putting the {{fa}} template at beginning of Farsi pages, content of the page will be wrapped into it, and so, Visual editor doesn't allow direct editing, but we should edit the content via an interface like text editor.

I found out if I put direct HTML of the template instead of the template itself, visual editor will work.

An example page that uses the {{fa}} to make the page RTL, and the same page that uses the following HTML directly (HTML code from template):

<div lang="fa" dir="rtl" class="mw-content-rtl" style="direction:rtl;text-align:initial;font-family:'Noto Naskh Arabic',Noto,'Segoe UI','Iranian Sans',Tahoma,sans-serif;font-size:initial;line-height:1.6">

My question: is there any solution to avoid using this long piece of HTML code and at the same time visual editor work properly? iriman (talk) 13:15, 22 May 2019 (UTC)

What formatting and templates (if any) do multilingual WMF wikis such as Wikimedia Commons, meta.wikimedia.org and Mediawiki.org use? Does the Visual editor work there? --Andrew (talk) 19:09, 22 May 2019 (UTC)

seems they don't have visual editor as we have here. It's a translate functionality. but on commons there is some templates, for example main page in persian wikimedia commons has a template that uses langcode parameter, however I couldn't find visual editor. iriman (talk) 13:37, 23 May 2019 (UTC)

I tried out a workaround so that for using it without a parameter we should use <div {{fa}}> instead of bare {{fa}}. Apparently it works. Please take a look at my draft. iriman (talk) 14:22, 23 May 2019 (UTC)

I want to modify {{Fa}} as its sandbox version. Then change all instances of {{fa}} to <div {{fa}}> on all pages of this wiki (~300 pages) with a comment for users who are following those pages.

This will not hurt inline ones {{fa|some text}}, as you can see in my draft mentioned on previous message.

I cannot do this task manually, and willing someone do it automatically.

After that we also need to update {{Ltr}} (~50 pages). iriman (talk) 14:51, 24 May 2019 (UTC)

Regarding your question: WM Commons seems to use the page content language property. According to the MediaWiki documentation, changing the page language wraps the content area in <div lang="xyz" dir="ltr/rtl" class="mw-content-ltr/rtl">page content</div>. So, in this case it would be <div lang="fa" dir="rtl" class="mw-content-rtl">.... This solution looks a bit more professional for me, but it would not necessarily include the additional style definitions by {{Fa}}. Is that an issue? (from a technical POV, we would need to request the system administrators to carry out some configuration changes and it may take a few days to review.) --Tigerfell  (Let's talk) 18:08, 24 May 2019 (UTC)

There is no Special:PageLanguage here though. --Andrew (talk) 08:44, 25 May 2019 (UTC)

That is what I meant with "configuration changes". First of all, they would need to enable setting languages for individual pages using $wgPageLanguageUseDB and then they need to assign the pagelang permission to some user group. I'd suggest either user or autoconfirmed (most of us are a member of both groups). The special page will then appear. The procedure for changing the page language would then work similar to changing the page content model using Special:ChangeContentModel. BTW, we could save the rest of the markup of {{Fa}} in MediaWiki:Common.css. --Tigerfell  (Let's talk) 10:57, 25 May 2019 (UTC)

@Tigerfell Definitely your solution is more professional. Font of the page and line height are important but not as important as page direction. With your solution if we'll have visual editor, I think we would be comfortable with it. iriman (talk) 11:24, 25 May 2019 (UTC)

@Iriman: The feature was added in openstreetmap/chef/pull/239. I already tried it out in my sandbox. Regarding the rest of the formatting, I would suggest you make an edit request at MediaWiki talk:Common.css for all RTL languages' formatting. --Tigerfell  (Let's talk) 20:52, 4 June 2019 (UTC)

Nice! Many thanks for following up on this issue. Ok, I will make a request there, thanks for the link! iriman (talk) 23:39, 4 June 2019 (UTC)

@Yurik: Is it possible to set this for all pages with language prefixes in their names by bot? --Andrew (talk) 06:21, 5 June 2019 (UTC)

Yes, it would be a fairly simple bot that would call action=setpagelanguage, but I am not sure how the bot will know the current language of the page - I couldn't find the api for that. Perhaps the bot will just keep a list of pages it has already modified. --Yurik (talk) 18:46, 5 June 2019 (UTC)

All pages except for those changed recently (after the configuration change) are in English (default language for this wiki). --Tigerfell  (Let's talk) 20:10, 5 June 2019 (UTC)

+1. Also we need to remove {{Fa}}, {{Ar}}, etc. from beginning of those pages. But note that there may be some of these templates currently explicitly transcluded in block mode {{fa}}...</div> or inline mode {{fa|...}}. They should remain as they are now. iriman (talk) 19:01, 5 June 2019 (UTC)

Actually currently we may have {{fa}}...</div> or inline mode {{fa|...}} in other namespaces that are ltr. not an issue here. iriman (talk) 08:16, 6 June 2019 (UTC)

Long term maintenance could be done various ways, for instance putting a warning message and tracking category in the language template if the language set in Mediawiki differs from the one inferred from the page name. Populating the language tags in the first place is the tedious bit. --Andrew (talk) 07:36, 6 June 2019 (UTC)

Why do we need to have the correct language setting for all pages? It would be obviously nice to know and a good info for search engines and the like, but apart from that? --Tigerfell  (Let's talk) 17:23, 6 June 2019 (UTC)

It could be useful for language-specific formatting, for example font face (since it's a common need between all languages). This is a possibility only. Users of a language may need it, or not if default configuratuon satisfies them. For Fa, Ar, He, etc. currently we have font settings on our templates {{fa}}, {{ar}}, {{he}}, etc.iriman (talk) 10:59, 8 June 2019 (UTC)

By use of @Wynndale: idea, I put a general notice on {{Fa}} template for a somehow long term maintenance on Farsi wiki. iriman (talk) 15:21, 13 June 2019 (UTC)

Hi again, could someone please take this issue in hand: Setting the page content language for new wiki pages automatically on page creation iriman (talk) 05:51, 17 June 2019 (UTC)

Discussion about Interwiki prefixes

In case you are interested, there is a discussion about interwiki prefixes at Wiki talk:Interwiki. Interwikis are prefixes for linking to an external webpage i.e. not wiki.osm.org using the syntax of an internal link. There are essentially two ways of linking then:

• using external links: https://en.wikipedia.org/wiki/OpenStreetMap https://en.wikipedia.org/wiki/OpenStreetMap
• using interwiki: wikipedia:OpenStreetMap [[wikipedia:OpenStreetMap]]

These prefixes can be changed by administrators. --Tigerfell  (Let's talk) 09:14, 3 June 2019 (UTC)

Upload file clarification

https://wiki.openstreetmap.org/wiki/Special:Upload dialog claims "Media files that are not covered by the project scope of Wikimedia Commons, but are useful in OpenStreetMap wiki pages: for example media of State of the Map conferences, Humanitarian OSM Team projects, mapping parties."

But there are https://commons.wikimedia.org/wiki/Category:State_of_the_Map https://commons.wikimedia.org/wiki/Category:Humanitarian_OpenStreetMap_Team https://commons.wikimedia.org/wiki/Category:OpenStreetMap_mapping_parties and as far as I know this files are withing Wikimedia Commons interests. I propose to delete this line from interface or switch examples to correct ones. Mateusz Konieczny (talk) 05:31, 11 June 2019 (UTC)

Well, I guess the question is whether the content is "realistically useful for an educational purpose" from the Commons POV. Regarding your argument, I would cite

An otherwise non-educational file does not acquire educational purpose solely because it is in use on a gallery page or in a category on Commons, nor solely because it is in use on a user page (the "User:" namespace), but by custom the uploading of small numbers of images (e.g. of yourself) for use on a personal Commons user page is allowed. Files relating to projects or events of the Wikimedia community, such as user meetings, are also allowed.

As you might have guessed, I am not sure if the files are considered "educational". I would suggest asking at the Commons help desk. --Tigerfell  (Let's talk) 13:26, 11 June 2019 (UTC)

I asked in the past, scope of commons is interpreted extremely broadly and generally anything where use can be justified is not deleted under this rules Mateusz Konieczny (talk) 13:40, 11 June 2019 (UTC)

Replacing the SlippyMap extension

There have been some bugs [1][2] with the unmaintained Slippy Map MediaWiki Extension and there was some discussion how we can replace it (see above). I now opened a request to add MultiMaps extension to this wiki to replace it (openstreetmap/chef/pull/241). I have outlined how this can be done using a bot at page User:TigerfellBot.

This is a pre-notification (because noting is installed yet). I plan to follow the steps of Automated Edits code of conduct, but in case someone has a question or objection, you can already raise it here. --Tigerfell  (Let's talk) 10:33, 15 June 2019 (UTC)

Can you please post a link to some wiki page with a map shown by this new extension? --Hufkratzer (talk) 11:09, 15 June 2019 (UTC)

• http://fr.nvcwiki.com/index.php/NVCwiki:Mise_%C3%A0_jour_en_cours Outlines the possibilities of this extension, we will be using OpenStreetMap only.
• http://www.jerezsiempre.com/index.php/Capilla_Santa_Gema_Galgani Short page with pictures and a map only.

Basically, you just place a Leaflet box with a map on the page. --Tigerfell  (Let's talk) 17:27, 15 June 2019 (UTC)

The last map on page http://fr.nvcwiki.com/index.php/NVCwiki:Mise_à_jour_en_cours contains a layer switcher. Is this also availabe in the OSM wiki? How? I couldn't find that in  Extension:MultiMaps/Documentation --Hufkratzer (talk) 10:03, 19 June 2019 (UTC)

This map does not use Leaflet, but some Yandex framework. There will be no layer switcher as of now, but you can select from two different tile providers (OSM standard and Thunderforest transport) by using the service parameter. This is similar to Slippy Map MediaWiki Extension. --Tigerfell  (Let's talk) 19:02, 21 June 2019 (UTC)

---

Update: The extension is available for about two months now, but there is a problem with the transportation layer. We are running version 0.7.2 which can not display them, because the never version 0.7.3 which can was not tested on MediaWiki 1.31 (current (LTS) version of this wiki). Since the whole backporting process has stalled about three weeks ago, I guess we will be waiting for version 1.34 of MediaWiki. This version will be probably compatible with 0.7.3 of MultiMaps. --Tigerfell  (Let's talk) 11:21, 17 August 2019 (UTC)

Update 2: The changes were backported yesterday, so the transport maps are available as of now.

--Tigerfell  (Let's talk) 12:54, 13 October 2019 (UTC)

I would like to start replacing the SlippyMap extension automatically using my account TigerfellBot. You can find the more details on the user page. I also created a new test version of Template:Place at User:Tigerfell/Sandbox. If you would like to test it, you can use Special:ExpandTemplates. In case of questions or concerns, please speak up now. Otherwise, I would execute my plans no earlier than in two weeks from now. --Tigerfell  (Let's talk) 12:16, 4 January 2020 (UTC)

Language bar template rewrite

Template talk:Languages#Lua rewrite proposes replacing {{Languages}} (the language bar at the top of nearly every page) with a rewritten version that takes 2–3 seconds less time to load than the current version. On short key/tag description pages, that can be a reduction in load time of up to 85%. The new template also improves maintainability. Thanks in advance for your feedback. – Minh Nguyễn ^💬 16:25, 19 June 2019 (UTC)

<includeonly> in templates

The interesting bits of some wiki templates are surrounded by <includeonly>…</includeonly>. These templates (except documentation if there is any) are not visible on the template page or in preview. Is there a good reason for this or should it be discouraged? --Andrew (talk) 19:50, 1 July 2019 (UTC)

IMHO that is a question of personal preference. Three examples for illustration:

Template:Relation

The whole template is wrapped in <includeonly> and <noinclude>. If would you transclude the template without parameters, it will trigger an error and add the page to the category Pages with script errors. The categorisation is built in by Scribunto extension and I wanted to avoid false positives.

Template:Ambox

The template page contains the template, but without a mandatory argument, so you see an error message but also an Ambox itself. So you might be able to guess what the template is about without reading the doc.

Template:Az:HelpMenu

There is no <includeonly> and also no error and no categorisation. It actually does not use any parameters at all. The display is helpful for users who would like to see what the template is about without knowing the language or switching to a translation.

I hope that is somewhat illustrative. --Tigerfell  (Let's talk) 20:31, 1 July 2019 (UTC)

Language icons

I am redesigning the icons that indicate languages of linked pages such as {{French}} ((fr)). I would appreciate comments and suggested text for the tooltip in different languages. --Andrew (talk) 11:09, 5 July 2019 (UTC)

Conventions for categorisation

Are there any conventions regarding categorisation beyond Wiki guidelines#Categories? I would like to structure the categories a bit more and avoid cases like Category:Mapping Party in Taiwan versus Category:Mapping parties in Latvia. I am particularly interested in conventions regarding

• use of plural parties vs. party
• translation aspects
  • What is Category:Belgium/translations good for?
  • When to use the "English" category?
• geographical structures e.g. Category:Municipalities in Belgium, Category:Provinces in Belgium, Category:Regions in Belgium, Category:Cities in Belgium, Category:Hamlets in Belgium, Category:Towns in Belgium, Category:Villages in Belgium
• naming for A in B categories like Category:Belgian tagging guidelines but Category:Transport in Belgium
• use of abbreviations

--Tigerfell  (Let's talk) 22:04, 10 July 2019 (UTC)

A lot of pages wind up using categories as if they were tags like one would find in Flickr, probably because of unfamiliarity with MediaWiki and its conventions. I've been trying to clean up import page categorization, but the very strong convention of naming the categories "Import from ..." continues to bug me. I think it's fine to rename categories to be more systematic, within reason, as long as the categorized pages don't get lost. {{Category redirect}} can be helpful for that. – Minh Nguyễn ^💬 00:15, 11 July 2019 (UTC)

How would you name the import categories? --Tigerfell  (Let's talk) 12:11, 18 July 2019 (UTC)

"Imports in …". Technically the data is being imported from one country to another, but "Import from" sounds like a command rather than a category name. It's pretty nitpicky, so that's why I haven't bothered to make the change yet. – Minh Nguyễn ^💬 16:58, 18 July 2019 (UTC)

Some ideas of my own:

• constantly using plural, because most categories use the plural form already
• translation
  • Could not really figure out the reason for .../translation categories
  • I suggest to use it for English pages only, file categorisation depending on the content language. If there is no language or context I suggest using the English category.
• Maybe it is best to create categories only when there are pages in them.
• Naming categories <Topic> in <Country> seems more flexible and clear than the other variant
• I would advise against using abbreviations.

Some other things I came up with when looking at the current categorisation.

• Category names should be descriptive and not to broad like Category:Photos or Category:SVG.
• Category hierarchies should not contain loops.
• I suggest using the prefix Wiki (note the space) for categorising Wiki stuff like clean-up categories and templates.
• Categorising the format does not look like a good idea (like Category:Photos). I would suggest rather grouping events.
• A category name <Features> by <Country> seems to indicate a container category, but that does not mean that all container categories follow that schema.
• I suggest changing the language indication from prefix to suffix. Category:IT:Wiki would become Category:Wiki/it and avoid using slashes in any other case. This would avoid some codes being capitalised while other use lower case.

--Tigerfell  (Let's talk) 12:48, 19 July 2019 (UTC)

Update license choices for uploads

I suggest to update the list of licenses to choose from when uploading. You can find my suggestion at MediaWiki talk:Licenses. --Tigerfell  (Let's talk) 11:34, 21 July 2019 (UTC)

Removing "WikiProject" prefix

Hi, I am Daniel, from Spain. I am renaming the wiki pages related to country mapping project to remove the "Wikiproject" prefix following the pages name conventions.

I have already renamed the United States, Canada, Spain, and all Spanish-speaking countries mapping project pages. I am in contact with the communities in Australia and New Zealand to find out if you would like to rename their country pages as well.

If anyone wants to collaborate, you're very welcome! We need volunteers. (I recommend contacting the local communities first to avoid unnecessary discussions.)

Thank you! --Dcapillae (talk) 21:34, 25 July 2019 (UTC)

I am currently in a loose contact with the mappers from Bangladesh. As it turns out now, they are confused by the prefix and want to restructure the country-specific pages. (Not sure if they just consider doing something of if they have a clear mission.) --Tigerfell  (Let's talk) 09:47, 26 July 2019 (UTC)

Resolving redirected categories

With regards to a user reverting the redirection of a category, because he thought the redirect "didn't work", I would like to suggest to resolve those redirected categories after a while. By resolving, I mean 'using a bot to change all pages in the category to the new category name'. There is a list of redirected pages which still contain pages. Any objections? --Tigerfell  (Let's talk) 19:58, 2 August 2019 (UTC)

I would of course check if it is reasonable to change the category and if it is not an error or a broken template that causes the categorisation. --Tigerfell  (Let's talk) 20:07, 2 August 2019 (UTC)

 Support --Dcapillae (talk) 23:32, 2 August 2019 (UTC)

 Support --Tordanik 15:40, 5 August 2019 (UTC)

Categories in Spanish

The categories in Spanish are not shown now in the language bar. Many categories in Spanish exist with the language prefix "ES" (Category:ES), but the template has now changed to use the prefix "Es" (Category:Es) by default. I don't know what I can do about it. There are a lot of categories in Spanish. Is it related to the redirects? What can I do to fix it? --Dcapillae (talk) 21:26, 9 August 2019 (UTC)

No, this is related to a recent rewrite of the language bar. The template now defaults to Es: for categories, but it recognizes either ES: or Es: if the category already exists. Note that, if the category name has been translated into Spanish, there needs to be a redirect or else the non-Spanish pages will be unable to detect the Spanish page. If the template isn't working as designed, please provide an example in Template talk:Languages and I'll sort it out. – Minh Nguyễn ^💬 00:09, 10 August 2019 (UTC)

Ah, in fact, the template did have a bug omitting links to any language with its own namespace in categories, templates, etc. This issue is now fixed. Thanks for spotting it! – Minh Nguyễn ^💬 01:49, 10 August 2019 (UTC)

Lua errors on Key- and Tag-pages

I'm seeing "Lua error in Module:DescriptionFromDataItem at line 822: attempt to index field 'wikibase' (a nil value)." on Key- and Tag-pages currently. Whoever broke it, please get it fixed again. --Lyx (talk) 19:17, 27 August 2019 (UTC)

See https://github.com/openstreetmap/operations/issues/325#issuecomment-525424195 Mmd (talk) 19:34, 27 August 2019 (UTC)

Wiki Adminship for Tigerfell

Some time ago, Yurik proposed me as an administrator in this wiki. I declined this, arguing that I would need some more experience, but I would be available at a later time. Today, I am in a situation where I would like to have unsused and broken Interwiki links removed, the list of licence choices being updated, and a shorter queue of deletion requests. Additionally, I would like to move the spam blacklist on GitHub to this wiki, so that administrators can edit them without requesting changes from the system administrators. Each of these actions require administrator status. That is why I would like to propose myself for becoming an administrator.

I am an active wiki contributor, who translates articles, updates the calendar, participates in discussions about the wiki, assists others, and does general maintenance. I often review Special:RecentChanges, but try to let others edit the wiki in their own ways without forcing my ideals on others. I have asked the system administrators to add multiple extensions to the wiki (like “Thanks” extension) and to update some settings (tile inclusion via HTTPS, automatic redirect resolution, renaming the project namespace) following user requests (List of my changes to the configuration). Since November 2018, I am working on a solution to replace Slippy Map extension.

On the negative side, I want to name the fact that I was possibly too optimistic or too inexperienced when starting DE:Proposed features/Empfehlung zur Verwendung von Multipolygonen(de), a proposal about when to use multipolygons instead of closed ways in Germany, and Wiki:Deletion policy, for which there was no consensus in the end. I would say that I have learnt that sometimes there is no consensus or at least you are not the right person to establish one and then it is better to withdraw and that writing a proposal is more difficult when multiple people do it together.

Perspectively, I would like this wiki to gain and maintain a supportive role for the OpenStreetMap project.

Since there is no established voting process for wiki administrators, I suggest that you indicate whether you approve or disapprove my nomination below. A bureaucrat could make a decision when everyone interested have placed their vote. Please also feel free to pose questions. --Tigerfell  (Let's talk) 18:36, 4 September 2019 (UTC)

 Support --Dcapillae (talk) 18:44, 4 September 2019 (UTC)

 Support good helpful contributor. --Yurik (talk) 00:10, 5 September 2019 (UTC)

 Support -- Naveenpf (talk) 01:23, 5 September 2019 (UTC)

 Support Tigerfell has shown deep commitment to this wiki's health and enthusiasm for its continued development. – Minh Nguyễn ^💬 05:25, 5 September 2019 (UTC)

 Support --Władysław Komorek (talk) 18:23, 5 September 2019 (UTC)

abstain -- I value your contributions but am not convinced you have enough experience and the deletion discussion is still in fresh memory. On the other hand bad experiences are sometimes the most instructive ones so I am not against. RicoZ (talk) 22:17, 8 October 2019 (UTC)

 Support -- Harry Wood (talk) 15:10, 28 October 2019 (UTC) . It's clear Tigerfell is enthusiastic, and I think we could probably do with a bit of that on our little list of wiki administrators. Although it's important for admins to weild their power in a slow and thoughtful way, sometimes we're a bit slow and unresponsive :-)

 Support --Tordanik 20:32, 28 October 2019 (UTC)

There was no activity here for about a week, but I was asked to act on Talk:Portugal, so maybe the bureaucrats (@Firefishy:, @Harry Wood:, @Lyx:, @Pigsonthewing:, and @Steve:) could make a decision? --Tigerfell  (Let's talk) 06:16, 13 September 2019 (UTC)

I am unclear as to what the process is for agreeing a new admin; and it does not seem to be documented. Can anyone point to a prior case or cases for precedent? Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 11:51, 10 October 2019 (UTC)

You can find my take on the issue three sections down on this page. --Lyx (talk) 22:45, 10 October 2019 (UTC)

Yeah there's no process. We're only little wiki, so we don't have a full chain of processes and rules in place. The common sense buck stops with the administrators! Any objections to adding Tigerfell? -- Harry Wood (talk) 15:10, 28 October 2019 (UTC)

DONE Y - User:Tigerfell is now an administrator! (See Special:Listadmins). -- Harry Wood (talk) 21:47, 30 October 2019 (UTC)

Merge zh-hans and zh-hant to Zh, and Reform the translation process of this wiki

As mentioned here, it is really hard to maintain both Traditional and Simplified Chinese. It is also unnecessary since the only difference between the two are vocabulary. It is also a really simple task (It is a built in feature for MediaWiki) and I do not understand why it take so long for this wiki to do this. All the admin need to do is to use Special:PageLanguage to change the language of the Chinese page to Zh, this will automatically enable the Language Conversion listed here on Mediawiki. Change page language to zh-hans or zh-hant will not trigger the conversion tab, you have to change it to zh, see here for an example. In this test page I create, the conversion tool is displayed with page language set to zh.

Since the language conversion problem is solved, it will be the best to deprecate of both zh-hans and zh-hant, and re-list zh so translators like me could easily maintain pages with one language code rather than six language codes.

However, letting admin to change every page's language is ridiculous, and the current translation process of this wiki is ridiculous as well. The Translate extension can automatically use Page Content Language Hook of MediaWiki to automatically add the correct page language once the page is created. It is also an ease for translators to translate the pages (I translate on the translatewiki as well as meta-wiki, and the translation extension is absolutely a lifesaver). I understand there is a discussion a few months ago. However, I would really want to bring back discussion since the extension's benefit outweighs the disadvantages.

The Translate Extension can provide translators a general idea of how many things that waiting to translate, update and proofread. You can see Statistic of Metawiki to have a look. The extension can eliminate the need of maintaining {{Translated}} by only use <language />(Which will be automatically put by the extension). The extension also eliminate the need of manually put {{Translation out of sync}}} on pages, since it automatically flag the changes made is the source (like the exact wording it changed) and present the outdated translation to the translators. The translated page itself will also flag the outdated translation with colored background. The most importantly part is that the extension eliminate the need for translator to figure out the layout issue after translation and only focus on the translation. For example, I just started translate Wiki to Zh-hans:Wiki and I still cannot figure out what went wrong with the layout. If Translate extension is implemented in this wiki, I will not need to worry about this since the extension will take care of this automatically.

I see some people argue that "especially the requirement to clutter the English text with various markers that make wiki editing less accessible to non-technical editors" and it is a mess. I just want to say that please look at the MediaWiki Translation guide, you do not need to add these tag manually, the extension will automatically add these tag for you. Also, adding the tag should not interfere with the ability of editing since visual editor will not read the tag and people who use wikiEditor should have enough knowledge for basic syntax.

It will also great to eliminate language namespace and use /zh, /jp format (which is the same format as wikipedia). I understand the original purpose for having language namespace is [Wiki_Translation#Language_prefixes_and_namespaces|easier for search]. However, with [3] installed, you can define narrow the search based on page language and prefix, which solve this problem.

Overall, I hope this community could consider my suggestion and implement the following step:

1: Merge zh-hans and zh-hant to Zh (This should be easy and quick).

2: Install the Extension:Translation

3: Convert the current naming of translation for Zh-hans:wiki format to wiki/zh (This step may be necessary since it seems extension:Translate produce page in this format.)

VulpesVulpes825 (talk) 14:52, 6 September 2019 (UTC)

You can use Special:PageLanguage by yourself as every user is able to change it. I would say, that we are currently on our way to remove the namespaces slowly no matter if we introduce the extension or not. --Tigerfell  (Let's talk) 17:08, 6 September 2019 (UTC)

All right, I will start to change the language and merge zh-hans and zh-hant to zh, as well as change Module:Languages/config to reflect this. However, I would still like to continue the conversation about having Extension:Translate. VulpesVulpes825 (talk) 18:10, 6 September 2019 (UTC)

Rename a wiki page with wrong title

Hello. I don't know if this is the right place for this request. So feel free to delete this if it's wrong here.

I created the wiki page DE:Key:lcn=yes. According to the naming conventions the Page should be called DE:Tag:lcn=yes instead. I can't correct the name of the page by myself. I would appropriate if an admin could fix my mistake.

Page has been moved. --Lyx (talk) 19:26, 24 September 2019 (UTC)

Creating new Wiki Admins

As you might have noticed there is no published procedure how to create new Admins in this wiki. The procedure I have used so far is "forward requests to firefishy", possibly with an added comment what I think of the request. I expect to continue following that procedure in the future. However, I'ld like to tell you what the role of Wiki Admin and the requirements to fill it should be in my opinion. Please note that this is only my personal opinion and in no way an official position, and the fact that I am one of the Admins doesn't make my opinion any more or less valuable than the opinion of any other community member.

The role of a Wiki Admin is IMHO a serving and moderating role. Therefore an Admin should try to keep a neutral position in discussions in this Wiki, preferably keeping completely out of heated exchanges except for trying to moderate the tone, maybe summarize the positions of all sides and help the community find consensus. There are cases where quick action is required; in those cases make sure that those actions can still be discussed. --Lyx (talk) 19:57, 24 September 2019 (UTC)

@Lyx: there are two separate tasks that require adminship -- moderation and UI administration. I agree about your thoughts about moderation aspects, but there is also a number of changes that require the person to be trusted with technology - i.e. being able to change javascript for all users of the site. Moreover, usually there are far fewer UI admins than moderation admins (as we can see with the English Wikipedia, where such division was introduced a year or two ago). We do not separate those two roles, simply because size-wise OSM wiki is far smaller than EN Wikipedia, so this division is excessive, but we should always keep in mind that UI adminship is a valid and frequently required skill. --Yurik (talk) 23:43, 10 October 2019 (UTC)

LaTeX <math>..</math> Extension

Wer kann im OSM-Wiki die Erweiterung zur Darstellung von Formeln installieren? Gruss, --Markus (talk) 20:25, 10 October 2019 (UTC)

Please can you install https://www.mediawiki.org/wiki/Extension:Math to the OSM-Wiki? Thanks for help, --Markus (talk) 22:31, 11 October 2019 (UTC)

The system administrators can do that. You can create a ticket for them at https://github.com/openstreetmap/operations/issues (same address as provided at the very top of this page). In theory, a wiki administrator's approval is desired. --Tigerfell  (Let's talk) 12:51, 13 October 2019 (UTC)

Help profiling a template

I have a revised version of {{LangSwitch}} based on the Wikimedia Commons version. How can I time the effect on page performance? --Andrew (talk) 21:15, 13 October 2019 (UTC)

You can transclude the template on a sandbox page and after creating the first preview, there are some data about CPU and real time usage in the section "Parser profiling data" below the editing box just above the categories. There are also browser tools as part of many web browsers. There are run time analysis and network analysis for instance. The usage of the web console for MediaWiki was briefly explained in Talk:Wiki/Archive 5#Optimizing wiki templates. --Tigerfell  (Let's talk) 21:17, 14 October 2019 (UTC)

Possible spam account

Please take a look on https://wiki.openstreetmap.org/wiki/Special:Contributions/Lavie_Labs_Hydrolift_Review . I've already wiped his SEO spam.--Kundera (talk) 13:26, 14 October 2019 (UTC)

@Tigerfell: More spam users -> User:Visirestore Review.--Zhukov (talk) 09:17, 12 November 2019 (UTC)

@Minh Nguyen: Administrators, please do something: User:Subliminal Guru Review 2‎; User:Gluco Type 2 Review Tab‎; User:Floraspring Review‎.--Zhukov (talk) 11:58, 12 November 2019 (UTC)

All of the accounts were blocked (not by me). I temporarily blocked the creation of accounts with names similar blocked to these ones. Hope that helps. Blanking or replacing the content with {{d|spam}} is usually sufficient as a first measure. --Tigerfell  (Let's talk) 20:06, 12 November 2019 (UTC)

Template: Mini-map around a node/feature

I'm looking for a template that embeds on a wiki page a small map of the area around a given node. The Templates index has one that does very roughly what I'm looking for: Template:Node transcludes a link to the map at the node specified.

The result can be simplified using Template:NodeIconLink, but I can't see how to give more info: I want an image (slippy or not) of that node in its context. (I don't want to have to click the link and open the map on another page to see this.)

I've also looked at Wiki:Maps (thanks again @Tigerfell:). I think to embed a map I need to manually find a node's lat-long to specify which bit of the map is shown, and I just want to code the node id. (As it happens the next question will be: is there a template that will display the lat/long for a given node?)

Any pointers? Fwiw this relates to the wiki page Sustrans Millennium Mileposts. Many thanks, eteb3 (talk) 20:46, 27 October 2019 (UTC)